startup-evaluation
Evaluate startup health using entrepreneurship, VC, and execution frameworks. Use when assessing a startup idea, company, pitch, due diligence target, fundraising readiness, or business model health.
git clone --depth 1 https://github.com/Mark393295827/third-brain-v5-skills /tmp/startup-evaluation && cp -r /tmp/startup-evaluation/skills/startup-evaluation ~/.claude/skills/startup-evaluationSKILL.md
# Startup Evaluation Evaluate the health of a startup, not just the attractiveness of its pitch. This skill combines: - MIT Disciplined Entrepreneurship: beachhead, customer, value, business model, validation - Timmons model: opportunity x team x resources dynamic fit - VC 5T model: Team, Target Market, Tech/Product, Traction, Terms - PMF and pretotyping: behavior evidence before build effort - Efficiency models: define the question, use MECE, test assumptions cheaply ## Usage Template **Prompt** ```text Use startup-evaluation on this company/idea. Assess startup health, evidence quality, red flags, fundraising readiness, and the next cheapest validation step. ``` **Use Case** - Founder wants a health check before building, hiring, or fundraising. - Investor wants a due diligence memo or pass/lean-in decision. - Team wants to identify the one constraint limiting progress. **Expected Result** - A structured startup health memo with scores, evidence, risks, and validation experiments. **Output Example** - Stage: Seed. Health score: 62/100. Verdict: promising but not Series A ready. Top constraint: weak retention evidence. Next test: 20-customer paid pilot with D30 retention threshold. **Verification Case** - The output separates facts, assumptions, and opinions; every score cites evidence or marks missing evidence. **Verified Effect** - Startup enthusiasm becomes a health dashboard, risk register, and concrete validation plan. ## Success Metrics - Stage, startup type, and evaluation objective are explicit. - Scores distinguish evidence-backed health from narrative confidence. - The memo identifies top constraint, fatal risks, runway status, and next cheapest test. - VC-scale companies are judged by power-law upside; bootstrapped companies are judged by cashflow and durability. ## When to Use - "Evaluate this startup." - "Is this business healthy?" - "Should I invest / join / keep building / fundraise?" - "Review my pitch deck or startup idea." - "What is the next validation experiment?" ## Startup Health Model Use this equation as the mental model: ```text Startup Health = Opportunity quality x Team quality x Evidence momentum x Capital discipline x Learning velocity - Fatal risks ``` Do not average away a fatal flaw. A brilliant market with no reachable customer, no team fit, or six weeks of runway is unhealthy. ## Step 1: Classify the Case Before scoring, classify: | Field | Options | |---|---| | Stage | idea, pre-seed, seed, Series A, growth, mature | | Startup type | lifestyle/SME, innovation-driven, VC-scale, hard tech, AI-native | | Evaluation lens | founder health check, investor due diligence, fundraising readiness, pivot decision | | Evidence state | narrative only, interviews, behavior, payment, retention, repeatable growth | If data is missing, continue with assumptions and mark confidence low. ## Step 2: Evidence Ladder Rank claims by evidence quality: | Level | Evidence | Weight | |---|---|---| | 0 | Founder belief, TAM slide, friend feedback | very weak | | 1 | Customer interviews about past behavior | weak | | 2 | Landing page, waitlist, demo usage | moderate | | 3 | Paid pilot, preorder, signed LOI, repeated use | strong | | 4 | Retention, expansion, organic referral, healthy unit economics | very strong | Quotes and intentions do not prove demand. Payment, repeated usage, retention, and referral are stronger. ## Step 3: Score Startup Health Default weights. Adjust only when stage or startup type clearly requires it. | Dimension | Weight | Healthy signal | Red flag | |---|---:|---|---| | Customer pain and beachhead | 15 | narrow painful use case, reachable buyer, urgent workflow | vague user, nice-to-have pain | | Market and timing | 15 | large/growing market or focused profitable niche, clear timing window | TAM-only logic, market too early/late | | Value proposition and 10x | 15 | 10x better, 1/10 cost, or new capability | marginal improvement | | PMF and traction | 15 | retention, payment, pull, repeatable channel | paid growth only, high churn, weak usage | | Business model and unit economics | 10 | LTV/CAC > 3, clear pricing, gross margin path | CAC unknown, payback too long | | Team and governance | 15 | founder-market fit, complementary roles, written equity/decision rules | solo gaps, cofounder conflict, weak recruiting | | Capital and runway | 10 | 12-18 month runway, milestone-based spend, financing plan | <6 month runway, unfocused burn | | Moat and risk control | 5 | data, network, distribution, regulatory or execution moat | easily copied, platform/model dependency | Score each dimension: ```text 0 = absent 1 = narrative only 2 = weak signal 3 = plausible but incomplete 4 = evidence-backed 5 = strong and repeatable ``` Final score: | Score | Status | Meaning | |---:|---|---| | 80-100 | Healthy | Scale or fundraise if risks are bounded. | | 65-79 | Promising | Continue, but fix the top constraint before major spend. | | 50-64 | Fragile | Narrow scope and validate before hiring/fundraising. | | 0-49 | Unhealthy | Pivot, pause, or redesign assumptions. | ## Step 4: VC 5T Cross-Check For VC-backed or investor-facing evaluations, add a 5T view: | 5T | Question | |---|---| | Team | Why this team? What unfair insight or execution proof exists? | | Target Market | Can this become a power-law outcome, not just a good business? | | Tech/Product | Is there defensibility beyond using current tools? | | Traction | Is growth pulled by customers and retention, not only paid push? | | Terms | Does valuation, dilution, and round structure leave room for returns? | Use the 5T view to decide whether the company is venture-scale. A healthy bootstrapped company can still be a poor VC investment. ## Step 5: AI-Native and Hard-Tech Addendum Use when relevant: | Question | Why it matters | |---|---| | Is this Type 1, 2, or 3 AI? | Tools on existing software, replacement software, or software becoming labor have different TAM and pri
Execute a daily knowledge compound closed loop — 7 Key Results from input to feedback with scoring. Use when the user wants to do a daily review, plan their day, or run a knowledge workflow.
Extract reusable knowledge from a work session and save concepts, entities, corrections, patterns, ideas, decisions, and gaps to the wiki. Use when ending a session or when the user says to extract knowledge.
Estimate and track token usage and cost across the knowledge pipeline. Run before expensive tasks to budget, after tasks to log actuals.
Health-check the knowledge wiki — find orphans, broken links, missing frontmatter, contradictions, stale content, and statistical drift. Use when the user says "lint the wiki", "health check", or periodically for maintenance.
Command multi-agent work with bounded roles, ownership, integration gates, and verification loops. Use when the user needs Claude Code Agent Teams, parallel agents, delegation strategy, or multi-agent orchestration.
Design or refactor agent skills, workflows, and operating loops for model-native Agentic Engineering. Use when making skills more autonomous, concise, verifiable, long-horizon capable, token-efficient, and lower-friction for human-LLM collaboration.
Design an AI Six Sigma Black Belt operating model for property service, maintenance dispatch, environmental testing, quote generation, CRM follow-up, and workflow quality dashboards. Use when the user needs a Property Agent OS, AI + Ontology + DMAIC management system, CTQ metrics, agent-team roles, work-order states, or MVP roadmap for operations quality.
Improve a personal or team operating system with self-evolving loops, CASH allocation, 3B creativity, predictive coding, and diagnostics. Use when the user wants to redesign a work method, learning loop, or cognitive operating system.