{"slug":"business/68-fundraising-story","title":"68 — Fundraising Story","section":"business","sectionLabel":"Business","status":"unclassified","type":"document","path":"business/68-fundraising-story.mdx","bytes":5624,"description":null,"updated":null,"source":"integratewise/Integratewise-docs-wiki","content":"\nStatus: CANONICAL · Commercial OS\nOwner: Founder\nLast verified: 2026-07-21\nRelationship: process + sequencing for the narrative in [67](67-investor-narrative.md); evolves `docs/product/FUNDRAISE.md` to current stage logic.\n\n---\n\n## Purpose\n\nHow the raise is run: sequencing against proof milestones, the materials stack, target-list logic, and process discipline. The governing principle: **we raise on evidence thresholds, not on runway anxiety** — the story compounds with each design-partner conversion, so timing the raise _is_ the strategy.\n\n**Target audience:** Founder (operator); advisors.\n\n---\n\n## 1. Raise Logic & Timing\n\n**Round:** Seed, $750K–1.2M (allocation per [67 §10](67-investor-narrative.md); base case buys 13 months to $85K MRR trajectory per FINANCIAL_MODEL §5).\n\n**The proof ladder (each rung re-prices the story):**\n\n| Rung     | Evidence                                      | Story unlocked                                                             |\n| -------- | --------------------------------------------- | -------------------------------------------------------------------------- |\n| R1 (now) | Working product, doctrine, this Commercial OS | \"Exceptional preparation\" — angel/pre-seed conviction money                |\n| R2       | 8 design partners live, activation ≥ 70%      | \"Users work differently\" — seed conversations open                         |\n| R3       | 4 paying conversions + documented catches     | \"They pay for it\" — **the raise runs here (target: Q4 2026, with launch)** |\n| R4       | 25 customers, NRR evidence                    | Series A story begins ([77](../13-operations/77-annual-gtm-plan.md))       |\n\nRaising at R3 with launch momentum ([51](../09-gtm/51-launch-strategy.md)) means the process runs while the category noise peaks — the launch is a fundraising asset and vice versa.\n\n**Bridge honesty:** if runway pressures before R3 (SWOT T3 tripwire [10](../02-category-market/10-swot-analysis.md)), raise a smaller angel bridge on R2 evidence rather than a weak seed on R2.5 — a discounted story now costs more than bridge dilution.\n\n## 2. Materials Stack (all derive from the narrative — one story, three depths)\n\n1. **The email (5 lines):** wound story hook ($8M morning) → thesis sentence ([67 §1](67-investor-narrative.md)) → one traction number → the ask → a specific reason it's _this_ investor (their thesis/portfolio adjacency).\n2. **The deck (12 slides):** [67]'s ten sections, one per slide, plus title and ask. The demo film embedded at slide 4 — the approval + refusal beats are the slides that raise.\n3. **The data room:** this Commercial OS (the discipline artifact — few seed companies have one; it answers the \"solo founder, can he operate?\" question silently) · FINANCIAL_MODEL + assumptions · design-partner agreements + metrics dashboards · product access (a sandbox tenant — let them touch the morning) · cap table, corporate docs · security posture ([42](../07-sales/42-security-faq.md), honest status).\n\n## 3. Target List Logic (quality over coverage: ~40 names, three rings)\n\n**Ring 1 (10):** seed funds with published theses on AI applications + governance, future-of-work, or vertical-AI-with-moats; partners who've written about agent accountability or the copilot disappointment. **Ring 2 (15):** funds with portfolio adjacency (CS-tech, RevOps, workflow) without direct conflict — check conflicts hard (an investor in an agent-autonomy company is a Ring 3 at best). **Ring 3 (15):** strong generalists + operator angels from MuleSoft/Salesforce ecosystem and CS leadership world (angels who _are_ the ICP validate the wedge in the room).\n\n**Warmth rule:** every Ring 1–2 approach through a real connection (design partners' investors, ecosystem relationships, content-earned relationships — [57](../11-marketing/57-founder-led-marketing.md) S4 exists partly for this). Cold only into Ring 3, only with the 5-line email.\n\n## 4. Process Discipline\n\nBatch the process: all first meetings inside 3 weeks (parallel, not serial — solo founders die by serial fundraising) · selling time protected: fundraising ≤ 50% of founder hours for the sprint, sales pipeline pre-loaded before it starts ([50 §5](../09-gtm/50-gtm-strategy.md)) · every meeting logged: questions asked, pushback type ([67] pre-answers updated weekly), restatement accuracy · pass fast, gracefully — a slow maybe costs more than a quick no; ask every pass for the _reason_ (it tunes the story) · terms: standard seed instruments, no exotic structures, board-light; the doctrine applies to the cap table too — clean paper, no surprises.\n\n**The story's spine in every meeting:** the founder lived the problem ([14](../01-foundation/14-founder-story.md)) → the category is inevitable ([04](../01-foundation/04-long-term-narrative.md)) → the forks make it defensible ([67 §5](67-investor-narrative.md)) → the evidence is real (R3 proof) → the money buys named milestones ([67 §10](67-investor-narrative.md)).\n\n**KPIs:** meetings booked/Ring-1-2 approaches ≥ 40% · first-meeting → second-meeting ≥ 30% · process length ≤ 10 weeks · founder selling-hours protected (pipeline health during the raise — the metric everyone forgets) · post-raise: milestone delivery vs. [67 §10] commitments (the next raise starts there).\n\n---\n\n**Related:** [67 Investor Narrative](67-investor-narrative.md) · [10 SWOT](../02-category-market/10-swot-analysis.md) · [77 Annual GTM Plan](../13-operations/77-annual-gtm-plan.md) · [51 Launch](../09-gtm/51-launch-strategy.md)\n"}