A SaaS pricing calculator helps you test tiers, discounts, conversion assumptions, and upgrade paths before they appear on your launch page. This guide provides a repeatable worksheet for estimating launch revenue, comparing monthly and annual plans, checking gross margin, and translating pricing decisions into clearer calls to action.
Overview
Pricing is not only a number on a pricing page. It is a set of linked assumptions about who buys, which plan they choose, how often they pay, what it costs to serve them, and how their account may expand over time. A useful SaaS pricing model template makes those assumptions visible instead of allowing them to remain hidden in a launch forecast.
Use the model to answer practical questions such as:
- What monthly recurring revenue could a launch generate at different signup and conversion rates?
- Does an annual discount improve upfront cash without reducing contribution margin too far?
- How many customers or qualified leads are needed to reach break-even?
- Which plan should the launch landing page emphasize?
- When should a customer move from an entry tier to a higher tier?
The model is not a prediction. It is a decision tool. Its value comes from comparing scenarios consistently and showing which assumptions have the greatest effect on the result. Pair the calculation with a product launch landing page template so the promise, audience, plan structure, and call to action remain aligned.
How to estimate
Start with one customer cohort and one pricing scenario. Avoid building a complex forecast before the basic arithmetic is clear.
1. Calculate revenue by plan
For each tier, multiply the number of paying customers by the price they pay during the selected period.
Monthly recurring revenue = paying customers × monthly price
For annual plans, convert the contract value into a monthly equivalent when comparing recurring revenue:
Monthly equivalent revenue = annual customers × annual price ÷ 12
Keep annual cash collected separate from monthly recurring revenue. An annual customer may pay the full contract value at the start of the term, but the revenue comparison should still use a consistent time basis.
2. Estimate customers from the funnel
Connect the pricing model to launch demand. A simple funnel might include visitors, email signups, trial starts, and paid customers.
Paid customers = qualified visitors × trial or demo rate × paid conversion rate
If the landing page receives 10,000 qualified visitors, 8% start a trial, and 20% of trials become paid accounts, the estimate is 160 customers: 10,000 × 0.08 × 0.20. That figure should then be divided among plans using an explicit mix assumption, such as 60% entry, 30% middle, and 10% highest tier. The percentages are planning inputs, not universal benchmarks.
3. Add discount and payment effects
A SaaS discount calculator should show the difference between list price and collected price.
Discounted price = list price × (1 − discount rate)
If a plan is priced at 100 per month and the discount is 20%, the discounted price is 80 per month. Then subtract payment-processing costs, refunds, credits, and other variable costs that apply to each transaction.
Contribution margin = collected revenue − variable costs
Contribution margin percentage = contribution margin ÷ collected revenue × 100
Use the same cost definitions across every scenario. Otherwise, an apparently better discount may simply be benefiting from incomplete cost inputs.
Inputs and assumptions
Put the following inputs in a worksheet with one row per plan and a separate section for funnel assumptions. Record the date and owner for each input so the model can be updated without guesswork.
Plan structure
- Plan name: Use a customer-facing name and an internal label if they differ.
- Monthly list price: The price before promotional reductions.
- Annual list price: The total amount charged for a year, if available.
- Discount depth: Record launch discounts, annual discounts, coupons, and credits separately.
- Included limits: Seats, usage, projects, storage, or other measurable boundaries.
- Upgrade trigger: The event that makes a higher tier relevant.
Demand and conversion
- Landing-page visitors by source
- Waitlist or email signup rate
- Trial, demo, or checkout-start rate
- Paid conversion rate
- Expected plan mix
- Refund, cancellation, or failed-payment allowance
Keep traffic sources separate when possible. Visitors from a product launch announcement may behave differently from visitors searching for a solution. A blended conversion rate can hide that difference and make the forecast harder to improve.
Costs and expansion
Include payment fees, infrastructure, support, onboarding, sales commissions, and other costs that rise with customer count or usage. If you do not know an input yet, label it as an assumption rather than presenting it as a fact.
Expansion revenue should be modeled separately from initial conversion. For example:
Expansion revenue = starting customers × expansion rate × average expansion amount
Only include expansion after defining what causes it: additional seats, higher usage, a plan upgrade, or an add-on. This makes the upgrade path useful for both the forecast and the pricing page copy.
Worked examples
Consider a simple launch scenario with three plans:
- Starter: 100 per month
- Growth: 180 per month
- Scale: 350 per month
Assume the launch produces 160 paying customers, distributed as 60% Starter, 30% Growth, and 10% Scale. That creates 96 Starter customers, 48 Growth customers, and 16 Scale customers.
The estimated monthly recurring revenue is:
- Starter: 96 × 100 = 9,600
- Growth: 48 × 180 = 8,640
- Scale: 16 × 350 = 5,600
Total estimated MRR: 23,840
Now compare a 20% first-year discount applied to all plans. The monthly equivalent becomes 19,072 before variable costs. The discount reduces modeled revenue by 4,768 per month at the same customer count, so the team must decide what improvement in conversion, annual prepayment, or retention would justify it.
A better comparison is not simply “discount versus no discount.” Create at least three scenarios:
- Base: List prices, expected plan mix, and current conversion assumptions.
- Discount: Reduced price with a clearly stated expected change in conversion or annual-plan adoption.
- Conservative: Lower traffic, weaker conversion, higher support cost, or a less favorable plan mix.
Then connect each scenario to the launch page. If the Growth plan is the intended upgrade path, explain the limit it removes and make that benefit visible near the primary call to action. If an annual plan is important for cash flow, show its total price and equivalent monthly rate without making the comparison confusing. For broader launch planning, the marketing ROI and break-even calculator guide can help connect pricing output to acquisition costs and launch spend.
When to recalculate
Revisit the SaaS pricing calculator whenever a material input changes, not only at the end of a campaign. Recalculate before publishing a new pricing page, changing plan limits, introducing an annual option, adding a launch discount, or changing payment terms.
Update the model after an experiment has enough results to inform a decision. Compare actual visitors, signup rates, paid conversion, plan mix, refund behavior, and support effort with the original assumptions. Do not overwrite the original scenario; preserve it so the team can see what changed.
Review payment-processing assumptions and other variable costs when rates, currencies, billing tools, or transaction patterns change. Refresh the model when product usage grows enough to affect infrastructure or support costs. Revisit expansion assumptions when customers begin reaching plan limits or using upgrade features.
A practical review workflow is:
- Duplicate the current worksheet and date the copy.
- Mark every changed input, including price, discount, conversion, plan mix, and cost.
- Run base, conservative, and upside scenarios.
- Compare contribution margin and break-even timing, not revenue alone.
- Update the pricing page headline, plan descriptions, FAQs, and calls to action to match the selected scenario.
- Record the decision and the next condition that will trigger another review.
Pricing becomes easier to manage when the model is treated as a living launch tool. Keep the worksheet simple enough to inspect, separate known values from assumptions, and connect every important number to a customer behavior or page element. That approach gives the team a clearer basis for experiments without pretending that a forecast can remove uncertainty.
