agentleFS
impactbrusselsimpactbrussels/FounderOS/skills/pitch-deck/SKILL.md

pitch-deck

Skill2 starsChanged 5 months agoApache-2.0View on GitHub

Use when a founder needs to build or fix an investor pitch deck - when they say "help me make a pitch deck", "my deck isn't landing", "what slides do I need", "investors keep ghosting after the deck", or are about to send a deck to a VC/angel. Builds the investor narrative first, then a tight ~10-12 slide deck where every slide carries ONE message, pressure-tested with a skeptical-investor lens. Pair with investor-pipeline.

24 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use email-marketing, go-to-market and 5 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • claude-office-skillsSkill

    email-marketing

    Email marketing automation - campaign creation, sequence building, A/B testing, deliverability optimization, and analytics

    Also in 4 projects that use this

  • walternateSkill

    go-to-market

    Build a go-to-market (GTM) strategy for launching a product or entering a new market. Use when planning how to reach customers, position your product, choose channels, set pricing, and execute launch. Covers market entry strategy, customer segmentation, positioning, channel strategy, and GTM execution plan. Trigger on "go-to-market", "GTM strategy", "market entry", "launch strategy", "how to reach customers", "GTM plan".

    Also in 3 projects that use this

  • vijpatel7Skill

    cold-outreach

    Write highly effective cold emails and LinkedIn messages to recruiters, hiring managers, founders, and engineers at target companies. Based on Ben Lang's proven cold outreach framework (Next Play). Use when the user wants to: (1) write a cold email to someone at a company they want to work for, (2) craft LinkedIn messages or InMail to recruiters or hiring managers, (3) reach out about unadvertised positions, (4) follow up on outreach or applications, (5) network with founders or executives for job opportunities, (6) prepare an outreach campaign to multiple companies. Triggers on: cold email, outreach, reach out to, contact recruiter, email founder, write to hiring manager, job email, networking email, LinkedIn message, InMail.

    Also in 3 projects that use this

  • nicolas-webdevSkill

    landing-page

    Architecture and copywriting framework for high-converting landing pages. Use when building landing pages, sales pages, product pages, or lead capture pages. Follows a proven 8-section structure optimized for conversions.

    Also in 4 projects that use this

  • AnthropicSkill

    contract-review

    Lightweight NDA, MSA, and vendor contract review for SMBs without legal on staff. Reads contracts from local files, mail attachments (Gmail or M365), a connected file store (Google Drive or M365), or DocuSign envelopes; flags non-standard terms; explains risks in plain English; and outputs a marked-up redline as a separate DOCX. Use when the user says "review this contract," "what am I signing," "red flags," "flag any concerns," "check the payment terms," or uploads/forwards a contract or legal agreement.

    Also in 3 projects that use this

  • AnthropicSkill

    content-strategy

    Analyzes sales data from PayPal and QuickBooks to find top performers and slow movers, layers in seasonality, and produces a prioritized 30-day content brief: what to push, what offers to run, what to hold. Strategic output only — no calendars or assets. Use when the user asks what to post, wants a content plan, asks what's selling, or what to promote this month.

    Also in 4 projects that use this

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 22 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:

    Read each slide as the investor who *wants a reason to pass*.

    line 57
  2. Distinctive:

    A sourcing to-do list: every number (especially market size) marked sourced or needs-source, with where to get it.

    line 77

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

Pitch Deck

A pitch deck is not a document - it's an argument. First-time founders lose rounds because they build a feature catalogue instead of a story, and because each slide tries to say five things and therefore says nothing. Investors decide in minutes whether to keep reading; they are pattern-matching on a narrative, not grading your design. This skill builds the story first, then forces each slide down to a single message a tired partner could repeat from memory.

The method

Built on the Founder OS scaffold (High tier). Full frameworks in references/deck-narrative.md.

Step 1 - Fix the audience and the round before writing a word

A pre-seed angel deck and a Series A partner deck are different arguments. Pin down:

  • [STAGE] and round - what you're raising and what evidence that stage expects (an idea vs. a working product vs. real traction).
  • Audience - angel, pre-seed fund, Series A partner, accelerator. Each weights the slides differently (see references: "what investors actually look for per slide").
  • The job of the deck - get the meeting, or close the meeting. A teaser/forward deck and a presented deck are not the same artefact.

State these out loud. The rest of the deck is downstream of this decision.

Step 2 - Build the story arc before the slides

Slides are the delivery system; the arc is the product. Draft the spine in plain sentences:

Problem → Why now → Solution → Traction → Market → Business model → Team → Ask.

Each link should make the next feel inevitable. If "why now" is weak, the whole deck reads as "nice idea, no urgency." Write the arc as eight sentences first. If the sentences don't connect, no slide design will save it.

Step 3 - Draft each slide's ONE message

For every slide, write the single sentence the investor should walk away believing. The headline of the slide is that sentence - not "Market," but "A $X wedge into a $Y category growing Z% a year." Everything else on the slide exists only to support that headline. If a slide needs two messages, it's two slides. A draft is not a decision: get the messages down, then cut.

Step 4 - Pressure-test with the skeptical-investor lens

Read each slide as the investor who wants a reason to pass. For each, ask: "What's the obvious objection, and does the slide pre-empt it?" Market slides invite "is this number real or invented?" - so market-size figures must be sourced (top-down + bottom-up), never fabricated; if you don't have the source yet, flag it and tell the founder to get it before the meeting. Traction slides invite "is this growth or noise?" See references for the objection per slide.

Step 5 - Tighten to ~10-12 slides and one message each

Cut until removing anything would break the argument. Ten to twelve slides is the target; an appendix holds the deep cuts (detailed model, cohort data, competitor matrix) for the partner who asks. Batch all edits, then decide the final cut in one pass rather than fiddling slide by slide.

Output

  • The story arc in eight sentences (problem → ask), connected so each beat earns the next.
  • A slide-by-slide deck plan: for each slide, its ONE headline message + the 2-3 supporting points, in canonical order.
  • A skeptical-investor pass: the top objection per slide and how the slide answers it.
  • A sourcing to-do list: every number (especially market size) marked sourced or needs-source, with where to get it.
  • Next skill: investor-pipeline to run the raise.

Constraints

  • One message per slide. If you can't say the headline in a sentence, the slide isn't ready.
  • Never invent market numbers. Source top-down and bottom-up, cite it, or label it a placeholder to verify. A made-up TAM is the fastest way to lose a credible investor.
  • Story before slides; design last. A beautiful deck with no arc still fails.
  • Traction is not only revenue - early signal (usage, retention, waitlist, LOIs, pilots) counts; see references for options at pre-revenue stage.
  • Stay theme-agnostic; the founder supplies [STARTUP_NAME], [ONE_LINER], [ICP], [PROBLEM], the domain and the numbers - you supply the structure and the rigour.

Copy-paste version

Act as a sharp, kind pitch-deck coach for a first-time founder raising a round.
My startup: [STARTUP_NAME] - [ONE_LINER]. Stage/round: [STAGE]. Who I'm pitching: [investor type].
My customer: [ICP]. The problem: [PROBLEM]. My goal for this deck: [GOAL].
Help me:
1. Confirm what this stage/audience expects to see before we design anything.
2. Write my story arc in 8 sentences: problem -> why now -> solution -> traction -> market -> business model -> team -> ask. Make each beat set up the next.
3. For each of ~10-12 slides, give me the ONE headline message and the 2-3 points that support it.
4. Read it back as a skeptical investor looking for a reason to pass: name the top objection per slide and whether the slide answers it.
5. Flag every number - especially market size - that I must SOURCE (top-down + bottom-up), and tell me NOT to invent any. Mark anything unsourced as a placeholder to verify.
Keep it to ~10-12 slides, one message each, and put deep detail in an appendix.

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.