Pricing experimentation software for SaaS price tests and pricing page A/B testing

Who needs pricing experimentation software

For a US SaaS founder, head of growth or finance lead at 20,000 to 2 million USD ARR, a pricing decision needs more than a conversion chart. You need to know whether the offer brings in enough revenue to justify the change, including the buyers it loses.

Common triggers include a Team plan that stays at its launch price, an annual offer few buyers choose, and a paywall that attracts trials without paid subscriptions. Rising service costs can also make the current price harder to defend. Each trigger suggests a hypothesis you can test.

A competitor's price increase is useful context, but your buyers may respond differently. Use the competitor price tracker to inform a hypothesis, then measure it on your own audience. For a broader backlog of changes, start with pricing optimization. Keep the first experiment narrow enough that its result answers a specific decision.

What you can test and how it reaches buyers

Monetisation supports page experiments and billing interventions. They answer related questions using different comparisons. Growth and Scale provide the snippet for pricing page and web paywall variants. Starter covers Stripe-side changes and manual playbooks without a snippet.

A toggle's presentation can also be a snippet test with a holdout. Adding or changing the underlying annual price is a billing intervention. Record which part changes so the comparison matches the question.

Keep a manual rollout checklist

Before applying a playbook, confirm the audience, current offer, proposed change, baseline period and owner. Check checkout behavior, customer notices and a rollback route. Record the effective date and any concurrent promotion. For existing subscriptions, the SaaS price increase guide explains rollout considerations separately from acquiring new customers.

All connectors are read-only. Monetisation never changes Stripe prices. Your team owns checkout routing, billing edits and the price each buyer receives, including when a page experiment displays different offers.

How measurement connects the offer to revenue

Revenue per visitor divides attributed revenue by eligible visitors over the same observation window. It combines purchase rate with what buyers actually pay. Compare equivalent windows and use a consistent treatment of annual payments, discounts and refunds so timing does not decide the result.

Conversion alone can mislead in either direction. A lower price may attract more buyers while reducing total revenue. A higher price may lose some buyers while increasing revenue per visitor. Trial starts sit further from the decision because some trials never pay. Follow conversion alongside revenue, plan mix and retention.

Holdouts compare visitors during the same period

For snippet experiments, server-side assignment determines the variant, and the holdout sees the current offer. Monetisation measures results against Stripe revenue. Keeping a concurrent comparison helps account for conditions both groups experience, such as a stronger sales week or a shift in acquisition demand.

Define visitor eligibility and check that each displayed offer leads to the correct checkout. A pricing page cannot validate a price test if the buyer sees one amount and pays another.

Billing interventions compare periods against a trend

For changes you apply in Stripe, record the intervention date. Monetisation compares the period after the change with the baseline trend established before it. This pre and post approach supports changes that do not have a concurrent holdout.

Its attribution is weaker than a well-run randomized comparison. A campaign, renewal cluster or unrelated product change can also move revenue. Document those events and interpret the result accordingly. The measurement and estimate methodology explains why a forecast range and an observed result serve different purposes.

Read the interval alongside the verdict

Lift expresses the measured change relative to the comparison. The interval shows uncertainty around that estimate. Results carry a verdict of win, flat, loss or not enough data. A positive estimate with substantial uncertainty still needs care, and an unresolved result does not establish that two offers perform equally.

Agree on the primary metric and decision rule before launch. Keep the observation window long enough to include the buying behavior you want to measure. Checking a chart frequently does not make a small sample more conclusive.

An illustrative Team plan price test

This example is illustrative, not a customer result. Suppose eligible new visitors see either a Team plan at 49 USD per month or a variant at 59 USD per month. Assume each group contains 1,000 visitors and all purchases cover one monthly period without discounts or refunds.

The holdout earns 40 times 49 USD, or 1,960 USD. The variant earns 36 times 59 USD, or 2,124 USD. Revenue rises by 164 USD across equal visitor counts. Relative revenue per visitor lift is (2.124 / 1.96 minus 1) times 100, or about 8.37 percent.

Conversion falls by 0.4 percentage points, a 10 percent relative decline. Looking only at conversion would favor the lower price. The revenue calculation favors the variant for this observation window, but it does not establish a win by itself. An interval, enough observations and later retention evidence still matter. The example makes no assumption about future renewals.

How to run a price test in four steps

1. Define the decision and baseline. Choose the offer, audience and hypothesis. Record current revenue, traffic and billing mix. Set the observation window, required sample and acceptable downside before seeing results. Use revenue per visitor as the primary measure for a visitor experiment, with conversion and retention as supporting checks.
2. Choose the delivery method. Use the Growth or Scale snippet for pricing page or paywall variants with server-side assignment and a holdout. For a billing intervention, follow the playbook and make the Stripe changes yourself. Confirm eligibility and checkout amounts before exposing buyers.
3. Run the agreed observation window. Keep other pricing changes out of the same audience where practical. Record promotions and acquisition changes. Allow trials and delayed purchases to reach payment, and compare revenue on a consistent basis. Treat early movement as provisional until the planned review.
4. Review the evidence and act. Read lift, interval and verdict together. Continue a supported winner, revise a losing offer, or gather more evidence when the result remains unresolved. Document the decision and rollback details. Check later renewals before assuming an acquisition gain improves long-term revenue.

How Monetisation compares with other approaches

The right tool depends on whether the hard part is delivering variants, managing product access or deciding which pricing change earns more. The pricing page A/B testing tools comparison covers general testing options in more detail.

General testing suites suit teams experimenting across the whole website. Stigg handles entitlements when product access and packaging infrastructure are the immediate need. Consultants help when buyer research matters more than another dashboard. Monetisation fits recurring pricing decisions where the team wants a revenue comparison and retains control over billing.

Choose a plan for your experiment workload

Choose Starter for changes your team applies and measures against a baseline. Choose Growth when the question needs pricing page or paywall variants with a holdout. Scale supports a larger experiment workload and includes API and webhooks. The homepage sample audit is a one-time demo with no card.

Compare the Monetisation plans to match your delivery method and experiment workload to a subscription.