| name | saas-ai-funding-stage-playbook |
| description | Use when producing or reviewing the saas ai funding stage playbook component of a business plan; applies its specialist evidence, decisions, and acceptance tests instead of neighbouring pipeline skills. |
| metadata | {"portable":true,"compatible_with":["claude-code","codex"]} |
SaaS AI Funding Stage Playbook Skill
Overview
The standard SaaS funding ladder (bootstrap → F&F → pre-seed → seed → A → B → growth) sits in saas-valuation-and-fundraising-strategy / saas-funding-stage-playbook.md. AI startups raise differently: AI-specialist funds set different bars, generalist SaaS funds discount or ignore the AI thesis, sovereign-AI funds (in select jurisdictions) have separate envelopes, AI-for-good DFIs / grantmakers run different rubrics. This skill installs the AI overlay.
Use When
- Section 11 of an AI-feature-led SaaS plan is being built
- A fundraise is being planned and investor-archetype targeting must be intentional
- A founder is asking which funders fit and which don't
- DFI / grant pathway is being explored alongside commercial fundraise
Do Not Use When
- AI is internal-efficiency only — use
11-funding-request + saas-funding-stage-playbook.md
- Plan is bank-loan only (CAMPARI; AI is incidental)
Required Inputs
- ARR / MRR + AI-attribution share (from
saas-ai-market-and-tam)
- AI bankability scorecard
- AI moat score
- Valuation range with AI adjustments
- Use-of-proceeds plan (AI-specific spend)
- Geography / regulatory context
Workflow
- Identify the stage based on standard SaaS criteria (ARR, growth, team size, customer count, GM, NRR) plus AI-specific signals (eval coverage, model-mix maturity, AI revenue share, governance maturity).
- Apply the AI-specific milestone breakpoints per
references/saas-ai-funding-stage-playbook.md:
- Pre-seed: AI prototype in production with ≥1 paying customer; eval suite started; cost-per-tenant directional
- Seed: 10-30 AI-paying customers; AI Gross Margin >50%; eval coverage >40%; AI-cost-as-%-of-ARR <15%; governance policy drafted
- Series A: $1-3M AI-ARR or $3-5M total ARR with AI driving net new; AI GM >65%; eval coverage >60%; cost engineering visible; moat thesis testable
- Series B: $5-15M ARR; Rule-of-40-AI adjusted ≥35; AI GM trajectory positive; vendor concentration <70%; governance committee operating
- Growth: $20M+ ARR; Rule of 40 ≥40; AI premium clearly priced into valuation; multi-region; AI compliance for enterprise
- Map to investor archetype per
references/ai-investor-archetype-map.md:
- AI-specialist funds: a16z AI, Index AI, Bessemer AI, Cohere founders fund, Khosla AI, Lightspeed AI, AIX Ventures, AI Grant, Conviction, South Park Commons, Costanoa, Greylock AI track
- Generalist SaaS funds: Sequoia, Accel, Benchmark, Iconiq, Battery, Insight, Tiger, Coatue — AI thesis must be defensible but not the primary pitch
- Sovereign-AI funds: G42 / MGX (UAE), French sovereign-AI envelope, German / EU AI funds, Saudi Vision 2030 AI envelopes — usually for AI-platform / sovereign-AI archetype
- DFIs with AI envelopes: IFC AI envelopes, AfDB AI-for-development, Norfund, BII (formerly CDC), FMO, Proparco, Swedfund
- AI-for-good grantmakers: Mozilla African Innovation Mradi, GSMA AI for Impact, IDRC AI4D, Lacuna Fund (training-data grants), Google.org AI for Social Good, Microsoft AI for Good, Patrick J. McGovern Foundation, Gates AI envelopes
- Africa-focused funds with AI thesis: Norrsken22, TLcom, Partech Africa, P1 Ventures, 4DX, Renew Capital, Future Africa, Catalyst Fund, Ventures Platform, Antler Africa
- Set the use-of-proceeds AI lines — AI infra (compute, model APIs, vector DBs); AI hiring; eval pipeline build-out; AI governance / compliance build; training-data acquisition; AI sales / marketing.
- Set the milestones the round funds in AI-specific terms — eval coverage target, AI GM target, AI-revenue target, AI moat-evidence target, governance maturity target.
Stage Readiness Table (indicative)
| Stage | AI ARR | AI GM | Eval coverage | Governance | Moat evidence |
|---|
| Pre-seed | $0-$50k | n/a / >40% | >40% on top features | policy in draft | thesis only |
| Seed | $50k-$500k | >50% | >50% | policy + decision log | first proprietary-data signal |
| A | $1-$5M | >65% | >60% | committee operating | data accrual + workflow moat |
| B | $5-$20M | >70% | >75% | full RACI + eval program | proven moat + 1-2 dimensions |
| Growth | $20M+ | >75% | >85% | external audit / SOC2 + AI | 3+ moat dimensions defensible |
Quality Bar
- Stage declared with AI-specific evidence
- Investor archetype targeted; not "all VCs"
- Use-of-proceeds has AI-specific lines, not "team + product + sales"
- Milestones the round funds stated in AI-specific terms
- Foundation-model platform-risk addressed
- Grant + commercial blend considered for Africa-context plans
- Cross-references to bankability and valuation
Anti-Patterns
- One pitch deck for all investor archetypes
- "Raising $5M" with no AI-specific use-of-proceeds breakdown
- Targeting generalist SaaS funds with an AI pitch and getting AI-discount valuations
- Ignoring AI-for-good DFI / grant pathways in Africa-context plans
- No moat-survives-platform-risk story
- Round milestones in generic SaaS terms, not AI terms
Outputs
- Stage declaration with AI evidence
- Investor archetype map (who fits, who doesn't, in priority order)
- Use-of-proceeds with AI-specific lines
- Round-fund milestones in AI terms
- Foundation-model platform-risk response
- Grant + commercial blend plan
- Investor-pipeline list
Living-Plan Cadence Defaults
| Element | Cadence | Owner | Variance threshold |
|---|
| Stage readiness review | quarterly | CEO + CFO | round-not-ready signal |
| Investor pipeline | monthly | CEO | conversion stall |
| Use-of-proceeds vs spend | monthly | CFO | overspend on AI infra |
| Round-fund milestones | monthly | CEO + CFO | slip >45 days |
| Investor archetype map | semi-annual | CEO | new fund category emerges |
| Grant pipeline | quarterly | CEO + Grants lead | grant cycle slip |
References
references/saas-ai-funding-stage-playbook.md — full stage ladder + investor-archetype detailreferences/ai-investor-archetype-map.md — named funds per archetype with thesis notesskills/saas-valuation-and-fundraising-strategy/SKILL.md — base SaaS funding skillskills/meta-ai-bankability-and-investor-readiness/SKILL.md — bankability that supports stageskills/meta-ai-valuation-adjustments/SKILL.md — valuation overlayskills/11b-grant-proposal/saas-ai-for-good-grant-proposal/SKILL.md — grant pathwaycountry-context/africa-regional/africa-ict-saas-market-context.md — Section 7 funding ecosystem
Africa / Uganda Application Notes
- Blended-finance approach is often optimal: commercial seed + AI-for-good grant funding training-data + ethics + local-language coverage.
- DFI cycles are slower (6-18 months) than commercial VC; plan runway accordingly.
- Sovereign-AI tender pre-funding is emerging in select African jurisdictions (RW, KE, NG, ZA, EG) — tender wins can be quasi-funding events.
- Diaspora capital + African-roots funds (Norrsken22, P1, TLcom, Partech Africa, 4DX, Future Africa) increasingly comfortable with AI thesis; international AI-specialist funds still rare in African deals.
- Use-of-proceeds in DFI plans should include training-data acquisition, local-language curation, local AI-team hiring, governance build-out — these are often DFI / grant priorities.
- FX exposure on USD-funded plans must be modelled as a runway risk.
July 2026 Portable Contract
Required Inputs
| Input artefact | Source/provider | Required | Behaviour when absent |
|---|
| Reconciled funding need, use-of-funds schedule, financing capacity, traction evidence, milestones, and investor or lender criteria for saas ai funding stage playbook | Financial model, implementation plan, client records, and target-financier materials | Yes | If absent, the funding gap, uses, repayment capacity, dilution effect, or stage evidence is unavailable, return a financing-readiness gap note and withhold the amount or instrument recommendation. |
| Finalised business brief, target reader, country, and stage | Client intake and engagement owner | Yes | Stop section decisions and route the missing context to client intake. |
| Reconciled upstream assumptions that this section consumes | Named pipeline owners | Conditional | Record the dependency, affected claim, owner, and recovery step; do not substitute an invented value. |
Outputs
| Artefact | Consumer | Observable acceptance condition |
|---|
| Audience-specific funding request with instrument, uses, milestones, and repayment or return logic | Plan author and target decision-maker | The artefact answers the section decision and traces each material conclusion to the supplied evidence. |
| saas ai funding stage playbook exception and handoff note | Downstream section owners | Every blocked or conditional item names its consequence, owner, evidence request, and restart condition. |
| saas ai funding stage playbook release record | Reviewer or plan assembler | Records the checks completed, failures, unassessed items, professional review required, and release state. |
Evidence Produced
| Evidence | Format | Acceptance condition |
|---|
| Ask-to-use reconciliation, financing-option decision record, milestone release logic, and caveat register | Source-linked table, calculation, or annotated prose | The evidence is reproducible from named inputs and distinguishes verified fact, management assumption, and inference. |
| saas ai funding stage playbook decision record | Decision note | States the selected action, rejected credible alternative, countercase, rationale, and risk accepted or avoided. |
| saas ai funding stage playbook review trace | Gate entry | Identifies the date, input versions, reviewer role, failed checks, recovery owner, and any check that remains not assessed. |
Capability and Permission Boundaries
For saas ai funding stage playbook, the controlling focus is AI venture maturity, model dependency, data rights, economics, milestones, and investor archetype. This skill may analyse financing options and draft the ask; it may not solicit investors, submit applications, negotiate terms, value securities, or bind the client without explicit authority and professional review. Its normal mode is read-only analysis and drafting. Any mutation, external communication, spending, certification, or professional conclusion outside that boundary requires explicit authority and must remain traceable to the approving role.
Degraded Mode
For saas ai funding stage playbook, loss of evidence about AI venture maturity, model dependency, data rights, economics, milestones, and investor archetype activates degraded mode. If the controlling saas ai funding stage playbook evidence is unavailable, the same boundary applies. When the funding gap, uses, repayment capacity, dilution effect, or stage evidence is unavailable, return a financing-readiness gap note and withhold the amount or instrument recommendation. Return the verified subset, label the affected decision qualified or not assessed, explain the downstream consequence, and state the smallest evidence request or authorised action that permits recovery. Do not convert the missing check into a pass.
Decision Rules
| Choice or condition | Action | Failure or risk avoided |
|---|
| For saas ai funding stage playbook, the preferred instrument does not match cash-flow capacity, stage, security, or investor-return evidence | reject it, compare the viable alternatives, and state the milestone needed to reopen the option | A mismatched ask can create unaffordable debt, avoidable dilution, or failed diligence |
| For saas ai funding stage playbook, A current legal, regulatory, tax, accounting, market, or platform claim controls the saas ai funding stage playbook decision | Verify the controlling source, effective date, jurisdiction, and reviewer status before release | Stale external facts become permanent plan assumptions |
| For saas ai funding stage playbook, The evidence reconciles with neighbouring sections and the countercase does not overturn the choice | Complete audience-specific funding request with instrument, uses, milestones, and repayment or return logic, attach the evidence and release record, and hand off named dependencies | Premature release and repeated downstream rework |
Workflow
- Define the exact saas ai funding stage playbook decision, intended reader, jurisdiction, business stage, and permission boundary.
- Collect reconciled funding need, use-of-funds schedule, financing capacity, traction evidence, milestones, and investor or lender criteria and map each material conclusion to its source; stop the affected conclusion when an input could change it.
- Apply the specialist methods and directly linked references already contained in this skill, retaining its domain thresholds, calculations, and Uganda or East Africa context where applicable.
- Compare the credible alternatives, test the countercase and failure path, and apply the decision table rather than selecting a template default.
- Produce audience-specific funding request with instrument, uses, milestones, and repayment or return logic with the evidence, exception, and handoff records; reconcile every shared assumption with its owning section.
- Run the section quality checks, applicable finance or professional review, and anti-slop gate. If a gate fails, correct the evidence or decision and return to the responsible step.
Quality Standards
- Audience-specific funding request with instrument, uses, milestones, and repayment or return logic must answer a real decision for the named bank, investor, DFI, grant, board, or strategic-partner reader.
- Ask-to-use reconciliation, financing-option decision record, milestone release logic, and caveat register must be source-linked, dated where facts can change, and sufficient for another reviewer to reproduce the conclusion.
- The section exposes its countercase, stop condition, recovery action, and effect on neighbouring sections.
- No unavailable source, calculation, tool, or professional review is reported as passed; finance and statutory judgements follow the governing doctrine.
- Language remains specific to saas ai funding stage playbook, uses British English naturally, and passes the repository anti-slop gate without promotional filler.
Anti-Patterns
- In saas ai funding stage playbook, treating an unavailable reconciled funding need, use-of-funds schedule, financing capacity, traction evidence, milestones, and investor or lender criteria as confirmed. Correction: qualify the affected conclusion and issue the named evidence request.
- Producing audience-specific funding request with instrument, uses, milestones, and repayment or return logic that restates the brief but makes no choice. Correction: record the choice, rejected alternative, rationale, countercase, and implication.
- Ignoring a conflicting upstream assumption. Correction: return it to its owning section and resume only from a reconciled version.
- Reporting an unavailable check as passed. Correction: mark it not assessed and narrow the release state.
- Claiming compliance, assurance, bankability, or investor readiness from narrative quality. Correction: run the applicable gate and retain its evidence.
- Copying the worked example into a client plan. Correction: use the method only and replace every fact with verified engagement evidence.
Worked Example
An AI venture owns customer workflow data but depends on one model provider and has unstable inference margin. Target investors suited to technical risk and tie funding releases to portability and margin gates.
References
- Use the verified project evidence register and the owning upstream pipeline section for saas ai funding stage playbook; no local deep-dive reference is declared.
- For saas ai funding stage playbook claims involving money, tax, grants, reserves, revenue, cost, valuation, or financial statements, apply the Chwezi finance doctrine and record the required professional-review state; illustrative figures never become client facts.
