himself65/finance-skills

saas-valuation-compression

Analyze SaaS company valuation compression between funding rounds.

查看源码
仓库原始内容

按源仓库内容呈现,保留标题、案例、代码、表格、链接以及原文引用的演示图片。

SaaS Valuation Compression Analyzer

What This Skill Does

For a given SaaS company, research its funding history and compute ARR-based valuation multiples at each round. Then explain the compression (or expansion) using a structured framework that covers macro rates, growth trajectory, narrative shifts, and comparables.

Always render the output as an inline visualization (using the Visualizer tool) plus a concise prose explanation. Do not just return a wall of numbers.


Step-by-Step Workflow

1. Gather Data via Web Search

Search for each of the following. Run searches in parallel where possible.

For the target company:

  • [company] funding rounds valuation ARR revenue
  • [company] Series [X] raised valuation for each round
  • [company] annual recurring revenue ARR [year] for each round date
  • [company] investors lead investor [round]

For macro context:

  • SaaS ARR valuation multiples [year] private market
  • Use the known benchmark table below as fallback if search is thin.

For narrative context:

  • [company] AI customers product announcement [year] — AI narrative premium?
  • [company] growth rate churn NRR [year] — fundamentals shift?

2. Build the Data Model

For each funding round, extract or estimate:

FieldHow to get it
Round nameDirect from search
DateDirect from search
Amount raisedDirect from search
Post-money valuationDirect or compute from ownership %; if unavailable, note as estimated
ARR at round dateSearch explicitly; if not found, estimate from customer count x ARPC or interpolate
ARR multiplevaluation / ARR
Lead investorDirect

ARR estimation heuristics (when not public):

  • Seed/Series A: ARR often $500K–$3M
  • Series B: typically $5M–$20M
  • Series C: typically $20M–$60M
  • Cross-check against customer count x average deal size if available

3. Compute Compression Metrics

For each consecutive round pair (e.g., B → C):

multiple_compression_pct = (later_multiple - earlier_multiple) / earlier_multiple × 100
valuation_growth_pct = (later_val - earlier_val) / earlier_val × 100
arr_growth_pct = (later_arr - earlier_arr) / earlier_arr × 100

Key insight: valuation_growth = arr_growth + multiple_change If ARR grows faster than the multiple compresses, absolute valuation still rises.

4. Attribute Compression to Causes

Use this checklist. For each cause, rate it: Primary / Contributing / Not applicable.

Macro / Rate Environment

  • Was the earlier round during 2020–2021 ZIRP bubble? (adds ~2–5x artificial premium)
  • Was the later round during 2022–2023 rate hikes? (removes bubble premium)
  • Was the later round during or after the April 2026 Software Meltdown? (public SaaS down 40–86% from 52w highs; tariff/trade-war driven selloff crushed multiples sector-wide — even high-growth names like Figma -87%, monday.com -80%, HubSpot -70%, ServiceNow -58%)
  • Reference: SaaS private market median multiples by period:
PeriodApprox Median ARR Multiple (private)Context
2019~8–12xPre-pandemic baseline
2020~12–18xZIRP begins, multiple expansion
2021 Q1–Q3 peak~35–45xPeak bubble
2022 H2~15–20xRate hikes begin, first compression wave
2023 trough~8–12xRate plateau, valuation reset
2024~12–18xAI narrative recovery, selective re-rating
2025 H1~16–22xContinued AI-driven recovery
2025 H2–2026 Q1~10–16xTariff shock / trade-war selloff begins
2026 Q2 (Apr meltdown)~6–10xSoftware Meltdown — broad sector crash, public SaaS down 40–86% from 52w highs

(These are rough private market estimates. Public SaaS multiples are ~30–50% lower. The April 2026 figures reflect the acute selloff; private marks typically lag public by 1–2 quarters.)

Growth Deceleration

  • Did YoY ARR growth rate slow materially between rounds? (most common cause)
  • Did NRR/net retention drop?

Narrative Shift

  • Did the company lose a major product story (e.g., lost PLG thesis, missed category leadership)?
  • Did competitors emerge or incumbents catch up?

AI Premium (positive or negative)

  • Does the company serve AI-native companies (OpenAI, Anthropic, etc.) as customers? → premium
  • Did the company pivot to AI narrative credibly? → premium
  • Did the company fail to articulate AI story? → discount vs peers
  • Note: In the Apr 2026 meltdown, even strong AI narratives did not protect multiples — Snowflake (-53%), Datadog (-46%), MongoDB (-48%) all cratered despite AI tailwinds. AI premium may be necessary but not sufficient in a macro-driven selloff.

Competitive / Market

  • Market saturation signal (e.g., Okta pressure on WorkOS, Auth0 competition)
  • Customer concentration risk revealed

Investor Supply / Demand

  • Was the later round smaller and more selective? → price discipline
  • New tier of lead investor (e.g., Tier 1 growth fund vs seed fund)? → may signal higher or lower conviction

5. Build the Visualization

Use the Visualizer tool to render:

  1. Metric cards row — valuation at each round, ARR at each round, multiple at each round, compression %
  2. Line chart — ARR multiple over time for the company vs macro SaaS median
  3. Bar chart — valuation growth vs ARR growth vs multiple change (decomposition)
  4. Comparison bar — company compression vs 2–3 peer comparables (Vercel, Netlify, Fastly, or sector peers)
  5. Cause attribution table inline in prose (Primary / Contributing / N/A per factor)

See design guidance: use teal for positive/growth, coral for compression/negative, gray for macro baseline, blue for valuation figures. Follow the CSS variable system throughout.

6. Write the Prose Summary

Structure as:

  1. One-sentence verdict — e.g., "Multiple compressed 36% but ARR grew 5x, so absolute valuation rose 3.8x."
  2. Primary cause — the #1 factor explaining compression
  3. Narrative premium/discount — AI story, category leadership, or lack thereof
  4. Comparable context — how does this company's compression compare to peers?
  5. Forward implication — what would need to be true for the multiple to expand at next round?

Output Format

Always produce:

  • Inline visualization (Visualizer tool) — comes first
  • Prose summary (5–8 sentences) — follows the visualization
  • Optional: flag data confidence level if ARR had to be estimated

Known Benchmarks & Comparables (pre-loaded)

Use these as context when search results are thin or for the comparison chart.

CompanyRound pairEarlier multipleLater multipleCompression %Primary cause
VercelD → E (2021→2024)~140x~32x-77%ZIRP unwind + growth decel
WorkOSB → C (2022→2026)~105x~67x-36%Partial ZIRP unwind; defended by AI narrative
NetlifyB → stalled (2021→?)~90xN/AN/ANo new round; AI narrative absent
FastlyPublic (2021 peak→2024)~35x rev~3x rev-91%No AI pivot, growth decel
StripePrivate; est. flat/compressed 2021→2023 down round
HashiCorpAcquired by IBM 2024Acq at ~8x ARR vs ~40x peak

April 2026 Software Meltdown — Public SaaS Drawdowns

As of April 9, 2026, a broad tariff/trade-war driven selloff crushed public software valuations. Use these as reference for how private multiples will lag-compress over the following 1–2 quarters.

TickerCompanyΔ from 52w HighSector relevance
FIGFigma-86.7%Design/dev tools — worst hit
MNDYmonday.com-80.2%Work management SaaS
TEAMAtlassian-75.7%Dev tools / collaboration
HUBSHubSpot-69.9%Marketing/CRM SaaS
WIXWIX-65.1%Website builder
GTLBGitLab-63.6%DevOps
CVLTCommvault-61.7%Data protection
WDAYWorkday-59.1%HR/Finance SaaS
NOWServiceNow-57.8%Enterprise IT workflows
INTUIntuit-56.0%FinTech/SMB SaaS
SNOWSnowflake-52.8%Data cloud
KVYOKlaviyo-52.9%Marketing automation
DOCUDocuSign-52.3%eSignature
MDBMongoDB-47.9%Database
SAPSAP-47.6%Enterprise ERP
DDOGDatadog-45.7%Observability
APPAppLovin-47.6%AdTech/mobile
CRMSalesforce-42.5%CRM market leader
ADBEAdobe-34.6%Creative/doc SaaS
ZMZoom-13.9%Video/collab (already de-rated)

Source: @speculator_io, April 9, 2026. Average drawdown across tracked software names: ~50–55%.


Edge Cases

  • Down round: Multiple and absolute valuation both dropped. Note dilution implications.
  • No public ARR: Use customer count x estimated ARPC, and label as estimate with +/- range.
  • Single round only: Compute multiple vs sector median for that date; can't do compression analysis. Explain this.
  • Pre-revenue: Use forward ARR or GMV multiple if applicable; note the different basis.
  • Acqui-hire / strategic acquisition: Acquisition price often reflects strategic premium or distress, not pure ARR multiple — flag this.
来自同一仓库

更多 Skills

全部 Skills
himself65
社区

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.

安装量
2
GitHub Stars
3290
最近更新
8月27日
himself65
社区

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.

安装量
2
GitHub Stars
3290
最近更新
8月27日
himself65
社区

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".

安装量
2
GitHub Stars
3290
最近更新
8月27日
himself65
社区

estimate-analysis

Deep-dive into analyst estimates and revision trends for any stock using Yahoo Finance data. Use when the user wants to understand analyst estimate direction, how EPS or revenue forecasts changed over time, compare estimate distributions, or analyze growth projections across periods. Triggers: "estimate analysis for AAPL", "analyst estimate trends for NVDA", "EPS revisions for TSLA", "how have estimates changed for MSFT", "estimate revisions", "EPS trend", "revenue estimates", "consensus changes", "analyst estimates", "estimate distribution", "growth estimates for", "estimate momentum", "revision trend", "forward estimates", "next quarter estimates", "annual estimates", "estimate spread", "bull vs bear estimates", "estimate range", or any request about tracking or comparing analyst estimates/revisions. Use this skill when the user asks about estimates beyond a simple lookup — if they want context, trends, or analysis, this is the right skill.

安装量
2
GitHub Stars
3290
最近更新
8月27日