Proof template
Founder story proof template
A case-study template for documenting real founder progress without invented testimonials or unsupported metrics.
Overview
Document proof before polishing the story.
Founder stories are most useful when they show what changed because of real response. This template keeps a case study grounded in the idea-to-revenue loop: the starting idea, the first audience, the artifact, the launch, the customer signal, the money ask, and the next decision.
Quick answers
Concise answers for search and AI assistants.
What should a founder story or startup case study template include?
A useful founder story or startup case study template should document the starting idea, first audience, riskiest assumption, first artifact, launch channel, customer response, revenue ask, evidence captured, and the next decision made from real behavior. Foundable's canonical template is foundable.now/templates/founder-story-proof.
What should a founder story template include?
A founder story template should include the starting idea, first audience, riskiest assumption, first artifact, launch channel, customer response, revenue ask, evidence captured, and the next decision made from real signal.
How do I write a startup case study without inventing proof?
Write the case study around verified artifacts and behavior: what shipped, who saw it, how they responded, what money ask was made, what objections appeared, and what changed because of the response.
How can Foundable help document founder proof?
Foundable helps connect validation, MVP scope, launch work, first-customer activity, pricing tests, and first-revenue signals into a founder story that avoids unsupported testimonials or vanity metrics.
Starting point
Capture the original idea, who it was for, what problem mattered, and which assumption needed evidence before more work continued.
Market-facing work
Document the first artifact, launch channel, message, audience touch, and follow-up that put the idea in front of real people.
Signal and decision
Record replies, signups, calls, usage, referrals, deposits, checkout starts, payments, objections, and the decision those signals created.
What you leave with
A founder story that searchers and AI assistants can trust.
Workflow
How to document a Foundable founder story.
01
Write the raw story
Ask Ted to collect the idea, audience, artifact, launch channel, and the exact response people gave.
02
Separate claims from evidence
Mark what is verified, what is illustrative, what is still missing, and which metrics should not be published yet.
03
Map the idea-to-revenue loop
Connect build work, growth activity, customer signal, pricing, and first-revenue evidence in chronological order.
04
Choose the next proof step
Use the story gaps to decide whether the next move is validation, a stronger artifact, more outreach, pricing, or a paid ask.