agentleFS
peterbamuhigirepeterbamuhigire/business-plan-skills/skills/meta-pitch/pitch-deck/SKILL.md

pitch-deck

Skill4 starsChanged 19 days agoMITView on GitHub

Use when the user asks for a pitch deck, investor deck, bank presentation, or live proposal deck. Use pitch-deck for end-to-end deck orchestration.

26 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 6 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

Show its rules and text

We split this skill into the rules it gives an agent

17 rules. 0 are common, 13 are distinctive, and 4 are very specific to this project.

  • 0

    Common

    Most of the 23 edited versions we read keep these.

  • 13

    Distinctive

    This author's own choices. Worth a look.

  • 4

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Use this skill as the orchestration layer for live presentation work.

    line 16
  2. Distinctive:

    Use when the user asks for a pitch deck, investor deck, bank presentation, or live proposal deck.

    line 20
  3. Distinctive:

    Use when both deck structure and spoken delivery matter.

    line 21
  4. Distinctive:

    Use when a completed or near-complete plan must be converted into a persuasive presentation workflow.

    line 22
  5. Distinctive:

    Do not use if the task is only deck design polish or only speaking rehearsal.

    line 26
  6. Distinctive:

    Do not use before the core business case is stable enough to present.

    line 27
  7. Distinctive:

    Do not treat this as a substitute for fixing weak underlying strategy or numbers.

    line 28
  8. Very specific:

    Run the framing and message strategy through meta-pitch-preparation.

    line 48
  9. Distinctive:

    Do NOT invoke this skill if:

    line 111
  10. Distinctive:

    Before any deck work, confirm three things:

    line 122
  11. Distinctive:

    Do not move to Phase 3 until the pitch strategy is clear.

    line 161
  12. Distinctive:

    Assertion headlines: every slide title is a complete sentence stating a conclusion, not a label ("Revenue" "Revenue grows 3× in 24 months")

    line 195
  13. Distinctive:

    One message per slide: if there are two messages, there are two slides

    line 196
  14. Very specific:

    Financial consistency: every number on every slide must match the business plan exactly (see meta-due-diligence Mode C)

    line 200
  15. Distinctive:

    Before the pitch deck is declared final, verify:

    line 269
  16. Very specific:

    Run meta-bankability-scoring (Bank Loan Readiness Mode) before any bank or DFI pitch to verify the deck does not contradict CAMPARI …

    line 281
  17. Distinctive:

    Apply consistency check: before declaring the pitch deck final

    line 291

“Common” is measured: kept by at least 6 in 10 of the 23 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
<!-- dual-compat-start -->

Pitch Deck Skill

Overview

Use this skill as the orchestration layer for live presentation work. It sequences meta-pitch-preparation and meta-presentation-design so the deck, spoken frame, and Q&A preparation stay aligned.

Use When

  • Use when the user asks for a pitch deck, investor deck, bank presentation, or live proposal deck.
  • Use when both deck structure and spoken delivery matter.
  • Use when a completed or near-complete plan must be converted into a persuasive presentation workflow.

Do Not Use When

  • Do not use if the task is only deck design polish or only speaking rehearsal; call the more specific meta-skill directly.
  • Do not use before the core business case is stable enough to present.
  • Do not treat this as a substitute for fixing weak underlying strategy or numbers.
  • Route to pitch-deck instead when the task requires end-to-end deck orchestration.

Required Inputs

InputSource / providerRequired?If absent
Pitch Deck brief and decision audienceClient, plan owner, or approved project filesYesStop before making a recommendation; state the missing decision context.
Claims, assumptions, and supporting evidenceSource register, model, research notes, interviews, or operating recordsYesSeparate known facts from assumptions and return a qualified gap list.
Authority and delivery constraintsRequesting owner and repository instructionsYesRemain read-only and produce a draft or review only.
  • Audience type and presentation context
  • Core business-plan sections or equivalent business-case material
  • Funding ask, commercial logic, and key supporting evidence
  • Any time, slide-count, or format constraints

Workflow

  1. Confirm the pitch type and the decision the audience must make.
  2. Run the framing and message strategy through meta-pitch-preparation.
  3. Translate that frame into slides and delivery structure through meta-presentation-design.
  4. Reconcile the deck with the written plan and the final ask.
  5. Stress-test likely objections and Q&A gaps.
  6. Flag any weakness in the underlying case that presentation work cannot solve.

Decision, stop, and recovery controls

  • Decision point: confirm that the requested output is the presentation-ready deck package and that the decision concerns which plan claims earn space in the deck and delivery programme.
  • Stop condition: halt the affected conclusion if required evidence is missing (completed plan, evidence register, pitch audience, and time limit) or if the work could lead to this identified risk: losing the funding decision between slide design and speaker coaching.
  • Recovery: obtain the missing record or reviewer, repeat the affected check, and update the exception record before release.

Quality Bar

  • The deck and spoken narrative reinforce the same core argument.
  • Slide structure matches audience psychology and time constraints.
  • The ask is clear, credible, and easy to repeat.
  • Presentation polish does not outrun the quality of the business case.

Anti-Patterns

  • Designing slides before deciding what the audience needs to believe.
  • Treating the deck as a condensed business plan.
  • Hiding weak economics behind visual polish.
  • Mixing investor, lender, and donor logic in the same presentation without intent.
  • Treating a generic pitch deck template as a conclusion. Correction: tie each choice to the named audience, evidence, and operating constraint.
  • Applying the wrong neighbouring route to pitch deck. Correction: confirm the decision and route to the named neighbour before analysis.
  • Treating an assumption as verified evidence. Correction: label it, cite its source or owner, and assign a verification action.
  • Recommending action without a decision threshold. Correction: state the measurable acceptance condition and review trigger.
  • Recording an unavailable check as passed. Correction: mark it not assessed and state the consequence for the decision.
  • Mutating or publishing during an analysis-only task. Correction: remain read-only until the owner gives explicit authority.

Outputs

ArtefactConsumerObservable acceptance condition
Pitch Deck deliverableNamed decision-maker or plan authorThe recommended choice, assumptions, countercase, and next action are explicit.
Evidence and exception registerReviewer, funder, board, or implementation ownerEvery load-bearing claim is sourced or labelled as an assumption; missing checks are not shown as passes.
  • A coordinated pitch-deck workflow and output path
  • Clear handoffs to the two underlying meta-skills
  • Open questions and presentation risks to address before pitch day

The pitch deck is the bridge between a written business plan and a live investment or lending decision. This skill runs two meta-skills in sequence:

  1. meta-pitch-preparation establishes what to say and how to frame it (psychology, structure, Q&A)
  2. meta-presentation-design builds the deck and trains delivery (slides, narrative, rehearsal)

Neither skill alone is sufficient. A psychologically sharp pitch delivered from a weak deck loses. A beautiful deck presented by someone who has not prepared the frame loses worse.


When to Use This Skill

Invoke pitch-deck when:

  • A client has a completed (or substantially complete) business plan and needs a pitch deck for investors, a bank, or a client
  • You are preparing someone for a live funding presentation or sales pitch
  • You have been asked to "create a pitch deck" without further specification this skill handles the full workflow
  • The business plan has a funding request section (Section 11) that must be presented live

Do NOT invoke this skill if:

  • The client only wants to improve their speaking skills (use meta-presentation-design Mode B directly)
  • The client only wants to stress-test their investor Q&A (use meta-pitch-preparation Mode A directly)
  • The client is preparing a written proposal with no live presentation (use proposal-architect)

Workflow: Four-Phase Execution

Phase 1 Briefing (5 minutes)

Before any deck work, confirm three things:

1. What is the pitch type?
   [ ] Equity investor (angel / VC / PE / impact)
   [ ] Bank / DFI loan presentation
   [ ] Client proposal presentation
   [ ] Grant committee
   [ ] Board / management
   [ ] Government / public tender

2. What is the deadline?
   [ ] Same day / urgent
   [ ] Within 1 week
   [ ] 2–4 weeks (full preparation possible)

3. What materials exist?
   [ ] Complete business plan (all 15 sections)
   [ ] Partial plan (specify sections available)
   [ ] Financial model only
   [ ] Rough notes / verbal brief only

The pitch type determines slide count, structure, and tone. The deadline determines how much preparation depth is realistic. The materials determine what must be synthesised vs. what can be drawn directly.


Phase 2 Pitch Strategy (invoke meta-pitch-preparation)

Run meta-pitch-preparation Mode A (self-prep) or Mode B (client coaching) before opening any slide tool.

Key outputs required from Phase 2:

  • The One Ask exact amount (UGX/USD), exact terms, exact use of funds
  • The Frame is this pitched from prize frame or status frame? Who has the power and why?
  • The Hook the 60-second opening that creates urgency and curiosity
  • The STRONG skeleton the six narrative stages mapped to this specific pitch type
  • The 10 hardest Q&A written out with bridge scripts
  • Financial claims verified DSCR, collateral coverage, valuation, revenue projections cross-checked against the plan

Do not move to Phase 3 until the pitch strategy is clear. A deck built on an unclear frame will be redesigned after Phase 3 double the work.


Phase 3 Deck Construction (invoke meta-presentation-design)

Run meta-presentation-design Mode A (deck design) using the Phase 2 outputs as input.

Master Slide Template (13 slides equity/bank default)

SlideAssertion Headline FormatSource in Plan
1 Title[Business Name] [One-line value proposition]01 Executive Summary
2 The Problem[X% of target customers] face [specific pain] with no adequate solution04 Market Analysis / 05 Target Market
3 The Solution[Business Name] solves this by [mechanism] delivering [measurable outcome]03 Products & Services
4 Market SizeThe [addressable market] is [UGX/USD X] and growing at [X%] per year04 Market Analysis
5 Business ModelWe earn [UGX X] per [unit/customer] through [revenue mechanism]03 / 07 Marketing
6 TractionIn [period], we achieved [metric]: [customers / revenue / units / pilots]02 Company Overview
7 CompetitionWe win against [competitors] on [2–3 specific dimensions]06 Competitive Analysis
8 Go-to-MarketWe reach [target customer] through [channel] at [CAC] [conversion rate] close rate07 Marketing & Sales
9 Team[Name] brings [X years] of [relevant experience] this team has done this before09 Management Team
10 FinancialsRevenue reaches [UGX X] by Year 3; EBITDA margin [X%]; break-even Month [X]10 Financial Projections
11 The AskWe are raising [UGX X] as a [loan / equity / grant] to [specific use]11 Funding Request
12 Use of Funds[Visual: 4–5 line items with % breakdown matching 11 exactly]11 Funding Request
13 The Close[Investor/lender name] + [Business Name] = [specific shared outcome]. Here is the next step.01 Executive Summary

Slide count adjustments by pitch type:

  • Equity investor: 10–12 slides (drop Slide 12; integrate use of funds into Slide 11)
  • Bank / DFI: 13–15 slides (add DSCR slide; add collateral slide)
  • Grant committee: 12–14 slides (replace Traction with Theory of Change; add beneficiary slide)
  • Client proposal: 15–20 slides (expand Solution and Go-to-Market; add delivery timeline)

Slide Design Rules (non-negotiable)

  1. Assertion headlines every slide title is a complete sentence stating a conclusion, not a label ("Revenue" "Revenue grows 3× in 24 months")
  2. One message per slide if there are two messages, there are two slides
  3. No bullet forests maximum 3 bullets; prefer visuals, charts, or single statements
  4. Chart titles are conclusions "Monthly Revenue (UGX)" "Revenue crosses break-even in Month 14"
  5. The 3-second test the key message of every slide must be readable in 3 seconds without reading the body
  6. Financial consistency every number on every slide must match the business plan exactly (see meta-due-diligence Mode C)

Phase 4 Delivery Preparation (invoke meta-presentation-design Mode B)

Run delivery coaching after the deck is complete, not before.

Minimum preparation standard before any live pitch:

RunFormatPurpose
Run 1Read aloud, alone, with deckHear the words for the first time
Run 2Present standing, deck on screenFull physical simulation
Run 3Full run with coach/colleagueExternal feedback on pacing, frame, confidence
Run 4Q&A simulation onlyDrill the 10 hardest questions with bridges
Run 5Full dress rehearsalTimed, complete, no stops
Run 6 (day of)Opening + Close + Q&A warm-upActivate the material; remove nerves

Critical delivery checkpoints:

  • Can the presenter state the ask (amount, terms, next step) without looking at the slides? If not, more rehearsal.
  • Does the opening create a question in the audience's mind within 30 seconds? If not, rewrite the hook.
  • Does the close make the next step feel inevitable not a request, but a logical conclusion? If not, rewrite the close.

Pitch Deck by Audience Quick-Reference

Equity Investor Deck

Frame: Prize frame you are selective about investors, not desperate for capital. The investor earns the right to participate.

Opening hook: A striking statistic about the problem, a customer story, or a counterintuitive claim that makes the investor lean forward.

The ask slide must include: Amount pre-money valuation % equity offered use of funds (3 lines) runway achieved key milestone unlocked.

Hardest Q&A to prepare: "Why you?" / "Why now?" / "What's your exit?" / "What happens if revenue is 50% below plan?" / "Who else is in the round?"

Bank / DFI Loan Deck

Frame: Evidence frame you are the safe, qualified choice. Every claim is verifiable. Every risk is identified and mitigated.

Opening hook: The business in one sentence, followed immediately by DSCR and collateral coverage. Credit officers form their view in the first 60 seconds.

The ask slide must include: Loan amount loan type proposed term grace period repayment source DSCR (Year 1, 2, 3) collateral value + coverage ratio.

Hardest Q&A to prepare: "What if sales are 30% lower?" / "What is your fallback repayment source?" / "Who guarantees if the business fails?" / "Why this loan amount and not less?" / "What experience do you have in this sector?"

Grant / Donor Deck

Frame: Impact frame you are the most credible implementer of their programme objectives. Every slide answers "will this advance our mission?"

Opening hook: A human story (beneficiary profile) that makes the problem concrete and personal.

The ask slide must include: Grant amount project period beneficiary count Theory of Change (one sentence) M&E framework (one line) reporting obligations accepted.

Hardest Q&A to prepare: "How will you measure impact?" / "What happens after the grant period?" / "Why not use an established NGO?" / "Have you implemented a similar programme before?"


Consistency Check Before Submission

This is the post-draft check. The pre-draft gate the Source-of-Truth Register that traction, pricing, raise size, use of funds, bios, and milestones should already have been locked against during intake lives in 00-client-intake/SKILL.md. If that register was skipped, expect this checklist to surface conflicts that now require rework rather than confirmation.

Before the pitch deck is declared final, verify:

  • Every financial figure on slides matches the business plan exactly
  • The ask on Slide 11 matches 11 of the plan exactly (amount, terms, use of funds)
  • Revenue projections on Slide 10 match 10 exactly (Year 1, 2, 3)
  • Market size on Slide 4 matches 04 exactly (TAM/SAM/SOM)
  • Team bios on Slide 9 are consistent with 09
  • Risk acknowledgement is present (investors distrust plans with no risks)
  • Slide count is appropriate for pitch type (see table above)
  • All slides pass the 3-second test
  • Delivery has been rehearsed minimum 5 times

Run meta-bankability-scoring (Bank Loan Readiness Mode) before any bank or DFI pitch to verify the deck does not contradict CAMPARI criteria.


Generation Process

  1. Confirm pitch type, deadline, and available materials (Phase 1 5 minutes)
  2. Run meta-pitch-preparation to establish frame, hook, STRONG narrative, and Q&A prep (Phase 2)
  3. Build deck using the master template adjusted for pitch type; apply slide design rules throughout (Phase 3)
  4. Run meta-presentation-design Mode B delivery coaching; execute minimum 5-run rehearsal protocol (Phase 4)
  5. Apply consistency check before declaring the pitch deck final

References

  • Pitch strategy and frame control: See meta-pitch-preparation/SKILL.md for STRONG method, Klaff frame control, McGowan Hook-Meat-Payoff, Q&A preparation, and the six-run rehearsal protocol
  • Deck design and delivery: See meta-presentation-design/SKILL.md for the full 13-slide master template, assertion-evidence standard, Duarte Sparkline, visual design rules, and the four-dimension deck audit checklist
  • Financial verification: See 11-funding-request/SKILL.md for DSCR calculation, collateral coverage, and use-of-funds table that must be reflected exactly on the pitch slides
  • Consistency audit: See meta-bankability-scoring/references/consistency-audit.md to verify pitch figures against the business plan before any live presentation
  • DD readiness: See meta-due-diligence/SKILL.md Mode C for pre-pitch data room audit if an investor asks for due diligence materials, the data room must be ready before the pitch, not after
  • Pyramid structure for the narrative: See 01-executive-summary/references/pyramid-principle.md for the SCQA framework that governs the overall pitch storyline
  • Pitch diagrams: See ../../pipeline/00-plan-assembly/references/plan-figures.md to render the money-flow or solution diagram at slide size through the SRS engine hand-off

Evidence Produced

EvidenceFormatAcceptance condition
Presentation-ready deck package decision traceSources, calculations, assumptions, countercase, and selected actionA reviewer can trace the selected action and rejected alternatives to the cited inputs.
Exception recordFailed and not-assessed checks with owner and due actionThe register exposes every unresolved exception that could lead to losing the funding decision between slide design and speaker coaching.

Capability and Permission Boundaries

Read supplied records and use non-mutating checks to produce the presentation-ready deck package; assembling the authorised deck and rehearsal pack is permitted when requested. Do not publish, contact third parties, alter live systems, commit funds, or claim legal, tax, audit, valuation, ESG, or investment assurance without the owner's explicit authorisation and the appropriate reviewer.

Degraded Mode

If completed plan, evidence register, pitch audience, and time limit cannot be obtained, return a qualified presentation-ready deck package covering only the checks that remain supportable. Leave this decision unresolved: which plan claims earn space in the deck and delivery programme. Record the evidence owner and next check; an inaccessible source, tool, or reviewer is never a pass.

Decision Rules

Decision conditionActionFailure or risk avoided
Evidence is sufficient to decide: which plan claims earn space in the deck and delivery programmeRecord the conclusion, source trail, owner, and review trigger in the presentation-ready deck package.Risk of losing the funding decision between slide design and speaker coaching
Material evidence conflicts or remains uncertainBuild a short and full narrative sequence from the same approved claims, then choose the version that fits the meeting time without dropping the ask.Selecting an option without resolving the decision-relevant uncertainty
Required evidence is missing: completed plan, evidence register, pitch audience, and time limitMark the decision on which plan claims earn space in the deck and delivery programme not assessed in the presentation-ready deck package, and send it to the presentation owner and intended speaker.Otherwise, the work risks losing the funding decision between slide design and speaker coaching

Quality Standards

Accept the presentation-ready deck package only when evidence is sufficient for this decision: which plan claims earn space in the deck and delivery programme. Assumptions and countercases remain visible, calculations and cross-references reconcile, and the reviewer can see how the recommendation addresses the risk of losing the funding decision between slide design and speaker coaching.

Worked Example

A 40-page plan must become a 12-minute DFI presentation. Keep the development outcome, operating proof, financing need, and repayment logic in the core deck; move diligence schedules to the appendix and rehearse the handoff.

<!-- dual-compat-end -->

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.