Question 1

Is this only for blockchain protocols, or do you work with all web3 teams?

Accepted Answer

We work with any web3 team — Layer 1 and Layer 2 protocols, DeFi platforms, GameFi projects, NFT infrastructure, Web3 SaaS products, node providers, RWA tokenization platforms, and DAO organizations. If you are building in web3 and need clear documentation or content, we can help.

Question 2

What does a web3 content agency actually do?

Accepted Answer

A web3 content agency builds the content system around your product — developer docs, user guides, API references, SDK documentation, content strategy, marketing copy, and AI integration. Unlike a generic writing service, we specialize in web3, so we understand your technology, audience, and ecosystem from day one.

Question 3

How much does a web3 documentation or content system cost?

Accepted Answer

Our audit is free. Core packages are €16,000 for a Documentation Layer (full docs system in 6–8 weeks) and €11,000 for a Content Layer (content strategy and execution in 3–4 weeks). Add-ons include an AI Integration at +€2,500 and Ongoing Support at +€8,000/month. You can also combine everything into a custom package — if you need docs, content, and add-ons together, we put together a tailored quote based on your scope.

Question 4

Do you only write developer documentation, or do you cover other content types too?

Accepted Answer

We cover every content type a web3 team needs — developer docs, SDK references, API documentation, smart contract documentation, user guides, onboarding flows, product content systems, blog posts, social content, token launch copy, and content strategy. Most engagements combine technical writing with broader content work because the two support each other.

Question 5

Should we hire a web3 technical writer or work with a web3 content agency?

Accepted Answer

Hiring a web3 technical writer takes time to recruit and onboard. A specialist web3 content agency gives you immediate access to documentation, technical writing, and content strategy — while also keeping everything current as your product evolves. That means faster output, less onboarding friction, and no knowledge loss when priorities shift.

Question 6

How long does it take to build a web3 documentation or content system?

Accepted Answer

Most projects run between 6 and 8 weeks depending on scope. A Documentation System typically takes 6 weeks, while a broader content system can take longer. We start writing in Week 1 and publish directly into your documentation infrastructure using a docs-as-code workflow.

Question 7

Can you maintain our existing blockchain documentation and keep it current?

Accepted Answer

Yes. We offer ongoing content and documentation support to update existing docs, add new material for every product release, and keep everything current as your protocol evolves. Stale documentation is one of the fastest ways to lose developer trust, so we treat maintenance as part of the system, not an afterthought.

Question 8

Can you migrate our documentation to a better platform?

Accepted Answer

Yes. We handle documentation migrations to platforms like Docusaurus, GitBook, Mintlify, and Read the Docs. We review your current setup, restructure the information architecture, improve content where needed, and move everything over with minimal disruption.

Question 9

Can you build SDK documentation, API references, and smart contract documentation?

Accepted Answer

Yes. We write SDK references, API reference guides, OpenAPI documentation, and smart contract documentation using standards such as Hardhat NatSpec, TypeDoc, and Solidity documentation workflows. We work directly with your engineers to validate technical accuracy before anything goes live.

Question 10

Do you build documentation that works with AI assistants and AI search?

Accepted Answer

Yes. We structure content for LLM retrieval, GEO, and AI search visibility so it performs better in ChatGPT, Perplexity, Claude, and other AI-driven systems. We also support Kapa.ai, llms.txt, and embedded Claude-powered assistants so your documentation produces accurate answers instead of unreliable ones.

Let's build your content layer.

Build your own package

Free Audit

Let's build your content layer.

Build your own package

Free Audit