SaaS Tier Price Optimizer: Good-Better-Best Pricing From a Survey

What should your Starter, Pro and Team plans cost?

Paste what each person you surveyed would pay per month for each plan. The tool assumes everyone buys the plan that leaves them the most surplus, tests the price ladders that matter, and returns the prices that earn the most profit, how many customers land on each plan, and what that is worth against your current prices.

Arithmetic on the survey you paste. Not pricing, business or financial advice. The example survey is made-up placeholder data, not any business's.

Your plans

Plan names, cheapest first (1 to 3, separated by commas)

Cost to serve one customer per month, per plan

Hosting, support and payment fees per customer, comma separated in plan order. Use 0 if unsure. Prices are never set below cost.

Current monthly prices (optional)

Shown side by side with the suggestion so you can see what changing is worth.

Survey (one respondent per line)

Each line: the most that person would pay per month for each plan, in plan order, separated by commas. Leave a plan blank or put - if they would not buy it. An optional last number counts that line more than once. A first line with plan names is ignored. Up to 2,000 lines.

Maximum monthly price per plan

Needs at least 5 survey lines.

Questions founders ask

How do I price Good-Better-Best SaaS plans?

Ask a sample of customers or prospects the most they would pay per month for each plan, paste one row per person, and the tool tests the price ladders that matter. Each respondent is assumed to buy the plan that leaves them the most surplus (their maximum price minus the price), or nothing if no plan has any. It returns the prices that earn the most profit, who ends up on each plan, and what that is worth against your current prices.

Why not price each plan at what the average customer would pay?

Because customers choose between plans. Raising the middle plan can push people to the cheap one or up to the top one. The tool prices the whole ladder together, which is what moves the numbers.

How many survey responses do I need?

Enough that the answer does not swing when a few change. Try deleting a handful of rows and re-running: if the prices jump, collect more. With under 30 rows treat the result as a direction, not a number.

Is a willingness-to-pay survey reliable?

Stated prices usually run above what people pay. Use the result to rank ladders and see how fragile your prices are, then test the top candidate on real signups. This is arithmetic on your survey, not pricing or financial advice.

Not decided

Which features go in which plan, annual versus monthly pricing, discounts and trials, free tiers, usage-based add-ons, taxes and currencies, competitor prices, and how real customers will behave compared with what they said. Treat the output as a ranking of options to test.