Ship Fast, Price Slow: The Case for a Pricing Constitution

The gap between how fast you ship and how slow you price

Most product teams ship every week and price once a year, badly. That gap is where margin leaks out and where the pricing conversation becomes a standing tax on every launch. The fix is to write a pricing constitution before the next release, not after the one that goes wrong.

Here is the pattern. Engineering and product have compressed the build cycle to days. A team spins up a feature, tests it, ships it to a cohort, and moves on. Pricing has not compressed at all. It still runs on the old rhythm: a committee, a spreadsheet, a founder or a VP making a judgment call the week before launch because nobody made it earlier. Elena Verna named this problem when she argued that your company needs a pricing constitution. The velocity mismatch is why it matters more now than it used to.

When shipping was slow, ad hoc pricing was survivable. You made a few big packaging decisions a year and lived with them. When shipping is fast, every feature raises a pricing question, and answering each one from scratch means pricing becomes the slowest thing you do. The bottleneck is the meeting about what to charge for the build.

Improvised pricing fails harder the more you scale it

Ad hoc pricing fails for reasons that compound. The first is inconsistent logic. When each price is set in isolation, the underlying rationale drifts. One feature is priced on seats, the next on usage, the next thrown into an existing tier because arguing about it felt expensive. Customers notice the incoherence before you do. So does your sales team, which now has to explain why two similar features live in two different parts of the pricing model.

The second is the race to discount. Without guardrails, every deal negotiation starts from list price and moves in one direction. Reps discount to close, because closing is what they’re paid for, and each discount resets the anchor for the next quarter. Willingness-to-pay is not a fixed property of the customer. It is shaped by the last number you quoted them. Erode the anchor once and you have repriced the whole book of business downward.

The third is internal friction that reads as external friction. When pricing lives in someone’s head instead of in a document, every non-standard deal escalates. The rep waits on the manager, the manager waits on finance, finance waits on the founder. The customer feels the delay and reads it as disorganization, which it is. Deals that should close in a week close in a month, or do not close at all.

None of these are pricing problems in the narrow sense. They are governance problems. The price is wrong because the process that produced it had no standing rules.

A constitution is principles, not a price list

A pricing constitution is the set of durable principles that govern how you price, separate from any specific price you charge. That distinction is the whole idea. Prices change constantly. The logic that produces them should not.

Three things belong in it. The first is your value metric: the single unit you charge against, and the reason it is the right one. If you charge per seat, the constitution says why seats track the value the customer receives, and what would have to be true to change that. This is the most consequential decision in the document, because the value metric determines whether your revenue grows as your customers succeed or stays flat while they do.

The second is packaging rules: how features map to tiers, what makes something a paid add-on versus a core capability, and what belongs in the free surface if you have one. These rules let a PM answer “which tier does this go in” without a meeting, because the answer is derivable from principles already agreed on.

The third is discount guardrails: the floor below which no rep can go without approval, the specific approvals required at each threshold, and the concessions that are never on the table. This is what stops the race to the bottom. Not by forbidding discounts, but by making the shape of an acceptable discount known in advance.

The constitution is not a fixed price list handed down from on high. It does not say “the Pro tier costs $49.” It says “premium tiers are priced at a consistent multiple of the base, and repricing happens on a defined cadence with defined inputs.” The numbers are downstream. The principles are the constitution.

Writing the rules before the launch changes team behavior

The behavioral shift is the point. When the principles are written down, PMs ship pricing alongside features instead of escalating each time. A product manager building a new capability can look at the constitution, determine which tier it belongs in and what it is worth, and launch it priced correctly on day one. No committee. No week-before-launch scramble. The pricing decision moves at the same velocity as the build because the hard thinking already happened, once, at the constitutional level.

This is the same move that good engineering organizations made years ago with deployment. You do not convene a meeting to decide whether each commit is safe to ship. You build the tests and the guardrails once, and then shipping is routine. A pricing constitution does for monetization what CI did for deployment: it turns a recurring high-stakes judgment call into a governed default that only escalates at the edges.

It also protects the two things ad hoc pricing erodes. Margin holds because discounting has a floor and a shape. Trust holds because the pricing model stays coherent as the product grows, so customers and reps both encounter logic instead of improvisation. A coherent pricing model is one a customer can reason about, and a customer who can reason about your prices is a customer who trusts your numbers.

Draft one without building a bureaucracy

The obvious objection is that this is rigidity dressed up as discipline. Markets move, competitors reprice, a big customer needs a custom deal, and a constitution written last year becomes a straitjacket this year. That objection would land if a constitution were a price list. It is not. A constitution sets the principles and the amendment process, and it fully expects the prices to change. The rigid thing is the absence of one, where every change requires reopening the entire question from zero.

Drafting one does not require a task force. Start with the value metric, because everything else depends on it, and write down the one you already use and why. Then write the packaging rules you are already following implicitly, and the discount thresholds sales already respects in practice. Most companies have an unwritten constitution already. The work is making it explicit and fixing the parts that do not hold up once they are on the page.

Governance is one owner and a review cadence, not a committee. Someone owns the document, and it gets revisited on a schedule and when a real trigger fires, not every time a rep wants a bigger discount. The failure mode to avoid is recreating the improvisation you were trying to kill, one exception request at a time.

The companies that ship weekly and still price by improvisation are running a modern build cycle on a pricing process from a slower era. Close that gap before your next release, and pricing stops being the thing that slows you down.