One decision, two very different bets · Founding edition

Do not add a pricing tier because raising the price feels scary.

A seven-day decision sprint for SaaS founders choosing between charging more for today’s product and building a new package that earns a higher price.

Take the 3-minute fit check Founding enrollment closed
01

Your team keeps asking whether a higher price needs new features to justify it.

02

The proposed upper tier is a list of leftovers rather than a coherent promise for a specific buyer.

03

Every debate ends with more packaging work because nobody has named the uncertainty the change is meant to resolve.

Choose the smallest pricing move that answers the most important question.

Is the current offer underpriced?

Use customer behavior, current value, win-loss evidence, and segment differences to decide whether the existing package can simply support a higher price.

Is there really another buyer?

Require a specific buyer, job, and willingness-to-pay boundary before turning internal feature differences into another tier.

Which test separates the bets?

Design a first test that distinguishes pricing power from package demand instead of changing price, features, and audience at once.

$12 / $24 → $19 / $29

One self-serve B2B SaaS team raised both existing paid prices without changing the packages. After roughly seven business days, the higher-price arm produced almost twice the early revenue and every new checkout chose Pro.

It was an early signal, not a universal result. Its value here is cleaner: the team tested pricing power without confusing it with a new package.

For the raise-or-tier decision

Make the decision before another quarter makes it for you.

Bring one live pricing question and the customer, revenue, and usage evidence you already have. Leave seven days later with a decision memo your team can ship.

See if the sprint fits Founding enrollment closed September 1, 2026. Take the fit check or ask about the next edition. Terms · Privacy