Pitch Deck FrameworkSAFE

An agent skill published by revfactory.

The instruction file, verbatim from the audited commit — this is the text the model reads, and the surface the audit's instruction layer examines. Quoted here so you can judge it without cloning anything.

---
name: pitch-deck-framework
description: "Framework for pitch deck structure, storytelling, and slide design for fundraising. Use this skill for 'pitch deck framework', 'investor PT structure', 'pitch storyline', 'slide design', 'investor Q&A preparation', and other pitch deck writing tasks. Note: actual investment contract writing, legal review, and graphic design execution are outside the scope of this skill."
---

# Pitch Deck Framework — Investor Pitch Deck Design Guide

A skill that enhances pitch deck creation for the pitch-creator and launch-reviewer.

## Target Agents

- **pitch-creator** — Creates compelling investor pitch decks
- **launch-reviewer** — Evaluates pitch deck quality and investment readiness

## Standard Deck Structure (12 slides)

```
1. Cover — Company name, one-line description, contact
2. Problem — The pain point (with data or story)
3. Solution — Your approach + key differentiator
4. Product/Demo — Screenshots, user flow, features
5. Market — TAM/SAM/SOM with credible sources
6. Business Model — Revenue model, pricing, unit economics
7. Traction — Key metrics, milestones, growth chart
8. Competition — 2x2 positioning map, competitive moat
9. Go-to-Market — Customer acquisition strategy, channels
10. Team — Founders, key hires, relevant experience
11. Financials — 3-year projection, key assumptions
12. The Ask — Amount, use of funds, next milestones
```

## Storytelling Arc

```
Hook (Slide 1-2): Capture attention with a compelling problem
Build (Slide 3-6): Show your solution and the opportunity
Prove (Slide 7-8): Demonstrate traction and competitive position
Close (Slide 9-12): Show the path forward and make the ask
```

## Per-Slide Design Rules

```
- One key message per slide
- Maximum 6 bullet points per slide
- Font size minimum 24pt (presentation), 14pt (reading)
- Data visualization > text whenever possible
- Consistent color scheme throughout
- White space is your friend
```

## Investor Q&A Preparation

### Must-Have Answers
```
1. Why now? (Market timing)
2. Why you? (Team unfair advantage)
3. How do you acquire customers? (GTM strategy)
4. What if [big competitor] does this? (Competitive moat)
5. What are the key risks? (Self-awareness)
6. How will you use the funding? (Capital allocation)
7. What are your next milestones? (Execution plan)
8. What is your exit strategy? (Return path)
```

### Financial Q&A Preparation
```
- What are the key assumptions behind your projections?
- What is your current burn rate and runway?
- When do you expect to reach profitability?
- What metrics do you track weekly?
- How does your unit economics compare to industry benchmarks?
```

## Common Pitch Deck Mistakes
```
1. Too many slides (>15) — keep to 12
2. No clear problem statement — lead with pain
3. TAM/SAM/SOM without sources — always cite data
4. Hockey stick projections without basis — show milestones
5. Ignoring competition — never say "no competitors"
6. Ask without use of funds breakdown — be specific
7. No traction slide — show any validation you have
8. Team slide without relevant experience — highlight domain fit
```

SAFEgrade B · trust 89/100 Nothing in the source contradicts what it says it does. Grade A is reserved for packages that have also passed the behavioural sandbox.

What the source does

Filesystem

none-observed

Network

none-observed

Shell

none-observed

Dependencies

pinned

Secrets in source

none-found

Findings (0)

No findings outside the package's declared scope.

Gates applied: no_behavioural_pass.