FrançaisEnglishEspañolItalianoDeutschPortuguêsNederlandsPolski

SaaS Pricing Calculator: Find Your Price Floor

Published on March 1, 2026 · Jules, Founder of NoNoiseMetrics · 10min read

Most founders aren’t guessing their price — they’re benchmarking the wrong thing. They look at a competitor, pick a number slightly lower to feel “competitive,” and ship it. No cost model. No revenue target check. No margin math.

The result is pricing that looks reasonable and fails quietly. Not through some obvious collapse — through slow ARPU erosion, a plan mix that never generates enough, and a business that requires three times the customers it projected.

A SaaS pricing calculator doesn’t pick your final price. It tells you the minimum price below which your economics stop making sense — and it shows whether your current pricing can actually reach your revenue targets. That’s the floor. Everything above it is a judgment call. Below it is subsidizing customers with founder time. OpenView Partners SaaS pricing benchmarks show that the majority of early-stage SaaS products are priced below their actual price floor when cost structures are modeled correctly.


Use the calculator

Four inputs. Two primary outputs. No spreadsheet required.

→ Open the Price Floor Calculator

The calculator below requires:

  1. Target monthly revenue — what you’re trying to reach (MRR target)
  2. Target customer count — how many customers at that revenue level
  3. Variable cost per customer per month — infra, AI API costs, payment fees, support overhead
  4. Target gross margin — the margin % you need the business to operate at

It outputs:

  • Price floor — the minimum monthly price that supports your margin target
  • Required ARPU — the average revenue per customer implied by your revenue and count targets
  • Viability verdict — whether current pricing can plausibly reach the target

Wondering if your last pricing change actually moved ARPU? See plan-level MRR breakdown →


The two formulas behind the calculator

Price floor formula

Price Floor = Variable Cost Per Customer / (1 - Target Gross Margin)

If your variable cost per customer is €10/month and your target gross margin is 80%:

Price Floor = 10 / (1 - 0.80) = 10 / 0.20 = €50/month

Any plan priced below €50 can’t produce 80% gross margin at €10/customer cost. That’s not a preference — it’s arithmetic.

Variable costs to include: cloud infrastructure per customer, AI/LLM API costs (if usage-based), payment processing fees (~1.5% + €0.25 on Stripe in Europe, or roughly €1–€3 at typical SaaS price points), support overhead per customer, and any third-party data costs.

Variable costs to exclude: your time (yet), fixed SaaS tools you’d pay regardless, and one-time development costs. Gross margin measures the recurring economics of each additional customer, not total company profitability. Stripe Atlas billing guides provide detailed breakdowns of Stripe fee structures to help model variable cost per customer accurately.

Required ARPU formula

Required ARPU = Target Monthly Revenue / Target Customer Count

If you’re targeting €20,000 MRR with 200 customers:

Required ARPU = 20,000 / 200 = €100/month

Your plan mix needs to average €100/month across all customers. If your entry plan is €19/month and most customers stay there, that’s not a pricing problem — it’s a plan structure problem that pricing alone can’t fix.

The comparison that matters

The price floor tells you the minimum economically viable price. Required ARPU tells you the average price your revenue target implies.

If required ARPU > price floor: viable with room to price confidently. If required ARPU ≈ price floor: tight — small cost increases or margin pressure will hurt. If required ARPU < price floor: the revenue target requires more customers, lower cost structure, or a higher margin expectation. Something has to change.


Worked example: a SaaS analytics tool

Inputs:

VariableValue
Target MRR€15,000
Target customers180
Variable cost/customer/month€8
Target gross margin82%

Outputs:

Price Floor = 8 / (1 - 0.82) = 8 / 0.18 = €44.44/month

Required ARPU = 15,000 / 180 = €83.33/month

Verdict: Required ARPU (€83) is well above the price floor (€44). The economics are viable — but only if the plan mix actually averages €83. A €19 Starter plan that captures 70% of customers without upgrading will pull the real ARPU down to ~€35, which is below the floor.

What this tells you:

  • A €19 Starter plan can exist, but must drive upgrades aggressively
  • A €49 Growth plan should be the obvious default
  • A €99 Scale plan captures the tail — but the middle tier is where the math has to work
  • If plan mix shows most customers on €19 after 90 days, pricing structure (not pricing level) is the problem

This is the kind of clarity the calculator is built to surface.


What the calculator can’t do

A pricing calculator is a floor-finding tool, not a complete pricing strategy. It answers the economic question — can this price sustain this business? — but not the market question (will customers pay it?), the positioning question (does it feel right for this product?), or the packaging question (which features belong in which tier?).

It can’t tell you willingness to pay. For that, you need customer conversations, pricing page experiments, or structured willingness-to-pay research.

It can’t account for competitive dynamics. Your price floor might be €50, but if the dominant alternative is priced at €30, the gap matters.

It doesn’t replace packaging. The calculator outputs work with a single average price. Real pricing is a plan mix — and whether customers land on the right plan is a packaging decision, not a pricing decision.

For packaging, see SaaS Pricing Model Template: Copy/Paste Tiers That Sell. For the value metric that drives the tier progression, see the guide on picking one unit that makes everything obvious.

For the broader pricing models context, the minimalist guide covers all five model types and when each makes sense.


Common pricing calculation mistakes

Forgetting variable cost entirely. The most common error in AI-adjacent products. If you’re using OpenAI, Anthropic, or similar APIs per-request, that cost is real, it scales with customers, and it belongs in the denominator. A product with €15/customer/month in LLM API costs that charges €29 has almost no margin at standard SaaS gross margin targets.

Optimistic customer counts. “We’ll make it up in volume” only works if you can actually reach that volume. A €10/month plan that needs 3,000 customers to hit €30K MRR requires extraordinary acquisition efficiency. Price floor math is easy to game by plugging in aspirational customer counts.

Confusing price floor with final price. The floor is the minimum, not the target. Value-based pricing means charging above the floor based on the outcomes the product delivers — not hugging the floor to feel “accessible.”

No churn sensitivity. The formulas above assume a stable customer count. In practice, you need to reach the target count net of churn. At 5% monthly churn, you’re replacing 5% of the customer base every month just to stay flat. The required acquisition volume to hit 200 stable customers is much higher than 200.

Plan mix blindness. Required ARPU is an average. If 60% of customers are on your lowest tier, the average will be well below your headline Growth or Scale prices. Model the plan mix explicitly: (Starter count x €19) + (Growth count x €49) + (Scale count x €99) / total customers = real ARPU. If the real ARPU is below the required ARPU, the plan structure needs adjustment.

SaaStr’s pricing research identifies plan mix blindness as one of the top three pricing mistakes at the €10K–€100K MRR stage — founders who track blended ARPU instead of plan-level ARPU miss the structural issue until it becomes a growth ceiling.


Churn sensitivity: the number most pricing calculators skip

At different churn rates, the stable customer count you need grows significantly:

Monthly churnCustomers needed to maintain 200 stableMonthly new customers required
1%~201~2
3%~206~6
5%~211~11
8%~217~17

At 8% monthly churn, you need to acquire ~17 new customers every month just to stand still at 200 customers. If your CAC is €200, that’s €3,400/month in acquisition spend just to maintain current MRR — before growing it.

This is why churn and pricing are inseparable. A price floor calculator that ignores churn produces overly optimistic output. The interactive calculator above includes a churn sensitivity toggle for this reason.


Using the outputs to build a pricing structure

Once you have the floor and required ARPU, the sequence is:

1. Set the Growth plan first. The default plan should be at or above required ARPU, priced above the floor with comfortable margin. This is the plan most of your revenue comes from.

2. Set Starter to create real value, not a demo. Price it below Growth but above a threshold where customers can get a genuine first outcome. If Starter doesn’t create value, it doesn’t generate upgrades.

3. Set Scale to capture outliers naturally. At 2× the Growth price or more, with limits that genuinely matter to high-usage or team customers.

4. Check your plan mix assumptions. Model the scenario where 60% of customers stay on Starter. Does the blended ARPU still exceed the floor? If not, Starter is either too cheap or needs stronger upgrade triggers.

For the full plan structure framework, see SaaS Pricing Model Template.


JSON model for builders

{
  "pricing_calculator": {
    "inputs": {
      "target_mrr": 15000,
      "target_customer_count": 180,
      "variable_cost_per_customer_per_month": 8,
      "target_gross_margin_pct": 0.82,
      "monthly_churn_rate": 0.03
    },
    "outputs": {
      "price_floor": 44.44,
      "required_arpu": 83.33,
      "viable": true,
      "margin_buffer": 38.89,
      "customers_needed_with_churn": 186
    },
    "plan_mix_check": {
      "starter_pct": 0.50,
      "growth_pct": 0.35,
      "scale_pct": 0.15,
      "starter_price": 19,
      "growth_price": 49,
      "scale_price": 99,
      "blended_arpu": 45.40,
      "plan_mix_viable": false,
      "note": "Blended ARPU below required ARPU — too many customers on Starter"
    }
  }
}

The plan_mix_check block is the part most pricing discussions skip. It surfaces the gap between required ARPU and the ARPU the actual plan distribution produces — which is often where the real pricing problem lives.


FAQ

What is a SaaS pricing calculator?

A SaaS pricing calculator is a tool that uses cost structure, revenue targets, and margin assumptions to find the minimum viable price for a SaaS product. It doesn’t determine final pricing — it identifies the floor below which the pricing model becomes financially unsustainable.

What is a price floor in SaaS?

A price floor is the minimum monthly price that supports a target gross margin given a product’s variable cost per customer. Below the floor, every additional customer either generates no margin or negative margin — the business is subsidizing usage rather than monetizing it.

How do you calculate a SaaS price floor?

Price Floor = Variable Cost Per Customer Per Month / (1 - Target Gross Margin). For example: variable cost €12, target margin 80% → price floor = 12 / 0.20 = €60/month.

What is required ARPU and why does it matter?

Required ARPU is the average revenue per user your customer count and revenue target imply: Required ARPU = Target MRR / Target Customer Count. It matters because low pricing can look viable on paper while being incompatible with the actual revenue target unless paired with unrealistic customer volumes.

Can a pricing calculator tell me what to charge?

No. A pricing calculator identifies the economic floor and required ARPU. Final pricing depends on value delivered, market expectations, competitive context, and willingness-to-pay research. The calculator removes the “obviously wrong” scenarios; positioning and packaging determine the right price within the viable range.

How does churn affect SaaS pricing?

Churn doesn’t directly affect the price floor formula, but it significantly affects how many customers you need to acquire to maintain a stable MRR. At 5% monthly churn, you lose 5% of your base every month — meaning you need continuous acquisition just to stay flat, and the CAC load of maintaining a stable customer count should factor into your margin calculations.

After you set your price, you need to know if it works. NoNoiseMetrics tracks ARPU and MRR by plan automatically. Connect Stripe →


Free Tool
Try the SaaS Pricing Calculator →
Interactive calculator — no signup required.
Share: Share on X Share on LinkedIn
J
Juleake
Solo founder · Building in public
Building NoNoiseMetrics — Stripe analytics for indie hackers, without the BS.
See your real MRR from Stripe → Start free