In short: write one product truth, then one belief statement per audience, then a claims register that says what you can prove. Everything else — the deck, the homepage, the community announcements — is derived from those three.
Key points
- A product truth is one sentence: what it is, who buys it, and what changed that makes it necessary now.
- Investors, community and customers each need a different belief and accept different proof.
- Investor logos impress investors but mean almost nothing to a treasury manager deciding where to deposit.
- A claims register lists every public claim with evidence and an approver, catching words like "guaranteed" before they ship.
- In web3, lead with what the protocol does for a user; in AI, position on the workflow, not the model.
The product truth
One sentence with three parts: what it is, who buys it, and what changed that makes it necessary now.
Bad: "The intelligence layer for the future of work." No buyer, no reason, no thing.
Better: "An AI agent that answers support tickets inside the help desk your team already uses, for B2B software companies whose ticket volume grew faster than their headcount."
The second one is less exciting and much more useful. An investor can size it. A customer can recognise themselves in it. A community member can explain it to a friend.
One belief per audience
Each audience needs to hold a different belief before they act. Write them down.
| Audience | Must believe | Proof that works | Proof that doesn't |
|---|---|---|---|
| Investors | This can be large, this team will win it, and now is the moment | Named customers, usage curves, a credible path to the next milestone | TAM slides, "the future of…" |
| Community | Being here early is worth something real | Access, a role, recognition, a visible say in what ships | Vague token hints, giveaways |
| Customers | It solves my problem, it's safe, and someone like me already uses it | A case study from a peer, an audit, a pilot with clear terms | Your raise, your investors' logos |
The right-hand column matters. Founders reuse proof across audiences because it's what they have. Investor logos impress investors and mean almost nothing to a treasury manager deciding where to deposit.
The claims register
A short table of every claim you make publicly, with the evidence for each and who approved it. It sounds like compliance. It's actually the fastest way to stop a team saying five different things.
In web3 it does double duty: claims about yield, safety and returns carry real regulatory and reputational risk, and the register is where you catch "guaranteed" before it ships. In AI it catches the accuracy number that was true on one benchmark in March.
Where web3 and AI differ
Web3: the token collapses audiences. Your holder is an investor, a community member and sometimes a customer. That makes the product truth more important, not less, because the token story will drown it unless it's written down first. Lead with what the protocol does for a user, and let the token be the mechanism, not the headline.
AI: the model is not the product. Investors may care about the model; customers care about the workflow. Position on the job done and the result, and keep the model story for the deck appendix.
The checklist
- [ ] One-sentence product truth: what, who, why now
- [ ] A written belief statement for each audience
- [ ] The proof each audience will actually accept, mapped
- [ ] A claims register with evidence and an owner
- [ ] Homepage hero tested on a customer, not an investor
Common questions
How do I write a product positioning statement for a startup?
Write one sentence with three parts: what it is, who buys it, and what changed that makes it necessary now. It should be specific enough for an investor to size and a customer to recognise themselves in.
What is a claims register?
A short table of every claim you make publicly, with the evidence for each and who approved it. It stops a team saying different things and catches risky claims about yield, safety or accuracy.
Should a web3 company lead with its token?
No. The token collapses audiences, so write the product truth first, lead with what the protocol does for a user, and let the token be the mechanism, not the headline.
What proof do customers want compared with investors?
Investors want named customers, usage curves and a path to the next milestone. Customers want a peer case study, an audit or a pilot with clear terms, not your raise or your investors' logos.