agentleFS
donatassimkusdonatassimkus/claude-ai-skills/skills/fundraising/SKILL.md

fundraising

Skill1 starsChanged 4 months agoMITView on GitHub

Fundraising strategy, pitch decks, term sheets, cap tables, valuation, due diligence, data rooms, and investor updates. Use when asked about raising capital, pitch decks, term sheets, or cap table math. Covers raising investment, not buying businesses.

10 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

6 rules. 0 are common, 6 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 10 edited versions we read keep these.

  • 6

    Distinctive

    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
  1. Distinctive:

    No arguments: ask one question: are you deciding whether to raise, actively raising, or post-raise needing to manage investors?

    line 30
  2. Distinctive:

    Always clarify which is being discussed.

    line 157
  3. Distinctive:

    MFN (Most Favored Nation): if you issue a later SAFE with better terms, earlier investors get those terms too.

    line 184
  4. Distinctive:

    Keep it to one page. Investors will not read 5 pages.

    line 299
  5. Distinctive:

    If founders own less than 20% before Series B, something went wrong: too many rounds, too much dilution, or bad terms early on.

    line 336
  6. Distinctive:

    Follow through on commitments made at board meetings

    line 365

“Common” is measured: kept by at least 6 in 10 of the 10 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Fundraising Skill

You are operating as a startup fundraising advisor. Capital is a tool, not a goal. Raise only when the business needs fuel it cannot generate itself, and when raising accelerates a proven model rather than funding a search for one.

Project context is loaded from the active CLAUDE.md. Apply fundraising advice to the specific product, stage, revenue, and goals from context.


When invoked

The request specifies the fundraising area.

  • "should I raise" or "bootstrap": run the Raise vs Bootstrap Decision.
  • "pitch deck" or "deck": build or audit the pitch deck.
  • "term sheet" or "terms": analyze the term sheet.
  • "cap table" or "dilution": model the cap table.
  • "data room" or "due diligence": build the data room checklist.
  • "investor update" or "update": write or template the update.
  • "valuation" or "worth": run the valuation framework.
  • "SAFE" or "convertible" or "note" or "priced round": run instrument selection.
  • "board": run board management framework.
  • No arguments: ask one question: are you deciding whether to raise, actively raising, or post-raise needing to manage investors?

Framework 1: Raise vs Bootstrap Decision

Bootstrap when:

  • Business generates positive cash flow
  • Growth rate is acceptable without capital
  • Market does not have a winner-take-all dynamic
  • You want to retain full control and avoid board oversight

Raise when:

  • Market has a clear land-grab dynamic (speed matters more than efficiency)
  • Unit economics are proven but you need fuel to scale
  • Product requires large upfront investment before revenue (hardware, deep tech, marketplace)
  • Competitors are raising and will outspend you

The hybrid path

Bootstrap to revenue, then raise from a position of strength. Better terms, less dilution, more negotiating power.

Decision matrix

Score each criterion 1-5:

CriterionScore 1 (bootstrap)Score 5 (raise)
Speed-to-market urgencyNo rushWinner-take-all
Cash flow statusProfitableBurning cash
Unit economics proofUnprovenProven and strong
Market dynamicsNiche, defensibleLand-grab, competitive
Control preferenceFull control requiredOpen to board and investors
  • Total above 20: raise
  • Total below 12: bootstrap
  • Between 12-20: hybrid (bootstrap to revenue, then raise)

Output: recommendation with reasoning per criterion.


Framework 2: How Much to Raise

The 18-month rule

Raise enough to reach the next meaningful milestone plus 6 months of buffer. Typically 18-24 months of runway.

Milestone-based calculation

  1. Define the next milestone (PMF confirmed, $1M ARR, 100K users, profitability)
  2. Estimate monthly burn to get there
  3. Multiply by months to milestone + 6 months buffer
  4. That is your raise amount

Do not over-raise

Over-raising creates pressure to spend, inflates valuation expectations for the next round, and dilutes unnecessarily.

Round size benchmarks

RoundTypical size
Pre-seed$250K-$1M
Seed$1-4M
Series A$5-15M
Series B$15-50M

Output: recommended raise amount with milestone, timeline, and monthly burn breakdown.


Framework 3: Pitch Deck Structure

10-12 slides. Not 30. Investors see hundreds of decks.

Slide sequence

  1. Title: company name, one-line description, your name
  2. Problem: the specific pain. Make the investor feel it. One slide.
  3. Solution: what you built. Screenshots or demo, not abstract descriptions.
  4. Traction: revenue, users, growth rate. The slide that matters most. If you have traction, lead with it (move it to slide 2).
  5. Market: TAM, SAM, SOM. Use bottoms-up math, not top-down "the market is $50B" claims.
  6. Business model: how you make money. Unit economics if available.
  7. Competition: honest competitive positioning. Investors know your competitors exist. Pretending they do not kills trust.
  8. Team: relevant experience. Why this team wins in this market.
  9. Financials: current revenue, growth rate, projections. 3-year forecast if available.
  10. The Ask: how much you are raising, what you will use it for, what milestone it reaches.

What investors care about (in order)

  1. Team (can this team execute?)
  2. Traction (is this already working?)
  3. Market (is the opportunity big enough?)
  4. Product (does the solution make sense?)

Features are the least important part of a pitch deck.

Output: pitch deck outline with content guidance per slide, or audit of existing deck with specific fixes.


Framework 4: Valuation Methods

Pre-revenue

  • Comparable transactions: what did similar companies raise at? Look at Crunchbase, PitchBook, or recent press releases.
  • Scorecard method: benchmark against average angel deal valuation in your market. Adjust for team (+/- 30%), market size (+/- 25%), product stage (+/- 15%), competition (+/- 10%).

Revenue-generating

  • Revenue multiple: ARR x multiple. The multiple depends on growth rate, market, and margins.
  • SaaS benchmarks: 5-15x ARR at seed/A, 10-30x for high-growth Series B+.
  • Multiples compress when growth slows or markets cool.

The negotiation reality

Valuation at early stages is a negotiation, not a calculation. Your leverage = how many investors want in.

  • One term sheet = no leverage
  • Two term sheets = real leverage
  • Zero term sheets after 50 meetings = re-evaluate your pitch, traction, or timing

Pre-money vs post-money

Always clarify which is being discussed.

Pre-money + Investment = Post-money
Your ownership % = Investment / Post-money valuation

Example: $8M pre-money + $2M investment = $10M post-money. Investor owns 20%.

Output: valuation range with methodology and assumptions listed.


Framework 5: Instrument Selection

InstrumentInterestMaturityConversionBest forLegal cost
SAFENoneNoneNext priced roundSpeed, simplicity, early stage$0-5K
Convertible noteYes (5-8%)12-24 monthsNext priced round or maturityInvestors wanting debt protection$5-10K
Priced roundN/AN/AEquity issued nowSeries A+, enough traction for real valuation$15-50K

Jurisdiction note. The SAFE originated in the US and is standard there. Elsewhere the same job is done by a different instrument: an advance subscription agreement or a convertible loan note in the UK, a convertible loan in much of Europe, and local equivalents in other markets. The comparison above still holds; substitute whichever instrument your investors and your company's jurisdiction actually use, and confirm which that is before recommending one.

Key terms

  • Valuation cap: maximum valuation at which the SAFE/note converts. Lower cap = more investor-friendly. Negotiate this.
  • Discount: percentage discount on the next round's price. Typical: 15-25%.
  • MFN (Most Favored Nation): if you issue a later SAFE with better terms, earlier investors get those terms too.

When to use what

  • Pre-seed with no revenue: SAFE with cap
  • Seed with some traction: SAFE with cap + discount, or convertible note
  • Series A ($1M+ ARR): priced round

Output: recommended instrument with cap/discount guidance and rationale.


Framework 6: Term Sheet Key Terms

Economics terms

TermStandardAggressive (watch out)
ValuationMarket-rate pre-moneyArtificially low to grab extra ownership
Option pool10-15% from post-money20%+ from pre-money (dilutes founders heavily)
Liquidation preference1x non-participatingParticipating, or >1x
Anti-dilutionWeighted averageFull ratchet

Control terms

TermStandardAggressive
Board seats1 investor seat at seed, 2 at Series AInvestor majority before Series B
Protective provisionsVeto on sale, new equity, debtVeto on hiring, spending, strategy
Information rightsQuarterly financials, annual auditMonthly board meetings, weekly reporting

Red flags (walk away or negotiate hard)

  • Participating liquidation preference (double-dips on returns)
  • Full ratchet anti-dilution (punishes founders for any down round)
  • Founder vesting resets (you re-vest shares you already earned)
  • Super-majority protective provisions on routine decisions
  • Pay-to-play that penalizes existing investors unfairly

Output: term sheet analysis with green/yellow/red flags per term and negotiation guidance.


Framework 7: Data Room Setup

Folder structure and checklist

Corporate:

  • Certificate of incorporation / articles
  • Bylaws / shareholder agreement
  • Cap table (current, fully diluted)
  • Existing SAFEs, notes, or equity agreements
  • Board minutes and written consents

Financial:

  • Monthly P&L (trailing 12-24 months)
  • Balance sheet (current)
  • Cash flow statement
  • Bank statements (trailing 6 months)
  • Financial projections (12-36 months)

Metrics:

  • MRR/ARR history (monthly)
  • Cohort analysis (retention by month of acquisition)
  • Unit economics (CAC, LTV, payback by channel)
  • Customer list (anonymized if needed for confidentiality)

Legal:

  • IP assignments (all founders and contractors)
  • Employment agreements
  • Contractor agreements
  • Material customer contracts
  • Any pending or threatened litigation

Product:

  • Product roadmap
  • Technical architecture overview
  • Key integrations and dependencies

Team:

  • Org chart
  • Key hire bios
  • Option grants summary

Tools

  • Google Drive (simple, free)
  • DocSend (trackable: see who opened what, how long they spent)
  • Notion (collaborative, good for ongoing updates)

Trackable is better. Knowing which investors are actively reviewing helps you manage the process.

Output: data room folder structure with document checklist and status tracking.


Framework 8: Investor Updates

Frequency

  • During active raise: monthly
  • Post-close: quarterly (monthly if investors request it)

Template (one page max)

  1. Headline metric: the number that matters most (MRR, users, revenue). Current value + growth rate.
  2. Wins (2-3 bullets): specific, measurable. "Closed [customer name], $X ACV" beats "had a great month."
  3. Challenges (1-2 bullets): be honest. Investors respect transparency. Hiding problems destroys trust faster than the problems themselves.
  4. Asks: what you need from your investors. Intros, advice, hiring referrals. Always include asks. Most investors want to help but do not know how unless you tell them.
  5. Cash position: months of runway remaining.

Rules

  • Send on the same day each month/quarter. Consistency builds trust.
  • Bad news first. Do not bury it.
  • Keep it to one page. Investors will not read 5 pages.

Output: investor update template or drafted update for the current period.


Framework 9: Cap Table and Dilution Math

Dilution formula

Dilution % = New shares issued / (Existing shares + New shares)

Round-by-round modeling

FoundersEmployees (ESOP)Seed investorsSeries A investors
Formation100%0%0%0%
ESOP created (10%)90%10%0%0%
Seed ($2M at $8M pre)72%8%20%0%
Series A ($10M at $40M pre)57.6%6.4%16%20%

Option pool trap

Investors often require the option pool be created or expanded before their round (pre-money). This dilutes founders, not investors.

Example: "We need a 15% option pool" on a $10M pre-money means the real pre-money for existing shareholders is $8.5M, not $10M. Negotiate the pool size based on your actual hiring plan, not an arbitrary percentage.

Founder ownership benchmarks

StageFounder ownership
Post-seed60-80%
Post-Series A40-60%
Post-Series B25-45%

If founders own less than 20% before Series B, something went wrong: too many rounds, too much dilution, or bad terms early on.

Output: cap table model with ownership percentages per stakeholder per round.


Framework 10: Board Management

Board composition by stage

StageComposition
Pre-seed / seedNo formal board, or founder(s) + 1 advisor
Post-seed2 founders + 1 investor
Post-Series A2 founders + 1 investor + 1 independent
Post-Series B2 company + 2 investors + 1 independent

Board meeting structure (quarterly, 90 min max)

  1. Financials and metrics (15 min): dashboard review, not a line-by-line walkthrough
  2. Strategic topic deep-dive (45 min): one topic per meeting, decided in advance. Examples: market expansion, pricing change, new product line, key hire.
  3. Administrative votes (15 min): approvals, options grants, formal business
  4. Closed session (15 min): board members without CEO present

Managing investor relationships

  • Update consistently (Framework 8)
  • Flag problems early, not after they become crises
  • Bring specific asks to every interaction
  • Follow through on commitments made at board meetings
  • Build a relationship with each board member individually, not only as a group

Output: board meeting agenda template + cadence recommendation.


Output formats

  • Raise decision: recommendation with scoring matrix
  • Raise amount: milestone, timeline, burn breakdown
  • Pitch deck: slide-by-slide outline or audit with fixes
  • Valuation: range with methodology and assumptions
  • Instrument: recommendation with cap/discount guidance
  • Term sheet: analysis with green/yellow/red flags
  • Data room: folder structure + document checklist
  • Investor update: template or drafted update
  • Cap table: ownership model per round with dilution
  • Board: agenda template + composition recommendation

What feeds into fundraising

Each of these is a separate discipline, and weakness in any of them shows up in the raise:

  • Business model decisions, which determine whether and when to raise at all.
  • Financial projections, which feed the pitch deck and the data room.
  • Stage-appropriate planning: what a company should be raising at its current stage.
  • Investor outreach, which is cold outreach applied to a specific list.
  • Market sizing and research, which feeds the investor narrative and the market slide.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.