SaaS Revenue Model Excel Guide: 7 Steps (2026)

A SaaS revenue model Excel workbook should tell you how recurring revenue changes, how much cash the business needs, and which assumption breaks the plan first. It should not be a maze of hardcoded numbers that only its creator can explain.

This guide gives you a seven-step monthly model for a subscription business. You will connect customer growth, pricing, churn, expansion, costs, hiring, and cash in one workbook, then test a base, upside, and downside case. The goal is a model you can inspect and update, not a spreadsheet that performs confidence.

What a SaaS revenue model needs to answer

Your model has one job: turn operating assumptions into financial consequences. If trial conversion drops by two percentage points, what happens to MRR and cash six months later? If you hire two salespeople now, when must their pipeline convert? If churn rises, which hiring plan becomes unaffordable?

Keep the forecast monthly for at least 24 months. Weekly models create noise for most early-stage SaaS companies, while annual models hide timing and cash problems. Use one consistent timeline across every sheet so revenue, payroll, and cash move together.

Use a six-tab workbook structure

Use blue font or cell fill for manual inputs, black for formulas, and green for links from another tab. Add a source and last-updated note beside each assumption. This simple convention makes accidental hardcoding visible before it reaches an investor update.

Step 1: Set the timeline and assumptions

Put months across columns and assumptions down rows. Start with pricing by plan, new leads or trials, lead-to-paid conversion, monthly logo churn, expansion, contraction, payment collection timing, gross margin inputs, and hiring dates. Separate assumptions you control from outcomes you observe.

Do not enter one global growth percentage and call it a forecast. Model the operating driver behind growth. A self-serve product may start with website signups, activation, and paid conversion. A sales-led product may start with qualified opportunities, win rate, sales-cycle lag, and average contract value.

Give every rate an explicit unit. Store 3% monthly churn as 0.03, not 3. Label whether a price is monthly, annual, per seat, or per account. Most spreadsheet errors are not advanced mathematics; they are silent disagreements about units.

Step 2: Forecast customers by plan

For each plan, calculate opening customers, new customers, churned customers, and closing customers. The basic monthly formulas are: new customers equals qualified demand multiplied by conversion rate; churned customers equals opening customers multiplied by monthly logo churn; closing customers equals opening plus new minus churned.

Round customer counts only for presentation. Keep decimal values in the calculation layer because rounding every month compounds distortion. If your business has annual contracts, model renewal eligibility separately instead of applying monthly churn to customers who cannot cancel that month.

For a cohort-based version, create one row for each acquisition month. Move each cohort across the forecast using an age-specific retention curve. This takes more work but gives a better picture when onboarding improvements or early-life churn materially change retention.

Step 3: Build the MRR movement schedule

Start each month with opening MRR. Add new MRR and expansion MRR, then subtract contraction and churned MRR. Ending MRR equals opening MRR plus new plus expansion minus contraction minus churn. The next month’s opening MRR must link to the previous month’s ending MRR.

New MRR can be new customers multiplied by starting monthly price. Churned MRR should ideally use the revenue attached to customers expected to churn, not a generic customer count multiplied by a blended price. Expansion and contraction can be modeled as percentages of opening MRR until you have enough historical data for plan-level behavior.

Keep bookings, MRR, billings, collections, and recognized revenue separate. An annual contract signed today may create annual recurring revenue immediately, an invoice this month, cash after payment terms, and revenue recognized across twelve months. Combining those measures makes a healthy business look cash-rich or a cash-rich month look profitable.

Step 4: Model gross margin and operating costs

Calculate cost of revenue from the expenses required to deliver the service: hosting, third-party usage tied to customers, payment fees, and customer support or success costs according to your accounting policy. Gross profit equals recognized revenue minus cost of revenue. Gross margin equals gross profit divided by recognized revenue.

Model payroll employee by employee or role by role with a start month, monthly cash cost, and applicable taxes or benefits. Then add non-payroll expenses such as software, legal, rent, contractors, and marketing. A fixed percentage of revenue is acceptable for a first pass, but replace it with operating drivers where decisions matter.

Put hiring in the assumptions tab, not inside formulas. That makes it easy to delay a hire in the downside case without editing twelve cells. Include recruitment lag and ramp time for revenue roles; a salesperson starting in April does not produce a mature quota in April.

Step 5: Convert the forecast into cash and runway

Begin with opening cash. Add collections, financing, and other cash inflows. Subtract payroll, vendor payments, taxes, capital spending, debt payments, and other outflows. Closing cash equals opening cash plus inflows minus outflows, and it becomes the next month’s opening cash.

Model payment timing instead of assuming revenue equals cash. Annual prepayments may improve cash before the related revenue is recognized. Enterprise invoices may be collected 30 or 60 days after billing. Failed payments and refunds create another gap between expected and actual collections.

Runway is not simply current cash divided by last month’s burn when the team is hiring or collections are seasonal. Use the monthly closing cash row to identify the first month below your minimum cash threshold. That date is the decision deadline your operating plan must respect.

Step 6: Add base, upside, and downside scenarios

Create one scenario selector cell and a three-column assumption table. The base case should reflect the most defensible current evidence. The upside case should require identifiable causes such as higher conversion after a tested onboarding change. The downside case should combine plausible pressure on acquisition, churn, and collection timing.

Use Excel’s INDEX, XLOOKUP, or CHOOSE function to pull the active scenario into the model. Do not duplicate the entire workbook three times. Duplicated models drift, and soon your downside case contains formulas fixed only in the base case.

Track the assumptions with the largest effect on cash-out date, not just final ARR. For many SaaS companies those variables are conversion, net revenue retention, hiring start dates, annual prepayment share, and gross margin. Change one at a time first, then test combinations.

Step 7: Add checks and decision outputs

Add a checks section that must equal zero or return OK. Opening customers must link to prior closing customers. The MRR movement schedule must reconcile. The balance sheet or cash roll-forward must balance. No active customer count, MRR, or cash collection should become negative without an explicit reason.

Your summary tab should show ending MRR, ARR, net new MRR, customer churn, net revenue retention, gross margin, burn, closing cash, runway, and the next financing or profitability milestone. Show the plan beside actuals once a month closes. A forecast without variance analysis becomes fiction with formatting.

Assign each material variance to an owner and a decision. If paid conversion is below plan, decide whether to change acquisition spend, onboarding, pricing, or the forecast. If you simply replace the old forecast with actuals, you erase the evidence that would improve the next model.

Worked example: from customer assumptions to MRR

Suppose you open January with 200 customers paying an average of $100 per month, so opening MRR is $20,000. You expect 40 new customers, 2% monthly logo churn, 1.5% expansion, and 0.5% contraction.

New MRR is $4,000. Churned MRR is $400, expansion is $300, and contraction is $100. Ending MRR is $23,800: $20,000 plus $4,000 plus $300 minus $100 minus $400. February must start with that $23,800, not a separate manually entered figure.

Now change churn from 2% to 3% in the downside scenario and let the effect compound for 24 months. The gap is not limited to one month of lost revenue; every churned account also removes future recurring revenue and possible expansion. That is why scenario logic belongs inside the model, not in a note below it.

When Excel stops being enough

Excel is strong for assumptions, scenarios, financing plans, and one-off board questions. It becomes risky when actuals depend on repeated CSV exports, customer identities differ across systems, multiple people overwrite formulas, or the model must refresh every day.

Keep forecasting in Excel if it suits your team, but pull actual operating metrics from the source database. With AI for Database, you can ask for MRR movements, churn, conversion, and usage in plain English, save the answers as self-refreshing dashboards, and send an email, Slack message, or webhook when an actual metric crosses a threshold.

A practical split is simple: Excel owns assumptions and scenarios; your database owns actual customer and transaction records. Compare them on a fixed cadence. This preserves the flexibility of a model without pretending copied exports are a live reporting system.

Questions founders ask about SaaS revenue models

I need a SaaS revenue model in Excel. What should I include first?

Start with monthly customers by plan, MRR movements, recognized revenue, cost of revenue, payroll, other operating costs, collections, and closing cash. Add scenario analysis only after those schedules reconcile.

Should a SaaS revenue model use MRR or recognized revenue?

Use both because they answer different questions. MRR tracks the recurring run rate, while recognized revenue supports the income statement. Billings and collections belong in separate schedules for cash planning.

How far should a SaaS model forecast?

Use at least 24 monthly columns for operating and fundraising decisions. Extend to 36 or 60 months when investors require it, but treat distant years as directional because small assumption errors compound.

Can I connect an Excel forecast to live SaaS data?

Yes, but keep the responsibilities clear. Use live database data for actuals and Excel for assumptions and scenarios. Automate the comparison only after customer IDs, metric definitions, and timing rules are consistent.

Build the smallest model that changes a decision

Start with customers, MRR, costs, and cash. Make every input visible, every movement reconcilable, and every scenario tied to an operating cause. Then review forecast versus actuals monthly and update assumptions only when the evidence changes.

If your actuals already live in PostgreSQL, MySQL, Supabase, MongoDB, BigQuery, or another supported database, use AI for Database to query them without SQL, keep the core metrics refreshed, and alert the team when reality diverges from the plan. Try it at aifordatabase.com.