Who should see the increase?
Separate new-customer, existing-customer, and segment-specific decisions instead of forcing one universal answer.
Your price is stale · Founding edition
A seven-day decision sprint for founders whose product, customer, and costs have changed—but whose pricing has not.
This is probably your decision if…
The current price was chosen for a much earlier version of the product.
Your best customers barely react to price while your team obsesses over the most sensitive users.
Every proposed increase dies because nobody can agree what evidence would make it safe enough to test.
What the sprint resolves
Separate new-customer, existing-customer, and segment-specific decisions instead of forcing one universal answer.
Decide whether the price, package, value metric, or paywall is actually creating the constraint.
Set the audience, primary metric, guardrails, and decision rule before the first customer sees a variant.
Anonymized advisory case note
The feared conversion collapse did not appear.In one self-serve B2B SaaS test, prices moved from $12/$24 to $19/$29. After roughly seven business days, the higher-price arm showed almost twice the early revenue while all new checkouts selected Pro.
That does not prove your increase will win. It proves the internal demand curve should be treated as a hypothesis and tested against revenue and customer quality.For the price you keep postponing
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