Nautis Logo
GTM · Pricing

How to Price a SaaS Product

Frameworks for setting your initial price, the review cadence, and the pricing changes that actually move revenue.
9 min readUpdated Apr 30, 2026

Pricing is the single highest-leverage growth lever in SaaS. A 25% price increase usually drops 5% of demand and increases revenue 19%. Most founders touch pricing once and never re-examine it. The successful ones treat it as a quarterly operating practice.

Frame: charge for value, not cost

Cost-plus pricing is appropriate for hardware. SaaS is an intellectual product — your variable cost is near zero, so price should reflect customer value, not your hosting bill.

Three questions to set the initial price:

  1. What does the customer save or earn? Time saved per week × hourly cost; revenue gained from new conversions; risk avoided.
  2. What's the alternative they'd pay for? Existing tools, internal builds, manual processes. Your price should fit comfortably below the next-best alternative.
  3. What's a believable number? Customers anchor on familiar pricing — $20-100/user/month for SMB SaaS, $5-50K annual for mid-market, $50K+ for enterprise.

Triangulate to a number that's defensibly priced based on value but anchored at familiar levels. Then test.

Pick a value metric

Your value metric is what you charge by. Pick one that scales with customer value:

  • Per user / per seat. Default for collaboration tools. Easy to understand, easy to expand. Risks: heavy users vs casual users pay the same.
  • Per usage. API calls, transactions, GB of data, documents processed. Best when usage is the value driver.
  • Per outcome. Per lead generated, per dollar processed, per case resolved. Aligns interests perfectly but harder to forecast.
  • Tiered packages. Standard / Pro / Enterprise with feature gating. Common for products serving multiple ICPs.

Pick one primary value metric and one secondary. Three or more metrics confuses customers and creates pricing-page bounce.

Three-tier pricing — the default that works

Most SaaS pricing pages converge on three tiers because three creates a deliberate "decoy" effect: the middle tier wins.

A useful template:

  • Starter ($X/month). Designed for individuals or tiny teams. Limited but useful. Goal: convert free users and trials.
  • Pro ($3-4× Starter). The "best" choice. Includes everything most customers actually need. Designed to be the obvious pick.
  • Enterprise (custom or $10×+ Starter). Big customers who need SSO, SLAs, dedicated support. Don't list a public price — call sales.

The annual / monthly trick

Offer monthly and annual billing. Annual at 20% discount is the sweet spot. Reasons:

  • Better cash flow. 12 months upfront vs monthly.
  • Higher retention. Annual customers churn ~50% less than monthly.
  • Implicit anchor. Annual price feels like a discount; monthly feels like a premium.

Push annual hard for mid-market and up. SMB defaults to monthly — offering annual at modest discount converts about 30% to annual.

Raising prices — when and how

Most SaaS companies raise prices too rarely. Triggers to consider an increase:

  • You've shipped material new value (new product line, AI features, integrations).
  • NPS is high but win rates are softening — the price isn't the issue, but you have headroom.
  • Sales reps complain about "easy closes" at the current price.
  • Competitors have raised prices.

How to raise:

  • Grandfather existing customers on the old price for 6-12 months. Communicates fairness, prevents churn at the inflection point.
  • Raise list price first; discounts soften the impact for new customers. Old anchor, new floor.
  • Communicate value, not the price increase. "We're updating our pricing to reflect the new features we've shipped" beats "we're raising prices."

Common SaaS pricing mistakes

  • Pricing on intuition without data. Run pricing experiments. A/B test landing page prices for new traffic. Survey existing customers on willingness-to-pay.
  • Discounting too easily. Founder-led sales tends toward discounts. Set a discount-approval policy ("over 25% off requires a sales lead's approval") to protect price integrity.
  • Free tier with no path to paid. If the free tier solves customers' problems entirely, conversion stays low. Design the free tier to create constraint at growth points.
  • Hiding pricing for SMB. Small customers want to self-serve. If they have to call to see a price, they'll pick a competitor with public pricing.
  • Per-user pricing for products with low per-user utilization. A "team" tool that 80% of users don't log into has the wrong value metric. Switch to usage- or outcome-based.

Pair this guide with the CAC/LTV calculator to understand the impact of pricing changes on unit economics. A 20% price increase often improves payback period by 20%+ in lockstep.

FAQ

How often should I review pricing?+
Quarterly for early-stage; semi-annually after seed. Don't change more than once per quarter or you'll confuse customers and lose trust. Big pricing redesigns happen 1-2x in a company's life — usually after major product expansions.
Should I disclose pricing on my website?+
Yes for SMB and self-serve. No for enterprise / strategic deals where pricing is contextual. Hybrid: show 'starting at $X' with 'Contact us for enterprise.' Hidden pricing kills self-serve conversion rates.
Should I offer a free tier?+
Only if free users genuinely contribute (data network effects, viral loops, content ecosystems). Free as a 'try before buy' substitute usually under-converts compared to free trials.
How much should I charge for my first customer?+
Whatever they'd pay you. The 'design partner' price isn't free — it's a discount in exchange for product input. 25-50% off list with explicit feedback obligations is standard.
Should I price by user, by usage, or by feature?+
By the value created. SMB: usually per-user works. Mid-market: hybrid (per-user + usage). Enterprise: tiered packages by feature scope. Match the metric customers think about when they justify the spend.