the words / 04

Technical & Web3 writing

Complex product. Clear explanation.

what we’re really solving

The job behind the job

Some readers need the big picture. Others need to know exactly how the thing works. I write for both without treating either one like an afterthought. That could be a product explainer, an onboarding flow, a tutorial, or supporting documentation.

For LycanPay and Lycan Chain, my work covered payments, EVM compatibility, and blockchain interoperability. Those subjects need precise language. I start with the product and its actual behaviour, then work out what the reader needs to understand before they can use it or make a decision.

Best for: SaaS teams, fintech products, blockchain networks, crypto applications, and infrastructure businesses explaining a specialist product.

what’s in the folder

The deliverables

Product explainers, user guides, and practical tutorials
Onboarding copy for in-app screens, emails, or help content
Technical articles, protocol explainers, or whitepaper writing support
Tokenomics and blockchain explanations grounded in your supplied information
Supporting API documentation copy with technical review from your team

Final scope agreed before we start.

from first conversation to final full stop

How it comes together

I review the product, documentation, and audience, and collect questions for your technical team.

I map the explanation or user journey before writing the draft.

Your subject expert checks the technical details; I refine the language and structure around that feedback.

Timing & investment

Fixed quote by scope. We agree on the deliverables, technical review, and timeline before work begins.

Talk through the scope

good things to know

A few questions

What will you need from our team?

Product access where possible, current documentation, the intended audience, and someone who can verify technical details. I will flag gaps rather than fill them with guesses.

Can you write for developers and everyday users?

Yes. We define who each piece is for and how much background they have. A builder's integration guide and a new user's onboarding screen need different approaches.

Can you help with an existing whitepaper?

Yes. I can help with the narrative, terminology, structure, and readability. Your team remains responsible for confirming the underlying technical and financial details.

a little proof from the folder