SaaS Pricing Sprint

Pricing projects fail for one boring reason. They get scoped as a quarter long initiative, a committee forms, a consultant produces 60 slides, and then a product launch eats the calendar. Nothing ships.

This sprint is three lessons for exactly that reason. It produces one value metric decision and one tier map, which is the smallest change that actually moves revenue, and it stops there on purpose.

What you finish with

Four artefacts, all of them one page or less.

• A value metric decision, written as a single sentence with the evidence behind it
• A tier map with three or four packages, named features and list prices
• A sensitivity note naming which existing customers get worse off and by how much
• A rollout plan covering grandfathering, notice period and the comms sequence

That bundle is what a CFO needs to say yes. It is deliberately not a billing spec, because implementing usage metering in Stripe is a six to twelve week engineering project and does not belong inside a two week marketing sprint.

The three lessons

Lesson two is where most of the argument happens, because that is where somebody has to move a feature out of the tier their favourite customer is on. Lesson 2: Package and Price the Tiers has the grid and the rules for which features earn a tier boundary.

What you need before lesson one

Three things, and the sprint does not work without any of them.

A usage data export covering at least the last six months, with one row per account and the counts of whatever units your product meters: seats, workspaces, API calls, documents, contacts, transactions. Access to ten customers who will give you 20 minutes, ideally a mix of your best, your average and one who downgraded. And your last four quarters of win loss notes, even if they are messy Slack threads rather than CRM fields.

Run the pricing change readiness checklist before you begin. If more than three items come back red, the sprint will produce a good document that nobody can act on.

Who this is for, and who it is not for

Take this sprint if you are a founder, a product marketer or a head of growth at a company between roughly $500K and $30M ARR, with an existing price that was set by instinct two years ago, and a nagging sense that the good customers are underpaying.

Do not take it if you are pre product market fit. Below about 30 paying customers there is no signal in the usage data and your pricing problem is almost always a positioning problem wearing a costume. Also skip it if you already have a pricing analyst and a conjoint study budget. This course is for teams without one.

And if the real question is whether to charge at all, that is a different decision. The SaaS pricing strategy hub covers models, psychology and the arguments for and against freemium in more depth than a three lesson sprint should.

Why three lessons and not ten

Because a pricing project that takes ten weeks gets overtaken by a roadmap change. The two decisions that carry almost all the revenue effect are which unit you charge for and where the tier boundaries sit. Everything else, the discount policy, the annual uplift, the regional price list, is a refinement you can make later with better information.

There is a real tradeoff in that choice. A three lesson sprint will not catch cross elasticity between tiers, and it will not give you a defensible willingness to pay curve. If you are repricing a $200K ACV enterprise product where a five percent error is seven figures, hire someone. For everyone else the sprint gets you 80 percent of the value in four hours.

Pricing and packaging is where positioning gets tested, because it is the moment the customer has to agree with how you have described the value.

The vocabulary you will need

Two concepts come up constantly and get confused. Price elasticity is how demand moves when you change the price, which almost nobody can measure precisely in B2B SaaS and almost everybody claims to know. Price anchoring is the effect of the highest visible tier on how the middle tier reads, which is why the enterprise tier on a pricing page does a job even when few people buy it.

Lesson two leans on anchoring hard. Look at how Slack, Notion and Figma all put a high tier above the one they expect you to pick. That is not an accident and it is not greed. It is the cheapest way to make the middle option feel like restraint.

What happens after the sprint

The sprint ends with a proposal, not a launch. Turning the proposal into a live price change takes another 60 to 90 days, and that is what the 90 day pricing and packaging refresh playbook covers: legal review, grandfathering policy, sales enablement, billing changes and the customer comms sequence.

Before you commit, read a few real examples. The SaaS repricing case studies collection walks through changes that worked and two that were reversed inside a quarter, which is more instructive than the wins.

Related sprints

The same three to four lesson format covers two adjacent problems. The SaaS SEO Sprint builds a keyword map and a first content plan. The SaaS Positioning Sprint produces a positioning document, and it is the one to take first if your pricing confusion turns out to be a category confusion. Teams frequently start the pricing sprint, hit lesson two, and realise they cannot draw tier boundaries because they have not decided who the product is for.

Start here

Enter your email above to get the worksheet bundle, which includes the usage correlation sheet, the tier map grid and the interview script as one download. Lessons arrive one every four days, which is roughly the pace a small team can absorb without the project going quiet.

Then do the one thing that decides whether this works: book three customer calls for next week before you open lesson one.