The SaaS Pricing Calculator works backwards from the price most founders guess at: it starts with what each user costs you to serve, applies the gross margin you need, and returns the monthly price that makes the unit economics work, along with what your current or proposed price implies for margin, MRR, ARR, and CAC payback.
How It Works
Cost to serve per user is either the direct figure you enter, or the sum of infrastructure, support, and third-party costs per user. Price then follows the margin identity: to keep a given gross margin, price must equal cost divided by one minus the margin.
If you also enter a proposed price, the calculator reports the actual gross margin that price delivers. With a customer count it projects MRR and ARR at the evaluated price, and with a CAC figure it computes CAC payback in months: the acquisition cost divided by the monthly gross profit per user.
Parameters
| Input | Required | Meaning | |---|---|---| | Infrastructure cost per user | No | Hosting, compute, storage per user per month | | Support cost per user | No | Support and success time per user per month | | Third-party cost per user | No | APIs, data, and per-seat vendor fees | | Cost to serve per user | No | Direct total; overrides the three components when entered | | Desired gross margin | Yes | Target margin percent, 0 to under 100 | | Proposed price | No | A price to test; the calculator reports its real margin | | Customer count | No | For MRR and ARR projections | | CAC | No | Customer acquisition cost, for payback months |
Worked example
A product costs 3 of support, and 9 cost to serve. Targeting a 75% gross margin, price = 9 / (1 - 0.75) = 432 a year, leaving 7,200 MRR and 540, payback is 540 / 27 = 20 months, which the calculator will flag as slow: at typical churn, a 20-month payback means many customers leave before they have repaid their acquisition cost, so either price, margin structure, or acquisition efficiency has to move.
Choosing the target margin
Mature SaaS gross margins cluster around 70 to 85% because investors and acquirers price the business off them, and because the gross profit pool must fund all of sales, marketing, R&D, and overhead. Early products sometimes launch at 50 to 60% while infrastructure is inefficient, but pricing should be set for the margin you need at scale, with a plan to grow into it, or existing customers anchor you to a price that can never carry the company. Remember what does not belong in cost to serve: one-time onboarding can be charged separately, and engineering salaries for new features are R&D, not COGS, though support and reliability work genuinely is.
Price the value, floor it with cost
Cost-plus math gives a floor, not a market price. If customers would pay 36 floor donates margin; if the market clears at $25, the floor tells you the business does not work at current costs and something structural must change. Use this calculator to establish the floor and the CAC payback consequences, then set the actual tier prices from willingness to pay, packaging, and competitor anchors, checking each tier still clears the floor at its expected usage intensity. Heavy users on a flat tier are the classic way a healthy average margin hides a bleeding segment.
Limitations
The model is per-user and steady-state. It does not handle tiered or usage-based pricing curves, annual-discount effects, expansion revenue, churn-adjusted lifetime value beyond the payback heuristic, or taxes and payment fees unless you fold them into cost to serve. Verdicts use the figures you enter; garbage cost allocations produce precise nonsense.
Annual billing: price the discount honestly
Offering two months free for annual payment is a 16.7% price cut in exchange for cash upfront and lower churn exposure. Run it through the margin math before advertising it: a 360 a year instead of 9 cost to serve the effective margin on annual plans falls from 75% to about 72.5%, because costs run twelve months while revenue covers ten. That is usually a good trade, annual prepayment funds growth and prepaid customers churn less, but the calculator's MRR and ARR projections should use the discounted figure for annual cohorts or the forecast will overstate revenue all year.
When cost-plus says the business cannot work
Occasionally the floor price exceeds anything the market will pay. That is information, not a rounding error: it means cost to serve must fall (automation, cheaper infrastructure, self-serve support), the segment must change (larger customers spread fixed serving costs better), or the product must be repositioned to a higher-value problem. Discounting below the floor to win logos converts every new customer into a small monthly loss that growth only scales. The calculator's job is to say that early, while the fix is still cheap.
Frequently Asked Questions
What gross margin should a SaaS target?
70 to 85% is the healthy mature range. Below 60% leaves little room to fund growth functions unless the model is deliberately services-heavy, and the calculator flags thin margins accordingly.
Why is my CAC payback flagged as long?
Payback above roughly 12 to 18 months is risky because churn compounds against you: at 3% monthly churn, a fifth of customers are gone within seven months. Shorten it by raising price, cutting cost to serve, or acquiring more cheaply.
Should cost to serve include support staff salaries?
Yes, the share of support and customer-success time spent serving existing users is a genuine cost of revenue. Product development for new features is not; keep the two separate or your price floor will be overstated.