How to price your web app or SaaS

The right price for a SaaS is where your product’s value to a customer clearly exceeds what you charge, is easy to understand in one glance, and scales with usage so your best-fit customers happily pay more over time. To get there, pick a value metric that tracks customer outcomes, choose a pricing model that matches your sales motion, anchor the page with clear tiers, and iterate with data.

Key takeaways

• Tie price to a value metric that tracks outcomes (e.g., seats, automations, tracked keywords). Avoid vanity metrics that don’t correlate with value.
• Choose a model that fits your motion: self-serve leans to freemium or free trial; sales-assisted leans to tiers + usage; infrastructure often uses usage-based.
• Anchor your pricing page with a confident middle tier, strong feature differentiation, and one sentence per tier that explains who it’s for.
• Use simple rules for raises: new value → new price. Grandfather existing customers where practical; test increases first with annual renewals.
• Make upgrades a no-brainer: in-product nudges at limits, transparent overage pricing, and clear monthly vs. annual savings.
• Start simple, publish prices, and review quarterly. Pricing is a product; ship changes intentionally, not reactively.

The core decision: your value metric

Your value metric is the unit that scales the bill with customer value. Get this right and pricing updates, packaging, and expansion revenue all get easier.

Good value metrics share four traits:

• Correlates with value: as the customer is more successful, they use more of it.
• Predictable: buyers can reasonably forecast their bill.
• Measurable: your product can track it reliably.
• Controllable: customers can limit usage to manage spend.

Common value metrics by product type:

• Collaboration and productivity: seats or creators (not just viewers).
• Marketing tools: tracked keywords, subscribers, monthly sends, pages.
• Dev and infra: compute units, build minutes, requests, storage.
• Analytics: events, sources, workspaces, dashboards.
• Automations: tasks, runs, zaps/flows, active workflows.
• Support/success: agents, conversations, active contacts.

When in doubt, start with seats plus one capacity measure (e.g., “3 seats + 10,000 events”) and make overages explicit. Avoid purely feature-gated pricing that caps usage too tightly—it stalls expansion.

How to test a value metric quickly

• Run a 2–4 week cohort survey asking, “Which metric best reflects value for you?” Provide 3–5 options and one free-text.
• Analyze expansion revenue: which metrics already correlate with upgrades? Instrument now if you don’t have this.
• Offer two choices at checkout (e.g., seats vs. runs) only if both are intuitive. Otherwise, keep one and expose add-ons inside the product.

Red flags to watch

• Metrics tied to your costs but not customer value (e.g., API calls that users don’t understand).
• Metrics customers cannot forecast (“AI tokens” without clear tasks attached).
• Caps that block aha moments (e.g., very low limits before the first success).

Choose your model: freemium, free trial, usage-based, tiers, lifetime deals

Pricing models are tools. Match them to your activation motion, onboarding friction, and buyer type.

Freemium

Best when your aha moment is fast and value is obvious without setup. Works well with viral or product-led loops. The free plan should be useful but incomplete.

Pros:

• Low-friction top of funnel.
• Organic adoption inside teams.

Cons:

• Support and infra costs on free users.
• Can slow paid conversion if the free plan is too generous.

When to use:

• Self-serve PLG. Clear single-player value. Strong referral loop or shareable artifacts.

Design tips:

• Put one hard limit on the value metric that coincides with success.
• Reserve collaboration, security, and automation for paid.

Free trial (no credit card or with credit card)

Trials compress evaluation into time. Short, focused trials convert well when onboarding milestones are clear.

Pros:

• Predictable funnel, clear conversion points.
• Fewer long-term free users to support.

Cons:

• Can deter casual evaluators.
• Requires onboarding clarity.

When to use:

• Mid-market or above, or when setup is meaningful.

Design tips:

• 14 days is enough for most tools; 21–30 if data integrations are required.
• Consider credit card for trials only if you have strong brand trust and activation.

Usage-based (pure or hybrid)

Customers pay for what they use. Ideal when usage maps tightly to value, and variability is normal.

Pros:

• Natural expansion with customer success.
• Easy entry price; harder to churn if usage is embedded.

Cons:

• Revenue can be lumpy.
• Buyers need forecasting and guardrails.

When to use:

• Infrastructure, APIs, AI/ML inference, background processing.

Design tips:

• Publish overage rates. Offer budgets, alerts, and soft caps.
• Consider hybrid: base platform fee (predictable) + metered usage (scales).

Tiered plans

The default for many SaaS. Packages target different segments and jobs-to-be-done.

Pros:

• Clear choice architecture.
• Enables upsells via features and capacity.

Cons:

• Over-complexity creeps in fast.
• Can mismatch value if tiers hide key outcomes.

When to use:

• Most self-serve and sales-assisted SaaS.

Design tips:

• 3 public tiers cover 80% of cases; enterprise as a fourth.
• Name tiers by outcome, not vague labels: Starter, Growth, Scale.

Lifetime deals (LTDs)

A financing tool, not a pricing strategy. LTDs can seed your early user base and fund development, at the cost of future ARR.

Pros:

• Immediate cash, initial testimonials.
• Motivates early adopters to try.

Cons:

• Long-term support liability.
• Can anchor perceived value too low.

When to use:

• Short, capped cohorts with strict entitlements—ideally tied to early MVP.

Design tips:

• Limit support, seats, and usage. Be explicit that future features may require an upgrade.

Design your pricing page to convert

A pricing page is a sales page. It should answer three questions within five seconds: Which plan is for me? What do I get? What will I pay if I grow?

Layout essentials

• Three visible tiers, centered on your recommended plan.
• One sentence under each tier that says who it’s for.
• Annual toggle with genuine savings and an explanation (“2 months free”).
• Capacity limits displayed in plain language.
• Clear overage policy or upgrade path.
• Prominent CTA buttons with consistent copy.

Feature comparison that works

• Prioritize 6–8 differentiators that map to outcomes: collaboration, automation, security, support SLAs, integrations, performance.
• Group details behind accordions; keep the top table scannable.
• Use checkmarks and numeric limits; avoid vague “advanced” labels.

Anchoring and decoys

Anchoring frames your perceived value. Price the middle tier where the majority should land; make the lower tier feel constrained and the top tier aspirational.

• Use a “most popular” badge on the middle tier only if it’s objectively true from your funnel data.
• A “decoy” enterprise plan can make the middle tier feel more affordable, but it must be real and purchasable or quickly contactable.

Handling usage transparently

• Publish overage rates near the limit (“$X per 1,000 events after your plan’s limit”).
• Add an in-app estimator so customers can forecast bills with sliders.
• Offer budgets and alerts by default; it builds trust and reduces bill shock.

When to raise prices (and how)

Price increases should follow two conditions: (1) you deliver materially more value (product, performance, support), and (2) your market positioning justifies it.

Signals it’s time:

• Your win rate is high and discounting is minimal.
• You see heavy plan overages or consistent requests for features that sit above plan value.
• Expansion revenue lags usage growth because caps are misaligned.

How to execute:

• Announce clearly with 30–60 days’ notice for monthly; align with renewals for annual.
• Grandfather existing customers when possible; or offer a long runway with a loyalty discount.
• Pair the change with new value: features, higher limits, or included add-ons.
• Test with a small segment first (new signups, select geography, or self-serve only).

Messaging that lands:

• Lead with value outcomes, not your costs.
• Explain the improvements and what’s changing.
• Provide a simple path to keep current pricing (e.g., prepay annual) or to switch tiers.

Worked examples (hypothetical numbers)

These scenarios use round numbers purely for illustration. Swap in your own costs, conversion rates, and value metrics.

Example 1: Collaboration tool (seats + projects)

Context: A team collaboration app with quick time-to-value, solid single-player utility, and team network effects.

• Value metric candidates: seats, active projects, storage.
• Choice: seats as primary; projects as capacity.

Proposed tiers:

• Starter: $12/seat/month, up to 3 projects, basic integrations.
• Growth (recommended): $18/seat/month, unlimited projects, advanced integrations, automations.
• Scale: $28/seat/month, SSO, audit logs, priority support.

Overages and add-ons:

• Additional automations: $10 per 1,000 runs.
• Storage overage: $0.10/GB/month.

Why this works:

• Seats tie to collaboration value; projects encourage activation but don’t block core work beyond the early stage.
• Growth plan is anchored with meaningful differentiators (automations, integrations).

Conversion model (illustrative):

• Website to signup: 5%.
• Signup to activation (create first project + invite): 40%.
• Trial to paid: 25%.

Pricing levers:

• Offer annual at 2 months free (effective $15/seat/month for Growth).
• Free plan with 1 project and 2 seats to seed teams; hits value quickly but prompts upgrade on collaboration.

Example 2: Marketing analytics (events + dashboards)

Context: A tool that ingests website events and visualizes funnels. Setup requires a snippet install.

• Value metric candidates: monthly tracked events, dashboards, sources.
• Choice: events as primary; dashboards as packaging.

Proposed tiers:

• Starter: $39/month includes 100k events, 5 dashboards, community support.
• Growth (recommended): $99/month includes 1M events, 20 dashboards, API, team roles.
• Scale: $299/month includes 5M events, SSO, export, SLAs.

Overages:

• $2 per 100k events after plan limits.
• Budgets and alerts on by default.

Why this works:

• Event volume follows customer traffic and value.
• Overages are simple, predictable, and fairly priced.

Trial strategy:

• 21-day trial (no CC) due to setup friction; extend to 30 days if events flowing are below a target in week one.

Example 3: AI writing assistant (usage-based + seats)

Context: An AI tool where output quality and volume vary by user. Costs are tied to inference.

• Value metric candidates: generated words, tasks, documents, seats.
• Choice: hybrid — platform fee per seat + metered generated words.

Proposed tiers:

• Creator: $15/seat/month includes 100k words; $0.20 per additional 10k words.
• Team (recommended): $25/seat/month includes 300k words, shared style guides, brand voice.
• Business: $45/seat/month includes 1M words, SSO, custom models.

Controls:

• Workspace budgets and per-user limits.
• Real-time cost estimates in the composer.

Why this works:

• Base fee funds support and R&D; metering scales with heavy usage.
• Buyers can forecast and cap spend.

Example 4: Developer API (pure usage-based with tiers for support)

Context: An API with variable request volume and strong dev tooling.

• Metering: $1.50 per 1,000 requests.
• Minimums: none for self-serve; enterprise commits negotiated.

Support packages:

• Free: community support, shared infrastructure.
• Pro: $99/month adds higher rate limits, email support, dedicated IPs available.
• Enterprise: custom pricing, dedicated infra, 99.9% SLA.

Controls and trust:

• Per-key budgets, alerts at 50/80/100% of budget.
• Sandbox mode free up to 10k requests/month.

Messaging:

• “Only pay for the requests you use. Forecast with our calculator.”

Example 5: Automation tool (tasks + workflows)

Context: Workflow automation with clear business outcomes.

• Value metric: successful task runs (not just attempts).
• Packaging: workflows and integrations.

Proposed tiers:

• Starter: $19/month includes 2,000 task runs, 5 workflows, community connectors.
• Growth (recommended): $49/month includes 15,000 task runs, unlimited workflows, premium connectors, scheduling.
• Scale: $149/month includes 100,000 task runs, priority support, SOC 2 reports.

Overages:

• $3 per 1,000 runs after plan limits; soft-cap with pausing options.

Why this works:

• Customers understand “runs” and link them to time saved.
• Premium connectors and scheduling create real step-up value.

Packaging: features that drive upgrades

Features should ladder logically from self-serve to security and governance.

• Starter: personal productivity, basic integrations, limited collaboration.
• Growth: team collaboration, automation, permissions, bulk actions.
• Scale/Business: SSO/SAML, audit logs, advanced security, SLAs, custom roles, data retention, compliance.

Add-ons to consider:

• Priority support, dedicated IPs, custom domains, premium connectors, advanced analytics, additional workspaces.

Rules of thumb:

• Put admin/security up the ladder; don’t hold core value hostage.
• If a feature unlocks a new job-to-be-done, it can justify a higher tier.
• Avoid nickel-and-diming essentials that every serious user needs.

Discounts, annual plans, and commitments

Discounts are a steering wheel, not a business model.

• Annual plans: default to 2 months free. It’s standard and simple to explain.
• Startups/education/nonprofit: publish clear, modest discounts (e.g., 20–30%).
• Sales-assisted deals: use volume or term discounts instead of ad hoc percentage cuts.
• Grandfathering: honor old prices for a reasonable period; build goodwill and reduce churn.

Trials and onboarding that convert to paid

A great trial highlights the value metric and steers to the right tier.

• Guide users to the “aha” within 10 minutes: templates, sample data, checklists.
• Email and in-app nudges that connect milestones to plan limits (“You’re 80% to your first automation. Growth includes 15,000 runs.”)
• Ask for the card after value, not before. A post-activation paywall converts best.

Instrumentation and iteration

Pricing is not set-and-forget. Add the analytics you need to learn fast.

Track:

• Plan mix over time and by segment.
• Activation milestones vs. conversion.
• Expansion revenue drivers (which limits push upgrades).
• Discount rate and its impact on retention.

Run experiments:

• Price sensitivity surveys (Van Westendorp, Gabor-Granger) with active leads.
• Landing page split tests for tier names, limits, and default plans.
• Regional pricing tests only if your go-to-market supports it operationally.

Guardrails:

• Keep grandfathering logic simple.
• Maintain a single source of truth for pricing in code and docs.
• Document every change with reasons and expected impact.

How to choose your initial price (a simple process)

1. Define your target customer and core outcome. Write it in one sentence.
2. Pick a primary value metric that scales with that outcome; sanity-check predictability.
3. Sketch three tiers that match jobs-to-be-done; draft limits and 6–8 differentiators.
4. Choose a model: free plan or trial; monthly vs. annual; any usage metering.
5. Set list prices by anchoring to ROI, not costs. Your middle tier should feel like a great deal relative to the outcome.
6. Publish, instrument, and schedule a 60–90 day review.

A quick ROI lens

If your product saves a customer 10 hours a month at $50/hour, that’s $500 in monthly value. Pricing the recommended plan at $49–$99/month leaves room for clear ROI and upgrades as usage expands. Keep the math visible in your copy.

Common pitfalls (and their fixes)

• Too many tiers: cap at three public ones. Push edge cases to sales.
• Confusing limits: use round numbers and relatable units.
• Free plan that’s too good: ensure at least one core collaboration or automation feature is paid.
• Hidden overages: publish them. Surprises kill trust.
• Annual discount stacking: cap discounts and centralize approvals.
• Chasing competitors: know the landscape, but price to your value and motion.

Resources and next steps

• Browse Popular apps and Trending to see how leaders present pricing in your category.
• Explore Categories or search competitors with Search.
• Related reads on Zivvi: How to get your first 100 users for a web app, SEO for indie apps: a beginner's playbook, and How to write a landing page that converts.

Methodology

Zivvi catalogs more than 2,300 web apps and tracks their worldwide traffic rank using the Tranco list, a research ranking that averages several traffic sources. When we reference competitive landscapes or examples on Zivvi, ranks refer to worldwide traffic ranks as of November 6, 2026. Where we mention 30-day changes, we compare the rank about 30 days earlier with the latest value. We never sell placements; coverage, reviews, and links are editorial.

Frequently asked questions

What is the best pricing model for SaaS?

There’s no single best model; match the model to how customers find value. Self-serve tools usually do well with freemium or time-limited trials, while infrastructure and APIs lean usage-based. Many teams ship a hybrid: a base platform fee for predictability plus metered usage that scales with outcomes.

How do I pick a value metric that won’t backfire?

Choose a metric that correlates with customer success, is predictable to forecast, and you can measure accurately. Seats, tracked events, task runs, or dashboards are common because they map to outcomes. Avoid opaque units or caps that block aha moments before users see value.

Should I show prices publicly or make users contact sales?

Publish prices if you serve self-serve or SMB buyers; it builds trust and speeds evaluation. For complex enterprise packages, publish standard tiers and invite conversations for custom needs. Even with sales, a public anchor reduces friction and anchors expectations.

How often should I change SaaS pricing?

Review quarterly and adjust when you’ve added meaningful value or learned that packaging blocks adoption or expansion. Minor copy and limit tweaks can ship more frequently; major price changes should be tested with a segment and tied to new value. Keep change logs and grandfather thoughtfully.

Is a free plan or a free trial better for conversions?

If your aha moment is fast and single-player, a free plan can drive organic growth. If onboarding requires setup or collaboration, a time-limited trial focuses evaluation and increases paid conversion. You can combine them: a modest free plan for light use and trials that unlock premium features.

How do I handle overage charges without causing churn?

Publish clear rates, provide budgets and alerts, and let customers set soft caps. Offer one-click upgrades when they near limits and show before-and-after bills. Transparency builds trust and reduces bill shock, which in turn protects retention.

Ready to put your pricing to work? Explore competitors in your space via Categories and Search, and if you’re launching something new, get discovered by listing it on Zivvi at Submit.