Pricing change experiment checklist

Write the pricing hypothesis

Name whether the change tests willingness to pay, market fit, perceived value, discount recovery, higher-margin targeting, or a new positioning. Without a hypothesis, a price change becomes a finance guess.

Define the success metric before launch: proceeds, conversion rate, refund rate, support load, trial-to-paid rate, or paid-report completion.

Set market and user scope

• Countries, storefronts, currencies, taxes, existing users, new users, and promotion windows.
• Metadata, screenshots, landing pages, and support copy that mention price or value.
• Paid app, subscription, IAP, and bundle interactions.
• Refund and cancellation expectations.
• Rollback criteria and owner approval.

Prepare support for price questions

Users may ask why price changed, whether existing access changes, whether a sale will return, or whether a subscription is affected. Support should have clear answers before the price goes live.

AppReviewReady interpretation: price changes affect trust. Conversion gains are weak if they create refund and rating damage.

Measure the full outcome

1. Capture pre-change units, proceeds, refund rate, and conversion quality.
2. Monitor by territory and source, not only global revenue.
3. Compare support contacts and review sentiment after the change.
4. Check whether SEO pages need updated value framing.
5. Decide keep, rollback, or segment after the measurement window.

Pricing experiment ledger

The ledger makes pricing a repeatable growth operation rather than a one-time instinct.

Once analytics access improves, connect price changes with guide-level SEO demand. Some high-intent topics may support premium pricing better than broad traffic.

Avoid changing price and value proposition at the same time unless the experiment explicitly tests a bundle. Otherwise you will not know whether users reacted to price, copy, or perceived scope.

For international pricing, check whether local purchasing power and support cost change the conclusion. A globally uniform strategy can hide markets that are profitable at different thresholds.

If a price drop is temporary, prepare post-promotion messaging. Users who missed the sale may contact support or wait for discounts instead of buying.

For premium positioning, test whether higher price needs stronger proof rather than lower friction. A price experiment may fail because the page lacks evidence, not because the market rejects the price.

When increasing prices, separate new-user pricing from existing-user communication. Existing customers judge fairness, while new customers judge value.

After the test, document what you learned even if the change is rolled back. Failed pricing tests still improve future positioning.

Pricing experiment:
Product: [app/IAP/subscription]
Change: [old to new]
Markets: [list]
Hypothesis: [reason]
Success metric: [metric]
Support impact: [copy]
Rollback rule: [condition]