Pitching
How to Keep Your Startup Fundraising Materials Consistent
Reconcile the deck, financial model and data room using a definition register, source-of-truth map and controlled release checklist.
What you will learn
- Define a claim once across fundraising documents
- Resolve population/date mismatches without rewriting facts
- Release a consistent versioned materials pack
Keep fundraising materials consistent by defining each important claim once, mapping where it appears, and reconciling every exported version before sharing. Consistency means the same facts use the same definitions and dates, not that every document contains identical detail.
Bring the current deck, model, one-pager, diligence index and approved metric sources. This lesson owns cross-document reconciliation, not the full deck, financial model or data-room setup. Do not change historical results to make documents look aligned; explain period and definition differences accurately.
Make one claim register
Assign an owner, definition, time period, source and update trigger to each material claim. Typical candidates include customer count, recurring revenue, trial status, current headcount, forecast hiring, funding ask, cash balance and product availability.
The SEC’s statement guide distinguishes a point-in-time balance sheet from period-based income and cash flow. That distinction illustrates why two accurate numbers can differ when their dates or definitions differ. This operational register is not an accounting opinion.
Claim ID / plain-language definition: [ ]
Actual / forecast / hypothesis: [ ]
Period or as-of date: [ ]
Currency / units / denominator: [ ]
Authoritative working source and owner: [ ]
Locations in deck/model/data room/one-pager: [ ]
Approved wording and qualification: [ ]
Last verified / next trigger: [ ]Reconcile a fictional mismatch
Illustrative company: NarrowBridge’s deck says “40 customers,” its model uses 24 paying accounts, and its diligence overview lists 50 registered organizations. The documents may be referring to different populations, not simply wrong arithmetic.
Completed claim reconciliation
| Location | Original statement | Finding | Reviewed replacement |
|---|---|---|---|
| Deck | 40 customers | 40 organizations completed a defined trial task by September 30. | 40 trial-task completers;24 paying accounts at September 30. |
| Model actuals | 24 paying accounts | Matches the paid-account definition and date. | Keep 24; add definition/source link internally. |
| Diligence overview | 50 organizations | Registration count includes 10 without task completion. | 50 registered,40 completed,24 paying; separate populations. |
Do not make every document say 50 customers. Clarify what each number measures. If the figures are not traceable, hold the claim until the owner resolves it. These invented counts are a teaching example, not Finta customer data.
Separate actuals from forecast and plans
A current team count of five and a forecast team of nine are compatible if one is dated actual headcount and the other a future scenario. They conflict if the deck implies nine people already work at the company. Similarly, a planned integration is not current availability and an unsigned investment indication is not received cash.
- Fix the measurement date and definitions before checking values.
- Trace each figure to its approved working source.
- Compare the claim wherever it appears, including chart labels and image text.
- Resolve differences with the responsible owner.
- Update all affected derivatives, not only the editable source file.
- Keep an issue log for unresolved discrepancies.
If a legal or financial interpretation is disputed, preserve the question for the appropriate qualified adviser instead of settling it through copy editing.
Create a controlled release pack
Completed release-pack example
| Artifact | Version | Check | Owner |
|---|---|---|---|
| Deck export | Review packA | September 30 definitions and development labels match register. | Founder |
| Model | ScenarioA, actuals through September 30 | Forecast begins after actuals; no unreceived funding treated as cash. | Finance owner |
| Diligence index | PackA | Links point to approved files; access checked. | Operations owner |
| Issue log | PackA | Open questions visible with owners and response dates. | Founder |
Use a stable approved location or clear version labels. Avoid several different files named “final.” Do not overwrite a previously shared record without preserving what the recipient could have seen and deciding whether a correction is needed.
Copy the release and change log
Release pack / audience / date / owner: [ ]
Included artifact names and versions: [ ]
Actual-data cutoff / forecast start: [ ]
Claims reconciled to register: [ ]
Remaining discrepancies / owners / due dates: [ ]
Permissions and recipient access tested: [ ]
Exports checked against editable originals: [ ]
Changed claim / old value / new value / reason: [ ]
Affected artifacts updated: [ ]
Previously shared version retained: [ ]
Correction or follow-up decision: [ ]Common failures include checking only editable slides, leaving stale screenshots, mixing annualized and recognized revenue, reusing an old model tab, and updating a source while a public sharing link points to a different export.
- Material claims have owners and definitions.
- Actuals, forecasts and hypotheses are distinguishable.
- Every relevant artifact uses compatible dates and units.
- Exports and recipient links match approved versions.
- Unresolved issues and correction decisions are documented.
Use the financial-model lesson, send-ahead edit and diligence answer register for their individual tasks. Bring the reviewed pack into Finta Academy discussions or your team’s fundraising review.