How many slides per minute is a good ratio?

About 1-2 slides per minute for content-heavy presentations. For visual or demo-heavy talks, you might go faster. The outline should give you pacing guidance — if you have 20 slides for a 10-minute talk, you're moving too fast.

Should I include speaker notes in the outline?

Yes, especially for key points you might forget under pressure. The outline generator includes speaker notes for each slide. Think of them as 'what I'll actually say when this slide is up.'

Can I use these outlines in any presentation tool?

Yes. The outlines are text-based — copy them into PowerPoint, Google Slides, Keynote, Figma, or any tool. The structure works regardless of where you build the deck.

Examples

Presentation Outline Examples

Proven structures for common presentations. Copy the outline, add your content, skip the blank-slide struggle.

By DropFile Editorial Team · Last updated April 11, 2026

The hardest part of any presentation is deciding on the structure. Once you have a clear outline — slide titles, key points, and flow — building the actual slides is fast. These examples cover the most common business presentations with outlines you can copy and adapt.

Quarterly business review (QBR)

15-minute QBR for the leadership team covering Q1 revenue, customer churn, product updates, and hiring

**Slide 1: Q1 Business Review**
Date, presenter, one-line summary

**Slide 2: Revenue Summary**
• Q1 revenue vs. target (+/- %)
• Revenue by segment (new vs. expansion vs. renewal)
• Top 3 deals closed

**Slide 3: Customer Health**
• Churn rate vs. previous quarter
• NPS trend
• At-risk accounts and mitigation plan

**Slide 4: Product Highlights**
• Key features shipped
• Adoption metrics for recent launches
• Roadmap preview for Q2

**Slide 5: Team & Hiring**
• Current headcount vs. plan
• Open roles and hiring timeline
• Key hires made this quarter

**Slide 6: Q2 Priorities**
• Top 3 goals with owners
• Key risks and dependencies
• Ask from leadership (if any)

Six slides for 15 minutes — about 2.5 minutes per slide. Leads with the metric leadership cares most about (revenue), then works through the other business areas. Ends with forward-looking priorities and a clear ask.

Sales pitch deck outline

10-minute pitch for a B2B SaaS product to a prospective enterprise customer

**Slide 1: Title & Hook**
Company name, one-line value proposition, presenter

**Slide 2: The Problem**
• Specific pain point the prospect faces
• Cost of the problem (time, money, risk)
• Why existing solutions fall short

**Slide 3: The Solution**
• What the product does in one sentence
• 3 key capabilities mapped to the pain points
• Screenshot or product visual

**Slide 4: How It Works**
• 3-step process (simple, visual)
• Integration with prospect's existing tools
• Time to value

**Slide 5: Results & Proof**
• 2-3 customer logos
• Specific metrics ("reduced X by 40%")
• Short testimonial quote

**Slide 6: Pricing & Next Steps**
• Pricing overview or "let's discuss"
• Proposed next step (pilot, trial, follow-up call)
• Contact info

Follows the classic Problem → Solution → Proof → CTA arc. Six slides keeps it under 10 minutes. The 'How It Works' slide is where prospects decide if it's realistic for their setup.

Training / onboarding session

30-minute onboarding session for new engineers on our deployment pipeline

**Slide 1: Welcome & Agenda**
Session goal, what you'll be able to do by the end, agenda overview

**Slide 2: Architecture Overview**
• High-level diagram of the pipeline
• Key services and their roles
• Where code flows from commit to production

**Slide 3: Step 1 — Local Development**
• Dev environment setup
• Running tests locally
• Common gotchas

**Slide 4: Step 2 — CI/CD Pipeline**
• What triggers a build
• Test stages and gates
• How to read build logs

**Slide 5: Step 3 — Deploying to Staging**
• How to trigger a staging deploy
• Smoke test checklist
• Rollback procedure

**Slide 6: Step 4 — Production Release**
• Release process and approvals
• Monitoring dashboards to watch
• Incident response if something breaks

**Slide 7: Resources & FAQ**
• Links to docs, runbooks, Slack channels
• Who to ask for help
• Common questions from past onboardings

Seven slides for 30 minutes — about 4 minutes per slide with time for questions. Follows the actual workflow sequence so new engineers can follow along. Ends with resources they'll reference later.

Project status update

5-minute project status update for a cross-functional team meeting

**Slide 1: Project Status — [Project Name]**
Status: 🟡 On Track / 🔴 At Risk / 🟢 Complete
Date, sprint/phase number

**Slide 2: What's Done**
• Completed milestones (3-5 bullet points)
• Key metrics or deliverables

**Slide 3: What's Next**
• Current sprint goals
• Upcoming milestones with dates
• Dependencies on other teams

**Slide 4: Risks & Blockers**
• Active blockers (who can unblock)
• Risks being monitored
• Help needed from this group

Four slides for 5 minutes. Leads with status (the only thing most people in the room care about), then details for those who need them. Ends with asks — the most actionable part.

Tips

•One idea per slide. If a slide has two distinct topics, split it into two slides.
•Slide titles should be assertions, not labels. 'Revenue grew 15% QoQ' is better than 'Revenue Update'.
•Design for the back of the room — if someone can't read your slide from 15 feet away, there's too much text.
•Start with the outline before opening PowerPoint or Google Slides. Structure first, design second.
•For presentations over 15 minutes, add a mid-point agenda check or transition slide so the audience knows where they are in the flow.

Try it yourself

Open the Presentation Outline and generate your own results from a plain-English description.

Open Presentation Outline