Most pricing projects run for months, produce a thick deck, and change almost nothing. A focused six-week sprint fixes that by treating packaging and monetization as one coupled problem rather than two separate studies. Each week carries a single deliverable and a decision gate, moving from willingness-to-pay evidence to a value metric, three tiers, a modeled migration, and a live price in market. The payoff is a small, evidence-backed change that lifts average revenue per account and compounds through every renewal, not another slide deck nobody defends.
Why pricing projects stall, and why six weeks is the right box
Pricing is the single highest-leverage number a company controls, yet most pricing work never ships. A typical review runs four to six months, produces a 60-slide deck, and ends with a 3 percent list-price bump that nobody defends in the next renewal. The reason is scope: teams try to re-architect packaging, discounting, contracts, and billing at once, so nothing reaches market. A time-boxed sprint inverts this. Six weeks is long enough to gather real willingness-to-pay evidence and short enough that the organization commits to a single, shippable change instead of an open-ended study.
The other failure is treating packaging and monetization as separate. Packaging is what you sell as a unit; monetization is the metric you charge on and the price attached to each tier. Change one without the other and you get tiers that do not map to value, or a value metric that customers cannot forecast. The sprint below keeps them coupled. It assumes a B2B software or services business with an existing book of customers, a working funnel, and a finance team that can model a price change before it goes live.
The prize is concrete. Moving average revenue per account from 12,000 to 15,000 dollars across a base of 800 customers is 2.4 million dollars of recurring revenue at close to full margin, and it compounds through every future renewal. That is the kind of result a focused six-week sprint can defend, because the change is small, evidence-backed, and staged. The discipline is not in the analysis; it is in shipping one thing that moves the number and leaving the rest for the next cycle.
The six-week packaging and monetization sprint
Each week has one deliverable and one decision. Nothing carries forward until the prior decision is made, which is what keeps the sprint from turning into a study. The table below is the operating plan; treat the outputs column as the evidence you must produce before advancing.
| Week | Focus | Primary output | Decision gate |
|---|---|---|---|
| 1 | Willingness-to-pay evidence | Van Westendorp plus 15 to 20 buyer interviews; win/loss on the last 40 deals | Confirm the acceptable price band and top 3 value drivers |
| 2 | Value metric selection | Candidate metrics scored on alignment, predictability, and ease of metering | Pick one primary metric that scales with customer value |
| 3 | Packaging and tiers | Good/better/best design with feature fences and target ARPA per tier | Lock 3 tiers and the fences between them |
| 4 | Price setting | Price points, list vs floor, discount guardrails, expansion levers | Approve list prices and maximum discount authority |
| 5 | Finance and migration model | Cohort model: new logos, renewals, grandfathering, churn sensitivity | Sign off on net revenue impact and migration plan |
| 6 | Launch | Updated pricing page, quotes, CPQ rules, sales enablement, live change | Go live on new logos; schedule renewal migration |
The decision gates matter more than the artifacts. A gate forces a named owner to commit, which is what prevents the sprint from collapsing back into analysis. If a gate cannot be passed, you do not extend the week; you narrow the scope until the decision is makeable. In practice the hardest gate is Week 2, the value metric, because it touches billing and every downstream tier. Resist the urge to perfect it. A metric that is directionally right and easy to meter beats a theoretically ideal metric your systems cannot bill on for another two quarters, and you can refine it once live usage data arrives.
How to run the sprint so it ships
- Anchor Week 1 on real money, not opinions: pull win/loss notes and actual discount depth from your last 40 deals before you interview a single buyer, so willingness-to-pay evidence is grounded in what customers already paid rather than what they say they might pay.
- Choose a value metric that the customer can forecast a year out. If a buyer cannot predict their bill within roughly 20 percent, the metric will drive churn no matter how well it aligns to value, so favor a metric tied to a number the customer already tracks.
- Design exactly three tiers and defend the fences. Every feature you move up a tier should map to a documented value driver from Week 1, not to a hunch about what feels premium, and each fence should push a clearly different buyer to a clearly different tier.
- Model the migration before you set list prices, not after. Grandfathering, renewal timing, and discount guardrails swing net impact more than the headline number does, and a 15 percent list rise can turn net-negative once the installed base is protected.
- Ship the change on new logos in Week 6 and migrate the installed base on renewal. Never re-price the whole book at once; stage it so you can read elasticity from live cohorts and pull back before a bad assumption reaches every customer.
Where six-week pricing sprints go wrong
- Chasing a perfect value metric. Teams burn two weeks debating metering edge cases. Fix: pick the metric that is 80 percent right and easy to meter now; refine it in the next cycle once you have live usage data.
- Building four or five tiers to please every segment. This dilutes the good/better/best contrast and stalls sales. Fix: hold to three tiers and use add-ons for the edge cases.
- Setting price before finance models migration. A 15 percent list increase can be net-negative once grandfathering and churn are counted. Fix: make Week 5 sign-off a hard gate before any price is announced.
- Skipping discount guardrails. A clean list price collapses in the field when reps discount freely. Fix: set maximum discount authority by tier and route exceptions to a named approver in the CPQ rules.
- Launching without enablement. Reps quote the old price for months if the change is not built into quotes and scripts. Fix: treat CPQ rules, the pricing page, and a one-page battlecard as Week 6 launch blockers, not follow-ups.
Before you start the sprint
- Confirm you can pull actual discount depth and win/loss notes on the last 40 deals within two days.
- Name one decision owner per weekly gate and put the six dates on calendars now.
- Confirm finance can model a cohort migration, including grandfathering and churn sensitivity, in Week 5.
- Verify your billing and CPQ stack can meter the likely value metric before you commit to it in Week 2.
- Agree up front that Week 6 ships to new logos only, with installed-base migration staged on renewal.