Choose the question before the metric
Start with the uncertainty you want the slide to address. Are customers willing to pay? Are they using the product repeatedly? Is an initial group renewing? Each question needs different evidence. Registrations can describe interest, but they do not establish paid adoption or repeat use.
Write a specific heading that the evidence can support. “Paid accounts increased across the last three completed months” gives the chart a job. “Strong traction” asks the reader to supply the conclusion. If the evidence supports a narrower statement, use that statement.
Select one main measure and, where useful, a supporting measure that adds context. For example, new paid accounts describe acquisition; a renewal measure helps explain what happened to an earlier group. There is no universal set of metrics for every business or funding stage.
Define what each number counts
A metric needs a unit, a period and a counting rule. Explain whether “customers” means paying organisations, individual users, active subscriptions or everyone who has registered. State whether the figure is a month-end position, activity during a month or a total since launch.
Even familiar subscription labels need a definition. Stripe’s Billing documentation describes configurable rules for MRR, discounts and when subscribers become active. Its definitions belong to that reporting system; they are not a universal accounting standard. Agree your definition with the person responsible for the data and use it consistently in the deck.
Keep revenue, cash received, signed contract value and sales pipeline separately labelled. Show currency and the relevant date. If a figure comes from a management report, identify that report and its cut-off date in a readable source note.
Metric + who or what is counted + period + important exclusions + source. Keep the main label short; put the definition directly beneath the chart or in a clearly linked appendix.
Source: Stripe Docs — Billing analytics and metric definitions
Show the pace of growth, not just the accumulated total
Imagine a business added 20 new paying accounts in January, 30 in February and 25 in March. These are illustrative figures, not Pitchwave or client results. The cumulative acquisition total rises from 20 to 50 to 75, even though March brought fewer new accounts than February.
If the claim concerns acquisition momentum, plot the monthly additions. If the question concerns the current customer base, use a measure that also accounts for departures. The total number ever acquired cannot establish how many remain active.
Y Combinator’s July 2016 Demo Day guide cautions against cumulative growth charts and recommends giving each slide one main point. That presentation advice remains useful here; it does not establish a current fundraising benchmark.
Compare like periods. Label a partial month prominently, or keep it separate from completed months. Use consistent intervals and explain changes in measurement. Separate forecasts visually from observed results so a future target cannot be read as achieved growth.
Make retention comparisons comparable
When you show whether customers stay, explain which starting group you are following and how much time has passed. Comparing the first month of a recent group with the sixth month of an older group answers a different question from comparing both at month six.
Customer retention and revenue retention also describe different things. Stripe’s cohort documentation distinguishes remaining subscribers from their recurring revenue and notes that revenue retention can exceed 100% through expansion. A revenue percentage above 100% therefore does not mean every original customer stayed.
Show the starting group size and define the activity or payment required to count as retained. Small groups can be worth discussing, but give readers the actual counts alongside percentages. Keep a fuller cohort table in the appendix if the main slide needs only one comparison.
Source: Stripe Docs — Billing analytics and metric definitions
Present early evidence with its actual status
Before revenue, evidence may include product use, completed tests, paid pilots or documented commercial commitments. Explain what happened, with whom you can publicly identify it, and what remains unproven.
A free trial, a paid pilot, a signed agreement and an open sales conversation are different states. Group them separately. If a commitment has conditions, make those conditions visible. Use customer logos only when you have permission and the label describes the relationship accurately.
A small pilot can support a specific finding about a defined use case. It cannot, by itself, establish broad market demand. State what the pilot tested and the next question the team needs to answer. That gives early evidence a clear role without inflating it.
Use this traction slide checklist
Before design, read the proposed headline and the evidence together. Could someone reach the headline’s conclusion from the chart and notes alone? Resolve gaps in the underlying data before using visual emphasis to draw attention to it.
Pitchwave helps connect the evidence, narrative and design of an investor presentation. A useful starting brief includes the source reports, metric definitions and any questions the team has not yet resolved.
- ClaimOne clear point that the evidence supports.
- MeasureA defined metric relevant to that point.
- ComparisonConsistent periods, groups and counting rules.
- StatusActual results, targets, pilots and pipeline distinguished.
- ContextCurrency, dates, group sizes and material exclusions visible.
- TraceabilityA source report and an owner who can explain the numbers.