TinyKPI

PITCH DECK GUIDE

The 10 20 30 rule
for pitch decks.

What to include in ten slides, how to present them in twenty minutes, and how the 30-point font rule helps. Includes a sample deck and a free outline.

An illustrative pitch rehearsal with the 10-slide, 20-minute, 30-point rule on screen

THE RULE

What is the 10 20 30 rule?

The 10 20 30 rule means 10 slides, no more than 20 minutes, and a minimum 30-point font. Guy Kawasaki introduced it as a way to keep a pitch focused.

Use the slides to support what you’re saying. Put detailed explanations in your speaker notes, where they won’t compete for the audience’s attention.

EXAMPLE DECK

A ten-slide pitch deck example

This example is for an invoicing service used by small agencies. It covers the customer problem, the service, pricing, sales, and a funding request. Select a slide to see the example and its speaker notes.

THE AGENCY INVOICING DECK

Invoicing takes
time away
from client
work.

6 hourslost to invoicing.
Every week.

Hands sorting paper invoices at a studio desk; illustrative image
01 / 10 — The problem

About this slideThe opening identifies the customer’s problem and estimates the time it takes each week. In your own deck, use a figure you can support with interviews or time logs.

Speaker notes

Our initial customer is a 10–30 person agency. In this illustrative scenario, its operations lead spends six hours each week reconciling time logs and chasing approvals before invoices can go out.

Example pitch deck · Fictional business and figures

Invoicing takes
time away
from client
work.

6 hourslost to invoicing.
Every week.

Hands sorting paper invoices at a studio desk; illustrative image
1 / 10 · The problem

The business, figures, and team in this example are fictional. The slide previews are scaled to fit your screen.

SLIDE CONTENT

What to put on each slide

The outline below follows the topics in the original framework. Open a section for an example headline, writing advice, and the evidence you’ll need.

01The problemWhose problem is painful enough to pay for?

Describe who has the problem and what it costs them. For this example, that means agency staff spending time preparing invoices. Use interviews or time logs to support the estimate.

EXAMPLE HEADLINE

“Agencies spend six hours a week on invoicing.”

Supporting evidence: Replace the six-hour estimate with dated interviews or time logs. State how many agencies you observed and how you measured the work.

02Your solutionWhat changes for the customer?

Show how the customer would use the service. A product screenshot or short demo can help. Explain what they can do with it before listing features.

EXAMPLE HEADLINE

“Review approved work and prepare the invoice.”

Supporting evidence: Use a working demo or label a mockup as a concept. Only claim a time saving after measuring it against the original workflow.

03How you make moneyWho pays, how much, and for what?

State who pays and what the price includes. Keep subscription revenue separate from setup fees and services. If you haven't tested the price, label it as proposed pricing.

EXAMPLE HEADLINE

“A monthly subscription for each agency.”

Supporting evidence: Use billing records for actual revenue. Include gross margin and delivery costs in the appendix when you have enough data to support them.

04What makes it workWhy is your approach meaningfully different?

Explain how the service does the work. Here, a diagram connects each invoice to its approved time entries. Distinguish what you have built from what you plan to build.

EXAMPLE HEADLINE

“Check each invoice against its approved time entries.”

Supporting evidence: Show the workflow handling a real exception. Distinguish an implemented feature from a roadmap item or an untested technical claim.

05Finding customersHow will the next customers find and buy from you?

Describe your first customers and how you reach them. Show which sales methods have brought in customers and which ones you still need to test.

EXAMPLE HEADLINE

“Sell to small agencies through outreach and bookkeeper referrals.”

Supporting evidence: Bring actual funnel counts when available. Do not present a proposed referral program as a proven distribution channel.

06Customer alternativesWhy would a customer switch from what they do today?

Explain what customers use today, including manual work. Compare the factors that affect their buying decision and be honest about where another option works better.

EXAMPLE HEADLINE

“Agencies currently use spreadsheets or accounting software.”

Supporting evidence: Use customer interviews and observed product capabilities. Avoid an all-green comparison grid that makes every alternative look incompetent.

07The peopleWhy is this team equipped to solve this problem?

Introduce the people doing the work and their relevant experience. Say who handles product development, sales, and operations, and identify any important gaps.

EXAMPLE HEADLINE

“The founders have experience in agency operations and billing software.”

Supporting evidence: Replace the illustrative backgrounds with accurate experience. Only list an advisor, employee, or partner if that relationship exists and can be represented publicly.

08Numbers and milestonesWhat must be true for your plan to work?

Show how customer count and price produce the revenue figure. Label current results and future targets separately. Explain the sales and retention assumptions needed to reach the target.

EXAMPLE HEADLINE

“The twelve-month target is 100 paying agencies.”

Supporting evidence: Show a monthly customer bridge and expense plan in the appendix. If you have no revenue yet, use verifiable product or customer-validation milestones instead.

09Progress and next stepsWhat is done, what is next, and what could get in the way?

State what is finished and what the team will do next. Give each milestone a deadline, an owner, and a way to measure completion. Include the main unresolved risk.

EXAMPLE HEADLINE

“Review retention before increasing acquisition spending.”

Supporting evidence: Bring a dated milestone tracker. Keep customer retention data separate from anecdotes, pipeline, and future plans.

10The askWhat decision do you want, and what will it enable?

State how much you are raising, what you will spend it on, and what you expect to achieve. Base the amount on your budget and cash plan. End with the follow-up you want.

EXAMPLE HEADLINE

“Raise $500k to work toward 100 paying agencies.”

Supporting evidence: Reconcile the request with current cash, expected expenses, revenue assumptions, and a contingency. A round size alone does not establish runway.

12-month target:
100 paying agencies.

EXAMPLE: CURRENT REVENUE AND A FUTURE TARGET

Explain where the numbers come from

In this example, 40 agencies × $200 = $8,000 MRR. The audience can see how the customer count and subscription price produce the revenue figure.

The second bar shows the target: 100 agencies and $20,000 MRR. Label it clearly so nobody mistakes a projection for current revenue.

The striped bar is a target. ↖
When writing your slide

Use a specific heading, such as “40 paying agencies,” instead of “Traction.” If you haven’t started charging customers, show measured progress such as active trials or completed pilots.

Where should market size go?

Describe your target customer in the problem and sales slides. If market size needs a separate explanation, give it a slide and combine two shorter topics elsewhere.

TIMING

How to plan a twenty-minute pitch

You don’t have to spend two minutes on every slide. A team introduction may take one minute; explaining the financial plan may take three. The schedule below adds up to twenty minutes.

20 minYour pitch
40 minDiscussion, in a one-hour meeting

In a one-hour meeting, a twenty-minute pitch leaves forty minutes for questions. Adjust this split to your actual meeting length.

See the slide-by-slide timing 20:00 total
  1. 01The problem2:00
  2. 02Your solution2:00
  3. 03How you make money1:30
  4. 04What makes it work2:00
  5. 05Finding customers2:00
  6. 06Customer alternatives1:30
  7. 07The people1:00
  8. 08Numbers and milestones3:00
  9. 09Progress and next steps2:00
  10. 10The ask3:00

Time a full rehearsal

Present the deck aloud with a timer, including any demo. If you run over, remove a secondary point or move it to the appendix. Prepare a shorter version in case the meeting starts late.

Only have twenty minutes for the entire meeting? Try a 10–12 minute pitch and leave the rest for questions.

FONT SIZE

Use at least 30-point text

Set your body text to at least 30 pt in the presentation editor. If the slide becomes too crowded, shorten the text or move the explanation into your notes. This example shows how to simplify a slide.

BEFORE

How the invoicing service works

The service collects time entries from each project and checks that the work has been approved. The operations lead reviews any missing details or changed entries, prepares the invoice, checks it against the client agreement, and sends it. Payment reminders are queued after sending. The team can check the status of each invoice in the same place.

Time tracking · Approvals · Reconciliation · Follow-ups

The audience has to read a paragraph while you’re speaking.

AFTER

Approved work.
Ready to invoice.

≡Review
→
✓Approve
→
↗Send

Review and send invoices in one place.

The slide shows the three steps. You explain the details aloud.

Move the feature list
into your notes.

Replace the vague headline
with an outcome.

Show the workflow
in three steps.

Check chart labels, too. Share your screen and look at it on a smaller laptop. If someone needs to squint, simplify the chart or increase the type. A 30-point setting alone doesn’t guarantee readability.

EXCEPTIONS

When to adjust the rule

Ten slides and twenty minutes won’t suit every presentation. Adjust the format when the meeting calls for it.

A five-minute pitch

Use fewer slides and rehearse within the event’s time limit. Include the problem, your strongest evidence, and what you’re asking for.

A deck sent by email

Include enough explanation for someone to understand the deck without hearing you present it.

A technical review

Keep the overview short. Put architecture, validation, and detailed data in an appendix or a separate session.

A requested format

If an investor or event asks for a particular format, follow it. You can still keep the text readable and the presentation concise.

DOWNLOADS AND REFERENCES

Pitch deck resources

FREE WORKSHEET

Download the ten-slide outline

A text file with a writing prompt, suggested timing, and an evidence checklist for each slide.

Download the outline

Plain text · Editable in any document app · No signup

Your final rehearsal check0 / 6 ready

QUESTIONS

Frequently asked questions

What is the 10 20 30 rule?

It is Guy Kawasaki's presentation guideline: ten slides, a maximum of twenty minutes, and a minimum font size of thirty points. It gives you a simple starting structure for a concise live pitch.

Who created the 10/20/30 rule?

Guy Kawasaki introduced the rule in a 2005 article about business presentations. His original explanation focuses on venture pitches and also mentions sales and partnership presentations.

Does the title slide count toward the ten slides?

If you present it as a separate slide, count it. In the example on this page, the opening problem slide also serves as the introduction. You can use a dedicated cover, but combine or reorganize another topic to keep a ten-slide core.

Are the twenty minutes just for the pitch or also for questions?

The twenty minutes refers to the presentation. Leave additional time for discussion when the meeting allows it. If the entire meeting is twenty minutes, make your prepared pitch shorter so questions still fit.

Does every slide need exactly two minutes?

No. Twenty minutes across ten slides is an average. Spend more time on the evidence and decisions that matter, and move quickly through simple context. This guide includes a sample timing plan that adds up to twenty minutes.

Can I include more than ten slides?

You can adapt the guideline to the audience and the meeting. Keep supporting material in an appendix and open it when relevant. If an investor or event asks for a particular format, use that format instead of forcing the ten-slide structure.

Should a deck sent by email follow the same rule?

A deck that someone reads without you needs enough context to stand on its own. Keep it concise and legible, but add explanations where the live version relies on your narration. The twenty-minute speaking limit does not apply to an asynchronous document.

Is 30-point text always readable?

No. Thirty points is a starting constraint, not a guarantee of accessibility. Contrast, font choice, room size, screen sharing, and viewing distance all matter. Test the actual presentation setup and increase the size when needed.