Should we raise our prices?

Very few founders enjoy this conversation. Pricing feels like the one decision where a mistake is immediately visible: customers leave, a competitor undercuts you, and the quarter is ruined.

So prices stay where they were set, often two or three years ago, when the product did less, the team was smaller and the market was different. Meanwhile salaries rise every year, cloud costs rise, and the margin quietly closes.

The useful correction is arithmetic. Before deciding whether a rise is risky, work out exactly how much volume it could afford to lose.

The number that makes the decision calmer

If your contribution margin is m and you raise prices by p, total contribution stays level as long as volume falls by less than p divided by m plus p.

That formula does more to settle pricing arguments than any amount of discussion, because it turns a fear into a threshold.

• ·At a 25% contribution margin, a 10% price rise can lose 28.6% of volume before contribution falls.
• ·At 40%, it can lose 20%.
• ·At 50%, it can lose 16.7%.
• ·At 70%, it can lose 12.5%.
• ·And in reverse: at a 40% margin, a 10% discount needs volume to rise by 33% just to stand still.

Two things follow. Low-margin businesses have the most room to raise prices and the least room to discount, which is the opposite of how most of them behave. And a discount is a far bigger decision than a price rise, because it needs a large volume response to break even and usually does not get one.

Signs you are underpriced

The arithmetic tells you what you can afford. These signals suggest you probably should.

• ·You almost never lose a deal on price. A healthy win rate on price is not 100%.
• ·Customers say yes immediately, without negotiating.
• ·Your sales team discounts rarely, because they do not need to.
• ·Customers who joined three years ago pay what new customers pay, despite the product doing far more now.
• ·Support and delivery costs have grown but the price has not, so contribution per customer has fallen.
• ·You are visibly cheaper than alternatives your customers also considered.
• ·Churn is low and usage is high, which means customers are getting more value than they pay for.

Three or more of those and the question is not whether to raise prices but how much, and how to do it without unsettling the customers you most want to keep.

Raise on new customers first

The safest price rise affects nobody who has already bought. New customers have no reference point, so the only risk is on deals in the pipeline, and that risk is measurable within a quarter.

Run it as a test. Raise list prices, keep the old price available for deals already quoted, and watch three numbers for a quarter: win rate, average deal size, and how often price comes up as an objection. If win rate holds, the rise was overdue. If it falls slightly but average deal size rises more, you are ahead. If it collapses, you have learned something cheaply.

Most companies that do this discover the rise was smaller than it could have been.

Then handle the existing base

Existing customers are where the anxiety lives, and where the money usually is. A few rules make it go well.

1. 01Raise at renewal, not mid-contract, unless the contract explicitly allows it. Contracts that allow annual increases are worth writing that way from now on.
2. 02Give notice. Thirty to sixty days is normal, and the notice matters more than the amount.
3. 03Give a reason that is about them: what the product does now that it did not, what support they get, what has been invested. Not your cost base.
4. 04Protect the customers you most want to keep, explicitly, with a smaller rise or a longer transition. Decide who they are in advance rather than in response to complaints.
5. 05Offer something in exchange where you can: an annual plan at the old price, extra seats, a feature they have asked for.
6. 06Expect some churn and decide in advance what level is acceptable. Losing a few of your least profitable customers after a price rise often leaves the business better off.

A worked example

Illustrative figures for a fictional company. A B2B software business has 260 customers paying an average of ₹16,000 a month, with a contribution margin of 62%. Monthly revenue is ₹41.6 lakh and contribution is about ₹25.8 lakh.

It raises prices 9% for new customers immediately, and at renewal for the existing base over the following year. On the arithmetic, it could lose about 12.7% of volume before contribution falls.

What actually happens, in this illustration: win rate on new business is unchanged, and about 4% of existing customers leave at renewal, mostly the smallest accounts with the heaviest support load.

The result is roughly ₹43.5 lakh of monthly revenue and about ₹27 lakh of contribution, on a slightly smaller and noticeably less demanding customer base. That is ₹1.2 lakh a month, close to ₹14 lakh a year, from one decision, with no new customers and no extra spending.

A price rise is the only growth lever that costs nothing to pull and works immediately.

Running the test properly

A price change is one of the few decisions where a real experiment is available, and most companies skip it because the arithmetic feels obvious once it is written down. Running it anyway gives you evidence for the harder conversation about the existing base.

1. 01Fix the window: one quarter, or fifty deals, whichever comes first. Long enough for a pattern, short enough that you do not lose a year.
2. 02Change one thing. A new price and a new packaging structure at once tells you nothing about either.
3. 03Record the objection, not just the outcome. Price mentioned as a factor is different from price being the reason a deal was lost.
4. 04Watch deal size and cycle length as well as win rate. A rise that lengthens the sales cycle by a month has a cash cost that the win rate hides.
5. 05Check who you are winning. If the rise filters out customers who would have churned, that is a gain the revenue line will not show for a year.
6. 06Decide in advance what would make you reverse it, and what would make you go further.

One caution about averages. If your product sells into two quite different segments, run the test in each. It is common for a rise that is invisible to larger customers to be decisive for smaller ones, and that tells you the answer is segmented pricing rather than a single number.

Pricing is rarely one number

Most companies that think they have a pricing problem actually have a segmentation problem. One price for customers who get very different amounts of value means the larger ones are underpaying and the smaller ones are expensive to serve.

Three ways to split, in rough order of how easy they are to introduce.

• ·By size: seats, users, locations or transaction volume. Easy to explain, easy to administer, and it scales revenue with the customer rather than with your effort.
• ·By what is included: tiers with different features, support levels or service commitments. It lets customers self-select, and it gives your sales team something to offer other than a discount.
• ·By usage: charge for what is consumed. It aligns revenue with value, and it is the right answer for products whose costs scale with use, including most products built on paid models and APIs.

Whichever you choose, the finance work is the same: contribution by segment before and after, so you can see which customers were subsidising which, and what the change does to the mix rather than to the average.

What customers actually say

Founders imagine the worst reaction. What usually happens is duller. A minority ask for an exception, a smaller minority leave, and most simply accept it, particularly when the notice is decent and the reason is about them.

The exceptions are worth planning for. Decide in advance what you will offer: a longer transition, a smaller rise for multi-year customers, or an annual prepaid option at the old price. Handing that decision to whoever picks up the phone produces inconsistency, and inconsistency is what customers actually resent.

And expect the loudest objections from the smallest accounts. That correlation is common enough to plan around, and it is a reason to work out contribution per customer before the rise rather than after.

When not to raise prices

• ·When churn is already high. Fix retention first, or a price rise will accelerate what is already happening.
• ·When the product has visibly slipped: reliability problems, support backlogs, a feature everyone asked for that never arrived.
• ·When you are in the middle of a competitive displacement and price is genuinely the reason you are winning.
• ·When a few large customers are up for renewal at once, and the concentration risk of losing one outweighs the gain.
• ·When you cannot explain what customers get for the money. If you cannot articulate it, they will not accept it.

In most of these cases the issue is not pricing. It is that the value being delivered is not clear enough to charge for, which is a product and delivery problem wearing a pricing problem's clothes.

What about changing how you charge?

Sometimes the right answer is not a higher price but a different structure. Charging per seat when value scales with usage, or per project when the client wants certainty, creates a permanent mismatch between what you deliver and what you collect.

Three structures worth considering, each with a trade-off. Usage-based pricing aligns revenue with value and makes revenue less predictable. Tiered pricing captures more from customers who get more, and adds complexity to every sales conversation. Annual prepaid plans improve cash and retention, and require a discount.

Structure changes are slower and riskier than a price rise, so they belong in a planned review rather than a response to a tight quarter. But they are where most of the upside sits for companies whose pricing was set when the product was much simpler.

What to do this month

1. 01Calculate contribution margin properly, after every cost that varies with a sale, not just cost of goods.
2. 02Work out how much volume a 5% and a 10% rise could afford to lose.
3. 03Compare list price with realised price across your customers, and find out where discounts have been given and to whom.
4. 04Look at contribution per customer by segment. Underpricing is rarely uniform; usually one segment is carrying the rest.
5. 05Raise list prices for new customers, and watch win rate for a quarter.
6. 06Decide the renewal plan for the existing base, including who is protected and what the acceptable churn is.

The first two steps take an afternoon and change the conversation from a fear to a threshold. The rest is execution, and it is usually less dramatic than founders expect.

About Simplify

Simplify is a finance clarity and investment readiness practice working with founders across India, built on six years inside startups. We write about the questions founders bring before a decision, not after it.