Why an Annual Pricing Review Is Too Slow When You Ship Every Month

Most software companies ship something every month. Many ship every week. Pricing, in the same company, is usually opened once a year, argued about for six weeks, and then closed again until the next planning cycle. The product changes continuously. The price list changes annually. That gap is where uncaptured revenue sits.

This is not a rare problem. In the 2025 State of B2B Monetization, Kyle Poyar of Growth Unhinged reports that three in four companies changed pricing or packaging in the past year. Pricing is already moving more than once a year in most companies. What is missing is a process that expects it to.

The cost of waiting is specific, not vague

When a release ships and pricing does not respond, three things happen in order.

First, the new capability goes into whatever plan the customer already has. Nobody decided that. It is the default, because doing nothing is easier than reopening the price list. Second, sales teams start using the new capability as a closing argument, which converts it from a reason to pay more into a reason to discount. Third, by the time the annual review arrives, the feature has been free for nine months and repricing it reads to customers as taking something away.

None of those outcomes required a bad decision. They required no decision, repeated across several releases.

Why the annual cycle persists

The same Growth Unhinged research explains why the cadence does not change on its own. Poyar found that most companies were unprepared to keep up with the pricing changes they were already making, citing personnel gaps and legacy tooling. He also found that between $5M and $20M ARR, pricing ownership often falls between teams.

That last point matters more than it first appears. Pricing sits across product, finance and sales. When it belongs to all three it belongs to none of them, and work that belongs to nobody defaults to the slowest possible cadence, which is whatever the annual planning calendar imposes.

In text: 3 in 4 companies changed pricing or packaging in the past year. $5M to $20M ARR band where pricing ownership often falls between teams.

What a lighter review looks like

The answer is not to run the full annual exercise four times a year. That exercise is heavy because it tries to settle everything at once: model, price points, packaging, discounting and migration. Most releases do not require all of that.

A quarterly review can be narrow. It asks three questions about what shipped since the last one.

Does this capability change who the product is for, or what a customer can now do that they could not before? If the answer is no, it belongs in the plan it landed in and the review is over in ten minutes.

If the answer is yes, does it belong in the core plan, as a paid add-on, or in a higher tier? This is a packaging question, not a price question, and it is usually answerable from usage data plus a handful of customer conversations.

If it belongs somewhere other than where it landed, what does moving it do to existing customers? That is the only part that needs real modelling, and it only applies to the small number of changes that clear the first two questions.

In text: 1. List what shipped since the last review 2. Flag only what changes who buys or what they can do 3. Decide core, add-on or higher tier 4. Model the effect on existing customers

Ownership before cadence

Changing the calendar without changing the ownership produces a meeting that nobody can act on. One person needs to own the recommendation, with product, finance and sales represented rather than in charge. That person does not need to be a full-time pricing hire at every company size, but the role has to exist somewhere other than in the gaps between three teams.

The work also needs a standing data foundation. A quarterly review is only light if the inputs are already there. If each cycle begins by exporting billing records, pulling deal data out of the CRM and asking engineering for usage counts, the review will quietly become annual again, because the preparation is the expensive part.

What to change first

If you are running an annual cycle today, the first change is not the cadence. It is writing down who owns the recommendation and what data they get automatically. Once those two things exist, moving to quarterly is a calendar change rather than a project.

The second change is deciding, as a standing rule, what happens by default when a feature ships without a pricing decision. Right now the default at most companies is that it joins the cheapest plan the customer already has. That is a choice, even when nobody makes it deliberately.

If your release cadence has outrun your pricing cadence, our pricing and packaging work starts by building the baseline that makes a lighter review possible.

Related reading: The Four Data Sources Every Pricing Decision Needs and Using the Product Roadmap to Decide What Creates Value and How to Charge for It.