Truve Guide · 10 min read
Founder Track Record: What to Share Before a Fundraising Conversation
A practical checklist for presenting a startup’s progress: product, milestones, metrics, team, and fundraising materials, with guidance on what to keep private.
Published 2026-06-17 · Reviewed 2026-10-25 · Truve editorial guide
TL;DR
- A founder track record is a concise, dated record of what the team planned, shipped, learned, and changed.
- Separate verified results from goals and estimates; give every metric a time period, definition, and relevant denominator.
- Use a public page for context, not as a substitute for a pitch, financial statements, cap table, or diligence materials.
- Share only information that the company is authorized to disclose; keep sensitive customer, employee, financial, and security details private.
What a founder track record can explain
A founder track record is a dated account of the company’s progress: what the team planned, what it released, what it learned, and what changed. It can help a reader understand the context behind a pitch, but it cannot establish product-market fit or predict an investment decision.
Use it to make claims easier to follow. Tie milestones to demos or release notes where possible; explain changes to the plan rather than quietly rewriting history. Label estimates and targets so they are not mistaken for measured results.
Keep this separate from formal fundraising materials. The U.S. Securities and Exchange Commission’s capital-raising guidance discusses financials, cap tables, runway, use of proceeds, investor fit, and professional advisers. Requirements depend on jurisdiction and offering; consult qualified counsel.
Deck vs dossier vs data room
| Artifact | Purpose | Typical readers | When to update |
|---|---|---|---|
| Pitch deck | Summarize the opportunity and request | People in a fundraising conversation | When the story or request changes |
| Founder progress page | Show dated product and company context | Users, collaborators, and interested readers | When material facts change |
| Data room | Organize detailed company information | People invited into diligence | As the underlying information changes |
| Social posts | Share updates and direct attention | A channel’s audience | When there is something useful to say |
Make the first review easy to follow
A reader should be able to find the basics without guessing. This is an editorial checklist for clarity, not a claim about how every investor evaluates a company:
High-weight signals
- Product — what is usable today, with a demo or live link where appropriate
- Progress — dated releases and milestones, including items delayed or dropped
- Evidence — measured metrics with definitions, time periods, and sample or cohort context
- Team — current roles and relevant experience, shared with each person’s consent
- Plan — the next milestones and the assumptions they depend on
- Fundraising — amount, runway, and use of proceeds only when relevant and approved for disclosure
Use a clear milestone taxonomy
Use a small, consistent vocabulary that reflects how your own team works. Explain what ‘shipped’ means for this product; there is no universal investor stage taxonomy.
Describe progress in terms readers can verify
| Current state | Useful evidence | Avoid |
|---|---|---|
| Exploring | Problem hypothesis, interview method, and what you learned | Presenting assumptions as validated demand |
| Building | Working demo, release notes, and known limitations | Calling a prototype a finished product |
| Launched | Availability, audience, and measured usage with definitions | Unqualified user or revenue claims |
| Changing direction | What evidence changed the plan and what happens next | Deleting the old plan without context |
| Growing | Cohort or retention data and the period measured | Using cumulative totals as a substitute for retention |
Minimum viable dossier structure
Keep one current overview and link to the underlying evidence. This format is a practical starting point, not a required investor standard.
Founder progress page checklist
- Problem paragraph a non-expert understands in 30 seconds
- Solution paragraph with what exists today (not roadmap fantasy)
- Cover or demo link proving the product is real
- A dated roadmap that distinguishes shipped work from plans
- Updates that explain important changes and decisions
- At least one update explaining a decision or mistake
- Team row: founder + any cofounders with profile links
- Open roles only when actively recruiting and authorized to share them
- Fundraising details only when relevant and cleared for disclosure
Publishing metrics responsibly
Choose metrics that answer a real question about the product. Before publishing, define the metric, period, population, and any exclusions:
Examples of useful metric context
- Retention (D7/D30) or repeat usage for consumer
- Pipeline metrics for B2B (qualified demos, cycle length)
- Unit economics when positive or honestly negative with plan
- Operating costs over a stated period, with the relevant product or usage context
Review examples critically
Browse public project pages on Truve to see examples of product descriptions and dated updates. Treat these as examples of page formats, not evidence that investors endorse or review a particular platform.
90-day pre-fundraise dossier plan
- 1
Month 1 — Baseline
Publish a progress page with the problem, current product, next milestones, and what has shipped. Update it when material progress or plans change.
- 2
Month 2 — Decision posts
Record meaningful decisions and explain when milestones change. Use a cadence your team can maintain.
- 3
Month 3 — Metric + ask
Review the page for accuracy before sharing it in a fundraising conversation. Keep sensitive financial details in appropriate materials and share them only with authorized recipients.
Frequently asked questions
- Do investors replace pitch decks with public track records?
- No. A public progress page can add context, but it does not replace a pitch deck or investor diligence. Investors differ in what they request and review; follow the process and requirements of the specific investor and offering.
- What should be on a founder track record page?
- Problem thesis, solution approach, stage, roadmap with Shipped/In progress/Planned milestones (with dates), timestamped updates explaining decisions, team/cofounder visibility, and optional fundraising or acquisition signals if relevant.
- How far back should a track record go?
- There is no standard time window. Include enough history to explain the company’s current position and important changes. Do not manufacture a longer history or hide a relevant pivot.
- What can make a public build history hard to assess?
- Undated claims, goals presented as results, unexplained changes to the roadmap, metrics without definitions, and a demo that does not match the description. These are clarity issues; different readers will weigh them differently.
- Should I hide failed experiments?
- You can record an experiment as complete, stopped, or superseded and briefly explain what you learned. Do not reveal customer or company-confidential information in a post-mortem.
Sources and further reading
External sources support the factual and legal context. The checklists and operating suggestions are Truve’s practical guidance, not universal benchmarks.
- Ready to Raise Capital — U.S. Securities and Exchange Commission
- Fundraising advice and startup formation — Y Combinator
- Creating helpful, reliable, people-first content — Google Search Central
Related guides
Put the guide into practice
Publish a structured project dossier — free on Truve.