Public handbook trust surface
Publish a surprisingly detailed public handbook or operating manual on the main site so early prospects can inspect how the company works before they trust the product.
Why this can grow a startup
Early users often doubt there is a real company behind a new product, especially in technical or self-serve categories. A public handbook answers that doubt with specifics: values, processes, support norms, and the shape of the team. It works as brand, trust, and conversion infrastructure at the same time because the proof lives on the domain the buyer is already evaluating.
Company example
PostHog published a public handbook on its main site because the founders knew early users might doubt there was a real company behind the product, and used it to build credibility fast.
Source and metric
Source: PostHog Newsletter · Browse PostHog Newsletter tactics
Source discovered: May 24, 2026
When to use it
Use this when Website, Content, SEO is relevant to trust, 0-100, plg and you can run a bounded test with a free budget.
When not to use it
Do not use it as a substitute for customer evidence, a clear owner, or a measurable stop condition. Local platform rules and market behavior still need checking.
Founder checklist
- Read PostHog Newsletter and identify what is directly supported.
- Choose one channel context: Website, Content, SEO.
- Define the test around one observable customer behavior.
- Set an owner, evidence window, and stop condition before launch.
Explore the context
Apply this with an operator
Choose product surfaces that compound distribution without hiding weak activation or retention.