fundraising-stage-selector
Skill0 starsChanged 4 months agoMITView on GitHub
Use when a founder is deciding whether and how to raise. Triggers on "am I pre-seed or seed", "how much should I raise", "what stage am I", "what valuation can I get", "should I raise now or wait", "is my round too big". Sets the round, amount, and valuation envelope that every later step depends on.
In this repository19 other files it gives its agents.
- cap-table-managerSkill
- data-room-builderSkill
- due-diligence-checklistSkill
- financial-plannerSkill
- fundraise-closing-mechanicsSkill
- fundraise-readiness-auditSkill
- fundraise-team-hiringSkill
- fundraising-narrativeSkill
- investor-pipeline-crmSkill
- investor-targetingSkill
- investor-update-writerSkill
- market-sizingSkill
- pitch-deck-builderSkill
- pitch-practice-coachSkill
- safe-vs-priced-roundSkill
- series-a-readinessSkill
- term-sheet-explainerSkill
- term-sheet-negotiationSkill
- vc-pitch-emailSkill
The file
We split this skill into the rules it gives an agent
4 rules. About 0 are common, 4 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈4
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 8
Every later step - deck, targeting, terms - is wrong if the stage is wrong.
- Distinctive: line 20
Place the company by what is *proven*, not what is hoped:
- Distinctive: line 30
If the evidence straddles two stages, you are at the lower one.
- Distinctive: line 35
Do not raise "as much as you can." Raise the amount that buys the *next fundable milestone* plus margin:
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Fundraising Stage Selector
Every later step - deck, targeting, terms - is wrong if the stage is wrong. The most common founder error is raising at the stage they wish they were at, not the one their evidence supports. This skill fixes the stage first.
When to use this skill
Reach for it before writing a deck or emailing an investor, whenever the founder asks how much to raise, what valuation is realistic, or whether to raise at all yet. It produces the envelope; everything downstream is calibrated to it.
Read the stage off evidence, not ambition
Place the company by what is proven, not what is hoped:
- Pre-seed: a team and an insight, maybe a prototype or design partners. You are selling the founder and the bet. Typical raise $250k-$1.5M.
- Seed: a shipped product and the first signal of pull - early revenue, retention, or week-over-week usage growth. Typical raise $1.5M-$4M.
- Series A: a working engine. Repeatable acquisition, real retention, and a metric that scales (often ~$1M+ ARR for SaaS, with strong growth/retention). Typical raise $6M-$15M.
If the evidence straddles two stages, you are at the lower one. Investors price the floor of your story, not the ceiling.
Size the raise from the milestone, not the market
Do not raise "as much as you can." Raise the amount that buys the next fundable milestone plus margin:
- Name the milestone the next round requires (e.g. "$1M ARR at 120% NRR").
- Estimate monthly burn to get there and the months it takes.
- Raise milestone-cost x 1.5 (18-24 months of runway, never under 12).
- Sanity-check dilution: a healthy round sells 15-25%. If your target amount forces >25% at a realistic valuation, the amount is too big or the valuation too low - fix one.
Valuation envelope
Triangulate, never anchor on a single hope:
- Comparables: what companies with your traction raised recently, in your geography and sector.
- Dilution math: amount ÷ target dilution = post-money. ($2M for 20% => $10M post.)
- Instrument: pre-seed/seed usually a SAFE with a valuation cap; priced rounds start at seed/A. Pair with [[safe-vs-priced-round]].
The number you can defend beats the number you can dream. An overpriced round you barely fill creates a down-round trap next time.
Should you raise at all?
Push back before pulling forward. Don't raise if: the milestone is reachable on revenue, the story has no proof and no clock, or dilution buys less than a clear step-change. Bootstrapping a quarter to add proof often beats raising weak.
Anti-patterns
- Pricing on TAM instead of traction.
- A round so large it sets a Series A bar you cannot clear in 24 months.
- Raising on "everyone is raising" with no milestone to point the cash at.
Deliverable
A one-page raise thesis: stage (with the evidence that fixes it), amount, the named milestone it funds, months of runway, target dilution, and a defensible valuation range with its comparables. Hand this to [[fundraise-readiness-audit]] before going out.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

