How to Review Fundraising Materials Prepared by an Advisor

Review advisor-prepared fundraising materials in three passes: factual evidence, the meaning an investor could take from it and presentation clarity. Approve the substance before polishing the layout. The founder remains responsible for what the company shares, even when someone else wrote the first draft.

Start with a known version and the agreed deliverable. A review is not an invitation to add an unlimited new strategy project. Use qualified counsel or the appropriate professional for legal, accounting, financing-term and other specialist assertions.

1. Review the source of every consequential claim

Read the materials once without editing. Mark claims that could affect an investor's understanding: customer counts, revenue, product availability, market estimates, intellectual property, partner relationships, forecasts and fundraising status. Ask what source supports each claim, who owns it and which date or period it describes.

Do not treat a previous deck as the original source. It may contain an old error. Link the underlying customer report, approved model, signed agreement or other appropriate evidence, with sensitive material restricted. A third-party logo does not prove a customer relationship.

A recommendation about framing is not a new fact. The Techstars Mentor Manifesto encourages separating fact from opinion; use the same distinction in your review comments.

2. Ask what the claim implies, not only whether the words are true

1. Check definitions. “Customer” could mean a free account, a paid company or one location in a larger business. Choose a definition and keep it visible.
2. Check periods. A monthly figure and annualized run rate are not the same as recognized annual revenue. Route financial definitions to the finance owner.
3. Separate actuals from expectations. A forecast should not be placed beside historical data without labels that survive a quick read.
4. Check permissions. Confirm what names, quotations, customer details and partner references may be shared. Do not infer permission from an advisor's access.
5. Read the story without narration. A standalone reader should understand the relevant claim, evidence and remaining uncertainty.

Only then review visual hierarchy, jargon, slide order and readability. If the facts do not support the story, fix the story rather than searching for more persuasive design.

3. Worked example: turn vague feedback into accepted changes

Illustrative example: Harbor Sensor receives a revised deck. The headline says “Trusted by 50 manufacturers.” Its source report lists 34 paid organizations,10 free evaluations and 6 dormant pilot accounts. All 50 organizations exist, but the statement conceals meaningful differences.

Harbor's material-review ledger

Draft claim	Evidence question	Review decision
Trusted by 50 manufacturers	Which accounts are paid, active or evaluation-only?	Revise to 34 paid organizations as of the report date; describe trials separately
Signed enterprise partnership	Is this signed, and may the relationship be public?	Hold until owner confirms status and sharing permission
Revenue doubles next year	Is it a forecast and which model version supports it?	Label illustrative forecast or use the approved current scenario
“We are the only solution”	What evidence supports exclusivity?	Remove unsupported exclusivity; explain the specific difference

The founder sends this ledger, not “make it more credible.” The advisor revises the wording and adds source references to the internal review copy. The finance owner resolves the forecast definition. The founder rechecks the changed claims and approves only the cleaned version.

The approval does not automatically apply to later edits. A new number or changed partner description reopens the relevant review. Preserve a short version note so another teammate does not restore an earlier attractive but unsupported phrase.

4. Distinguish corrections from new work

Group feedback into factual corrections, agreed-scope improvements and new requests. An incorrect customer count is a correction. Asking for an entirely new customer study may be new scope. Keep the distinction clear without accepting inaccurate work because the deadline is near.

Use a single review owner to reconcile contradictory feedback. Ask reviewers to state the problem and evidence, not merely rewrite sentences in incompatible voices. Consolidate comments before sending a revision request.

5. Copy the acceptance record

Deliverable and version:
Agreed purpose / acceptance checks:
Claim / source / period / evidence owner:
What a reader could infer:
Actual, forecast, hypothesis or opinion:
Permission or specialist-review question:
Decision: Accept / revise / hold.
Required correction and reason:
Reviewer responsible:
Changes outside original scope:
Recheck of revised version:
Final approved version and sharing boundary:

Common review traps

• Polishing an unsupported claim: Stop the design pass and resolve the evidence first.
• Accepting a PDF only: Get the editable return if the agreed handoff requires it.
• Removing caveats that change meaning: Simplify wording without hiding relevant limitations.
• Reviewing only the cover: Inspect appendix, chart labels and linked material as well.

Completion check: You can trace the material assertions, distinguish approved facts from forecasts, identify the released version and explain why each held item remains held. Next use the materials-consistency guide to reconcile it with the rest of the fundraising packet.