Skip to main content

๐Ÿ“Š Lesson 7.1: Project โ€” A Pitch Deck

This is where it all comes together. Over six modules you've learned to build, structure, design, animate, share, and connect your work โ€” now you'll spend one focused session building a real pitch deck end to end. A pitch is the highest-stakes deck most people ever make: you have a few minutes to make someone believe in an idea. By the end you'll have a tight ~10-slide deck, built on a theme, one idea per slide, with speaker notes carrying the words you'll actually say.

๐Ÿ“š What You'll Learn

By the end of this lesson, you will be able to:

  • Lay out the canonical pitch structure โ€” Title, Problem, Solution, Product, Market, Traction, Business model, Team, and The Ask
  • Apply a theme and slide master so all ten slides feel like one confident deck
  • Hold the discipline of one idea per slide and minimal on-slide text
  • Build a strong title slide and a simple diagram that carries your "how it works"
  • Write speaker notes that hold your pitch, so the slides stay a visual aid
  • Assemble and rehearse a complete pitch deck you could actually deliver

โฑ๏ธ Estimated Time: 70 minutes

๐ŸŽฏ Project: Build a complete ~10-slide pitch deck โ€” for a real idea or a chosen scenario โ€” applying the theme, structure, one-idea-per-slide, a diagram, and speaker notes you've learned across the whole course.

In This Lesson

๐ŸŽค What a Pitch Deck Is Really For

A pitch deck isn't a report and it isn't a brochure. Its one job is to make an audience โ€” an investor, a boss, a grant committee, a client โ€” believe an idea is worth backing in the short window of a live talk. Everything about the way we build it flows from that. There are exactly three things a good pitch does: it makes the audience feel a real problem, it shows a solution they can picture working, and it makes a specific ask that's easy to say yes to.

That's why the deck is deliberately lean. A pitch deck is the ultimate example of our through-line โ€” Message โ†’ Structure โ†’ Design โ€” under pressure. The message has to be sharp because attention is short. The structure has to be a story, not a list. And the design has to get out of the way so the idea shines. The single biggest mistake people make is treating the slides as a script: cramming every word they plan to say onto the screen, then reading it aloud. The audience can read faster than you can talk, so they tune you out. Remember the course mantra โ€” the slide is a visual aid, not your script. The detail lives in your speaker notes and in your mouth.

๐Ÿง  Mindset

You are not "making slides." You are building the visual half of a short, persuasive story you'll tell. Picture yourself standing in front of the room. Each slide should be a single image or headline that supports the sentence coming out of your mouth at that moment. If a slide can't be understood in three seconds, it's doing your job for you โ€” and doing it worse than you would. Keep that picture in mind and every design decision gets easier.

๐Ÿงฑ The Canonical Pitch Structure

Over thousands of pitches, a structure has emerged that audiences expect and that reliably tells a convincing story. You don't have to follow it slavishly, but it's the safe backbone โ€” deviate on purpose, not by accident. Here is the canonical sequence and the one job each slide does.

# Slide The one job it does
1TitleName, one-line promise, and a strong first impression โ€” set the tone
2ProblemMake the audience feel a real, painful, specific problem
3SolutionYour one-sentence answer to that exact problem
4Product / How it worksShow it working โ€” a simple diagram or a screenshot, not a spec sheet
5Market / Why nowHow big the opportunity is and why this moment is the right one
6Traction / ProofEvidence it's already working โ€” users, revenue, pilots, results
7Business modelHow it makes money (or sustains itself) in one clear line
8TeamWhy you are the ones to pull this off
9The AskExactly what you want โ€” money, a decision, a partnership โ€” and what it buys

Nine slots, plus an optional closing "thank you / contact" slide, lands you at the classic ~10-slide deck. Notice the shape of the story: tension (problem) โ†’ relief (solution and product) โ†’ opportunity (market and proof) โ†’ credibility (model and team) โ†’ action (the ask). That arc is doing more persuasive work than any single fact on any single slide.

๐Ÿ’ก Not every pitch needs all nine

An internal pitch to your boss might drop "Market" and "Business model" and lean hard on Problem, Solution, and Ask. A grant pitch might expand "Traction" into impact evidence. Use the canonical list as a checklist of questions the audience will silently ask, then answer the ones that matter for your situation. Cut ruthlessly โ€” a tight seven-slide deck beats a bloated fifteen.

๐ŸŒ€ The Pitch Arc, Slide by Slide

Here's the whole sequence as a single arc so you can feel how the slides hand off to one another. Each box is one slide; each doing exactly one job before passing the audience to the next.

graph LR A["1 ยท Title
the promise"] --> B["2 ยท Problem
feel the pain"] B --> C["3 ยท Solution
the answer"] C --> D["4 ยท Product
show it working"] D --> E["5 ยท Market & why now
the opportunity"] E --> F["6 ยท Traction
proof it works"] F --> G["7 ยท Model
how it sustains"] G --> H["8 ยท Team
why you"] H --> I["9 ยท The Ask
make it easy to say yes"]

Read left to right, that's a complete persuasive story: here's a real problem, here's our answer, here's it working, here's how big and why now, here's proof, here's how it lasts, here's why we're the team, and here's exactly what we want from you. If you can say that arc out loud in two minutes without the deck, your deck will be strong โ€” because the slides are just illustrating a story you already own.

โš ๏ธ Watch Out

The most common failure isn't a weak slide โ€” it's a broken arc. Decks that jump into product features before establishing the problem lose the room, because nobody cares how something works until they care that it works on a problem they feel. Build the Problem and Solution slides first and get them genuinely sharp; the rest of the deck leans on them.

๐ŸŽจ Design & the One-Idea-Per-Slide Rule

You already have the design skills โ€” this project is about applying them with discipline. Three habits do almost all the work of making a pitch deck look like it came from a confident, credible team.

Design through the theme, not by hand

Pick or build a theme once at the start, and edit the slide master so your title font, colors, and logo placement are set in a single place. Then every new slide inherits that look automatically. This is the habit we've built all course: design through the theme and slide master, don't hand-decorate each slide. A pitch deck that's visually consistent reads as "these people have their act together" before you've said a word. Two fonts, a tight palette of two or three colors, and generous whitespace is plenty.

One idea per slide

This is the rule that separates decks that persuade from decks that exhaust. Each slide carries a single message, expressed as a short headline plus one supporting image, number, or short phrase โ€” not a paragraph. If a slide is trying to make two points, split it into two slides. Slides are free; attention isn't.

Show, don't spec

Your "How it works" slide should be a picture โ€” a simple three-box diagram, a screenshot, a photo of the thing in use โ€” not a bulleted feature list. A diagram you build with a few shapes and arrows (exactly the skills from Module 4) will out-persuade any wall of text. Big numbers on the Traction slide. A single clear sentence on the Ask.

โœ… Pro Tip

Do a "squint test" on every slide: lean back and half-close your eyes. You should still be able to tell what each slide is about from the headline and the dominant image alone. If you have to read body text to know what a slide says, there's too much text โ€” move the detail into your speaker notes, where it belongs.

๐Ÿ—ฃ๏ธ Notes, Rehearsal & Delivery

The slides are only half the pitch. The other half is you, talking โ€” and that half lives in your speaker notes. For each slide, write in the notes pane the two or three sentences you'll actually say when it's on screen. This does three things: it keeps the slide itself clean (the words are in the notes, not on the slide), it gives you presenter view during the real pitch so you never freeze, and it forces you to check that each slide really has one clear point.

Then rehearse out loud, ideally with presenter view showing your notes and a timer. Time yourself: a ~10-slide pitch usually runs three to six minutes. Rehearsing reveals the slides that don't hand off cleanly and the sentences that don't land, in a way silent editing never will. If you'll present remotely, practice sharing your screen; if in a room, practice with the actual clicker or keyboard. The goal is that on the day, the deck feels like a familiar path you've walked before.

๐Ÿ’ก Slides vs PowerPoint for pitching

For a live pitch, Google Slides has a real edge: you can send a share link so the room follows along or reviews it later, co-founders can polish the deck together the night before, and you can present from any computer by signing in โ€” no "the file's on my other laptop" panic. PowerPoint's advantage is deeper motion (Morph) and richer effects, which a clean pitch rarely needs. Whichever you use, the structure and delivery habits here transfer directly.

๐ŸŽฏ Project: Build Your Pitch Deck

Time to build the real thing. You'll produce a complete ~10-slide pitch deck from a blank deck to a rehearsed presentation. Use a real idea if you have one (a business, a project proposal, a club you want to start); if not, pick a scenario you can picture โ€” a food truck, a neighborhood app, a school program. Work through the steps in order; the times are a guide, not a race.

๐Ÿ‹๏ธ Build a complete pitch deck

Objective: A rehearsed ~10-slide pitch deck, built on a theme, one idea per slide, with a diagram and full speaker notes.

Instructions (about 55 minutes):

  1. (5 min) Open a new deck at slides.google.com. Write your pitch in one sentence at the top of a scratch slide: "We help ___ do ___ by ___, and we're asking for ___." This is your compass for everything that follows.
  2. (6 min) Choose a theme, then open Slide โ†’ Edit theme (in some versions View โ†’ Theme builder โ€” the slide master) and set your title font, a palette of two or three colors, and where any logo/name sits. Design here once so every slide inherits it.
  3. (6 min) Build a strong Title slide: your name/idea, a one-line promise, nothing else. Make it feel confident and uncluttered โ€” this is the audience's first impression.
  4. (6 min) Build the Problem and Solution slides. Problem: one sharp headline that makes the pain feel real. Solution: your one-sentence answer. Keep each to a headline plus at most one image or phrase.
  5. (7 min) Build the Product / How it works slide as a diagram โ€” three or four shapes and arrows showing the flow (e.g. Input โ†’ Your product โ†’ Result). Do not list features.
  6. (7 min) Add Market / Why now, Traction / Proof, and Business model slides. Use big numbers and short phrases, one idea each.
  7. (5 min) Add the Team slide (a photo or name per person plus one credibility line each) and a closing Ask slide with one crisp sentence: exactly what you want and what it enables.
  8. (8 min) Go slide by slide and write speaker notes โ€” the two or three sentences you'll say on each. As you do, delete any on-slide text that belongs in the notes instead.
  9. (5 min) Rehearse once out loud using presenter view and a timer. Note the two roughest transitions, fix them, and save. (It saves itself, but confirm the title and sharing are how you want them.)
๐Ÿ’ก Hint โ€” a ready-to-fill slide outline
My Pitch Deck (~10 slides)

1. Title        โ€” Name + one-line promise
2. Problem      โ€” "Today, ___ struggle to ___."
3. Solution     โ€” "We ___, so they can ___."
4. Product      โ€” diagram: Input -> Us -> Result
5. Market       โ€” how big + why now (one number, one reason)
6. Traction     โ€” proof: users / revenue / pilot / result
7. Model        โ€” how it makes money / sustains, one line
8. Team         โ€” who we are + why us (one line each)
9. The Ask      โ€” "We're asking for ___ to ___."
10. Thanks      โ€” contact + a share link

Compass sentence (write first):
"We help ___ do ___ by ___, and we're asking for ___."

Fill the compass sentence first โ€” if you can't, the pitch isn't clear yet, and that's the most valuable thing to discover before you build ten slides on it.

โœ… Project Completion Checklist

  • The deck has ~10 slides following the canonical arc (Title โ†’ Ask)
  • Every slide is built on one theme/master โ€” the look is consistent
  • Each slide carries a single idea; no slide is a wall of text
  • The "How it works" slide is a diagram or image, not a feature list
  • Every slide has speaker notes with what you'll actually say
  • You rehearsed it out loud once, timed, and fixed the roughest transitions

๐ŸŽฏ Quick Quiz

Question 1: Why should the detailed sentences of your pitch live in the speaker notes rather than on the slides?

Question 2: In the canonical pitch arc, why do we place the Problem slide before the Product slide?

โญ Best Practices for Pitch Decks

โœ… Do's

  • Nail the Problem and Solution first. They're the load-bearing wall; the rest of the deck leans on them.
  • Design once through the master. Consistency signals credibility, and it's the fast way to get there.
  • Rehearse out loud with a timer. A pitch is a performance; the deck only works when you know the words.

โŒ Don'ts

  • Don't put your script on the slides. That's the number-one pitch killer. Notes hold the words.
  • Don't lead with features. Show the problem, then the working product โ€” as a picture, not a spec.
  • Don't pad the deck. A tight seven or ten slides beats fifteen; cut anything that doesn't earn its slot.

๐Ÿ’ก Pro Tips

  • Make the Ask a single, specific sentence. Vague asks get vague answers.
  • End with your name, contact, and a share link โ€” so the deck keeps working after you sit down.

๐Ÿ““ Learning Journal

Keep a learning journal as you work through this course โ€” a separate document, a note, or even a slide at the end of the deck you're building. After each lesson, take a few minutes to write down:

  • Key concepts you learned
  • Techniques that clicked for you
  • Questions or confusion points to revisit
  • Ideas you want to try in your own decks
  • Your progress and feelings about learning this โ€” including where your confidence grew

โœ๏ธ This lesson's prompt: Which slide of your pitch was hardest to make simple, and why? What did you end up moving off the slide and into your speaker notes? After rehearsing out loud once, what surprised you about how the deck actually flows when you're talking? Note how it felt to build a complete, real deck end to end โ€” that's a milestone worth marking.

๐Ÿ“ Lesson Summary

๐ŸŽ“ Key Takeaways

  • A pitch deck exists to make an audience believe an idea is worth backing in a short live talk โ€” lean, persuasive, story-shaped.
  • The canonical structure โ€” Title, Problem, Solution, Product, Market/Why now, Traction, Business model, Team, The Ask โ€” is a checklist of the questions your audience will silently ask.
  • The arc matters more than any single slide: tension โ†’ relief โ†’ opportunity โ†’ credibility โ†’ action. Build Problem and Solution first.
  • Apply one theme/master, keep one idea per slide, show your product as a diagram, and keep the words in your speaker notes โ€” then rehearse out loud.

๐ŸŽ‰ What You've Accomplished

You built a complete pitch deck end to end โ€” from a blank deck and a compass sentence to a rehearsed ~10-slide presentation โ€” pulling together theme and master, structure, design discipline, a diagram, and speaker notes from across the whole course. This is a deck you could genuinely stand up and deliver. That's a real, portfolio-worthy skill, and you now have a repeatable process for the next pitch you're asked to make.

โ“ Common Questions at This Stage

How many slides should a pitch deck have?

The classic answer is about ten, one per section of the canonical arc plus a closing slide. But the real rule is "as few as tell the story clearly." An internal five-minute pitch might be seven slides; a formal investor pitch might be twelve. Fewer, sharper slides almost always beat more.

What if I don't have real traction or numbers yet?

Show whatever proof you honestly have โ€” a working prototype, early interest, a pilot, letters of intent, or even strong problem evidence (survey results, quotes from people with the problem). Never fake numbers. A credible "here's what we've validated so far" beats an unbelievable hockey-stick chart every time.

Should I animate the pitch deck?

Sparingly. A gentle appear on the diagram's steps can help you reveal one idea at a time, which supports the one-idea-per-slide rule. But heavy motion distracts from your words. Keep transitions simple and consistent โ€” the star of a pitch is you and the idea, not the effects.

๐Ÿ”ญ Looking Ahead

In the next lesson โ€” Lesson 7.2: Project โ€” A Lesson / Training Deck โ€” we shift from persuading to teaching. You'll build a training deck structured for learning (objectives โ†’ explain โ†’ demo โ†’ practice โ†’ recap), using progressive reveal, an embedded video, and speaker notes as a facilitator script, and handling a longer deck organized into sections.

โœ… Before the Next Lesson

  • Finish your pitch deck and run through it once more, timed
  • Think of a topic you know well enough to teach โ€” you'll build a training deck on it next
  • Write your Learning Journal entry for this lesson

๐Ÿ“š Additional Resources

๐ŸŒŸ Encouragement for the Journey

You just built the deck people find scariest โ€” a pitch โ€” using nothing but skills you already had. That's the whole point of these project lessons: proving to yourself that the pieces add up to real work. Carry that confidence into the next build. ๐Ÿ“Š