Market Sizing and Estimation Questions

Assumptions (explicit):

• City population: 1,200,000.
• Addressable demographic: adults 18–54 (primary fitness users) = 50% → 600,000.
• Active fitness consumers (attend classes/gym at least monthly) = 40% of demo → 240,000.
• Target customers open to on-demand booking (smartphone users comfortable with apps) = 70% of active → 168,000.
• Average bookings per user: 2 classes/month = 24/year.
• Average revenue per transaction (platform take + fees) = $6 (e.g., $2 booking fee + $4 commission).
• Year 1 penetration (market entry): 2% of addressable users.
• Year 3 penetration (growth): 8% of addressable users.

TAM (Total Addressable Market) — all spending by active fitness consumers if they used on-demand booking:

• TAM users = 240,000 (all active fitness consumers).
• Annual transactions = 240,000 * 24 = 5,760,000.
• TAM revenue = 5,760,000 * $6 = $34,560,000.

SAM (Serviceable Addressable Market) — addressable by app (smartphone-ready subset):

• SAM users = 168,000.
• Annual transactions = 168,000 * 24 = 4,032,000.
• SAM revenue = 4,032,000 * $6 = $24,192,000.

SOM (Serviceable Obtainable Market) — realistic share we capture:
Year 1:

• Users = 168,000 * 2% = 3,360.
• Annual transactions = 3,360 * 24 = 80,640.
• Year 1 revenue = 80,640 * $6 = $483,840.

Year 3:

• Users = 168,000 * 8% = 13,440.
• Annual transactions = 13,440 * 24 = 322,560.
• Year 3 revenue = 322,560 * $6 = $1,935,360.

Notes / sensitivity:

• ARPT sensitivity: if take-rate is $10, revenues scale proportionally.
• Frequency and penetration are the most sensitive assumptions; alternate scenarios: conservative (1% yr1 / 5% yr3) or aggressive (5% yr1 / 15% yr3).
• Use this as a baseline for go-to-market planning, CAC/LTV modelling, and to align sales/partnership targets with studio supply needs.

TAM, SAM, and SOM are hierarchical market-size estimates used to prioritize product strategy and GTM.

Definitions:

• TAM (Total Addressable Market): Total annual revenue if every potential customer in the universe bought your product. It’s the broadest view.
• SAM (Serviceable Available Market): Portion of TAM reachable given your product capabilities, geography, and target segments.
• SOM (Serviceable Obtainable Market): Realistic share of SAM you can capture in the near term given resources and competition.

Example (SaaS at $100/user/month, 100,000 potential customers):
Assumptions:

• Each customer = 1 paid user
• Price = $100/month = $1,200/year
• SAM = 40% of TAM (targeted segments/geography)
• SOM = 5% of SAM (near-term achievable share)

Formulas & calculations:

• TAM = total customers * annual price = 100,000 * $1,200 = $120,000,000
• SAM = TAM * 40% = $120,000,000 * 0.4 = $48,000,000
• SOM = SAM * 5% = $48,000,000 * 0.05 = $2,400,000

How each influences decisions:

• TAM: Sets long-term ambition and investor storytelling — “how big can this get?”
• SAM: Informs product scope and segmentation — focus features and region where product-market fit is plausible.
• SOM: Drives near-term resource allocation, sales targets, pricing experiments, and marketing channels. Prioritize high-conversion segments, build landing-page experiments, and allocate sales motions to hit SOM efficiently.

Always state assumptions, update with research, and use SOM for actionable roadmaps while keeping TAM for vision.

Framework (12-month horizon):

1. Clarify inputs/assumptions: user base (MAU), baseline conversion rate, whether conversion lift is absolute (percentage points) or relative (%), ARPU period (monthly or annual), retention delta (absolute pp), time horizon.
2. Compute incremental paying users from conversion lift:
   IncrementalUsers_conv = MAU * (conversion_lift_pp)
3. Compute incremental revenue from conversion:
   Revenue_conv = IncrementalUsers_conv * ARPU
4. Compute incremental revenue from retention:
   ExistingPaying = MAU * baseline_conversion
   AdditionalRetained = ExistingPaying * (retention_delta_pp)
   Revenue_retention = AdditionalRetained * ARPU
5. Total incremental revenue = Revenue_conv + Revenue_retention
6. ROI and payback:
   NetGain = Total incremental revenue - DevelopmentCost
   ROI = NetGain / DevelopmentCost
   Payback months = DevelopmentCost / (Total incremental revenue / 12) if annual ARPU

Example (given): Development cost = $200,000; conversion lift = +2 percentage points; ARPU = $50 (assume annual ARPU). I must assume baseline conversion and MAU; use conservative example:

• MAU = 100,000
• Baseline conversion = 5% (0.05)
• Retention delta = 1 percentage point (0.01)
• Time horizon = 12 months

Calculations:

• IncrementalUsers_conv = 100,000 * 0.02 = 2,000 users
• Revenue_conv = 2,000 * $50 = $100,000
• ExistingPaying = 100,000 * 0.05 = 5,000 users
• AdditionalRetained = 5,000 * 0.01 = 50 users
• Revenue_retention = 50 * $50 = $2,500
• Total incremental revenue = $100,000 + $2,500 = $102,500
• NetGain = $102,500 - $200,000 = -$97,500
• ROI = -$97,500 / $200,000 = -48.8%
• Payback: not recovered within 12 months (payback months ≈ 200,000 / (102,500/12) ≈ 23.4 months)

Interpretation / next steps:

• Under these assumptions the feature does not pay back in 12 months. To justify investment, either reduce cost, increase conversion lift or ARPU, improve retention delta, or target a larger MAU.
• Sensitivity: with MAU = 1,000,000 (10×), Revenue_conv = $1,000,000 and Total revenue ≈ $1,025,000 → NetGain ≈ $825,000 → ROI ≈ 412.5%.
• Use this framework in a short sensitivity table varying MAU, conversion lift, retention delta, and ARPU to guide go/no-go and prioritization.

Situation/Goal: Propose a paid enterprise feature — "SAML + SCIM + Audit Logs" for our mid-market/enterprise users to capture higher-value customers and increase ARR.

Assumptions (stated):

• Company: B2B SaaS with 12,000 active organizations (free + paid tiers).
• Target segment: companies >100 employees (enterprise-ready) = 8% of total customers.
• Pricing for the feature as an add-on: $4,000/year per account.
• Expected incremental ARPA for converted account: +$4,000/year (add-on).
• Conversion from target free/prospect segment to paid add-on = 10% first year (conservative), 20% long-run.
• One-time engineering & product launch cost: $250k (design, build, security certs, integrations).
• Ongoing annual cost (maintenance, support, infra): $60k/year.
• Sales/Marketing launch spend year 1: $40k.

TAM calculation:

• TAM segment = 12,000 * 8% = 960 enterprise-capable accounts.
• Year-1 expected conversions = 960 * 10% = 96 accounts.
• Annual revenue Year-1 = 96 * $4,000 = $384,000.

Costs Year-1 = $250k + $60k + $40k = $350k → Net Year-1 operating profit = $34k.

Payback period:

• Cumulative cashflow: After Year-1 small positive; with recurring revenue Year-2:
  • Year-2 revenue (assuming conversion grows to 15%): 144 * $4,000 = $576k.
  • Year-2 ongoing costs = $60k + $20k sales = $80k → Net Year-2 = $496k.
• Payback on initial $290k dev+marketing occurs in Year-2 (within 12–18 months).

ROI (3-year simple):

• Revenue over 3 years (conservative growth to 20% penetration): ~ $384k + $576k + $768k = $1.728M.
• Total costs (dev + 3 yrs ops + marketing) ≈ $250k + $180k + $60k = $490k.
• Net over 3 years ≈ $1.238M → ~252% return.

Sensitivity scenario:

• Best: Conversion 20% year-1 → 192 accounts → Year-1 revenue $768k; payback in <6 months; 3-yr net >$2.2M.
• Worst: Conversion 5% and ARPA discount to $2,500 (competitive pressure) → Year-1 revenue 48*$2,500=$120k; Year-1 loss ≈ $230k; payback >3 years — re-evaluate pricing/targeting.

Recommendation:

• Proceed with MVP enterprise feature, focus sales motion on existing trial-to-enterprise accounts, instrument metrics (conversion by cohort, CAC, churn), and run pricing A/B test to optimize ARPA.

Assumptions (explicit):

• Monthly visitors: 100,000 (given)
• Baseline checkout conversion: 8% (typical ecommerce; I’ll show sensitivity)
• Improvement: +2 percentage points → new conversion = 10%
• Average Order Value (AOV): $80
• Gross margin on AOV: 40% (contribution margin to P&L)
• Time window: monthly impact

Quick math — incremental orders:

• Baseline orders = 100,000 * 8% = 8,000 orders
• New orders = 100,000 * 10% = 10,000 orders
• Incremental orders = 2,000 orders/month

Revenue impact:

• Incremental revenue = 2,000 * $80 = $160,000/month

Profit (contribution) impact:

• Incremental contribution = $160,000 * 40% = $64,000/month

Comparison vs $50k/month support-cost feature:

• Feature A (conversion lift) contribution ≈ $64k/month
• Feature B (support cost reduction) = $50k/month saved
• Netier: conversion feature delivers ~$14k/month more contribution.

Other financial metrics:

• Annualized contribution: $64k * 12 = $768k
• Simple ROI ranking: Conversion feature > Support cost feature.

Considerations and caveats (prioritization factors):

• Confidence: How confident are we in achieving +2pp? If uncertain, run A/B test estimate or compute expected value (e.g., 50% chance → EV = $32k/month).
• Implementation cost & time: If conversion change requires 3 months dev at high cost, compute payback period. E.g., $150k implementation → payback ≈ 2.3 months at $64k/mo.
• Risk & strategic value: Conversion also scales with marketing efforts and improves lifetime value (LTV) if retention improves; support reduction is recurring cost saving and reduces churn risk if support issues were critical.
• Operational constraints: Support savings may free headcount for growth vs. conversion may require product/UX changes and analytics.

Recommendation framework:

• If confidence in the 2pp lift is high (good data/experiments) and implementation cost/time reasonable → prioritize conversion (higher monthly contribution, scalable impact).
• If conversion lift is speculative or costly/time-consuming while support reduction is low-risk, fast-to-deliver, and frees constrained resources → prioritize support reduction.
• Preferred pragmatic approach: Run a small pilot/A-B test for the conversion change to validate lift quickly; if validated, sequence conversion first; otherwise, choose the guaranteed $50k/month saving.

Sensitivity note: Replace baseline conversion/AOV/margin with company-specific numbers and compute expected value including probability of success and implementation cost to finalize prioritization.