Write a Pitch Deck for Partnerships or Funding

You'll end up with: A compelling pitch deck with problem, solution, traction, and ask slides

Overview
40-60 min
Intermediate
Free to start
2 tools
Common mistake

The deck explains everything about the product instead of one memorable thesis and one ask. AI will happily generate 20 crowded slides—force a max slide count and one headline per slide in every prompt.

Before you start
  • Know whether the primary reader is a partner org or a funder
  • Have a one-line description of what you sell or build
  • Gather any proof you already have (users, revenue, logos, testimonials—even rough)
  • Open Claude and pick one deck tool (Google Slides, Gamma, or Canva)
1

Lock reader, context, and single ask

Decide who sees the deck and what one outcome you want (pilot, BD intro, investor meeting, etc.).

ClaudeFreeOpen Claude
Exact action

1. Go to claude.ai and start a new chat. 2. Paste this prompt (fill in the brackets): "I'm building a pitch deck. Answer these, then output two lines only: (a) Primary reader: partner organization | funder (investor/grant/accelerator) | mixed audience — pick one: [your choice] (b) Company/product one-liner: [one sentence] (c) Geography/stage: [e.g. US / early revenue / pre-seed] (d) The single next step I want from this deck (one sentence): [e.g. schedule a pilot scoping call] Now return: • Line 1 — DECK THESIS: ≤12 words naming WHO benefits and WHAT changes for them (no buzzwords). • Line 2 — PRIMARY ASK: one sentence I will repeat on the last slide." 3. If the thesis tries to cover product + vision + team in one line, ask Claude: "Strip adjectives and jargon until the thesis names who it's for and what outcome they get." 4. Do not add a second ask (no "also maybe…"). Iterate until you accept both lines.

You have one thesis line and one ask line you accept; there is no second "also maybe" ask.
The thesis still packs product + vision + team — ask Claude to drop adjectives until the thesis names who it's for and what changes for them.
2

Choose your slide spine (10–12 slides max)

Lock a fixed outline so later steps don't sprawl — classic storyline for partnerships or small funding.

ClaudeFreeOpen Claude
Exact action

1. In the same chat, paste: "I already have a deck thesis and primary ask. Generate a numbered list of slide TITLES ONLY (10–12 slides max). Use this order unless you have a compelling reason to swap two adjacent slides: 1. Title 2. Problem 3. Why now 4. Solution 5. How it works (product/demo) 6. Traction or validation 7. Market or opportunity (stay modest) 8. Business model OR partnership shape (pick what fits my reader) 9. Competition / differentiation 10. Team 11. The ask 12. Appendix / contact (optional — merge into 11 if we need to stay at 10 slides) Rules: one headline slot per slide title — no sub-bullets in this list. If I'd exceed 12 slides, merge Appendix into Contact or drop Appendix." 2. Count the titles. If there are more than 12, ask Claude to merge until ≤12. 3. Confirm "The ask" is the last substantive slide before appendix/contact.

You have a paste-ready outline with ≤12 titles; the Ask is the last substantive slide before any appendix.
3

Draft core story slides (problem through solution)

Fill the middle of the deck with evidence and specificity — no filler. Use placeholders where data is missing.

ClaudeFreeOpen Claude
Exact action

1. In the same chat, paste your slide spine from step 2. 2. List any numbers, quotes, or facts you already have (revenue, users, logos, pilots). Say explicitly: "Do not invent statistics — use [NEED: metric] for gaps." 3. For slides 2–7 in your spine (adjust numbers to match — typically Problem through How it works), ask Claude for EACH slide: "For slide [N] — [title]: • Headline: ≤10 words • Bullets: 3 max — each must be a claim you could defend in a meeting • Optional visual: one line (diagram, screenshot, simple chart) Use [NEED: metric] / [NEED: quote] / [NEED: logo] instead of making up proof." 4. If any bullet is vague ("great UX", "seamless"), ask Claude to rewrite with an evidence type: metric, customer quote, or concrete workflow step.

Each of those slides has one headline; bullets are defensible claims; invented stats are absent or clearly marked with brackets.
Bullets are vague ("great UX", "best-in-class") — demand evidence types: metric, customer quote, or workflow step in your follow-up prompt.
4

Size traction, market, and differentiation honestly

Right-size credibility for partnerships vs funding; avoid a delusional top-down TAM slide.

ClaudeFreeOpen Claude
Exact action

1. Identify which slide numbers are Traction, Market/opportunity, and Competition in your spine. 2. Paste: "For my Traction, Market, and Competition slides, draft three credibility tiers each: • Tier A — no hard data yet (honest language, momentum story without fake numbers) • Tier B — some data (usage, revenue range, LOIs, pilots) • Tier C — strong data (repeatable metrics, named customers) I'll tell you which tier to use per slide. For Market: if I'm early-stage, use bottom-up logic (reachable customers × realistic conversion, assumptions stated). Do not use a giant irrelevant SAM or '$50B market' unless I'm truly going after that." 3. Choose Tier A/B/C per slide based on what you actually have. 4. For Market, reject any slide that only cites total addressable market from an industry report — ask Claude to rewrite bottom-up.

Each of those slides uses a tier that matches your evidence; the market slide doesn't rely on an irrelevant giant SAM.
5

Add team, roadmap, and the Ask (partner vs funding)

Build trust and make a concrete request — branch prompts for partnership vs funder readers.

ClaudeFreeOpen Claude
Exact action

1. Team slide: Ask Claude for bullets — each person: name, role, one proof point (years in domain, past employer, shipped product, relevant credential). No paragraph bios. 2. Roadmap slide: "Give me 3 milestones for the next 90–180 days. Each milestone is an outcome (not 'hire engineers') — e.g. '10 paying pilots', 'integration live with X'." 3. Ask slide — pick ONE path: If PRIMARY READER is a PARTNER, paste: "Draft the Ask slide: pilot scope, what you need from them (API access, co-marketing, intro path), success criteria, suggested timeline, what happens in the first 2 weeks." If PRIMARY READER is a FUNDER, paste: "Draft the Ask slide: amount or grant range (or 'raising up to $X'), runway months implied, use of funds in 3–4 buckets (e.g. product, GTM, hiring), what milestone unlocks next round." 4. End with one sentence: what happens next week (calendar hold, data room, trial kickoff).

The Ask slide states what you want, what they get, and what happens in the next week (meeting, data room, trial).
6

Build the deck, add speaker notes, and rehearse

Move from outline to a real file; tighten what you'll say out loud.

Google SlidesFreeOpen Google Slides
Exact action

1. Open Google Slides (slides.google.com) or Gamma (gamma.app) — pick one tool and stay in it for this deck. 2. Create a new deck from a simple template (or Gamma's pitch layout). Paste each headline and bullet from Claude slide-by-slide. 3. For every [NEED: …] placeholder, add a comment or sticky on that slide so you don't forget to fill it before sending. 4. Back in Claude, paste: "Turn my bullets for these 5 slides into speaker notes: opening/title, problem, solution, traction, ask. Each script under 90 words, conversational, no new claims not on the slide." 5. Copy speaker notes into the deck's notes field for those slides. 6. Start a 5-minute timer and present out loud. Any slide you skip or rush — merge it into another or cut it.

A deck file exists; the Ask slide matches your primary ask from step 1; speaker notes exist for title, problem, solution, traction, and ask.

All done!

You now have: A compelling pitch deck with problem, solution, traction, and ask slides

Explore more guides

Want this workflow built for your business?

Book a free audit