How to Price B2B Software in India
In Indian enterprise, the approval threshold shapes your deal size more than the value does.
Summary
- Indian enterprise buys through committees, approval ladders and three-quote rules, so a deal at ₹24 lakh and one at ₹26 lakh can go through entirely different processes.
- Waived implementation is the largest uncounted discount in Indian B2B software. Put it on the quote with a number against it, or run a paid pilot.
- Price differently by geography only behind a real fence, gate tiers on requirements-to-buy, and fix terms, escalation and discount rules in every contract.
Most pricing advice for B2B software is written for a market where the buyer has a budget, a mandate and a credit card, and where published pricing is normal.
Indian enterprise is not that market. Your buyer has a committee, a procurement process, an approval ladder, and quite possibly an obligation to get three quotes. Almost nothing is published. And the person most enthusiastic about your product is frequently not the person who can sign for it.
None of that makes pricing harder. It makes it different, and the differences are learnable.
Start with what they're comparing you to
Before anything else, find out what number is already in your buyer's head. Four candidates, and only one is a competitor.
A direct competitor, which founders over-research.
A different kind of solution. Often a consultancy, an agency, or an outsourced service, and often five to twenty times the direct competitor's price. This is where a premium position becomes defensible.
The status quo. A spreadsheet, a manual process, two analysts. It has a real cost in loaded salary and time, and it's the thing you most often lose to.
Building it in-house. Very live in Indian enterprise, where captive tech teams are large and capable. The reference is headcount times months, plus the risk it doesn't ship.
If you can only quantify the first, you're negotiating with one number when your buyer has four. Finding the other three is its own discipline.
The approval threshold problem
This is the most India-specific thing in this article, and almost nobody prices for it.
Most Indian enterprises have hard limits on what can be signed at each level. A department head can approve up to some figure. Above it, a committee. Above that, a formal multi-vendor process. The exact numbers vary by company, but the structure is near-universal.
Which means a deal at ₹24 lakh and a deal at ₹26 lakh may go through completely different processes, with completely different timelines and completely different odds.
Two practical consequences.
Ask about the threshold in discovery. Not "what's your budget?", which people deflect, but "what's the approval process for something at this level?" Champions answer that question happily, because they're thinking about it too.
Sometimes price just under the line. A ₹24 lakh deal that your champion can sign this quarter is frequently worth more than a ₹28 lakh deal that goes into a tender you might lose. Land it, prove the value, and expand next year from inside the account.
That's not under-pricing. It's routing around a process cost that has nothing to do with your value.
Reverse auctions and L1 bidding
If you sell to PSUs, banks, or large corporates with formal procurement, you'll meet these.
The trap is treating every one as an opportunity. A business that bids for everything wins the wrong things at the wrong price and calls it market pressure.
Three ways to handle it properly.
Decide in advance what you won't chase. If you're the third quote being used to validate someone else's pricing, that's a cost, not a pipeline. Learn the signals and decline.
Get into the specification early. The price is often decided before the bid opens, by whoever influenced the technical requirements. If your capabilities are in the spec, the bid is much less about price.
Make your bid hard to compare. Different scope, different inclusions, different service commitment. A bid that can be lined up against two others on a single number will be decided on that number.
Charge for implementation
The largest uncounted discount in Indian B2B software is waived implementation.
It never appears on the invoice, never reaches a discount report, and costs you real engineering and project management time. You gave 100% off something with a real cost, and no approval was required because technically no discount was given.
Put it on the quote with a number against it, even if you intend to waive it. That does three things: the buyer sees what they received, you can count it, and it becomes something to trade rather than something to give.
Better still, run a paid pilot. In Indian enterprise a paid proof of concept filters out the buyers who were never serious, secures budget approval early in the cycle rather than late, and converts far better than a free one. Price it to cover your cost, credit it against year one, and agree the success criteria and the conversion price in writing before you start.
The India-versus-global question
Almost every Indian B2B software company faces this and most handle it badly.
The instinct is to quote a steeply discounted India price because it feels necessary. Then one of two things happens. A US buyer's procurement team finds the Indian pricing. Or the Indian arm of a global company demands parity with what you charge their headquarters.
Either way, your lowest price becomes your global anchor.
If you price differently by geography, the fence has to be real:
- A separate entity, currency and contracting jurisdiction
- Genuinely different packaging: different support hours, data residency, feature set or onboarding depth
- A contractual restriction on use outside the licensed territory
- A different route to market, direct in one and through partners in the other
And be honest about why the domestic price is lower. If the real answer is "Indian buyers negotiate harder," that's a sales capability problem, and discounting is the most expensive possible way to solve it.
Package for the buyer, not for the feature list
Your tiers should separate on things that matter to an enterprise buyer.
The strongest gates in Indian B2B software are the requirements-to-buy: single sign-on, trails, role-based access, data residency, security certifications, uptime commitments, a named support contact, defined response times.
These work as gates because a large customer genuinely cannot buy without them, and a small customer genuinely doesn't need them. You're not withholding anything anyone would use, which makes the gate feel fair rather than extractive.
Usage or volume makes a good second gate. Feature count makes a poor one.
Terms are where the deal is actually won and lost
Three things to fix in every contract.
Payment terms. Sixty to ninety days is normal and costs you 2.3 to 3.5% of the invoice at a realistic cost of money. Price it. Offer a real discount for advance payment: it's often cheaper than carrying the receivable, and some buyers will take it.
The escalation clause. A 6% annual uplift in a three-year contract puts year three over 12% above year one, requires no renegotiation, and is far easier to agree at signature than to impose at renewal. It's standard in global enterprise contracts and rare in Indian ones. Ask.
Most-favoured-nation clauses. Refuse them. An early customer with an MFN clause can poison your entire future price list, and the cost arrives years later when you've forgotten you agreed to it.
Govern the discount before you need to
The four-row matrix is the highest-return hour you'll spend.
Who can approve up to 10%, who up to 20%, who beyond, and a contribution margin floor nobody crosses. Plus a rule that no concession is granted without something received in return: a longer term, advance payment, a case study, a reference call.
In a market where buyers are trained to extract, a company without written rules will concede continuously and call it commercial flexibility.
Where to start
Take your last twenty closed deals. For each, work out what you actually kept: after the discount, the waived implementation, the extra seats, the unbilled support and the cost of however long you waited to be paid.
Compare that to your list price.
That gap is your real pricing problem, and it's almost always larger than the number you've been arguing about in deal reviews.
Our Pricing Maturity Assessment gives you a short read across your pricing, including the discipline items that matter most in enterprise selling.
Frequently asked questions
Should Indian SaaS companies charge less in India than abroad?
Sometimes, but only with a real fence: a separate entity, different packaging, or a territory restriction. Without one, your Indian price becomes your global anchor as soon as an international procurement team finds it. And if the only reason for the discount is that Indian buyers negotiate harder, that's a sales problem rather than a market reality.
Should I charge for implementation?
Yes, or at least show it on the quote with a value against it. Waived implementation is the largest uncounted discount in Indian B2B software. It never reaches a discount report, but it consumes real engineering time. A paid pilot, credited against year one, works even better.
How should I handle reverse auctions and L1 bidding?
Decide in advance which you'll decline, get your capabilities into the technical specification before the bid opens, and structure your bid so it can't be compared on a single number. A business that bids for everything wins the wrong work at the wrong price.
How useful was this article?
One tap. It tells us what to write more of.
The next one
Get what we publish next, by email.
Working notes on raising, borrowing, protecting, growing and structuring capital in India. One email a week at most, and you can leave any time.
We use your address only to send this. See our privacy policy.
We store your address to send you these emails and nothing else. See our privacy policy.
Related reading
