agentleFS
wulaosijiwulaosiji/founder-skills/skills/investor-pitch-planner/SKILL.md

investor-pitch-planner

Skill9 starsChanged 2 months agoMITView on GitHub

Generate a structured fundraising pitch deck outline covering Problem, Solution, Market, Business Model, Team, and The Ask, with data visualization suggestions for each module. Transforms startup project information into a professional pitch deck outline through a structured SOP workflow. Use when: "pitch deck outline", "融资大纲", "investor presentation", "fundraising deck structure", "帮我写pitch deck", "BP框架", "startup pitch plan", "投资人材料", "pitch deck framework". For founders who need to structure their fundraising story and build a pitch deck content framework in English. Cross-references: fundraising-bp-planner, pitch-deck-creator, business-plan-ppt. Built by UniqueClub 🌐 https://uniqueclub.ai

The file

Show its rules and text

We split this skill into the rules it gives an agent

26 rules. About 0 are common, 26 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈26

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use this skill when:

    line 17
  2. Distinctive:

    Do NOT use this skill if:

    line 23
  3. Distinctive:

    All six modules must be complete (Problem, Solution, Market, Business Model, Team, The Ask)

    line 58
  4. Distinctive:

    Every module must include data visualization recommendations

    line 59
  5. Distinctive:

    Use of funds must have percentage allocation

    line 61
  6. Distinctive:

    No hardcoded data — all placeholders marked with [brackets]

    line 63
  7. Distinctive:

    When blocked, switch channels.

    line 64
  8. Distinctive:

    Every number must come from input, specific sources, or reproducible calculations:

    line 67
  9. Distinctive:

    Verify item by item with the quality checklist — read back output using a method different from the generation path:

    line 78
  10. Distinctive:

    All six modules complete

    line 79
  11. Distinctive:

    Every module includes data visualization recommendations

    line 80
  12. Distinctive:

    Use of funds has percentage allocation

    line 82
  13. Distinctive:

    If multiple revenue streams exist, state priorities

    line 217
  14. Distinctive:

    All data visualization recommendations use Markdown tables

    line 444
  15. Distinctive:

    Use the actual current date

    line 446
  16. Distinctive:

    Before outputting the final pitch deck outline, verify each item:

    line 466
  17. Distinctive:

    If the user provides feedback on the outline:

    line 489
  18. Distinctive:

    Keep data visualization recommendations consistent with the content

    line 493
  19. Distinctive:

    All placeholders marked with [brackets]

    line 504
  20. Distinctive:

    NEVER invent traction, market size, customer evidence, or team backgrounds

    line 520
  21. Distinctive:

    Do NOT hardcode data — all placeholders marked with [brackets]

    line 521
  22. Distinctive:

    Do NOT omit any of the six modules

    line 522
  23. Distinctive:

    NEVER present assumptions as verified facts

    line 523
  24. Distinctive:

    Do NOT output a module without data visualization recommendations

    line 524
  25. Distinctive:

    Do NOT leave the Information To Be Provided list empty — there is always data the user needs to supply

    line 525
  26. Distinctive:

    All six modules must be complete

    line 528

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Investor Pitch Planner

One-line request → Complete fundraising pitch deck outline: Through a structured SOP workflow, transform startup project information into a fundraising pitch deck outline covering six core modules — Problem → Solution → Market → Business Model → Team → The Ask — with data visualization recommendations for each module.

When to Use

Use this skill when:

  • The user needs to generate a fundraising pitch deck outline or business plan content framework in English
  • The user mentions pitch decks, fundraising, investor presentations, or asks for help writing a deck
  • The user is preparing to raise funds and needs to structure their story
  • The user needs an English-language pitch deck outline (six modules + data visualization suggestions)

Do NOT use this skill if:

  • The user needs an editable PPTX file → use pitch-deck-creator instead
  • The user needs a Chinese pitch deck outline → use fundraising-bp-planner instead
  • The user needs an 18-page Chinese-style PPT visual specification → use business-plan-ppt instead
  • The user needs a specific narrative framework (Sequoia/YC/Raskin) → use the corresponding framework skill
  • The user needs to convert an existing PPT to web → use deck-web-converter

Typical triggers:

  • "help me write a pitch deck", "fundraising outline", "investor presentation structure"
  • 「帮我写pitch deck」「融资大纲」「投资人材料」

Quick Start

Simply provide a basic project description, and the Agent will automatically generate a fundraising pitch deck outline following this workflow:

User: We built a smart financial SaaS for SMBs and want to raise a Pre-A round
Agent: [Outputs a complete pitch deck outline following the SOP workflow]

Workflow

本工作流遵循六步推进法,共6个步骤:

  1. 探查 (Probe):动手前先完整读取全部输入,确认目标和约束。
  2. 约束 (Constrain):验证输入完整性,设定边界和不可降级的交付标准,受阻时换通道。
  3. 证据 (Evidence):每个数字必须来自输入、具体信源或可复现计算,收集支撑数据。
  4. 执行 (Execute):调用脚本/API/生成内容,先给影响与结论,再给行动和必要证据。
  5. 验证 (Verify):用"可能失败"的动作验证——不同于生成路径的方式回读输出。
  6. 交付 (Deliver):返回结果,清理临时文件。

Step 1: Probe (探查)

Fully read the user's project description, identify industry, target audience, product form, and development stage. Extract core information needed to build the pitch deck outline.

Step 2: Constrain (约束)

Select interaction mode based on input detail level (Guided / Semi-automatic / Fully automatic / Express), set boundaries and non-negotiable delivery standards:

  • All six modules must be complete (Problem, Solution, Market, Business Model, Team, The Ask)
  • Every module must include data visualization recommendations
  • Market size must have TAM/SAM/SOM three-tier breakdown
  • Use of funds must have percentage allocation
  • Milestones must have measurable metrics
  • No hardcoded data — all placeholders marked with [brackets]
  • When blocked, switch channels; do not degrade the deliverable

Step 3: Evidence (证据)

Every number must come from input, specific sources, or reproducible calculations:

  • Market size data must cite sources (public data / industry report / internal company data / estimate)
  • Business metrics (user count, revenue, growth rate, retention, etc.) come from user input
  • Team backgrounds come from user input; do not fabricate
  • Self-estimated data must state assumptions
  • Collect supporting data; do not invent traction or market size

Step 4: Execute (执行)

Generate outline content module by module following the detailed SOP. Lead with impact and conclusion, then action and necessary evidence. See "Detailed SOP Workflow" below.

Step 5: Verify (验证)

Verify item by item with the quality checklist — read back output using a method different from the generation path:

  • All six modules complete
  • Every module includes data visualization recommendations
  • Market size has TAM/SAM/SOM three-tier breakdown
  • Use of funds has percentage allocation
  • Milestones have measurable metrics
  • Data sources cited or flagged for user to provide
  • Total slides within 10–15 slide recommendation
  • Information To Be Provided list is non-empty
  • No hardcoded data

Step 6: Deliver (交付)

Return the complete pitch deck outline document (Markdown format), containing each module's key points, data visualization recommendations, and presentation tips. Clean up temporary files. If user provides feedback, identify the affected module and re-execute from the corresponding Phase, cascading updates to all downstream content.

Detailed SOP Workflow

Phase 1: Project Information Gathering

Objective: Extract core information needed to build the pitch deck outline from the user's description.

Steps:

  1. Parse the project description: Identify the industry, target audience, product form, and development stage
  2. Ask clarifying questions (up to 5 key questions):
    • What core pain point does the project solve? How do target users currently cope with this problem?
    • What stage is the product at? (Concept / MVP ready / Paying customers)
    • What key business metrics can you share? (User count, revenue, growth rate, retention rate, etc.)
    • What are the core team members' backgrounds? (Especially industry-relevant experience)
    • What is the target fundraising amount and intended use of funds?
  3. If the user asks to skip clarification, proceed with reasonable assumptions and flag them in the "Information To Be Provided" section of the outline

Output: Project information summary (under 200 words)


Phase 2: Problem Definition (Problem)

Objective: Clearly define the pain point faced by target users, helping investors feel the problem's reality and urgency.

Steps:

  1. Pain point description:
    • Summarize the core pain point in one sentence
    • Describe how target users currently solve the problem and the shortcomings of existing approaches
    • Quantify the pain point's impact (time cost, financial loss, efficiency loss, etc.)
  2. Suggested outline content:
    • Core pain point statement (1 sentence)
    • Current state description (how users cope today)
    • Scale and impact of the pain point
  3. Data visualization recommendations:

    Data TypePresentation FormatNotes
    Scale of affected usersLarge-font number + brief annotatione.g., "32 million SMBs face this problem"
    Shortcomings of existing solutionsComparison table (Current vs. Ideal)Highlight the gap
    Losses caused by the pain pointSingle key figuree.g., "Each company wastes $XX per year on average"

Output: Problem module outline + data visualization recommendations


Phase 3: Solution (Solution)

Objective: Show how the product solves the problem defined in Phase 2, highlighting differentiated value.

Steps:

  1. Solution description:
    • Explain what the product is and what it does in one sentence
    • List 3 core features/value propositions (no more than 3 — stay focused)
    • Explain differentiation from existing solutions
  2. Suggested outline content:
    • One-line product positioning
    • Core value propositions (3 points)
    • Product demo/screenshot talking points
    • Before-and-after user comparison
  3. Data visualization recommendations:

    Data TypePresentation FormatNotes
    Product impact comparisonBefore / After comparisone.g., "Processing time reduced from 3 days to 2 hours"
    Core feature highlightsIcon + keyword + one-line description3 features displayed side by side
    User feedback/case studiesQuote cards (avatar + quote + role)1–2 real user testimonials

Output: Solution module outline + data visualization recommendations


Phase 4: Market Analysis (Market)

Objective: Demonstrate that the market is large enough and growing fast enough to warrant investor attention.

Steps:

  1. Market size estimation:
    • TAM (Total Addressable Market): How large is the entire market
    • SAM (Serviceable Available Market): The market you can reach
    • SOM (Serviceable Obtainable Market): The market you can capture in the near term
    • Cite data sources (industry reports, public data; if self-estimated, state the assumptions)
  2. Market trends:
    • 2–3 key trends driving market growth
    • Opportunity windows created by policy, technology, or behavioral shifts
  3. Competitive landscape:
    • Key competitors (2–4) and their positioning
    • Your differentiated positioning
  4. Suggested outline content:
    • TAM/SAM/SOM figures
    • Market growth trends
    • Competitive positioning
  5. Data visualization recommendations:

    Data TypePresentation FormatNotes
    TAM/SAM/SOMConcentric circles or funnel chartLarge to small, each layer labeled with amount and calculation basis
    Market growth rateLine chart or CAGR figuree.g., "25% CAGR"
    Competitive landscape2×2 matrixChoose two key dimensions to position yourself against competitors
    Market trendsIcon-labeled trend list2–3 trends, each with a one-liner

Output: Market module outline + data visualization recommendations


Phase 5: Business Model (Business Model)

Objective: Explain how the business makes money and grows, giving investors confidence in the commercial viability.

Steps:

  1. Revenue model:
    • Primary revenue streams (subscriptions / transaction fees / advertising / value-added services, etc.)
    • Pricing strategy and average revenue per user/contract
    • If multiple revenue streams exist, state priorities
  2. Key metrics (select based on project stage):
    • Early stage: User growth rate, retention rate, customer acquisition cost (CAC)
    • Growth stage: Monthly Recurring Revenue (MRR), Customer Lifetime Value (LTV), LTV/CAC ratio
    • Mature stage: Gross margin, net margin, unit economics
  3. Growth flywheel:
    • Describe the core growth engine (product-led / sales-led / channel-led)
    • Potential for network effects or economies of scale
  4. Suggested outline content:
    • Revenue model overview
    • Key business metrics
    • Growth strategy
  5. Data visualization recommendations:

    Data TypePresentation FormatNotes
    Revenue modelFlowchart or revenue structure diagramClearly show where the money comes from
    Key metricsKPI dashboard style3–5 core numbers in large font
    Growth trendsBar chart (monthly/quarterly)Show revenue or user growth curves
    Unit economicsSimplified formula diagrame.g., "LTV $X > CAC $Y, payback period Z months"

Output: Business model module outline + data visualization recommendations


Phase 6: Team (Team)

Objective: Show that the team has the capability to execute the plan, boosting investor confidence.

Steps:

  1. Core team:
    • List 3–5 core members
    • For each: Name/title, role, key background (one sentence)
    • Highlight experience relevant to the project (industry expertise, technical skills, past successes)
  2. Team strengths:
    • Complementary skills (technical + business + industry connections)
    • Unique advantages (why this team is the right one to build this)
  3. Advisors/investor endorsements (if applicable):
    • Notable advisors or early investors
  4. Suggested outline content:
    • Core team profiles
    • Team highlights
    • Advisor/endorsement information
  5. Data visualization recommendations:

    Data TypePresentation FormatNotes
    Core teamAvatar + name + role + one-line background3–5 people displayed in a row
    Team experienceKey number badgese.g., "50+ combined years of industry experience", "3 successful exits"
    Advisors/endorsementsLogo wall or quote cardsWell-known institutions or individuals

Output: Team module outline + data visualization recommendations


Phase 7: Fundraising Ask (The Ask)

Objective: Clearly tell investors how much money you need, what it will be used for, and what milestones it will achieve.

Steps:

  1. Fundraising details:
    • Amount being raised this round
    • Round designation (Angel / Pre-A / A / B, etc.)
    • Equity offered (if applicable)
  2. Use of funds:
    • Allocation by percentage (e.g., Product R&D 40%, Marketing 30%, Team expansion 20%, Operating reserve 10%)
    • Explain the specific purpose of each allocation
  3. Milestone roadmap:
    • 3–5 key milestones for the 12–18 months following the raise
    • Each milestone includes: timeline, objective, measurable metric
  4. Suggested outline content:
    • Fundraising amount and round
    • Fund allocation breakdown
    • 12–18 month milestones
  5. Data visualization recommendations:

    Data TypePresentation FormatNotes
    Use of fundsPie chart or donut chartClearly show each allocation's percentage and amount
    Milestone roadmapTimeline graphicHorizontal timeline with key milestones and targets
    Target metricsCurrent → Target comparisone.g., "Users: 5,000 → 50,000"

Output: Fundraising ask module outline + data visualization recommendations


Phase 8: Outline Assembly & Output

Objective: Assemble outputs from the previous seven phases into a complete pitch deck outline document.

Pitch Deck Outline Template:

# [Project Name] - Fundraising Pitch Deck Outline

> Round: [Fundraising Round] | Date: [Current Date]
> Status: Draft Outline

---

## 1. Problem

### Key Points
- Core pain point: [one sentence]
- Current state: [how users cope today]
- Pain point scale: [quantified impact]

### Data Visualization Recommendations
[Phase 2 data visualization table]

### Presentation Tips
- Suggested slides: 1–2
- Key visual elements: [specific recommendations]

---

## 2. Solution

### Key Points
- Product positioning: [one sentence]
- Core value propositions:
  1. [Value point 1]
  2. [Value point 2]
  3. [Value point 3]
- Differentiation: [how it differs from competitors]

### Data Visualization Recommendations
[Phase 3 data visualization table]

### Presentation Tips
- Suggested slides: 2–3 (including product screenshots/demo)
- Key visual elements: [specific recommendations]

---

## 3. Market

### Key Points
- TAM: [amount + calculation basis]
- SAM: [amount + calculation basis]
- SOM: [amount + calculation basis]
- Growth trends: [2–3 key trends]
- Competitive landscape: [key competitors + your positioning]

### Data Visualization Recommendations
[Phase 4 data visualization table]

### Presentation Tips
- Suggested slides: 2
- Key visual elements: [specific recommendations]

---

## 4. Business Model

### Key Points
- Revenue model: [how it makes money]
- Key metrics: [3–5 core KPIs]
- Growth strategy: [core growth engine]

### Data Visualization Recommendations
[Phase 5 data visualization table]

### Presentation Tips
- Suggested slides: 1–2
- Key visual elements: [specific recommendations]

---

## 5. Team

### Key Points
- Core members: [3–5 bios]
- Team highlights: [why this team]
- Advisors/endorsements: [if applicable]

### Data Visualization Recommendations
[Phase 6 data visualization table]

### Presentation Tips
- Suggested slides: 1
- Key visual elements: [specific recommendations]

---

## 6. The Ask

### Key Points
- Fundraising amount: [amount + round]
- Use of funds: [percentage allocation]
- Key milestones: [3–5 milestones]

### Data Visualization Recommendations
[Phase 7 data visualization table]

### Presentation Tips
- Suggested slides: 1–2
- Key visual elements: [specific recommendations]

---

## Appendix

### Information To Be Provided
- [ ] [Data or information the user still needs to supply]

### Overall Deck Recommendations
- Suggested total slides: 10–15
- Suggested presentation length: 10–15 minutes
- Style recommendation: [based on industry and round]

Document output requirements:

  • All data visualization recommendations use Markdown tables
  • Each module includes three sections: Key Points + Data Visualization Recommendations + Presentation Tips
  • Use the actual current date
  • Data sources must be cited (public data / industry report / internal company data / estimate)

Workflow Control Rules

Interaction Mode Selection

Choose a mode based on how detailed the user's input is:

User InputModeBehavior
Just one sentence (< 50 words)Guided modeRun Phase 1 questions, wait for answers before proceeding
Some detail (50–200 words)Semi-automatic modeAsk 2–3 key questions while starting to build the framework
Detailed project description (> 200 words)Fully automatic modeStart directly from Phase 2, skip information gathering
User says "just write it / don't ask"Express modeOutput a complete outline based on reasonable assumptions

Quality Checklist

Before outputting the final pitch deck outline, verify each item:

  • All six modules are complete (Problem, Solution, Market, Business Model, Team, The Ask)
  • Every module includes data visualization recommendations
  • Market size includes TAM/SAM/SOM breakdown
  • Use of funds includes percentage allocation
  • Milestones include measurable metrics
  • Data sources are cited or flagged for the user to provide
  • Total slides stay within the 10–15 slide recommendation
  • Suggested slide counts per module are reasonable
  • Information To Be Provided list is non-empty (there is always data the user needs to supply)
  • No hardcoded data — all placeholders are marked with [brackets]

Adjustments by Fundraising Round

RoundFocus ModulesData RequirementsStyle
AngelProblem + Solution + TeamMore assumptions acceptable; emphasize visionConcise and punchy, under 10 slides
Pre-A / Series AMarket + Business Model + MetricsEarly business data for validation requiredData-driven, 12–15 slides
Series B+Business Model + Financials + GrowthComplete financial data requiredProfessional and rigorous, 15–20 slides

Iterative Refinement

If the user provides feedback on the outline:

  1. Identify which module the feedback applies to
  2. Re-execute from the corresponding Phase
  3. Cascade updates to all downstream content
  4. Keep data visualization recommendations consistent with the content

Output

Output is a complete fundraising pitch deck outline document in Markdown format, containing:

  • Project name, fundraising round, date, status
  • Six modules (Problem, Solution, Market, Business Model, Team, The Ask), each containing:
    • Key Points
    • Data Visualization Recommendations (Markdown table)
    • Presentation Tips (suggested slide count + key visual elements)
  • Appendix: Information To Be Provided checklist + Overall Deck Recommendations
  • All placeholders marked with [brackets]
  • Data sources cited

Reference Methodologies

This SOP incorporates the following fundraising presentation methodologies:

  • Guy Kawasaki 10/20/30 Rule: 10 slides, 20-minute presentation, 30-point font
  • Sequoia Capital Pitch Deck Template: The classic Problem → Solution → Market → Business Model structure
  • Y Combinator Application Framework: Emphasis on problem definition and traction data
  • TAM/SAM/SOM Framework: Three-tier market sizing methodology
  • Unit Economics: Core metrics including LTV, CAC, and payback period

Guardrails

Anti-patterns

  • NEVER invent traction, market size, customer evidence, or team backgrounds
  • Do NOT hardcode data — all placeholders marked with [brackets]
  • Do NOT omit any of the six modules
  • NEVER present assumptions as verified facts
  • Do NOT output a module without data visualization recommendations
  • Do NOT leave the Information To Be Provided list empty — there is always data the user needs to supply

Constraints

  • All six modules must be complete
  • Market size must have TAM/SAM/SOM three-tier breakdown
  • Use of funds must have percentage allocation
  • Milestones must have measurable metrics
  • Total slides recommended within 10–15
  • Data sources must be cited (public data / industry report / internal company data / estimate)
  • Use the actual current date

Related Skills

  • fundraising-bp-planner — Chinese version of the pitch deck outline generator, with corresponding structure
  • pitch-deck-creator — After the outline is complete, generate an editable 10-slide PPTX from structured JSON
  • business-plan-ppt — For an 18-page Chinese-style PPT visual specification and editable PPTX

About UniqueClub

Part of the UniqueClub toolkit. 🌐 https://uniqueclub.ai

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.