Article
Startup Guide

Revenue Projection Templates — Formulas for SaaS, D2C, and Marketplace Models

2026.05.05·10 min·OPENSEED

Revenue projections are the section of a business plan most often inflated — which is exactly why reviewers check them first to test your credibility. A good revenue projection isn't a big number; it's a small number where 'assumption to formula to result' holds together consistently. This guide covers revenue projection formulas for three business models — SaaS, D2C, and marketplace — and how to validate the assumptions behind them.

Intro.

#Two Approaches to Revenue Projection — Top-Down vs. Bottom-Up

The top-down approach derives revenue by multiplying market size by an assumed market share. It's fast, but low on credibility. The bottom-up approach starts from a single unit of transaction and builds up from there. It takes longer to put together, but it's the form reviewers and investors can actually verify.

ApproachExample FormulaAdvantageRisk
Top-downTAM of ₩1T x 0.1% share = ₩1BFast, conveys ambitionWeak justification, invites immediate skepticism
Bottom-upCustomer count x price x conversion rate x purchase frequencyVerifiable, builds trustTakes significant time to build
주의
If your bottom-up and top-down results differ by more than 10x, that's a sign one of your assumptions is broken. Align toward the more conservative number and re-examine your assumptions.
02

#SaaS — The Cumulative ARR Formula

Because SaaS runs on monthly or annual subscriptions, ARR (Annual Recurring Revenue) is the core metric. New signups, churn, and upsells all move ARR, so you need a cumulative model with churn built in — not a simple 'customers x price' calculation.

VariableExample ValueDescription
Monthly new signups100Summed across marketing channels
Monthly churn rate5%Share of existing customers who cancel
Monthly ARPU₩29,000Average across paid plans
Cumulative MoM customersNew signups minus churn, compoundedCompound growth model
Annual ARREnd-of-month customers x ARPU x 12The standard reporting metric

The biggest trap in SaaS revenue projections is setting churn to zero, or to some unrealistically low number. Industry-average monthly churn runs 5-7% for B2C SaaS and 1-3% for B2B SaaS, and early-stage products often run even higher. Validate your own number against your first six months of cohort data.

03

#D2C — The Order Value x Purchase Frequency Formula

For direct-to-consumer (D2C) brands — think e-commerce, food, or household goods — revenue per order and repeat purchase frequency are what matter most. The ARR concept doesn't really apply here; instead, AOV (average order value), purchase frequency, and repeat purchase rate are the key variables in your revenue projection.

VariableExample ValueRole in the Formula
Monthly visitors50,000Output of marketing efforts
Conversion rate (CR)1.5%Visitor to buyer
Average order value (AOV)₩45,000Average revenue per order
Monthly repeat purchase rate20%Share of existing buyers who purchase again
Monthly revenueVisitors x CR x AOV + repeat purchase revenueSum of both
TIP
For D2C, credibility rises significantly when you separate 'new customer revenue' from 'repeat customer revenue.' A chart where both lines grow side by side is the clearest way to show cohort health.
04

#Marketplaces — The Two-Sided GMV Formula

A marketplace connects suppliers and consumers and takes a cut of the transaction value (GMV) as a fee. The structure is revenue = GMV x take rate, and GMV often carries more signal than revenue itself.

VariableExample ValueDescription
Registered suppliers1,000Verified, active suppliers
Monthly active users (MAU)30,000On the demand side
Monthly transactions8,000Completed transactions
Average transaction value₩120,000Per transaction
Monthly GMVTransactions x average value = ₩960MTotal transaction volume flowing through the platform
Take rate10%Platform's share of revenue
Monthly revenueGMV x take rate = ₩96MRevenue actually recognized

The single most important thing to validate in a marketplace revenue projection is liquidity. The platform only works if transactions per supplier and transactions per consumer both clear a minimum threshold each month. Without explicitly stating your liquidity assumption, you end up with a GMV number that looks big but isn't grounded in reality.

05

#Scenario Analysis — Base, Best, and Worst Case

A single revenue number collapses the moment one assumption breaks. Presenting three scenarios together — base, best, and worst case — makes your projection far more credible.

ScenarioAssumptionsYear 1 Revenue (Example)
Worst caseConversion rate halved, churn 1.5x higher₩120M
Base caseRealistic assumptions as-is₩350M
Best caseConversion rate 1.5x, churn two-thirds₩720M
주의
Reviewers and investors typically make their decisions based on the worst-case scenario. Leading with only the best-case number undermines your credibility. Show them that the business survives even in the worst case.
06

#Validating Your Assumptions — Sources and Data Backing

Every assumption behind your revenue projection needs a source. 'It'll probably be like this based on experience' isn't an assumption — it's a guess. Validated assumptions come from one of four sources.

  1. Your own product's beta or MVP data — the strongest evidence available
  2. Published KPIs from competitors or comparable companies — investor materials, press coverage, industry reports
  3. Industry-average statistics — from sources like Statistics Korea, KOSIS, or the Korea Electronics and Telecommunications Industry Association
  4. Expert interviews or surveys — with the interview dates, sample size, and respondent profile clearly stated

For a core assumption like 'a 1.5% conversion rate,' cite the source right next to the number in your table. Example citation formats: 'Domestic e-commerce average conversion rate of roughly 1-2% (measured over a 5-week internal beta)' or 'Based on a competitor's publicly disclosed investor materials.'

07

#Six Common Mistakes

  1. Presenting only a hockey-stick curve — flat in Years 1-2, then a sudden spike in Year 3 — with no supporting rationale
  2. Assuming 0% churn, as if every new customer stays forever
  3. Arbitrarily setting a conversion rate more than 2x the industry average
  4. Assuming linear growth in new signups without any corresponding increase in marketing spend
  5. Ignoring seasonality or shifts in the market environment
  6. Presenting only the base case and omitting worst- and best-case scenarios
TIP
In a business plan's revenue projection, 'a big number with no basis' zeroes out your credibility instantly. The safest structure is 'a small, well-supported number plus a growth scenario.'
Summary.

#Self-Check: A Founder's Checklist

  1. Which category does your business fall into — SaaS, D2C, marketplace, or a hybrid?
  2. Did you use the formula appropriate to that model? (Avoid a plain 'customers x price' shortcut.)
  3. Does every variable in your bottom-up formula have a source or direct measurement behind it?
  4. Are worst-case, base-case, and best-case scenarios all presented together?
  5. Do your churn, repeat purchase, and conversion rate assumptions fall within industry-average ranges?
  6. Are your Year 1-3 projections tied to a corresponding increase in marketing spend?
  7. Is the gap between your top-down and bottom-up results within a reasonable range (under 10x)?
CTA
OpenSeed's CFO agent automatically checks the internal consistency of your revenue formulas, the sourcing behind your assumptions, and how complete your scenario analysis is. It's included free alongside your business plan review during the current beta.
광고

Start by Verifying the Math Behind Your Revenue Projection

Our CFO agent automatically checks your assumptions, sourcing, and scenario completeness.

🔒 Free during beta · your submission isn't saved

Start Free AI Feedback →

관련 AI 피드백 서비스.

AI 피드백
사업계획서 AI 추천
AI 피드백
IR 덱 피드백
AI 피드백
IR 자료 검토
RELATED · Same categoryStartup Guide
Business Plans With No Unit Economics at All — Why Reviewers Dock Points Immediately2026.07.12 · 8 minBusiness Plan 'Competitive Advantage' — Why an Unsupported Comparison Table Costs You Points in Review2026.07.11 · 8 minBusiness Plan Mistake Log: When You Have a 'Problem Definition' But No Customer Validation2026.07.09 · 7 minThe Business Plan Mistake Log Series — 4 Point-Losing Patterns AI Review Keeps Finding2026.07.09 · 8 min3 Patterns Where the 'Problem → Solution' Logic Breaks Down in Korean Startup Grant Business Plans2026.07.09 · 8 min
← Back to Discovery