Pitching
How to Show Startup Traction Before You Have Revenue
Build a pre-revenue evidence pack that distinguishes interest, repeated use, commitments and technical progress without inventing commercial proof.
What you will learn
- Map pre-revenue evidence to a specific risk
- Write a scoped traction claim with denominators
- Choose a next test instead of overstating validation
Show traction before revenue by presenting dated evidence that reduces a specific risk in the business. Describe what people did, what the product demonstrated, and what remains untested. Do not relabel interviews, registrations or letters of intent as paying customers.
This lesson builds a pre-revenue pitch evidence pack and next-test plan. The existing vanity-metrics lesson owns metric interpretation, and the product-market-fit lesson owns the broader fit checklist. None of these requires inventing a revenue story before one exists.
Choose the risk your evidence addresses
Early evidence can address problem relevance, product feasibility, repeated use, buying process, or delivery. It does not all prove the same thing. A successful technical test may reduce implementation uncertainty while leaving customer demand unresolved.
YC’s seed-fundraising guide distinguishes product, team and adoption in a company story. Do not copy historical growth or financing benchmarks from that older guide into a current pitch. Use your actual stage and evidence.
Evidence-to-risk map
| Evidence | Can help assess | Does not establish alone |
|---|---|---|
| Permissioned interviews | Reported problem and context | Usage or willingness to pay |
| Defined technical test | Behavior under tested conditions | Customer adoption or scale reliability |
| Repeated job completion | Behavior in the observed cohort | Sustainable paid demand |
| Letter or pilot agreement | The exact written commitment | Revenue unless payment actually occurs and is properly recorded |
| Buying-process discussion | Buyer, budget path and next decision | Closed sale |
Work a pre-revenue evidence pack
Fictional example: TraceNest prototypes a handoff workspace for small research teams. It has no revenue. Its internal illustrative records say six teams tried a defined handoff task; four completed it once; two of those repeated it during the same four-week observation period. One team agreed to discuss a paid pilot. No purchase has occurred.
Completed evidence pack, fictional
| Risk | Observed evidence | Limit | Next test |
|---|---|---|---|
| Can teams complete the job? | 4 of 6 attempted teams completed one handoff. | Small selected cohort with assisted onboarding. | Observe onboarding friction in the next defined cohort. |
| Does the job recur? | 2 of 4 completers repeated the task in four weeks. | Window may not match every team’s workflow frequency. | Track the next expected handoff opportunity. |
| Will a buyer pay? | One paid-pilot discussion accepted. | No signed paid agreement or collected cash. | Confirm buyer, scope and decision process. |
A truthful slide can say: Two teams repeated the handoff in our four-week prototype trial. Add the denominator, assisted setup and no-revenue status. Do not say “six customers,” “50% retention” without defining the population, or “paid demand proven.”
The ratios are 4 ÷ 6≈66.7% first completion,2 ÷ 4 = 50% repeat among completers, and 2 ÷ 6≈33.3% repeat among attempted teams. They answer different questions. None is a stable benchmark from this tiny fictional sample.
Build an evidence ladder, not a vanity total
- Define the specific risk and the event that could inform it.
- Record eligible population, dates, measurement and assistance.
- Preserve negative and incomplete outcomes.
- Identify the strongest claim the evidence permits.
- Write what remains unresolved directly beside it.
- Choose one next test with a decision it could change.
Do not add interviews, registrations and pilot teams into one “traction” total. They can refer to overlapping people and represent different events. Keep permissioned supporting records internal when they contain personal or commercially sensitive information.
Copy the pitch evidence card
Business risk: [ ]
Claim for the pitch: [ ]
Event or milestone definition: [ ]
Cohort / eligible population / observation dates: [ ]
Observed count and denominator: [ ]
Source and collection method: [ ]
Assistance, selection and coverage limits: [ ]
Negative or incomplete outcomes: [ ]
Commercial status: [interest / discussion / agreement / cash]
What this does not prove: [ ]
Next test / decision / owner / date: [ ]Keep one card per meaningful claim. A separate evidence appendix can hold detail, while the main slide shows the strongest accurate point.
Verify before putting numbers in the deck
If users return only because the founder reminds them: disclose assistance and test recurrence separately. If a waiting list grows: show signups as interest, not usage. If one large brand joins a call: do not imply procurement or endorsement. If a technical milestone matters most: report the tested conditions and remaining work.
- Every number has an event, denominator and window.
- Interest, behavior, commitment and money stay separate.
- Small-sample uncertainty is visible.
- Non-results are not deleted from the record.
- The next test targets a real unresolved risk.
Use the appendix lesson for supporting evidence and the headline exercise to keep your claim proportionate.