Startup Analysis
Analyze a startup from three perspectives: VC investor, job applicant, and CEO/founder. Use this skill whenever the user wants to evaluate a startup, assess whether to invest in or join a startup, do due diligence, evaluate a job offer from a startup, understand a startup's competitive position, or assess company health and trajectory. Triggers: "analyze this startup", "should I join [company]", "is [company] a good investment", "evaluate [company]", "due diligence on [company]", "what do you think of [startup]", "should I take this startup job offer", "how healthy is [company]", "startup assessment", "company analysis", "is [company] worth joining", "what's the outlook for [company]", "research [company] for me", any mention of evaluating or assessing a startup or tech company from investment, career, or strategic perspectives — provide all three perspectives by default.
MCP get_skill({ skillId: "startup-analysis-6631ae03" })Use this skill with your agent
Create a free account and connect via MCP
# Startup Analysis Produces a multi-perspective analysis of a startup, examining it through three lenses that each reveal different aspects of company health and potential: 1. **VC Investor Lens** — Is this a good investment? Market size, unit economics, growth trajectory, team quality, defensibility 2. **Job Applicant Lens** — Should I work here? Equity value, runway risk, culture signals, career growth, compensation fairness 3. **CEO/Founder Lens** — How healthy is this company? Product-market fit, burn efficiency, competitive moat, organizational health Each perspective surfaces insights the others miss. A company can be a great investment but a terrible place to work (or vice versa). The goal is to give the user a 360-degree view so they can make informed decisions. --- ## Step 1: Gather Information Before analyzing, collect as much public information as possible about the startup. Use web search, the company's website, Crunchbase data, press coverage, and any other available sources. **Key data to gather:** | Category | What to find | |----------|-------------| | **Basics** | Founded year, HQ location, employee count, what the product does | | **Funding** | Total raised, last round (size, date, valuation if known), key investors | | **Product** | What they sell, who buys it, pricing model, key competitors | | **Traction** | Users, revenue (if public), growth signals, notable customers | | **Team** | Founders' backgrounds, key hires, LinkedIn headcount trends | | **Market** | Industry, market size estimates, tailwinds/headwinds | | **News** | Recent press, product launches, partnerships, layoffs, pivots | If certain data isn't publicly available (e.g., revenue for private companies), note the gap and infer what you can from indirect signals (hiring pace, customer logos, web traffic proxies, job postings). ### When information is insufficient Many startups — especially early-stage or niche ones — have limited public presence. If web search does not return enough information to produce a meaningful analysis (e.g., you can't determine what the company does, who founded it, or how it's funded), **ask the user to provide the company's website URL** before proceeding. The company website is often the single most information-dense source, and reading it directly (about page, pricing page, team page, blog) can fill most gaps. You can also ask the user for: - The company's website or landing page URL - A Crunchbase, LinkedIn, or PitchBook link - Any pitch deck, job listing, or press article they have - Specific context they already know (e.g., "they just raised a Series A from Sequoia") It is better to ask for a URL and produce an accurate analysis than to guess and produce a misleading one. --- ## Step 2: Determine Which Perspectives to Cover By default, produce all three perspectives. If the user specifies a particular angle (e.g., "I'm considering joining them" or "should I invest"), emphasize that perspective but still include the others as context — they often reveal relevant information. | User's situation | Primary perspective | Still include | |-----------------|-------------------|---------------| | Considering investing | VC Investor | Job Applicant (talent signal), CEO (operational health) | | Considering a job offer | Job Applicant | VC Investor (funding runway), CEO (strategic direction) | | Running the company / advisory | CEO/Founder | VC Investor (how investors see you), Job Applicant (talent attractiveness) | | General curiosity / research | All equally | — | --- ## Step 3: Analyze from Each Perspective Read the relevant reference files for the detailed framework for each perspective. These contain the specific criteria, metrics, and red/green flags to evaluate. ### VC Investor Analysis Read `references/vc-framework.md` for the full evaluation framework. Core areas to assess: - **Market opportunity** — TAM/SAM/SOM, market timing, secular trends - **Product & traction** — Product-market fit signals, growth metrics, retention - **Unit economics** — CAC, LTV, margins, burn multiple, path to profitability - **Team** — Founder-market fit, technical depth, hiring ability - **Defensibility** — Moats (network effects, switching costs, data, brand, regulatory) - **Deal terms context** — Stage-appropriate valuation, comparable exits Produce a clear **Investment Thesis** (bull case) and **Key Risks** (bear case). End with a verdict: Strong Pass / Lean Pass / Lean Invest / Strong Invest, with reasoning. ### Job Applicant Analysis Read `references/job-applicant-framework.md` for the full evaluation framework. Core areas to assess: - **Financial stability** — Runway, burn rate, funding trajectory, revenue health - **Equity value** — Option/equity package analysis, dilution risk, liquidation preferences, realistic exit scenarios - **Career growth** — Role scope, learning opportunity, resume value, mentorship - **Culture & work-life** — Glassdoor signals, employee tenure data, leadership style - **Product & market risk** — Is PMF real? What happens if the startup fails? - **Red flags** — High turnover, constant pivots, vague metrics, founders cashing out Produce a clear **Why Join** (pros) and **Watch Out For** (risks). End with a verdict: Strong Pass / Lean Pass / Lean Join / Strong Join, with reasoning. ### CEO/Founder Analysis Read `references/ceo-framework.md` for the full evaluation framework. Core areas to assess: - **Product-market fit** — Retention curves, organic growth, Sean Ellis test proxy - **Growth efficiency** — Burn multiple, CAC payback, magic number - **Competitive position** — Moat strength, competitive dynamics, market share trajectory - **Organizational health** — Hiring pipeline, attrition, team capability gaps - **Fundraising readiness** — Metrics vs. benchmarks for next round, investor narrative - **Strategic risks** — Platform dependency, customer concentration, regulatory exposure Produce a clear **Strengths to Double Down On** and **Urgent Areas to Address**. End with a health grade: Critical / Struggling / Stable / Strong / Exceptional, with reasoning. --- ## Step 4: Synthesize Cross-Perspective Insights After the three analyses, add a synthesis section that highlights: 1. **Where perspectives agree** — If all three lenses flag the same strength or weakness, it's probably real 2. **Where perspectives diverge** — A company can be VC-attractive (huge market) but employee-risky (high burn, low runway). Call these out. 3. **The bottom line** — One paragraph summary: what kind of company is this, what's its most likely trajectory, and what should the user do based on their stated (or implied) situation --- ## Step 5: Present the Report Structure the output as a clean, scannable report: ``` # [Company Name] — Startup Analysis ## Summary [2-3 sentence overview with key verdict] ## VC Investor Perspective ### Market Opportunity ### Product & Traction ### Unit Economics (if available) ### Team ### Defensibility ### Investment Verdict: [Strong Pass / Lean Pass / Lean Invest / Strong Invest] [Reasoning] ## Job Applicant Perspective ### Financial Stability ### Equity Value Assessment ### Career Growth Potential ### Culture & Work-Life Signals ### Risk Factors ### Employment Verdict: [Strong Pass / Lean Pass / Lean Join / Strong Join] [Reasoning] ## CEO/Founder Perspective ### Product-Market Fit Assessment ### Growth Efficiency ### Competitive Position ### Organizational Health ### Strategic Risks ### Health Grade: [Critical / Struggling / Stable / Strong / Exceptional] [Reasoning] ## Cross-Perspective Synthesis ### Points of Agreement ### Points of Divergence ### Bottom Line ``` Adapt section depth to available data — if financials are completely opaque, say so and focus on what's observable. Don't fabricate metrics, but do make informed inferences and state your confidence level. --- ## Reference Files - `references/vc-framework.md` — VC due diligence checklist with metrics, benchmarks, and red/green flags - `references/job-applicant-framework.md` — Job seeker evaluation framework with equity analysis and culture assessment - `references/ceo-framework.md` — CEO self-assessment framework with operational metrics and strategic analysis Read these when you need the detailed criteria and benchmarks for each perspective.
Related Skills
More skills in Business, Marketing & Sales
Ab Testing
When the user wants to plan, design, or implement an A/B test or experiment, or build a growth experimentation program. Also use when the user mentions "A/B test," "split test," "experiment," "test this change," "variant copy," "multivariate test," "hypothesis," "should I test this," "which version is better," "test two versions," "statistical significance," "how long should I run this test," "growth experiments," "experiment velocity," "experiment backlog," "ICE score," "experimentation program," or "experiment playbook." Use this whenever someone is comparing two approaches and wants to measure which performs better, or when they want to build a systematic experimentation practice. For tracking implementation, see analytics. For page-level conversion optimization, see cro.
Ab Test Setup
When the user wants to plan, design, or implement an A/B test or experiment. Also use when the user mentions "A/B test," "split test," "experiment," "test this change," "variant copy," "multivariate test," "hypothesis," "conversion experiment," "statistical significance," or "test this." For tracking implementation, see analytics-tracking.
Ab Test Setup
Ab Test Setup linked from Corey Haines marketing skills, with the upstream skill instructions available on GitHub.
Ab Test Store Listing
When the user wants to A/B test App Store product page elements to improve conversion rate. Also use when the user mentions "A/B test", "product page optimization", "test my screenshots", "test my icon", "conversion rate optimization", "CPP", or "custom product pages". For screenshot design, see screenshot-optimization. For metadata optimization, see metadata-optimization.
Account Research
Research a company or person and get actionable sales intel. Works standalone with web search, supercharged when you connect enrichment tools or your CRM. Trigger with "research [company]", "look up [person]", "intel on [prospect]", "who is [name] at [company]", or "tell me about [company]".
Account Research
Research a company using Common Room data. Triggers on 'research [company]', 'tell me about [domain]', 'pull up signals for [account]', 'what's going on with [company]', or any account-level question.
Explore Other Categories
Skills from other categories with shared topics
Company Valuation
Estimate the intrinsic value of a public company using DCF, relative (peer multiple) and sum-of-parts (SOTP) methods, then triangulate to an implied share price with upside/downside versus the current market price. Use this skill whenever the user asks: "what is AAPL worth", "valuation of NVDA", "fair value of TSLA", "intrinsic value", "DCF for MSFT", "build a DCF", "discounted cash flow", "WACC", "terminal value", "implied share price", "upside to fair value", "is X overvalued/undervalued", "relative valuation", "peer comparison valuation", "EV/EBITDA target", "SOTP", "sum of the parts", "how much is [company] worth", "price target from fundamentals", "value this company", or any ticker in the context of computing intrinsic or relative valuation. Default to running ALL three methods (DCF + relative + SOTP-if-applicable) and presenting a blended implied price with a sensitivity table. Do not answer valuation questions from memory — always run the workflow.
Earnings Preview
Generate a pre-earnings briefing for any stock using Yahoo Finance data. Use this skill whenever the user wants to prepare for an upcoming earnings report, understand what analysts expect, review a company's beat/miss track record, or get a quick overview before an earnings call. Triggers include: "earnings preview for AAPL", "what to expect from TSLA earnings", "MSFT reports next week", "earnings preview", "pre-earnings analysis", "what are analysts expecting for NVDA", "earnings estimates for", "will GOOGL beat earnings", "earnings beat/miss history", "upcoming earnings", "before earnings", "earnings setup", "consensus estimates", "earnings whisper", "EPS expectations", "what's the street expecting", "earnings season preview", any mention of preparing for or previewing an earnings report, or any request to understand expectations ahead of a company's earnings date. Always use this skill when the user mentions a ticker in context of upcoming earnings, even if they don't say "preview" explicitly.
Earnings Recap
Generate a post-earnings analysis for any stock using Yahoo Finance data. Use when the user wants to review what happened after earnings, understand beat/miss results, see stock reaction, or get an earnings recap. Triggers: "AAPL earnings recap", "how did TSLA earnings go", "MSFT earnings results", "did NVDA beat earnings", "post-earnings analysis", "earnings surprise", "what happened with GOOGL earnings", "earnings reaction", "stock moved after earnings", "EPS beat or miss", "revenue beat or miss", "quarterly results for", "how were earnings", "AMZN reported last night", "earnings call recap", or any request about a company's recent earnings outcome. Use this skill when the user references a past earnings event, even if they just say "AAPL reported" or "how did they do".