startup-business-analyst-business-case
Create comprehensive startup business cases for investors. Covers market opportunity, product solutions, and financial projections.
Install
mkdir -p .claude/skills/startup-business-analyst-business-case && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/988" && unzip -o skill.zip -d .claude/skills/startup-business-analyst-business-case && rm skill.zipInstalls to .claude/skills/startup-business-analyst-business-case
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Generate comprehensive investor-ready business case document withKey capabilities
- →Structure executive summaries for investor audiences
- →Perform market opportunity and TAM/SAM/SOM sizing
- →Draft competitive differentiation analyses
- →Outline startup financial projection models
- →Define funding ask and use of proceeds
How it works
Uses a structured questionnaire-to-document flow to organize startup-specific metrics and data into a standard investor-ready format.
Inputs & outputs
When to use startup-business-analyst-business-case
- →Writing investor pitch decks
- →Strategic business planning
- →Defining startup go-to-market strategies
About this skill
Business Case Generator
Generate a comprehensive, investor-ready business case document covering market opportunity, solution, competitive landscape, financial projections, team, risks, and funding ask for startup fundraising and strategic planning.
Use this skill when
- Working on business case generator tasks or workflows
- Needing guidance, best practices, or checklists for business case generator
Do not use this skill when
- The task is unrelated to business case generator
- You need a different domain or tool outside this scope
Instructions
- Clarify goals, constraints, and required inputs.
- Apply relevant best practices and validate outcomes.
- Provide actionable steps and verification.
- If detailed examples are required, open
resources/implementation-playbook.md.
What This Command Does
Create a complete business case including:
- Executive summary
- Problem and market opportunity
- Solution and product
- Competitive analysis and differentiation
- Financial projections
- Go-to-market strategy
- Team and organization
- Risks and mitigation
- Funding ask and use of proceeds
Instructions for Claude
When this command is invoked, follow these steps:
Step 1: Gather Context
Ask the user for key information:
Company Basics:
- Company name and elevator pitch
- Stage (pre-seed, seed, Series A)
- Problem being solved
- Target customers
Audience:
- Who will read this? (VCs, angels, strategic partners)
- What's the primary goal? (fundraising, partnership, internal planning)
Available Materials:
- Existing pitch deck or docs?
- Market sizing data?
- Financial model?
- Competitive analysis?
Step 2: Activate Relevant Skills
Reference skills for comprehensive analysis:
- market-sizing-analysis - TAM/SAM/SOM calculations
- startup-financial-modeling - Financial projections
- competitive-landscape - Competitive analysis frameworks
- team-composition-analysis - Organization planning
- startup-metrics-framework - Key metrics and benchmarks
Step 3: Structure the Business Case
Create a comprehensive document with these sections:
Business Case Document Structure
Section 1: Executive Summary (1-2 pages)
Company Overview:
- One-sentence description
- Founded, location, stage
- Team highlights
Problem Statement:
- Core problem being solved (2-3 sentences)
- Market pain quantified
Solution:
- How the product solves it (2-3 sentences)
- Key differentiation
Market Opportunity:
- TAM: $X.XB
- SAM: $X.XM
- SOM (Year 5): $X.XM
Traction:
- Current metrics (MRR, customers, growth rate)
- Key milestones achieved
Financial Snapshot:
| Metric | Current | Year 1 | Year 2 | Year 3 |
|--------|---------|--------|--------|--------|
| ARR | $X | $Y | $Z | $W |
| Customers | X | Y | Z | W |
| Team Size | X | Y | Z | W |
Funding Ask:
- Amount seeking
- Use of proceeds (top 3-4)
- Expected milestones
Section 2: Problem & Market Opportunity (2-3 pages)
The Problem:
- Detailed problem description
- Who experiences this problem
- Current solutions and their limitations
- Cost of the problem (quantified)
Market Landscape:
- Industry overview
- Key trends driving opportunity
- Market growth rate and drivers
Market Sizing:
- TAM calculation and methodology
- SAM with filters applied
- SOM with assumptions
- Validation and data sources
- Comparison to public companies
Target Customer Profile:
- Primary segments
- Customer characteristics
- Decision-makers and buying process
Section 3: Solution & Product (2-3 pages)
Product Overview:
- What it does (features and capabilities)
- How it works (architecture/approach)
- Key differentiators
- Technology advantages
Value Proposition:
- Benefits by customer segment
- ROI or value delivered
- Time to value
Product Roadmap:
- Current state
- Near-term (6 months)
- Medium-term (12-18 months)
- Vision (2-3 years)
Intellectual Property:
- Patents (filed, pending)
- Proprietary technology
- Data advantages
- Defensibility
Section 4: Competitive Analysis (2 pages)
Competitive Landscape:
- Direct competitors
- Indirect competitors (alternatives)
- Adjacent players (potential entrants)
Competitive Matrix:
| Feature/Factor | Us | Comp A | Comp B | Comp C |
|----------------|----|---------| -------|--------|
| Feature 1 | ✓ | ✓ | ✗ | ✓ |
| Feature 2 | ✓ | ✗ | ✓ | ✗ |
| Pricing | $X | $Y | $Z | $W |
Differentiation:
- 3-5 key differentiators
- Why these matter to customers
- Defensibility of advantages
Competitive Positioning:
- Positioning map (2-3 dimensions)
- Market positioning statement
Barriers to Entry:
- What protects against competition
- Network effects, switching costs, etc.
Section 5: Business Model & Go-to-Market (2 pages)
Business Model:
- Revenue model (subscriptions, transactions, etc.)
- Pricing strategy and tiers
- Customer acquisition approach
- Expansion revenue strategy
Go-to-Market Strategy:
- Customer acquisition channels
- Sales model (self-serve, sales-led, hybrid)
- Customer acquisition cost (CAC)
- Sales cycle and conversion rates
Marketing Strategy:
- Positioning and messaging
- Channel strategy
- Content and demand generation
- Partnerships and integrations
Customer Success:
- Onboarding approach
- Support model
- Retention strategy
- Net dollar retention target
Section 6: Financial Projections (2-3 pages)
Revenue Model:
- Cohort-based projections
- Key assumptions
- Revenue breakdown by segment
3-Year Financial Summary:
| Metric | Year 1 | Year 2 | Year 3 |
|--------|--------|--------|--------|
| Revenue | $X.XM | $Y.YM | $Z.ZM |
| Gross Margin | XX% | XX% | XX% |
| Operating Expenses | $X.XM | $Y.YM | $Z.ZM |
| Net Income | ($X.XM) | ($Y.YM) | $Z.ZM |
| EBITDA Margin | (XX%) | (XX%) | XX% |
Unit Economics:
- CAC: $X,XXX
- LTV: $X,XXX
- LTV:CAC ratio: X.X
- CAC Payback: XX months
- Gross margin: XX%
Key Metrics Trajectory:
| Metric | Current | Year 1 | Year 2 | Year 3 |
|--------|---------|--------|--------|--------|
| MRR/ARR | $X | $Y | $Z | $W |
| Customers | X | Y | Z | W |
| Net Dollar Retention | XX% | XX% | XX% | XX% |
| Burn Multiple | X.X | X.X | X.X | X.X |
Scenario Analysis:
- Conservative, base, optimistic
- Key drivers and sensitivities
Path to Profitability:
- Break-even timeline
- Key milestones
- Unit economics at scale
Section 7: Team & Organization (1-2 pages)
Leadership Team: For each founder/executive:
- Name, title, photo (if available)
- Relevant background (2-3 sentences)
- Key accomplishments
- Why they're uniquely qualified
Current Team:
- Headcount by department
- Key hires and their backgrounds
- Advisory board
Hiring Plan:
- Year 1-3 headcount growth
- Key roles to fill
- Recruiting strategy
Organization Evolution:
Current (5 people) → Year 1 (15) → Year 2 (35) → Year 3 (60)
Engineering: 3 → 7 → 15 → 25
Sales & Marketing: 1 → 4 → 12 → 20
Other: 1 → 4 → 8 → 15
Equity & Compensation:
- Option pool sizing
- Compensation philosophy
- Retention strategy
Section 8: Traction & Milestones (1 page)
Current Traction:
- Revenue or user metrics
- Growth rate
- Key customer wins
- Product development progress
Milestones Achieved:
- Product launches
- Funding rounds
- Team hires
- Customer acquisition
- Partnerships
Upcoming Milestones (12-18 months):
- Product milestones
- Revenue targets
- Customer goals
- Team goals
- Partnership goals
Section 9: Risks & Mitigation (1 page)
Market Risks:
- Market size assumptions
- Competitive intensity
- Substitute adoption
- Mitigation strategies
Execution Risks:
- Product development
- Go-to-market effectiveness
- Hiring and retention
- Mitigation strategies
Financial Risks:
- Burn rate management
- Fundraising market
- Unit economics
- Mitigation strategies
Regulatory/External Risks:
- Compliance requirements
- Data privacy
- Economic conditions
- Mitigation strategies
Section 10: Funding Request & Use of Proceeds (1 page)
Funding Ask:
- Amount seeking: $X.XM
- Structure: Equity, SAFE, convertible note
- Target valuation: $X.XM (if applicable)
Use of Proceeds:
Total Raise: $5.0M
- Product Development: $2.0M (40%)
• Engineering team expansion
• Infrastructure and tools
• Product roadmap execution
- Sales & Marketing: $2.0M (40%)
• Sales team hiring (5 AEs)
• Marketing programs
• Demand generation
- Operations & G&A: $0.5M (10%)
• Finance/legal/HR
• Office and facilities
- Working Capital: $0.5M (10%)
• 6-month buffer
Milestones to Achieve:
- Revenue: $X.XM ARR (X% growth)
- Customer: XXX customers
- Product: Key features launched
- Team: XX employees
- Metric: Key metric targets
Expected Timeline:
- 18-24 month runway
- Achieve milestones in 15-18 months
- 6-month buffer for next raise
Next Round:
- Series A in 18-24 months
- Expected metrics at that time
- Target raise amount
Step 4: Enhance with Visuals
Suggest including:
- Charts for market sizing (TAM funnel)
- Product screenshots or mockups
- Positioning maps
- Financial trend charts (revenue, customers, burn)
- Organization chart
- Timeline/roadmap
- Use of proceeds pie chart
Step 5: Provide Additional Sections (Optional)
If Relevant, Add:
- Regulatory/Compliance section (for regulated industries)
- Technology Architecture (for deep tech)
- Clinical/Scientific Data (for biotech/health tech)
- Unit Economics Deep Dive (for complex business models)
- Strategic Partnerships (if material to strategy)
Step 6: Create Executive Summary Slide
Provide one-page summary for quick review:
- Problem & Solution (3 bullets each)
- Market: TAM/SAM/SOM
- Traction: Key metrics
- Team: Founders
- Ask: Amount and use
- Contact information
Step 7: Save Business Case
Offer to save as markdown:
- Filename: `business-case-[compan
Content truncated.
When not to use it
- →Generating marketing copy unrelated to business strategy
- →Conducting actual proprietary financial audits
Limitations
- →Requires user-provided source data for accuracy
- →Cannot validate the financial or market assumptions
How it compares
It produces a modular business case following professional fundraising standards rather than generic business planning templates.
Compared to similar skills
startup-business-analyst-business-case side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| startup-business-analyst-business-case (this skill) | 6 | 4mo | No flags | Beginner |
| internal-comms | 8 | 3mo | No flags | Beginner |
| getting-started-guide | 1 | 8mo | No flags | Beginner |
| content-creation-flow | 0 | 4mo | No flags | Intermediate |
Try saying
Example prompts that trigger this skill in your AI assistant.
More by sickn33
View all by sickn33 →You might also like
internal-comms
anthropics
A set of resources to help me write all kinds of internal communications, using the formats that my company likes to use. Claude should use this skill whenever asked to write some sort of internal communications (status reports, leadership updates, 3P updates, company newsletters, FAQs, incident reports, project updates, etc.).
getting-started-guide
Microck
当用户开始新小说项目时激活 - 通过温和的提示和解释引导他们完成七步方法论(constitution → specify → clarify → plan → tasks → write → analyze)
content-creation-flow
OutSystems
Step-by-step content creation workflow for documentation and training materials. Includes MCP validation, discovery, content design, Jira planning, and draft generation with priority-based execution. Use when starting the content creation flow, creating documentation or training materials, or when t
project-proposals
SofiaDT
When the user wants to write a project proposal, business case, project charter, or project brief to get something approved. Use when the user says "I need to write a proposal," "business case," "project charter," "getting this approved," "I need to make the case for this project," or "project brief
write-a-prd
twentyonedot
Create a PRD through user interview, codebase exploration, and module design. Use when user wants to write a PRD, create a product requirements document, or plan a new feature.
identify-kill-list
lyndonkl
Names what the substacker writer should stop doing — habits with no evidence of use, goals that became theatre, sections with 2 consecutive dormant quarters, and agents in the team whose output the writer ignores. Produces a bulleted list, each item with one sentence of why. Max 4 items. Ordered by