SAAS FEATURE PACKAGING OPTIMIZER · RUNS IN YOUR BROWSER · NOTHING UPLOADED

Which features belong in Starter, Pro and Team?

Paste what each person you surveyed would pay per month for each feature. The tool tries which plan each feature should first appear in, prices the plans, assumes everyone buys the plan that leaves them the most surplus, and returns the packaging and prices that earn the most profit, with what each feature is worth in each plan.

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 and features

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

Put * after a feature that must stay in the cheapest plan, such as the core product.

One number per feature in the same order: 1 = cheapest plan, 2 = middle, 3 = top, 0 = not offered.

Leave blank to compare against your current packaging at its own best prices.

Survey (one respondent per line)

Each line: the most that person would pay per month for each feature on its own, in feature order, separated by commas. Leave a feature blank or put - if it has no value to them. An optional last number counts that line more than once. A first line with feature names is ignored. Up to 500 lines.

Needs at least 5 survey lines. With 8 features and a long survey it can take several seconds.

Questions founders ask

Which features should go in which SaaS pricing tier?

Survey a sample of customers or prospects on what each feature is worth to them per month, paste one row per person, and the tool tests which plan each feature should first appear in and what each plan should cost. Plans are nested (higher plans include everything in lower ones), a customer is assumed to buy the plan with the most surplus, and the result is the packaging and prices that earn the most profit on your survey.

Why not put every feature in every plan?

Because one flat price leaves money on the table: it is too high for light users and too low for heavy ones. Holding back the features only some customers value lets the cheap plan stay cheap while the people who value those features pay more. The tool shows what a single flat plan would earn so you can see the gap.

How do I ask about feature value in a survey?

Ask each person the most they would pay extra per month for each feature on its own, and record 0 or leave it blank where it has no value to them. Add a core-product column if you want to price the base product too, and mark it with an asterisk so it stays in the cheapest plan.

Is the answer exact?

The prices are exact for the placement chosen. The placement is found by local search from several starting points, which matches exhaustive search on small test surveys but is not guaranteed on every survey with eight features. Treat the output as a ranking of packaging options to test with real signups. This is arithmetic on your survey, not pricing or financial advice.

Not decided

Whether customers pay for a feature as a sum (features that only matter together, or substitutes, break that), annual versus monthly pricing, discounts and trials, free tiers, usage-based limits, seat counts, 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.

Related tools: the SaaS tier price optimizer (prices plans from per-plan survey answers), the usage-based pricing simulator and the annual plan discount calculator.