/fundraising

Fundraising

Separate storytelling problems from company-fact problems. Build the strongest defensible case without turning investor folklore into doctrine.

Choose a mode

• Raise/no-raise: test whether venture capital fits the company and alternatives.
• Fundability assessment: identify strengths, disqualifiers, and evidence gaps.
• Deck or memo audit: test narrative, claims, metrics, and consistency.
• Narrative workshop: develop a small number of defensible investment claims.
• Round planning: connect amount, runway, dilution, use of funds, and milestones.
• Investor research: verify firm and partner fit, conflicts, check size, and current activity.
• Meeting/diligence prep: objections, data room, difficult questions, and follow-up.

Use only the modes needed.

Workflow

1. Inspect existing deck, memo, metrics, product/customer evidence, cap table, financial model, prior feedback, and repository context before interviewing.
2. Establish stage, amount, runway, use of funds, milestone, market, customer, traction, growth, retention, economics, distribution, competition, team, geography, and financing constraints. Ask only blocking questions.
3. Test whether venture return expectations and financing dynamics fit the business. Present bootstrapping, revenue financing, debt, grants, angels, or a smaller round when materially relevant.
4. Map every important claim to a metric definition, cohort, customer fact, product mechanism, or sourced market observation. Flag unsupported claims and inconsistent periods or denominators.
5. Pressure-test problem importance, wedge, market expansion, product advantage, distribution, evidence of pull, economics, timing, founder fit, and round-specific risks.
6. For investor research, use current official firm/partner sources and recent primary evidence. Verify thesis, stage, geography, check size where published, portfolio conflicts, partner involvement, and retrieval date. Do not infer active interest.
7. Build headlines and evidence before slide prose. Adapt length and order to stage, format, and audience; do not force a fixed slide count.
8. Red-team market sizing, cohort metrics, financial consistency, dilution/runway math, competitive claims, and the milestone the round buys.
9. Prepare honest answers, disqualifiers, requested follow-up material, and next actions. Never invent traction, logos, quotes, market size, investor interest, or commitments.

Load conditional references

• Read pitch patterns for claim design, risk handling, deck headlines, and partnership-summary tests. Treat named historical frameworks as optional lenses, not current investor consensus.
• Read founder frameworks only when a market-pull, risk-reduction, dependency, or founder-reality lens helps. The reference states limitations.

This file remains authoritative for interaction, evidence, output, and verification.

Output contract

Return the sections required by the selected mode, such as:

• candid fit/fundability assessment and financing alternatives;
• strongest defensible narrative and claim-to-evidence map;
• metric, market, and operating evidence gaps;
• round amount/use/milestone/runway logic;
• investor-fit shortlist with sources and conflict notes;
• slide headlines or memo outline;
• objection handling, diligence requests, and next actions.

Verify

• Metric definitions, periods, cohorts, and denominators are consistent.
• Market sizing is triangulated and assumptions are visible.
• Round amount, use of funds, runway, dilution, and milestone agree.
• Investor-fit claims come from current primary evidence and do not imply interest.
• Every material pitch claim has support or is labeled as a hypothesis.
• Risks, disqualifiers, counterarguments, and financing alternatives are explicit.

Optional founder lenses

These are diagnostic lenses derived partly from older startup writing. Use one only when it clarifies the founder's current evidence. Do not present historical opinions as current facts or mandatory advice.

Market pull

Ask whether target users repeatedly adopt, retain, pay, refer, or expand without unsustainable effort. Use product-specific evidence:

• activation and cohort retention;
• sales-cycle and win/loss patterns;
• willingness to pay and expansion;
• organic/referral contribution;
• pull for a repeatable use case.

Press attention, investor enthusiasm, or a few loud users do not establish product-market fit. Define what evidence would change the conclusion.

Risk reduction

Classify the few risks that block this financing:

• customer/problem;
• product/technical feasibility;
• market size and expansion;
• distribution and economics;
• competition/differentiation;
• regulation/security;
• team/hiring;
• financing/runway.

Repeated investor rejection is evidence to analyze, not proof that the company is wrong. Separate investor fit, process quality, narrative, terms, timing, and company risk. Identify the cheapest milestone that materially changes the strongest objection.

Large-company dependency

For a partnership, platform, channel, or acquisition dependency:

• map champion, economic buyer, security/legal/procurement, and veto holders;
• estimate timing from comparable evidence, not optimism;
• identify what can proceed without the deal;
• cap investment before contractual commitment;
• maintain a fallback distribution or product path.

Do not automatically reject large-company distribution. Treat concentration and control as risks to price and mitigate.

Founder and team reality

Assess whether the team can reach the next milestone, not whether it matches a historical archetype or geography. Consider:

• domain/product/technical and distribution capability;
• hiring plan and scarcity;
• pace, decision quality, and learning;
• founder incentives and working relationship;
• location only where it materially affects customers, regulation, hiring, or investors.

Avoid categorical advice to relocate or add a “business person.” State the actual capability gap and evidence.

Use in a fundraising artifact

When a lens is used, output:

• observation and supporting evidence;
• alternative explanation;
• financing implication;
• next milestone or diligence item;
• confidence and what would change it.

Pitch and narrative patterns

This reference preserves useful ideas from historical venture-pitch frameworks without treating them as current consensus. The main skill controls task mode, research, interaction, output, and verification.

Claim design

Build the pitch around three to five claims an investor could repeat accurately. A claim should contain:

• specific fact or mechanism;
• evidence and time period;
• why it matters to the investment outcome;
• strongest uncertainty or counterargument.

Examples of claim categories:

• painful problem and identifiable buyer;
• non-obvious product or market insight;
• wedge with evidence of pull;
• advantage in product, data, cost, distribution, or speed;
• credible expansion from the wedge;
• team fit for the next risk, not generic prestige.

Avoid claims such as “huge market,” “no competitors,” or “AI-powered” without mechanism and evidence.

Risk map

Name the few risks that matter to this round. For each, record:

Do not hide a weak company fact with better prose. Put unsupported claims on the operating plan or remove them.

Headline test

Slide or memo headings should state the message, not merely the topic.

• Weak: Market
• Better: [Initial segment] spends [verified amount/time] on a workflow we can replace

Read headlines in order. They should explain what the company does, why the problem matters, the insight, evidence, expansion, economics/distribution, team, risks, and what the round achieves. Adapt the count and order to stage and format.

Partnership-summary test

Write the short internal summary a sponsoring investor could send without exaggeration:

1. what the company does and for whom;
2. why the opportunity could be venture-scale;
3. product/technical or market insight;
4. evidence of pull and distribution;
5. advantage and credible expansion;
6. round, milestone, and largest risk.

If this cannot be written clearly, find the missing fact or narrative break.

Objection preparation

For each likely objection:

• restate it fairly;
• answer with evidence, not defensiveness;
• distinguish known, estimated, and unknown;
• provide the relevant appendix or data-room artifact;
• state the planned de-risking action when evidence is incomplete.

Historical-framework limitation

Ideas such as emotional narrative, “lures,” fixed slide budgets, or a team-last order can be useful prompts but are not universal. Investor processes vary by stage, sector, geography, fund, and meeting type. Current behavior must be researched from the target investor and recent primary evidence.