agentleFS
HayatelinHayatelin/founder-skills/skills/fundraising-narrative/SKILL.md

fundraising-narrative

Skill0 starsChanged 5 months agoMITView on GitHub

Crafts the pitch narrative — problem, insight, why-now, solution, traction, market, and ask — for a pre-seed/seed AI startup. Trigger on "help me pitch", "pitch deck narrative", "fundraising story", "why now slide", "seed pitch", or "how do I tell my startup's story to investors".

3 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

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

  • 0

    Common

    Most of the 3 edited versions we read keep these.

  • 2

    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:

    When a founder is preparing to raise pre-seed/seed and needs a tight, investor-grade narrative arc — for a deck, a memo, or a verbal pitch.

    line 11
  2. Distinctive:

    Avoid: feature-first pitches.

    line 45

“Common” is measured: kept by at least 6 in 10 of the 3 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

When to use

When a founder is preparing to raise pre-seed/seed and needs a tight, investor-grade narrative arc — for a deck, a memo, or a verbal pitch.

Inputs to gather

  1. The problem, ICP, and what's broken about today's solutions.
  2. The founder's non-obvious insight / unfair advantage (why YOU, why now).
  3. Any traction: revenue, pilots, waitlist, design partners, growth rate.
  4. The raise amount, the milestones it funds, and rough use of funds.

Process

  1. Open on the problem — visceral, specific, in the customer's world (not "the market is huge").
  2. State the insight — the contrarian thing you believe that others don't; this is the spine of the pitch.
  3. Why now — the shift that makes this possible today (model capability, cost curve, regulation, behavior change). Investors fund timing.
  4. Solution — how it works in one breath, framed as the inevitable answer to the insight.
  5. Moat — be explicit: proprietary data, vertical depth, workflow lock-in, network effects, or regulatory edge. Pass the test: "if OpenAI/Anthropic shipped this tomorrow, what's left?" A thin wrapper won't clear seed bar in 2026.
  6. Traction — the steepest true line you have (revenue, design partners, retention, NRR). For vertical AI, outcome-based revenue + NRR 120-150% is a strong signal.
  7. Market — bottom-up sizing, then the wedge → expansion path.
  8. The ask — amount, the 2-3 milestones it buys, and the metric that earns the next round.

Output

  • One-line positioning ("We help [ICP] achieve [outcome] via [insight]").
  • Narrative arc: Problem → Insight → Why Now → Solution → Moat → Traction → Market → Ask, one tight paragraph or slide line each.
  • The ask with milestones and use of funds.
  • 3 anticipated hard questions + crisp answers (moat, defensibility, why-you).

Quality bar & pitfalls

  • Good = the insight and "why now" are memorable enough that an investor repeats them to a partner.
  • Traction speaks louder than vision at seed — lead with the steepest real number you have.
  • Avoid: feature-first pitches; vague "$X0B TAM" with no wedge; hand-waving the moat; a "why now" that was equally true three years ago.

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.