A recurring pricing call can be about raise size, seats, package structure, or the model itself — and still need defensible reasoning for the founder, the team, and the board. This page is the destination for the topic.
Raise and response calls are different shapes of the same pressure point: protect value, defend positioning, and avoid reflexive moves that reset your floor.
You can almost always charge more — briefly. The worked seven-section brief on whether a price increase will actually stick, and who it quietly costs you.
Read the worked brief →
A competitor shipped something and the internal Slack is on fire. The worked seven-section brief on deciding whether the move actually threatens you — before you reflexively answer it.
Read the worked brief →
When the decision changes how value is measured and sold, the call is about both customer behavior and go-to-market execution.
Decisions that lock in cost, segment mix, and support expectations should be treated as runway-risk and reversibility decisions, not simple discounts.
Reserved-instance discounts on GPU compute look free the moment you sign — the worked seven-section brief on the commitment decision every AI-product team is being sold right now.
Read the worked brief →
Closing a couple of big logos is not the same as being an enterprise company. The worked seven-section brief on whether to re-architect the whole business around a larger buyer.
Read the worked brief →
A price increase is a value capture test, not a panic fix for burn. The post recommends raising only when customers are receiving more value than they pay, churn is modelable, and a new price is first tested on the right slice instead of applied blindly to the base.
The post says to wait when the raise is mainly a reaction to short-term pressure and only act when the value delivered has increased, churn can be absorbed, and the team has run controlled tests. It treats pricing as a reversible sequencing problem first, not a hero move.
Usage-based pricing is framed as a fit check, not a trend choice. The post recommends switching only when a natural value meter exists, top accounts can forecast bills without major variance, and the go-to-market system can absorb variable revenue.
The post repeatedly says the default is rarely all-or-nothing. A hybrid with a predictable floor is often the lower-regret path when the meter and planning tests are not fully clean, because it preserves budgeting clarity while testing upside capture.
The upmarket call is treated as a company-level re-architecture, not a bigger plan. The post says to move only when larger-account demand is repeatable and the team is willing to rebuild sales, product, and support around the enterprise buyer while preserving the core that funds the move.
The post advises response only when the move threatens why customers choose you. If a 30-day do-nothing plan costs little, the highest-conviction play can be no immediate response, with price moves used as a last resort.
The post models this as a capacity-versus-flexibility decision: commitments save unit price only if utilization is stable and exit terms are acceptable. The recommendation is conservative tranching and no new irreversibility when the usage shape is still uncertain.
Give YourBrief the exact decision and the constraints you face; we return a structured recommendation with next steps.
Get your first brief for $1 (first 20 only)The Decision — free
The reasoning behind consequential product calls — including the ones we get wrong. No spam, no reselling your address, unsubscribe anytime.