SaaS Metrics & Financial Due Diligence

An acqui-hire is an acquisition made primarily to recruit the target company's engineering team rather than to acquire the product, technology, or customers. The purchase price is essentially a signing bonus distributed across the team, plus the cost of the acquisition process.

Acqui-hire economics: Typical purchase price range of $1-3M per engineer being acquired. Compare this to: recruiting cost per senior engineer ($50-100K), ramp-up time value ($150-250K in lost productivity during onboarding), and failure risk (40% of external hires don't work out within 18 months). Acqui-hires can be cost-effective for acquiring pre-formed, high-performing teams.

Risks: Team may leave after retention cliff (typically 2-3 year vesting), cultural integration challenges, and technology being acquired may require maintenance resources even if it's not the primary acquisition driver.

AI COGS (Cost of Goods Sold) refers to the variable costs directly attributable to delivering AI-powered features to customers. Unlike traditional SaaS (near-zero marginal cost per user), AI features have significant per-interaction costs.

**Components of AI COGS:** - LLM API fees (OpenAI, Anthropic, Google per-token charges) - Embedding generation and vector database queries - GPU compute for inference or fine-tuning - Data retrieval and processing pipeline costs - Monitoring, logging, and observability infrastructure - Error handling, retry logic, and fallback model costs - Human-in-the-loop review costs

**Impact on SaaS economics:** Traditional SaaS enjoys 80%+ gross margins. AI-heavy SaaS products can see margins compress to 40-60%, fundamentally changing valuation multiples and capital requirements.

Annual Contract Value is the average annualized revenue per customer contract. ACV = Total Contract Value ÷ Contract Length in Years. It normalizes contracts of different lengths for comparison.

ACV segments define go-to-market strategy: micro-SaaS ($0-1K ACV) uses product-led growth, SMB ($1K-25K ACV) uses inside sales, mid-market ($25K-100K ACV) uses field sales, and enterprise ($100K+ ACV) uses enterprise sales with longest cycles.

ACV distribution matters as much as average ACV. A company with $50K average ACV might have 80% of customers at $10K and 20% at $200K. The whale accounts drive revenue but create concentration risk.

ACV trends reveal pricing power. If ACV is increasing over time, your product commands higher prices — a sign of strong product-market fit. If ACV is decreasing, you may be competing on price (dangerous) or moving downmarket.

Annual Recurring Revenue (ARR) is the annualized value of recurring subscription revenue. It's the single most important metric for SaaS businesses and is calculated by multiplying Monthly Recurring Revenue (MRR) by 12, or by summing all active annual subscription values.

ARR is the foundation of SaaS valuation. In 2026, public SaaS companies trade at 5-15x ARR depending on growth rate, retention, and profitability. Private companies in growth stage typically value at 10-30x ARR.

ARR only includes recurring revenue — one-time fees, professional services, and usage overages are excluded unless they're contractually recurring. This distinction matters for valuation because investors value predictable, recurring revenue at a significant premium over variable revenue.

ARPU (Average Revenue Per User) and ARPA (Average Revenue Per Account) measure the average revenue generated per unit. ARPU tracks individual users; ARPA tracks company accounts. For B2B SaaS, ARPA is typically more relevant because one account may have many users.

ARPA = MRR ÷ Number of Active Accounts

ARPA trends reveal pricing power and product value. Increasing ARPA means customers are buying more (expansion) or you're moving upmarket. Decreasing ARPA may indicate competitive price pressure or moving downmarket.

ARPA segmentation is critical: break ARPA by customer segment (SMB, mid-market, enterprise), cohort (customers acquired this year vs. last year), and industry. This reveals which segments drive the most value.

The Burn Multiple is a capital efficiency metric that measures how much cash a company consumes to generate each new dollar of net Annual Recurring Revenue (ARR).

**Formula:** Burn Multiple = Net Burn / Net New ARR

**Benchmarks (2025-2026):** - **< 1.0x:** Best-in-class efficiency (AI-native startups) - **1.0x - 1.5x:** Excellent - **1.5x - 2.0x:** Good / median - **2.0x - 3.0x:** Concerning - **> 3.0x:** Unsustainable

The burn multiple has emerged as one of the most important metrics for Series A and B boards because it captures capital discipline in a single number that's harder to game than growth rate alone.

Burn Multiple is a capital efficiency metric that measures how much a company burns to generate each incremental dollar of ARR. It was popularized by David Sacks of Craft Ventures.

**Formula:** Burn Multiple = Net Burn / Net New ARR

**Benchmarks:** - **< 1x:** Amazing — generating more ARR than you burn - **1-1.5x:** Great — efficient growth - **1.5-2x:** Good — acceptable efficiency - **2-3x:** Concerning — burning too much per ARR dollar - **> 3x:** Bad — very inefficient growth

**Why it matters for fundraising:** In 2025-2026, investors use burn multiple as a primary efficiency screen. Companies with burn multiples above 2x face significantly harder fundraising environments.

Burn multiple directly connects to technical debt: if engineering inefficiency means it takes 3x as many engineers to deliver the same features, your burn multiple suffers proportionally.

Burn rate is the rate at which a company is spending its cash reserves. Monthly burn rate = total monthly expenses minus total monthly revenue. Runway is how many months of cash a company has left at its current burn rate: Runway = Cash Balance ÷ Monthly Burn Rate.

For startups, burn rate is the clock ticking toward either profitability or the next fundraise. A company with $3M in the bank burning $250K/month has 12 months of runway. Best practice is to maintain at least 12-18 months of runway.

Burn multiple — burn rate divided by net new ARR — measures how efficiently you're converting spending into growth. A burn multiple below 2x is efficient. Above 3x is concerning. Above 5x means you're burning cash without proportional growth.

CAC Payback Period is the number of months it takes for a customer's contribution margin to recoup their acquisition cost. It measures how quickly your sales and marketing investment pays for itself.

CAC Payback = CAC ÷ (Monthly ARPA × Gross Margin %)

Benchmarks: under 12 months is excellent, 12-18 months is good, 18-24 months is acceptable for enterprise, above 24 months is concerning, above 36 months requires reevaluation of unit economics.

Shorter payback means faster cash recycling — you get your money back sooner and can reinvest in acquiring more customers. Longer payback means you need more upfront capital to fund growth.

Payback period is closely related to capital efficiency. Companies with short payback periods (under 12 months) can fund their own growth from customer revenue. Companies with long payback periods (24+ months) are dependent on external funding to grow.

A capitalization table (cap table) is a spreadsheet or database that records who owns what percentage of a company — all equity shares, stock options, warrants, and convertible instruments.

**Key components:** - **Common shares:** Held by founders and employees - **Preferred shares:** Held by investors (with liquidation preferences) - **Option pool:** Reserved for future employee grants (typically 10-20%) - **SAFEs/Convertible notes:** Early-stage instruments that convert to equity

**Why it matters:** A clean cap table attracts investors. A messy cap table (dead equity, unclear ownership, missing documentation) slows fundraising and can kill deals during due diligence.

Tools: Carta, Pulley, Capshare, AngelList. Manual spreadsheets work for pre-seed but become error-prone by Series A.

A capitalization table is a spreadsheet or database that shows the ownership structure of a company: who owns what percentage, how many shares, what type (common, preferred), and the resulting dilution from each funding round.

Cap table components: founders' shares (common stock), employee option pool (typically 10-20% reserved), investor shares (preferred stock with special rights), convertible notes/SAFEs (convert to equity on trigger events), and warrants.

Key cap table concepts: fully diluted ownership (including all options, warrants, and convertibles), liquidation preferences (preferred shareholders get paid first in an exit), anti-dilution provisions (protect early investors from down rounds), and option pool shuffle (pre-money vs. post-money pool creation).

Cap table management tools: Carta, Pulley, and Shareworks automate cap table tracking, option grant management, and 409A valuations.

Churn rate is the percentage of customers or revenue lost over a given period. Customer churn (logo churn) measures the percentage of customers who cancel. Revenue churn measures the percentage of recurring revenue lost.

Churn is the silent killer of SaaS businesses. Even small churn rates compound dramatically. At 5% monthly churn, you lose 46% of your customers annually. At 3% monthly churn, you lose 31%. This means you need to acquire that many new customers just to stay flat.

Net revenue churn accounts for expansion revenue. If your customers who stay are upgrading enough to offset losses from cancellations, you achieve negative net churn — the holy grail of SaaS where your existing customer base grows without any new acquisitions.

A code audit is a comprehensive review of a codebase to assess quality, security, maintainability, and hidden risks. In M&A contexts, code audits reveal technical liabilities that interviews and demonstrations can't surface.

Code audit areas: Code quality (complexity, duplication, test coverage, documentation), Security (vulnerability scanning, authentication patterns, data handling, OWASP compliance), Architecture (coupling, cohesion, scalability, single points of failure), Dependencies (outdated packages, unmaintained libraries, license risks), and Technical debt (debt density, debt distribution, debt growth rate).

Automated tools: SonarQube (quality), Snyk/Dependabot (security), CodeClimate (maintainability). Human review is essential for: architectural assessment, business logic correctness, and security threat modeling.

Cohort analysis groups customers by a shared characteristic (usually their signup month) and tracks their behavior over time. It reveals patterns that aggregate metrics hide.

The most important SaaS cohort analysis is the revenue retention curve: for each monthly cohort, what percentage of their original revenue remains after 3 months, 6 months, 12 months, and 24 months?

Healthy cohort curves flatten (customers who stay beyond month 6 tend to stay indefinitely). Unhealthy curves continue declining (customers never stop churning). The best cohort curves increase over time as expansion revenue exceeds churn — this is what negative net churn looks like at the cohort level.

Cohort analysis also reveals whether your product and acquisition are improving. If newer cohorts retain better than older cohorts, your product is getting stickier. If newer cohorts retain worse, something is degrading.

Customer Acquisition Cost is the total cost of acquiring a new customer, including all marketing spend, sales team salaries, tools, and overhead divided by the number of new customers acquired in that period.

CAC = (Total Sales & Marketing Spend) ÷ (New Customers Acquired)

CAC varies dramatically by business model: B2C SaaS averages $50-200, B2B SMB averages $200-2,000, B2B enterprise averages $5,000-50,000+. The channel mix matters — organic/inbound CAC is typically 3-5x lower than paid/outbound CAC.

CAC payback period — the number of months it takes for a customer's revenue to recoup their acquisition cost — is equally important. A $10,000 CAC with 12-month payback is healthy. A $10,000 CAC with 36-month payback is capital-intensive and risky.

Customer Acquisition Cost (CAC) is the total cost of acquiring a new customer, including all sales and marketing expenses.

**Formula:** CAC = Total Sales & Marketing Spend / Number of New Customers Acquired

**2025 benchmarks:** - B2B SaaS average: ~$1,200 per customer - Enterprise SaaS: $5,000-$50,000+ per customer - SMB SaaS: $200-$2,000 per customer - PLG SaaS: $50-$500 per customer

**Critical ratios:** - **LTV:CAC ratio:** Should be ≥ 3:1 for healthy economics - **CAC Payback Period:** Months to recover CAC from subscription revenue (ideal: < 18 months)

Customer Lifetime Value (LTV or CLTV) is the total revenue expected from a customer account over the entire duration of their relationship with your company.

**Simple formula:** LTV = ARPA × Customer Lifetime

**More precise:** LTV = ARPA / Monthly Churn Rate

Where ARPA = Average Revenue Per Account

**Example:** - ARPA: $500/month - Monthly churn rate: 2% - LTV = $500 / 0.02 = $25,000

LTV is the most important metric to pair with Customer Acquisition Cost (CAC). The LTV:CAC ratio determines whether your unit economics are sustainable.

Dilution is the reduction in existing shareholders' ownership percentage when a company issues new shares — typically during fundraising, employee option grants, or convertible note conversion.

**Typical dilution per round:** - Seed: 15-25% dilution - Series A: 20-30% dilution - Series B: 15-25% dilution - Option pool: 10-20% reserved

**Example:** A founder with 50% ownership who raises a Series A with 25% dilution now owns 37.5% (50% × 75%). After Series B with 20% dilution: 30% (37.5% × 80%).

**Anti-dilution provisions:** Investors often get anti-dilution protection (weighted-average or full-ratchet) that protects their ownership in down rounds, shifting dilution further to founders and employees.

A down round occurs when a private company raises capital from investors at a lower pre-money valuation than the valuation established in its previous financing round.

Driven by the massive zero-interest valuation hyper-inflation of 2021/2022, 2025/2026 became the hallmark era of the "Down Round." Startups that were previously valued at $1B+ (Unicorns) were forced to raise new capital at $200M-$400M valuations to survive.

Down rounds trigger severe toxic anti-dilution provisions for earlier investors, aggressively wiping out the percentage ownership of common stock held by founders and employees.

DPI (Distributions to Paid-In Capital) is a core private equity and venture capital metric that measures the ratio of actual, realized cash returned to Limited Partners (LPs) compared to the capital those LPs originally invested into the fund.

If LP investors gave a VC fund $100M, and the VC fund has returned $20M through IPOs and acquisitions, the DPI is 0.20x.

In 2025/2026, the entire venture capital landscape shifted furiously from TVPI (paper valuations) to DPI. High interest rates demanded that VCs prove they could return actual cash to investors instead of simply marking up illiquid SaaS valuations on a spreadsheet.

An earn-out is a contractual provision in M&A that makes a portion of the purchase price contingent on the acquired company achieving specified performance targets after closing. It bridges valuation gaps between buyer and seller.

Common earn-out metrics: Revenue targets (most common), EBITDA thresholds, customer retention rates, product milestones (successful migration, new features shipped), and technology integration completion.

Earn-out risks: Founder misalignment (earn-out targets may conflict with acquirer's integration priorities), Measurement disputes (how revenue is attributed in combined entity), Technology control (founders need autonomy to hit targets but acquirers want integration), and Team retention (key personnel needed for earn-out may leave during integration uncertainty).

Engineering cost allocation is the process of categorizing engineering spend into functional buckets: new feature development (innovation), maintenance and support, infrastructure, and technical debt remediation.

Healthy allocation benchmarks: 40-60% innovation (new features), 20-30% maintenance (bugs, support), 10-20% infrastructure (tooling, platform), and 5-15% debt reduction (refactoring).

The Innovation Tax problem: most organizations believe they spend 60%+ on innovation. Richard Ewing's R&D Capital Audits consistently find the actual number is 25-40%. The gap is maintenance work embedded in feature sprints — engineers fixing bugs, updating dependencies, and refactoring within "feature" stories.

Accurate cost allocation requires: time tracking (at minimum, sprint-level categorization), clear definitions of each category, and regular auditing to prevent category drift.

The Evergreen Ratio is a financial engineering metric used to protect gross margins in AI-enabled SaaS applications. It measures the percentage of AI queries that are served from pre-computed, static caches versus those requiring expensive real-time inference from a frontier model.

**Formula:** (Cached Responses / Total AI Interactions) * 100

The sweet spot for a profitable AI feature sits between 60% and 80%. An Evergreen Ratio of 0% indicates maximum financial volatility, as the company pays full compute costs for every user interaction, even for repetitive queries.

FinOps (Financial Operations) is a cloud financial management discipline that brings financial accountability to the variable cost model of cloud computing. It combines engineering, finance, and business teams to make real-time data-driven spending decisions.

FinOps operates on three phases: Inform (visibility into cloud costs), Optimize (right-size, reserve, eliminate waste), Operate (continuously manage cloud economics).

FinOps (Financial Operations) is the practice of bringing financial accountability to the variable spend model of cloud computing. It brings together technology, finance, and business teams to collaborate on data-driven spending decisions.

**Core principles:** 1. **Teams need to collaborate** — engineering, finance, and business must work together 2. **Everyone takes ownership** — engineers are accountable for the cost of their infrastructure 3. **A centralized team drives FinOps** — a cross-functional FinOps team coordinates efforts 4. **Reports should be accessible and timely** — real-time cost visibility for all stakeholders 5. **Decisions are driven by business value** — cloud spend is evaluated by the value it generates, not just the cost

For AI-heavy organizations, FinOps extends to AI cost management — tracking LLM API costs, GPU inference costs, and embedding generation costs at the feature level.

Gross margin is the percentage of revenue remaining after subtracting the cost of goods sold (COGS). For SaaS companies, COGS includes: hosting and infrastructure costs, third-party software licenses, customer support costs, and professional services costs directly tied to revenue delivery.

Gross Margin = (Revenue - COGS) ÷ Revenue × 100

Healthy SaaS gross margins range from 70-85%. Below 70% is concerning and impacts valuation multiples. Above 80% is excellent and commands premium valuations.

AI-powered SaaS products face margin pressure because AI inference costs are variable COGS. Each AI query costs compute — unlike traditional software where serving an additional user has near-zero marginal cost. This is what Richard Ewing calls the Cost of Predictivity problem.

For AI economists, gross margin is the most important financial metric after revenue growth. It determines how much money is available for R&D, sales, and profit — the engine of the business.

Gross Margin Preservation is the discipline of protecting software gross margins as AI features are added to the product. Traditional software has near-zero marginal cost of serving an additional user. AI features introduce variable inference costs (API calls, GPU compute, token usage) that erode gross margins with every interaction.

**The Margin Trap:** - Traditional SaaS gross margins: 75-85% - AI-enhanced SaaS gross margins: 50-70% - AI-native products with poor controls: 20-40%

Gross Margin Preservation strategies include: model right-sizing (using the smallest model that achieves acceptable accuracy), intelligent caching, request batching, and tiered AI access (reserving expensive models for high-value interactions).

Gross Revenue Retention measures the percentage of recurring revenue retained from existing customers, excluding expansion revenue. Unlike NRR which includes upsells, GRR only measures the revenue you keep.

GRR = (Starting MRR - Contraction - Churn) ÷ Starting MRR × 100

GRR can never exceed 100%. It measures pure retention — how much of your existing revenue you keep without any upsells or cross-sells.

Benchmarks: below 85% is poor, 85-90% is below average, 90-95% is good, 95-100% is excellent. Enterprise SaaS companies should target 95%+ GRR.

GRR is a purer measure of product stickiness than NRR because it isn't masked by expansion revenue. A company can have 120% NRR but 80% GRR — meaning they grow through aggressive upselling despite significant churn. This pattern is unsustainable.

Incident Management Cost is the true financial bleed of Sev-1 outages, calculated not just by immediate transactional revenue lost, but by the engineering capital burn of the "War Room" and SLA penalties.

The True Outage Equation: Lost Revenue + (War Room Hours × Hourly Engineer Cost) + SLA Fines = Total Cost. When a Sev-1 incident occurs, pulling 10-40 highly paid engineers off feature development into a War Room incinerates capitalized R&D wages that should have been spent on new capabilities.

Integration risk is the probability and impact of technical challenges that arise when merging two companies' technology platforms, teams, and processes after an acquisition. It's the #1 reason M&A deals fail to deliver expected value.

Common integration risks: Platform incompatibility (different tech stacks that can't easily merge), Data migration complexity (schema differences, data quality issues, compliance constraints), Team attrition (key engineers leave during integration uncertainty), Process clashes (different DevOps cultures, release cadences, quality standards), and Customer disruption (downtime, feature gaps, or UX changes during migration).

Mitigation: Identify integration risks during due diligence, not after closing. Build a 90-day integration plan before signing. Retain key engineers with structured retention packages. Use a strangler fig pattern for platform consolidation rather than big-bang migration.

Key-person dependency (also: bus factor = 1) exists when critical knowledge, skills, or relationships are concentrated in a single individual. If that person leaves, gets sick, or becomes unavailable, the organization suffers disproportionate disruption.

In technology: a single engineer who understands the legacy billing system, the architect who designed the core platform, the DevOps engineer who manages production infrastructure without documentation. In M&A due diligence, key-person dependencies are critical risk factors.

Mitigation: documentation requirements (architecture decision records, runbooks), knowledge sharing (pair programming, tech talks), cross-training programs, and retention packages for identified key persons during M&A.

Lifetime Value is the total revenue a company expects to earn from a single customer over the entire duration of their relationship. It's the fundamental metric for understanding customer value and justifying acquisition spend.

Simple LTV = Average Revenue Per Account (ARPA) × Average Customer Lifetime

For SaaS: LTV = ARPA ÷ Monthly Churn Rate (for monthly metrics) or ARPA × (1 ÷ Annual Churn Rate) for annual metrics.

More sophisticated LTV calculations account for expansion revenue, variable margins, and discount rates. A customer who starts at $500/month but expands to $2,000/month over 3 years has a very different LTV than one who stays at $500/month.

The LTV:CAC ratio is the most important unit economics metric in SaaS. A ratio of 3:1 means every dollar spent acquiring a customer generates $3 in lifetime revenue. Below 1:1 means you're losing money on every customer.

Monthly Recurring Revenue (MRR) is the predictable, recurring revenue a SaaS business earns each month from its subscription customers. MRR is the building block of ARR (Annual Recurring Revenue = MRR × 12).

MRR can be broken into components: New MRR (from new customers), Expansion MRR (upgrades and add-ons from existing customers), Churned MRR (lost from cancellations), and Contraction MRR (downgrades). Net New MRR = New + Expansion - Churned - Contraction.

Tracking MRR components gives you a much richer picture than total MRR alone. If your total MRR is growing but churned MRR is also growing, you have a leaky bucket that will eventually cap your growth.

Net Dollar Retention is the percentage change in recurring revenue from existing customers, including expansion, contraction, and churn. It measures whether your customer base is growing or shrinking independently of new customer acquisition.

NDR = (Starting MRR + Expansion - Contraction - Churn) ÷ Starting MRR × 100

NDR above 100% means your existing customers spend more over time — you grow even without new customers. NDR below 100% means your customer base is eroding.

Benchmarks: below 90% is concerning, 90-100% is average, 100-120% is good, 120-140% is excellent, 140%+ is elite. The best SaaS companies (Snowflake 158%, Datadog 130%) prove that existing customers can be the primary growth engine.

NDR is functionally identical to Net Revenue Retention (NRR). The terms are used interchangeably in the industry.

Net Revenue Retention (NRR), also called Net Dollar Retention (NDR), measures the percentage of recurring revenue retained from existing customers over a period, including expansion, contraction, and churn.

NRR is calculated as: (Starting MRR + Expansion - Contraction - Churn) ÷ Starting MRR × 100.

An NRR above 100% means your existing customers are spending more over time — you're growing even without new customers. Elite SaaS companies achieve 120-150% NRR. Snowflake famously reported 158% NRR. Below 100% means your customer base is shrinking.

NRR is the single best predictor of SaaS company valuation. Companies with 130%+ NRR trade at 2-3x higher multiples than companies with 90% NRR, even with similar growth rates.

Net Revenue Retention (NRR) — also called Net Dollar Retention (NDR) — measures the percentage of recurring revenue retained from existing customers over a period, including expansion (upgrades), contraction (downgrades), and churn (cancellations).

**Formula:** NRR = (Starting MRR + Expansion - Contraction - Churn) / Starting MRR × 100

**Benchmarks:** - **Below 90%:** Concerning — customer base is shrinking - **90-100%:** Average — some growth from existing customers - **100-120%:** Good — existing customers growing - **120-140%:** Excellent — strong expansion revenue - **140%+:** Elite — (Snowflake at 158%, Datadog at 130%)

NRR above 100% means your existing customer base grows without any new customer acquisition. This is the "holy grail" of SaaS because it means you grow even if you stop acquiring new customers.

NRR is the #1 predictor of SaaS valuation multiples. Companies with 130%+ NRR trade at 2-3x higher multiples.

Open-source license risk refers to legal and financial exposure from using open-source software in ways that violate license terms. In M&A due diligence, OSS license compliance is a critical assessment area because violations can force code rewrites, public disclosure of proprietary code, or litigation.

Risk levels by license type: Permissive (MIT, Apache 2.0, BSD) — minimal risk, allows commercial use with attribution. Weak copyleft (LGPL, MPL) — moderate risk, requires modifications to the library itself to be shared. Strong copyleft (GPL, AGPL) — high risk, may require releasing derivative works under the same license. AGPL is the highest risk for SaaS: if AGPL code is used in a network service, the entire application may need to be open-sourced.

Mitigation: SBOM (Software Bill of Materials) generation (tools: Syft, FOSSA, Snyk), license scanning in CI/CD pipeline, and OSS policy that prohibits copyleft licenses without legal review.

Operating leverage measures how effectively a company converts revenue growth into profit growth. High operating leverage means each additional dollar of revenue costs less to generate than the previous dollar — revenue grows faster than costs.

Software companies have inherently high operating leverage because the marginal cost of serving an additional customer is near-zero (for traditional software). AI features reduce operating leverage by introducing variable costs that scale with usage.

A pitch deck is a presentation (typically 10-15 slides) used by startups to communicate their business opportunity to potential investors. The standard structure follows Guy Kawasaki's 10/20/30 rule: 10 slides, 20 minutes, 30pt font.

**Essential slides:** 1. **Title/Hook:** Company name, one-line description 2. **Problem:** What pain point you solve 3. **Solution:** How your product solves it 4. **Market size:** TAM, SAM, SOM 5. **Business model:** How you make money 6. **Traction:** Growth metrics, customer logos 7. **Team:** Key team members and backgrounds 8. **Competition:** Competitive landscape and differentiation 9. **Financials:** Revenue, projections, unit economics 10. **Ask:** How much you're raising and what you'll do with it

The best pitch decks tell a story, not list features. Sequoia's pitch deck template remains the gold standard.

Platform consolidation is the process of merging multiple technology platforms — typically after an acquisition or during a portfolio company's growth — into a unified architecture. It's one of the largest, most complex, and most frequently underestimated engineering projects.

Consolidation strategies: Big-bang migration (rebuild everything at once — highest risk, fastest timeline if successful), Strangler fig (gradually replace legacy components — lowest risk, longest timeline), Parallel operation (run both platforms simultaneously — highest cost, moderate risk), and API-first integration (connect platforms via APIs without merging — lowest effort but limited consolidation).

Key success factors: Executive alignment on timeline and trade-offs, dedicated migration team (not engineers splitting time), customer communication plan, rollback strategy for each migration phase, and financial model for true total cost (including productivity loss during transition).

R&D capitalization is the accounting practice of recording certain software development costs as assets on the balance sheet rather than expenses on the income statement. Under ASC 350-40, costs incurred during the "application development stage" can be capitalized.

Three stages: Preliminary Project Stage (all costs expensed — planning, research, feasibility), Application Development Stage (costs can be capitalized — coding, testing, direct labor), and Post-Implementation Stage (costs expensed — maintenance, bug fixes, training).

What can be capitalized: developer salaries during coding, third-party software costs, testing costs, and directly related overhead. What cannot: maintenance, data conversion, general overhead, and training.

Capitalization matters because it shifts costs from the income statement (reduces current profit) to the balance sheet (spreads cost over the asset's useful life via amortization). This can significantly change reported profitability and tax liability.

Revenue recognition is the accounting principle that determines when and how revenue is recorded on financial statements. For SaaS companies, ASC 606 (the US standard) requires that revenue be recognized when performance obligations are satisfied — typically ratably over the subscription period.

Key implications for SaaS: a $120K annual contract signed in January is not $120K of January revenue. It's $10K/month recognized over 12 months. Billings (cash collected) and revenue (recognized) are different numbers.

This distinction matters for financial reporting, tax planning, and metrics. A company can have strong billings (lots of cash coming in from new annual contracts) but modest recognized revenue (because the revenue is spread over the contract term).

For AI economists, revenue recognition also affects R&D capitalization. Under ASC 350-40, certain software development costs can be capitalized rather than expensed — but only costs incurred during the application development stage, not planning or maintenance.

The Rule of 40 is a SaaS benchmark that states a healthy software company's combined revenue growth rate and profit margin should equal or exceed 40%. For example, a company growing at 30% with 10% profit margins meets the Rule of 40. A company growing at 60% can afford -20% margins.

The Rule of 40 balances growth and profitability. High-growth companies can justify burning cash if they're growing fast enough. Slower-growing companies need to show profitability. The formula is: Revenue Growth Rate (%) + EBITDA Margin (%) ≥ 40.

In 2026, the Rule of 40 has become the default benchmark for SaaS board meetings and investor presentations. Companies exceeding the Rule of 40 trade at 2-4x higher valuation multiples than those below it.

Runway is the number of months a startup can continue operating at its current spending rate before running out of cash. It's the most critical operational metric for any pre-profitable company.

Runway = Cash Balance ÷ Monthly Net Burn Rate

Net burn rate = Monthly expenses - Monthly revenue. A company with $3M cash and $250K net monthly burn has 12 months of runway.

Runway planning requires scenario modeling: what happens if revenue grows 20% slower than planned? What if a key customer churns? What if the fundraising cycle takes 6 months longer than expected?

Richard Ewing's rule of thumb: always add 6 months to your estimated time to next milestone. If you think you need 12 months of runway, you actually need 18. This buffer accounts for the inevitable surprises that consume cash faster than planned.

The SaaS Magic Number measures sales efficiency — how much new ARR is generated for every dollar spent on sales and marketing. It answers the question: "Is our sales investment paying off?"

Magic Number = (Current Quarter ARR - Previous Quarter ARR) ÷ Previous Quarter S&M Spend

Interpretation: below 0.5 means sales spend is inefficient (tighten spend). 0.5-0.75 is acceptable but room for improvement. 0.75-1.0 is good. Above 1.0 is excellent (invest more aggressively).

The Magic Number is a lagging indicator — it reflects the efficiency of sales spend from the previous period. It works best for B2B SaaS with sales-led motions and should be combined with CAC payback period for a complete picture.

SaaS valuation is the process of determining the economic value of a software-as-a-service business. SaaS companies are typically valued as a multiple of their Annual Recurring Revenue (ARR), with multiples ranging from 3x for slow-growth companies to 30x+ for high-growth, high-retention businesses.

Key factors that drive SaaS valuation multiples include: ARR growth rate, net revenue retention (NRR), gross margins, Rule of 40 score, capital efficiency, market size (TAM), competitive positioning, and team quality.

In 2026, the median public SaaS company trades at approximately 7-8x forward revenue. High-growth companies (40%+ growth) trade at 12-20x. AI-native SaaS companies with strong unit economics command premium multiples.

A Software Bill of Materials (SBOM) is a comprehensive inventory of all software components, libraries, dependencies, and their versions used in a software product. Think of it as the "ingredient label" for software — required for security compliance, license compliance, and supply chain risk management.

SBOM formats: SPDX (Linux Foundation standard), CycloneDX (OWASP standard). Executive Order 14028 (2021) requires SBOMs for software sold to the US government. Many enterprise buyers now require SBOMs as procurement prerequisites.

SBOM use cases: Vulnerability management (quickly identify if a CVE affects your dependencies — like Log4Shell), License compliance (ensure no GPL/AGPL contamination in proprietary software), Supply chain security (identify single-maintainer dependencies), and M&A due diligence (comprehensive view of technology dependencies).

Series A, B, and C are sequential rounds of venture capital financing that fund a startup's growth:

**Pre-Seed / Seed ($500K-$5M):** Product development, initial hiring, finding product-market fit. Investors: angels, micro-VCs. Typical valuation: $5-20M.

**Series A ($5M-$25M):** Scaling after PMF. Build the repeatable sales engine. Investors: early-stage VCs. Typical valuation: $20-100M. Key metric: evidence of PMF (retention, engagement).

**Series B ($15M-$75M):** Aggressive scaling. Expand markets, hire significantly. Investors: growth-stage VCs. Typical valuation: $100-500M. Key metric: revenue growth rate (2-3x YoY).

**Series C+ ($50M-$500M+):** Market dominance, international expansion, M&A preparation. Investors: growth equity, crossover funds. Key metric: path to profitability or market leadership.

Each round comes with dilution — founders typically own 10-20% by Series C.

Synthetic COGS (Cost of Goods Sold) refers to the variable, unmanaged compute costs generated by integrating LLMs and Generative AI into SaaS platforms. Unlike traditional software where compute costs per user are relatively fixed and predictable, AI features incur distinct API or compute charges for every single interaction.

Synthetic COGS can rapidly compress gross margins, especially when flat-rate subscription models are used to subsidize power users who consume disproportionate amounts of AI compute.

Technical Due Diligence (Tech DD) is the systematic evaluation of a company's technology, engineering practices, architecture, and technical debt prior to investment, acquisition, or strategic partnership. It answers the question: "Is the technology a strategic asset or a hidden liability?"

**Comprehensive Tech DD covers:** - **Architecture assessment:** Scalability, reliability, security - **Code quality:** Technical debt levels, maintenance burden, test coverage - **Team evaluation:** Skill distribution, retention risk, key-person dependencies - **AI/ML evaluation:** Model performance, inference costs, data quality - **Infrastructure:** Cloud costs, vendor dependencies, disaster recovery - **Projection:** Technical Insolvency Date, maintenance trajectory

Technical due diligence is a systematic evaluation of a target company's technology assets, architecture, team, processes, and technical risks — conducted during M&A, investment, or PE acquisition. The goal is to identify hidden technical liabilities that could destroy post-acquisition value.

Key assessment areas: Architecture quality (scalability, maintainability, security), Technical debt burden (using the Product Debt Index), Team capability (retention risk, key-person dependencies), DevOps maturity (deployment frequency, incident response), IP ownership (code ownership, OSS license compliance), and AI/data assets (training data rights, model portability).

Richard Ewing's R&D Capital Audit framework is designed specifically for PE/VC technical due diligence, providing quantitative metrics (PDI, TID, Innovation Tax) rather than subjective assessments.

Technology valuation is the process of assigning economic value to a company's technology assets — code, architecture, data, AI models, and engineering team capability. In M&A, technology valuation determines how much of the purchase price is attributable to technology (vs. revenue, brand, or customer relationships).

Valuation approaches: Replacement cost (what would it cost to rebuild from scratch?), Income approach (what revenue does the technology enable?), Market approach (what have comparable technology assets sold for?), and Richard Ewing's PDI-adjusted valuation (discount technology value based on technical debt burden and proximity to Technical Insolvency Date).

Common errors: Overvaluing code (code depreciates rapidly — the value is in architecture and team), ignoring technical debt (a platform worth $50M in replacement cost but requiring $15M in immediate debt remediation is worth $35M), and conflating team value with technology value (if key engineers leave, technology value drops dramatically).

Total Addressable Market is the total revenue opportunity available for a product or service if it achieved 100% market share. TAM is used by investors and strategists to evaluate the scale of opportunity.

TAM can be calculated top-down (use industry research: "The global SaaS market is $200B, our segment is 5% = $10B TAM") or bottom-up (count potential customers × average revenue per customer).

TAM, SAM, SOM: TAM (total market), SAM (Serviceable Addressable Market — the portion you can reach), SOM (Serviceable Obtainable Market — what you can realistically capture in 3-5 years). Investors care most about SAM and your path to capturing SOM.

VCs typically want TAM of $1B+ for venture-scale investments. Smaller TAMs can support great businesses but aren't suitable for the venture model (which requires 10-100x returns).

Unit economics measures the direct revenues and costs associated with a particular business unit — typically a customer, transaction, or product unit. In SaaS, unit economics focuses on Customer Acquisition Cost (CAC), Lifetime Value (LTV), and the LTV:CAC ratio.

Healthy SaaS unit economics have: LTV:CAC ratio of 3:1 or higher, CAC payback period under 18 months, and gross margins above 70%. When these metrics are healthy, scaling the business generates increasing returns.

For AI products, unit economics are more complex because AI features have significant variable costs (compute, API calls, inference). Richard Ewing's AI Unit Economics Benchmark (AUEB) tool helps companies calculate the true unit economics of AI features, including the Cost of Predictivity.

Venture capital due diligence is the investigation process investors conduct before committing capital. It covers technology, team, market, financials, legal, and governance.

**Technology due diligence specifically examines:** - **Architecture quality:** Scalability, maintainability, security - **Technical debt level:** Maintenance burden, deployment frequency - **Team capability:** Engineering talent depth and retention - **IP ownership:** Clear ownership of all code and technology - **Dependency risk:** Critical vendor dependencies, open-source licensing

Richard Ewing's R&D Capital Audit framework provides the quantitative assessment investors need: Product Debt Index score, Technical Insolvency Date, Innovation Tax percentage, and dollar-denominated debt.

Venture capital funding follows a structured progression of stages, each corresponding to a company's maturity, risk level, and capital needs.

Pre-Seed ($50K-500K): Idea stage. Funding from founders, friends/family, and angels. Used to validate the concept.

Seed ($500K-3M): Early product. Funding from angel investors and seed-stage VCs. Used to build MVP and find initial customers.

Series A ($3M-20M): PMF achieved. Led by institutional VCs. Used to scale the business model and hire key roles.

Series B ($15M-50M): Proven model. Led by growth-stage VCs. Used to scale aggressively into new markets and segments.

Series C+ ($50M-200M+): Market leader. Led by growth equity and crossover funds. Used for international expansion, acquisitions, or pre-IPO preparation.

Each stage has different investor expectations, valuation norms, and dilution levels. Founders typically retain 20-30% by Series B.