ops-pitch-deck
架構募資簡報,十二張投影片講完問題、解方到募資需求
中文翻譯
---
name: "ops-pitch-deck"
description: "規劃並撰寫投資人簡報(pitch deck),涵蓋問題、解方、市場、商業模式、traction(成長動能)、團隊和財務。使用者需要製作募資簡報、準備投資人會議,或規劃新創的 pitch 結構時使用,就算他們說的是「做一份 pitch deck」、「向投資人簡報」、「準備募資」或「我的 pitch 該怎麼架構」也一樣。"
metadata:
category: "WP-10 通用商業"
tags: ["business", "pitch-deck", "fundraising", "startup"]
---
# Pitch Deck
## 框架
```
IRON LAW: 10-15 Slides, One Idea Per Slide
Investors see 100+ decks per month. They spend 3-4 minutes on average.
Every slide must earn its place. If a slide doesn't advance the core
narrative (problem → solution → why us → why now), cut it.
```
### 標準 Pitch Deck 結構(12 張投影片)
| # | 投影片 | 目的 | 時間 |
|---|-------|---------|------|
| 1 | **標題** | 公司名稱、一句話描述、你的名字 | 10 秒 |
| 2 | **問題** | 痛點:具體、有共鳴、有數據支持 | 30 秒 |
| 3 | **解方** | 你怎麼解決它:清楚、具體 | 30 秒 |
| 4 | **Demo/產品** | 用秀的,不要用講的:截圖、影片或流程 | 45 秒 |
| 5 | **市場規模** | TAM → SAM → SOM,附方法論 | 30 秒 |
| 6 | **商業模式** | 你怎麼賺錢:定價、單位經濟(unit economics) | 30 秒 |
| 7 | **Traction(成長動能)** | 你已經達成什麼:營收、用戶、成長率 | 30 秒 |
| 8 | **競爭** | 2×2 定位圖:你在哪裡贏 | 20 秒 |
| 9 | **團隊** | 為什麼是「這個」團隊會贏:相關經驗 | 20 秒 |
| 10 | **財務** | 3 年預測:營收、關鍵假設 | 30 秒 |
| 11 | **募資需求(The Ask)** | 要多少、用在哪、能達成哪些里程碑 | 20 秒 |
| 12 | **聯絡方式** | 姓名、email、下一步 | 5 秒 |
### 逐張投影片指南
**問題投影片:**
- 要讓聽眾「感受到」那份痛
- 用具體的例子或數據點(「40% 的中小企業每月花 20 小時以上在手動開發票」)
- 避免抽象的問題(「企業需要更好的解決方案」)
**市場規模:**
- TAM = 整體可及市場(如果你拿下 100%)
- SAM = 可服務的可及市場(你的區隔)
- SOM = 可取得的可服務市場(實際的 3 年目標)
- 要秀方法論,不要只放一個數字
**Traction 投影片(對募資最重要):**
- 營收曲線(向右上方走)
- 成長率(月增率或年增率)
- 關鍵里程碑:客戶、合作、產品上線
- 如果還沒有營收:候補名單、意向書(LOI)、試行成果
**競爭投影片:**
- 用 2×2 矩陣,不要用功能比較表
- 選能讓你在右上角明顯勝出的軸
- 包含間接競爭者和替代方案
**募資需求(The Ask):**
- 金額:具體的數字(「NT$30M A 輪」)
- 資金用途:前 3 大分配(產品 40%、銷售 35%、營運 25%)
- 這筆資金能達成的里程碑(「達到 $1M ARR、拓展到 3 個市場」)
## 輸出格式
```markdown
# Pitch Deck Outline: {Company}
## Slide-by-Slide Content
### 1. Title
- Company: {name}
- Tagline: {one line}
### 2. Problem
- Pain point: {specific, data-backed}
- Who has this problem: {target customer}
### 3. Solution
- What we do: {one sentence}
- How it works: {2-3 bullet points}
### 4. Product
- {Screenshot/demo description}
### 5. Market
- TAM: ${X}
- SAM: ${X}
- SOM: ${X} (methodology: {how calculated})
### 6. Business Model
- Revenue model: {subscription/transaction/etc.}
- Pricing: {specifics}
- Unit economics: {LTV, CAC, margins}
### 7. Traction
- {Key metric 1}: {number}
- {Key metric 2}: {number}
- Growth: {rate}
### 8. Competition
- 2×2 axes: {X axis} vs {Y axis}
- Our position: {top-right quadrant and why}
### 9. Team
- {Name}: {relevant credential}
- {Name}: {relevant credential}
### 10. Financials
| | Y1 | Y2 | Y3 |
|---|-----|-----|-----|
| Revenue | ${X} | ${X} | ${X} |
### 11. The Ask
- Raising: ${X}
- Use: {allocation}
- Milestones: {what this funding achieves}
## Design Guidelines
- Font size: ≥ 24pt (readable from back of room)
- Max words per slide: 30-40
- One chart/visual per slide maximum
```
## 注意事項
- **Traction 勝過一切**:一份 traction 很強但設計普通的簡報,會贏過一份漂亮卻沒有 traction 的簡報。用你最強的指標開場。
- **不要把投影片唸出來**:投影片是視覺輔助。故事由你來講;投影片提供證據。如果你在唸條列項目,就代表條列項目太多了。
- **「我們沒有競爭對手」= 警訊**:投資人知道這代表你沒做功課。永遠都有競爭,就算只是「什麼都不做」或「用試算表」。
- **財務預測「一定」會被質疑**:「你怎麼算出第 3 年 $10M 的?」要準備好由下而上的模型。單靠由上而下的市占率假設很薄弱。
- **寄 email 時要寄濃縮版**:簡報現場用的版本(文字極少、大圖)和 email/會前閱讀的版本(文字較多、能自己說明清楚)不一樣。兩種都要準備。
## 參考資料
- 預測背後的財務建模請看 fin-modeling skill英文原文
---
name: "ops-pitch-deck"
description: "Structure and write investor pitch decks covering problem, solution, market, business model, traction, team, and financials. Use this skill when the user needs to create a fundraising presentation, prepare for investor meetings, or structure a startup pitch — even if they say 'build a pitch deck', 'present to investors', 'prepare for fundraising', or 'how should I structure my pitch'."
metadata:
category: "WP-10 通用商業"
tags: ["business", "pitch-deck", "fundraising", "startup"]
---
# Pitch Deck
## Framework
```
IRON LAW: 10-15 Slides, One Idea Per Slide
Investors see 100+ decks per month. They spend 3-4 minutes on average.
Every slide must earn its place. If a slide doesn't advance the core
narrative (problem → solution → why us → why now), cut it.
```
### Standard Pitch Deck Structure (12 Slides)
| # | Slide | Purpose | Time |
|---|-------|---------|------|
| 1 | **Title** | Company name, one-line description, your name | 10 sec |
| 2 | **Problem** | The pain point — specific, relatable, data-backed | 30 sec |
| 3 | **Solution** | How you solve it — clear, concrete | 30 sec |
| 4 | **Demo/Product** | Show, don't tell — screenshot, video, or flow | 45 sec |
| 5 | **Market Size** | TAM → SAM → SOM with methodology | 30 sec |
| 6 | **Business Model** | How you make money — pricing, unit economics | 30 sec |
| 7 | **Traction** | What you've achieved — revenue, users, growth rate | 30 sec |
| 8 | **Competition** | 2×2 positioning map — where you win | 20 sec |
| 9 | **Team** | Why THIS team wins — relevant experience | 20 sec |
| 10 | **Financials** | 3-year projection — revenue, key assumptions | 30 sec |
| 11 | **The Ask** | How much, what for, what milestones it enables | 20 sec |
| 12 | **Contact** | Name, email, next step | 5 sec |
### Slide-by-Slide Guide
**Problem Slide:**
- Make the audience FEEL the pain
- Use a specific example or data point ("40% of SMBs spend 20+ hrs/month on manual invoicing")
- Avoid abstract problems ("businesses need better solutions")
**Market Size:**
- TAM = Total Addressable Market (if you captured 100%)
- SAM = Serviceable Addressable Market (your segment)
- SOM = Serviceable Obtainable Market (realistic 3-year target)
- Show methodology, not just a number
**Traction Slide (most important for fundraising):**
- Revenue curve (up and to the right)
- Growth rate (MoM or YoY)
- Key milestones: customers, partnerships, product launches
- If pre-revenue: waitlist, LOIs, pilot results
**Competition Slide:**
- 2×2 matrix, NOT a feature comparison table
- Choose axes that make you the clear winner in the top-right
- Include indirect competitors and substitutes
**The Ask:**
- Amount: specific number ("NT$30M Series A")
- Use of funds: top 3 allocations (product 40%, sales 35%, operations 25%)
- Milestones the funding enables ("reach $1M ARR, expand to 3 markets")
## Output Format
```markdown
# Pitch Deck Outline: {Company}
## Slide-by-Slide Content
### 1. Title
- Company: {name}
- Tagline: {one line}
### 2. Problem
- Pain point: {specific, data-backed}
- Who has this problem: {target customer}
### 3. Solution
- What we do: {one sentence}
- How it works: {2-3 bullet points}
### 4. Product
- {Screenshot/demo description}
### 5. Market
- TAM: ${X}
- SAM: ${X}
- SOM: ${X} (methodology: {how calculated})
### 6. Business Model
- Revenue model: {subscription/transaction/etc.}
- Pricing: {specifics}
- Unit economics: {LTV, CAC, margins}
### 7. Traction
- {Key metric 1}: {number}
- {Key metric 2}: {number}
- Growth: {rate}
### 8. Competition
- 2×2 axes: {X axis} vs {Y axis}
- Our position: {top-right quadrant and why}
### 9. Team
- {Name}: {relevant credential}
- {Name}: {relevant credential}
### 10. Financials
| | Y1 | Y2 | Y3 |
|---|-----|-----|-----|
| Revenue | ${X} | ${X} | ${X} |
### 11. The Ask
- Raising: ${X}
- Use: {allocation}
- Milestones: {what this funding achieves}
## Design Guidelines
- Font size: ≥ 24pt (readable from back of room)
- Max words per slide: 30-40
- One chart/visual per slide maximum
```
## Gotchas
- **Traction trumps everything**: A deck with amazing traction and mediocre design beats a beautiful deck with no traction. Lead with your strongest metric.
- **Don't read slides aloud**: Slides are visual aids. You tell the story; slides provide evidence. If you're reading bullets, there are too many bullets.
- **"We have no competition" = red flag**: Investors know this means you haven't researched. There's always competition — even if it's "doing nothing" or "using a spreadsheet."
- **Financial projections WILL be questioned**: "How did you get to $10M Y3?" Have a bottom-up model ready. Top-down market share assumptions are weak alone.
- **Send a condensed version for email**: The presentation deck (with minimal text, big visuals) differs from the email/read-ahead deck (more text, self-explanatory). Prepare both.
## References
- For financial modeling behind the projections, see the fin-modeling skill