We write the documents that close.

Pitch decks, whitepapers, one-pagers, litepapers and technical documentation — the core document types a raise, a launch or a technical evaluation actually runs on. Each format serves a different reader and a different moment: a deck for a partner meeting, a whitepaper for technical diligence, a litepaper for a first-touch read, a one-pager for a forwarded intro, technical docs for developers integrating with the product.

A whitepaper is the full technical and tokenomics document built to survive diligence; a litepaper is the same narrative compressed into a two-minute read for a first touch. Most serious token launches need both — the litepaper gets the initial audience in the door, the whitepaper is what a technical investor or auditor actually reviews line by line.

Yes — investor-ready pitch decks are a core deliverable, built around a single narrative arc and market sizing that holds up to a partner's own diligence, not just a polished slide template. Scope ranges from a seed-stage narrative deck to a full data-room-ready Series B package.

Yes — architecture docs, API references and integration guides, drafted with input from the engineers who actually built the product, not paraphrased from a spec sheet. Documentation that developers actually use tends to cut integration support load measurably.

Document count and format mix, technical depth, design system complexity, review depth, revision cycles and update cadence. A single pitch deck is a different scope than a full raise package built across four formats.

Your counsel does. We write it; they clear it. What we bring is the discipline of writing for that review from the first draft instead of producing something strong and watching it get taken apart. We ask your legal team up front which claims are off the table, draft inside those limits, and send work back while changing it is still cheap. This matters most on whitepapers and litepapers, though any document describing token economics goes through the same loop.

No — a single pitch deck or a standalone technical-documentation engagement is a normal scope on its own, not just part of a full raise package. Most clients start with whichever document is on the critical path — usually the deck if a round is active, the whitepaper if a token launch is close — and add the rest as it becomes relevant.

By building one underlying narrative first, then adapting it per format — instead of writing each document independently and hoping they line up. The same market sizing, the same problem framing and the same numbers appear across every document in the set.

Start with the document that unblocks the nearest decision. For a raise, that is usually the deck and the one-pager. For a technical audience, the whitepaper or protocol documentation. For a product launch, the site copy and the explainers. Teams rarely need the full suite at once, and producing it all up front usually means rewriting half of it after the positioning settles. We scope to the immediate need and build outwards as the story firms up, which costs considerably less overall.