Writing
Complex subjects, explained plainly
Breakdowns of my own posts, and samples of product copy.
Thread · 3 August 2026Two ways prediction markets break: payout dilution and dead booksYou can call it right and still lose the payout.Read the breakdown
Commentary · 31 July 2026Onboarding friction is a product decision, not a compliance afterthoughtVerification belongs inside onboarding, not bolted on after.Read the breakdown
Thread · 2 May 2026Build in public: an honest ledger of shipped and not-yet-shippedName what is live and what is not, in one post.Read the breakdown
Thread · 19 January 2026Tokenomics decks fail because nobody understands them, not because the math is wrongLead with the benefit, show the flow, keep the math for later.Read the breakdown
Published posts
Copywriting samples
Posts published on LinkedIn.
DeFi product narrative and launch thread
Explaining an AI trading platform to people who do not want to lose money learning
Read on LinkedInHow I approached it
- Context
- An AI trading platform needed a story a nervous first-time trader could follow — without leading with specifications or tokenomics.
- What I wrote
- A problem-and-solution narrative thread: the reader’s real fear first, the product as the removal of that friction, the outcome in weeks rather than months.
- Approach
- I framed the product around the reader’s lived problem instead of its features, then structured the thread so each line earns the next. The brand responded to the thread publicly, which is the useful signal — the structure landed with the audience it was written for.
Tokenomics clarity and investor-facing copy
Most tokenomics decks fail because humans cannot read them
Read on LinkedInHow I approached it
- Context
- Founders explain utility the way a whitepaper does; investors read it the way a legal brief is read. The deck closes and the opportunity is lost.
- What I wrote
- A short set of rewriting rules with worked before-and-after examples — lead with the outcome rather than the mechanism, show flow instead of formulas, write simply and add one layer of sophistication only if asked.
- Approach
- I treated clarity as the deliverable and rewrote the same claim at two levels of complexity so a founder can reuse one version in a deck and the other on an onboarding screen.
Institutional yield messaging
Restaking yields do not need to scream — they need to prove
Read on LinkedInHow I approached it
- Context
- Restaking protocols advertise APYs like lottery tickets, while the capital they want is looking for certainty rather than a headline number.
- What I wrote
- A messaging shift: frame yields as risk-adjusted outcomes, anchor to familiar benchmarks, use precision language, and write hooks that pre-qualify the reader instead of attracting everyone.
- Approach
- I compared the raw-percentage appeal against the language institutional allocators actually respond to, then wrote the same offer both ways so the difference is visible rather than asserted.
Technical explanation and onboarding
How I turn technical whitepapers into onboarding copy
Read on LinkedInHow I approached it
- Context
- Whitepapers lose readers in the first paragraph, and onboarding screens then inherit the same jargon at the exact moment a new user is deciding whether to continue.
- What I wrote
- A three-step method — strip the jargon, translate the mechanism into a user benefit, then map each message to the stage of the funnel it belongs to — demonstrated with a before-and-after pair.
- Approach
- I rewrote the same technical claim at three depths so the method is visible in the output: the technical statement, the eighth-grade-English translation, and the user-benefit line that belongs on the onboarding screen.
SaaS activation copy
Your onboarding does not have a UX problem, it has a copy problem
Read on LinkedInHow I approached it
- Context
- A dashboard with strong retention fundamentals and a specific activation failure — users see the interface and cannot tell which action to take first.
- What I wrote
- Three concrete copy fixes: replace system language with job-to-be-done language, front-load value before asking for effort, and write microcopy that predicts the user’s anxiety at loading states.
- Approach
- I diagnosed the drop-off as a labelling problem rather than an interface problem, then rewrote the labels and the surrounding microcopy as a checklist a team can apply without a redesign.
Research areas
Subjects I have researched for content work. They are research subjects, not clients.