himself65/finance-skills / plugins/startup-tools/skills/startup-analysis
startup-analysis
VerifiedAnalyze a startup from three perspectives — VC investor, job applicant, and CEO/founder — covering market, traction, unit economics, team, defensibility, runway, equity value, culture, and competitive position, with a verdict for each. Use this skill whenever the user wants to evaluate a startup or private tech company: due diligence, whether to invest in it or join it, weighing a startup job offer, company health, outlook, or competitive position, or open-ended asks such as "what do you think of [company]" or "research [company] for me".
| File | Kind | Size |
|---|---|---|
| README.md | markdown | 2.0 KB |
| SKILL.md | skill md | 8.6 KB |
| references/ceo-framework.md | markdown | 7.8 KB |
| references/job-applicant-framework.md | markdown | 7.4 KB |
| references/vc-framework.md | markdown | 6.4 KB |
references/vc-framework.md
View on GitHub# VC Investor Due Diligence Framework
Detailed evaluation criteria for assessing a startup as a potential venture investment. Organized by stage — earlier stages weight team and market heavier, later stages weight metrics and unit economics heavier.
---
## 1. Market Opportunity
### TAM / SAM / SOM
| Term | Definition | What good looks like |
|------|-----------|---------------------|
| TAM | Total addressable market | $1B+ for venture-scale returns |
| SAM | Serviceable addressable market | $100M+ realistic near-term |
| SOM | Serviceable obtainable market | Credible path to $10M+ ARR |
**How to estimate:** Use top-down (industry reports, public comp revenue) AND bottom-up (# of potential customers × average deal size). If these converge, the estimate is more credible.
### Market Timing
- **Why now?** — What changed (technology, regulation, behavior, cost curve) that makes this possible today but not 5 years ago?
- **Secular tailwinds** — Is the market growing regardless of this company? (e.g., cloud migration, AI adoption, remote work)
- **Headwinds** — Regulatory risk, platform dependency, cyclical exposure
### Green Flags
- Market growing >20% annually
- Clear "why now" with structural shifts
- Multiple adjacent markets to expand into
- Winner-take-most dynamics
### Red Flags
- Market is shrinking or saturated
- "If only X% of a huge market" reasoning (lazy TAM)
- Heavy regulatory uncertainty with no clear path
- Market exists only because of a temporary condition
---
## 2. Product & Traction
### Product-Market Fit Signals
| Signal | Strong PMF | Weak PMF |
|--------|-----------|----------|
| Organic growth | >40% of new users from word-of-mouth | Almost all paid acquisition |
| Retention (D30) | >40% for consumer, >80% for B2B SaaS | Rapid dropoff after onboarding |
| NPS | >50 | <20 |
| Usage frequency | Daily/weekly active use | Monthly or declining |
| Customer pull | Customers asking for features, integrating deeply | Need heavy sales/success effort to retain |
### Growth Metrics by Stage
| Stage | Key metric | Good benchmark |
|-------|-----------|----------------|
| Pre-seed / Seed | User growth rate | >15% MoM |
| Series A | Revenue growth | >3x YoY, $1-3M ARR |
| Series B | Revenue growth + efficiency | >2.5x YoY, $5-15M ARR, improving unit economics |
| Series C+ | Path to profitability | >$20M ARR, positive unit economics, clear path to FCF |
### Engagement Depth
- How much of the product do users actually use?
- What's the "aha moment" and how quickly do users reach it?
- Is usage expanding within accounts (land-and-expand)?
---
## 3. Unit Economics
### Key Metrics
| Metric | Formula | Good benchmark |
|--------|---------|----------------|
| CAC | Total S&M spend / new customers | Payback <12 months (SaaS), <6 months (consumer) |
| LTV | ARPU × gross margin × (1/churn rate) | LTV:CAC > 3:1 |
| Gross margin | (Revenue - COGS) / Revenue | >60% for SaaS, >40% for marketplace |
| Burn multiple | Net burn / net new ARR | <2x (efficient), <1.5x (excellent) |
| Net dollar retention | Expansion + retained revenue / prior period revenue | >110% for B2B SaaS, >100% for SMB |
| Rule of 40 | Revenue growth % + profit margin % | >40% |
### Burn & Runway
- **Monthly burn rate** — How fast are they spending?
- **Runway** — Months of cash left at current burn
- **Burn trajectory** — Is burn accelerating or decelerating?
- **Good benchmark:** 18-24 months runway post-raise; <12 months is danger zone
---
## 4. Team Assessment
### Founder Evaluation
| Criteria | What to assess |
|----------|---------------|
| Founder-market fit | Do they have unfair insight into this problem? Domain expertise, lived experience, or unique technical capability |
| Technical depth | Can the team build the product without outsourcing core IP? |
| Execution speed | Velocity of shipping — how much have they built with how little? |
| Resilience | Have they navigated adversity before? How do they handle setbacks? |
| Storytelling | Can they recruit, fundraise, and sell with conviction? |
| Coachability | Do they take feedback? Do they learn fast? |
### Team Composition
- **CTO / technical co-founder** — Essential for technical products; red flag if all business people
- **Full-stack founding team** — Ideally covers product, engineering, and distribution
- **Early hires** — Quality of first 10-20 hires signals judgment and network
- **Advisor/board quality** — Who's helping them? Domain experts or just check-writers?
### Red Flags
- Solo non-technical founder building a technical product
- Founder team that hasn't worked together before (for first-time founders)
- High executive turnover early on
- Founders with pattern of starting and quickly abandoning companies
---
## 5. Defensibility & Moats
| Moat type | Description | Strength | Example |
|-----------|-------------|----------|---------|
| Network effects | Product gets better with more users | Very strong | Marketplace, social network |
| Switching costs | Painful to leave once adopted | Strong | Enterprise SaaS with deep integrations |
| Data moat | Proprietary data that improves the product | Strong | Training data, usage data, customer data |
| Brand / community | Trust and loyalty that's hard to replicate | Moderate | Developer tools with strong community |
| Economies of scale | Cost advantages from size | Moderate | Infrastructure, logistics |
| Regulatory / IP | Patents, licenses, regulatory approval | Variable | Biotech, fintech, defense |
| Speed / execution | Simply moving faster than competition | Weak (temporary) | Only valuable if converting to durable moat |
### Competitive Dynamics
- Who are the direct competitors? Indirect competitors?
- What happens if a FAANG/big tech company enters this space?
- Is there a platform risk (building on top of someone else's platform)?
---
## 6. Investment Verdict Framework
### Scoring
Rate each area 1-5:
| Area | Weight (Seed) | Weight (Series A+) |
|------|--------------|-------------------|
| Market | 30% | 20% |
| Team | 30% | 20% |
| Product/Traction | 20% | 30% |
| Unit Economics | 10% | 20% |
| Defensibility | 10% | 10% |
### Verdict Scale
| Verdict | Meaning |
|---------|---------|
| **Strong Invest** | Exceptional across most dimensions, clear path to venture-scale returns |
| **Lean Invest** | Good opportunity with manageable risks, worth deeper diligence |
| **Lean Pass** | Interesting but significant concerns in 1-2 critical areas |
| **Strong Pass** | Fundamental issues in market, team, or business model |
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 471k | Updated | Claude CodeCodex | Verified | Install |
| diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness. | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |