B2B SaaS pricing for India: why discounting is not a strategy

Every SaaS sales conversation in India eventually arrives at the same request: what can you do on price. The instinct that usually follows -- shave 20 to 30% off the US list price and call it the India rate -- is not a pricing strategy. It is an admission that the price architecture was built for one market and stretched to cover another.

The stakes for getting this right are not small. Gartner forecasts that software spending in India will grow 17.6% in 2026 to reach $24.7 billion, inside a broader IT spending market projected to cross $176 billion (Gartner, November 2025). That growth is concentrated in enterprises and mid-market companies that are increasingly sophisticated buyers of software, not a single undifferentiated price-sensitive market waiting for a discount. Vendors who treat India pricing as a line-item markdown on a global price book are leaving structured revenue on the table in the segments that can pay full freight, and losing deals they should win in the segments that cannot.

This piece covers four things: why a flat percentage discount fails structurally, why India's mid-market and large-enterprise buyers need different price architectures rather than one number, why usage-based pricing beats seat-based in most India SaaS contexts, and what Indian enterprise buyers are actually comparing your price against.

Why flat percentage discounts fail

A flat India discount treats an entire country as one buyer. In practice, willingness to pay for the same SaaS category can differ by a factor of five or more between an Indian mid-market company and a large enterprise or a global capability centre -- buyers a flat percentage cannot distinguish between. That has three specific consequences.

It invites negotiation theater instead of a value conversation. When both sides understand list price to be inflated, procurement's only job becomes finding the real number. OpenView Partners' enterprise SaaS benchmarks put typical discount levels at 15 to 25% for high-growth category leaders, 20 to 35% for established solutions in competitive markets, and 30 to 40% for mature, commoditised products. Once a pattern like this becomes known behaviour inside a buyer community as small and well-networked as enterprise IT and CFO circles across Delhi, Mumbai and Bengaluru, every renewal conversation starts from what the last account got, not what the product is worth.

The discount becomes the new list price. RAIN Group's 2026 negotiation research puts the median discount on closed-won B2B SaaS deals at 12 to 22%, with enterprise deals trending toward the higher end. Whatever a rep gives to close a deal quickly becomes the number procurement anchors to at renewal, and the number the next prospect's CFO hears about before your rep is even in the room.

It ignores that discount depth should track deal risk and structure, not geography. A three-year commit, a multi-product attach, or a reference-account arrangement all justify a deeper price than list. A flat India percentage collapses all of that into a single number applied regardless of what the buyer is actually offering in return.

A single India percentage sits somewhere inside structural discount ranges by accident. The discount that is correct for a mature, commoditised product competing on price is not the discount that is correct for a category leader with no real India substitute.

Mid-market and large enterprise are not the same India buyer

Indian mid-market companies, broadly in the Rs.100 to 1,000 crore revenue band, typically run a lean buying process: a business head who owns the budget, a finance or IT lead who validates the number, and rarely a formal RFP. Decisions move in weeks. The comparison set is whatever else the founder or CXO has recently priced -- usually a mix of India-built SaaS and global tools a peer company is already using. Price sensitivity is real, but it is sensitivity to the wrong number, not to value, which means the right price architecture can shift the conversation entirely.

Large enterprise -- Rs.1,000 crore-plus groups -- and India-based global capability centres operate on a different clock entirely. Procurement is formal and RFP-driven, and the procurement function's mandate, cost reduction, runs independently of the business case the requesting department built. Security review, data residency checks and legal redlining routinely add eight to twelve weeks to a cycle that the business sponsor thought would close in a month. Budget authority for a six or seven-figure annual software commitment sits two or three layers above the person championing the product.

These two buyers do not respond to the same price architecture. A single flat discount applied uniformly across both either overcharges the mid-market buyer -- who could close at a leaner structure with a lighter contract -- or leaves enterprise value uncaptured, because procurement will always find room to negotiate against a number it does not respect.

Why usage-based beats seat-based in most India SaaS contexts

Global pricing has already been moving away from seats for several years. Gartner projects that 70% of businesses will prefer usage-based pricing over per-seat models, and OpenView Partners' benchmark of roughly 600 SaaS companies found usage-based pricers growing 29.9% year over year against 21.7% for seat-based peers -- close to 38% faster -- with net dollar retention near 120% against 110% for seat-based peers.

That global shift matters more in India than the average market, for a reason that has little to do with global trends and everything to do with how Indian finance teams manage software cost. Indian mid-market and enterprise finance functions scrutinise seat utilisation aggressively, because unused licenses are one of the easiest line items for a CFO to cut in an annual budget review, and because the conversation about utilisation starts before a contract even renews. A seat-based pricing model hands procurement a reason to downsize the contract at every annual review. Usage-based pricing removes that lever.

This is not an argument for pure usage-based pricing everywhere. Hybrid pricing -- a predictable base fee plus a usage or outcome-based layer -- is now the most common structure globally. Chargebee's 2025 State of Subscriptions Report found 43% of SaaS companies already using hybrid models, projected to reach 61% by end of 2026. In India specifically, hybrid does more work than pure usage-based or pure seat-based: it gives the CFO a predictable floor for budget planning and a variable layer that correlates cost to value delivered.

The Indian CFO's objection is rarely "your price is too high." It is "I cannot defend this line item at the next budget review." Usage-based pricing answers that objection. Seat-based pricing invites it.

Building an India price architecture that does not undermine global pricing

Five mechanics keep an India-specific price from leaking into, or undercutting, the global price book.

• Price on a different unit than the global list, where possible. A per-seat price in INR is trivially comparable to a USD per-seat price with a currency converter. A usage or outcome-based unit, priced independently against India-specific value delivered, is far harder for a global prospect's procurement team to cross-reference, because it is not the same unit of measure.
• Anchor the India number to research, not a discount off the US number. Purchasing power differences between India and developed markets are real and documented -- the World Bank's International Comparison Program is the standard reference for cost-of-living differentials -- but a defensible India price is one built from India-specific willingness-to-pay data for your category and segment, not a percentage borrowed from another vendor's India strategy.
• Keep the India price book operationally separate, with its own SKUs, quote templates and approval workflow, so a rep selling into Singapore or Dubai cannot casually apply the India number to a deal outside India. Deal desk should treat any cross-border quote referencing the India price sheet as an escalation requiring sign-off.
• Verify buyer geography before applying India pricing, particularly in self-serve or product-led motions where checkout can be gamed with a billing address or a VPN. Enterprise deals carry lower risk here, since procurement geography is verifiable through the contracting legal entity, but any self-serve India tier needs geography verification built into the flow.
• Document the rationale internally. When a global account team or a board member asks why the India number is a third of the US number, "an India-specific willingness-to-pay study put the number at X, and India cost-to-serve at Y" survives scrutiny. "Sales wanted to close the deal" does not -- and that difference is what separates a price architecture from an ad hoc discount that happened to repeat itself.

What Indian enterprise buyers actually compare your price against

This is where most global SaaS vendors misread the India conversation. The default assumption is that the Indian buyer is comparing your price against a competitor's price card. Across GreyRadius mandates involving India buyer research, the more consequential comparison is rarely competitor-to-competitor. It is build-versus-buy, and the build side of that comparison is unusually cheap in India.

Indian offshore engineering talent bills at $20 to $45 an hour, a 50 to 85% reduction against equivalent US hires depending on role seniority (Wisemonk India IT Services Analyst Report, 2026). For an Indian IT leader evaluating a six or seven-figure annual SaaS contract, the mental comparison is not "what does the closest global competitor charge." It is "what would it cost to build and staff a team to replicate the most critical features of this product." That benchmark sets a ceiling on India willingness-to-pay that is far lower than a global pricing model typically assumes.

The second comparison Indian buyers reach for is the domestically-built SaaS alternative, priced for exactly this market. Zoho's CRM Enterprise tier lists at $40 per user per month against Salesforce Enterprise at $175 -- a gap of roughly 77% at list price (checkthat.ai pricing analysis, 2026). Freshworks, Kissflow and a deep bench of India-built SaaS products occupy similar territory. Global vendors rarely lose to these products on features. They lose because these products have set the reference price point in the Indian buyer's head for what enterprise software costs. A global vendor's India price does not need to match that number, but it needs a credible answer for why it costs multiples more -- and "because that's our global price converted to rupees" is not that answer.