pricing strategy

Most PMs will spend years agonizing over feature specs, sprint planning, and roadmap prioritization. They will spend almost zero time thinking about pricing. This is a mistake. Pricing determines who your customer is, how they perceive your product, and whether your company survives. Get every feature right and price wrong, and you have built a beautiful thing nobody pays for.

The reason PMs avoid pricing is that it feels like someone else’s job. Finance sets the numbers. Sales negotiates deals. Marketing positions the tiers. But pricing is a product decision. It shapes what you build, who you build it for, and how they use it. A PM who does not understand pricing cannot make good product decisions — they are designing a car without knowing whether it is a Maruti or a Mercedes.

This page covers pricing models, strategies, and the specific decisions Indian PMs face — where willingness to pay, market structure, and competitive dynamics differ significantly from Silicon Valley playbooks.

The three pricing models that matter in software

Forget cost-plus pricing. In SaaS and digital products, your marginal cost of serving one more user is close to zero. Cost-based thinking leads you to underprice your product because your costs are low, or overprice it because you are trying to recoup R&D. Neither reflects what the customer values.

Three models matter for software PMs:

Competitive-based pricing

You look at what competitors charge and position yourself relative to them. This is the default model for most Indian SaaS companies, and it is the laziest one.

When Zoom entered the video conferencing market, they benchmarked against existing players and priced slightly below. When Indian SaaS tools enter a category — project management, CRM, marketing automation — the instinct is to price 30-50% below the American incumbent and compete on cost. This works for market entry. It becomes a trap when it trains your entire customer base to see you as the cheap alternative.

Competitive pricing tells you where the market is. It does not tell you where your product should be. Use it as an input, never as the strategy.

Value-based pricing

You price based on the value your product creates for the customer, not based on what it costs you to build or what competitors charge. If your product saves a logistics company 40 lakhs a year in operational costs, charging 4 lakhs a year is reasonable — they get a 10x return.

This is the model every pricing expert recommends. It is also the hardest to execute, because it requires you to know, quantify, and prove the value you create. Most PMs cannot answer the question: “How much money does your customer make or save because of your product?” If you cannot answer that question, you cannot do value-based pricing.

The key insight: when you set value-based pricing, you price at a fraction of the value created. Not 50%. More like 10-20%. If you help a company save a crore, you charge 10-20 lakhs. The customer needs to feel that the ROI is obvious and undeniable. The moment they have to squint to see the value, you have priced too high.

Usage-based pricing

You charge based on consumption — API calls, transactions processed, seats used, storage consumed. AWS, Stripe, and Twilio built empires on this model. It aligns your revenue with your customer’s growth: when they do well, you do well.

Usage-based pricing is increasingly common in India, especially for infrastructure and developer tools. But it creates a PM challenge: your roadmap now directly affects revenue in ways that are hard to predict. A feature that reduces API calls might make the product better while reducing your revenue. A feature that increases engagement increases your revenue but might annoy users who feel they are being charged for clicking around.

If you go usage-based, the PM must own the pricing metric — the unit of value you charge for. Pick the wrong metric and you create misaligned incentives. Slack charges per seat. Twilio charges per message. Snowflake charges per compute second. Each metric reflects what value the customer actually receives. Charging per seat for a product where only two people use it actively but the whole team needs access is a fast way to lose deals.

The freemium trap

Every second SaaS pitch deck in India includes “freemium” as a strategy. Free tier to acquire users, paid tier to monetize them. Simple in theory. A graveyard in practice.

Freemium works when three conditions are met simultaneously:

1. The free tier delivers real standalone value. Not a crippled trial. A genuinely useful product. Notion’s free tier lets a single user do almost everything. That is why people adopt it.

2. There is a natural expansion trigger. Something in the user’s growth forces them to upgrade. For Notion, it is collaboration — you need the team plan when your team grows. For Dropbox, it was storage limits. The trigger must be organic, not artificial.

3. Your cost to serve free users is low enough to sustain at scale. If each free user costs you meaningful infrastructure money, freemium will bleed you dry before the conversion math works out.

The Trello story is the cautionary tale every Indian PM should study. Trello had a phenomenal free product. Millions of users. But the free tier was too good — most users never needed to upgrade. When Atlassian acquired Trello, the conversion rate was painfully low. A product used by millions that could not build a billion-dollar standalone business because the free tier consumed the value that should have been monetized.

The alternative to freemium is not always a paywall. It can be a time-limited trial (14 or 30 days), a usage-limited free tier (Slack’s 90-day message history), or a reverse trial (full product access that downgrades after the trial period). Each one changes user behavior in different ways. The PM’s job is to pick the model that creates the right conversion pressure without destroying the adoption flywheel.

Pricing in the Indian market: what the textbooks skip

Indian PMs face pricing dynamics that most Western pricing content ignores entirely.

Willingness to pay is structurally different. A mid-market Indian company will not pay $50/seat/month for a SaaS tool, even if the American equivalent charges $50 and the Indian company gets the same value. The reference point is different. Purchasing power parity matters. India pricing for most SaaS products is 30-60% of US pricing — and this is not “discounting,” it is market-appropriate pricing.

Annual billing is the norm, not the exception. Indian businesses prefer annual contracts. Monthly billing feels transactional. Annual billing with a discount (typically 15-20%) is the default expectation. If you only offer monthly billing in the Indian B2B market, you are leaving money on the table and creating unnecessary churn risk.

Decision-making involves more stakeholders. Pricing that targets a single buyer persona (the “PM who can expense $20/month on a credit card”) does not work in most Indian companies. Procurement is involved. Finance signs off. The ticket size that requires no approval is much lower — often under 5,000 rupees. Design your pricing tiers with this in mind: the tier that lands below the approval threshold gets adopted fastest.

The “jugaad” competitor. In almost every software category in India, there is a local competitor offering 80% of the functionality at 20% of the price, often built on top of open-source tools. You cannot out-price them. You must out-value them. This is where value-based pricing becomes not just a nice idea but a survival requirement — you need to articulate exactly why your product is worth 5x more, in terms the buyer’s finance team will approve.

Tiered pricing: where features meet segments

Most SaaS products end up with tiered pricing — three or four plans at different price points. The PM’s job is to decide what goes where. This is a product decision disguised as a pricing decision.

The principle: each tier should correspond to a different customer segment with a different willingness to pay and a different use case. Not a different “level” of the same use case.

Notion does this well. The free tier is for individuals. The team tier ($8/member/month) adds collaboration. The enterprise tier adds admin controls and security. Each tier maps to a segment — individual, team, organization — not to “basic,” “better,” “best” versions of the same thing.

The common mistake: putting a feature in the expensive tier to create “upgrade pressure” when that feature is actually core to the product’s value proposition. If your reporting module is what makes users successful but you lock it behind the enterprise plan, your free and mid-tier users will churn before they ever get to the upgrade conversation.

Price discrimination done right: find the axis of value that naturally separates your customer segments. For Slack, it is team size. For AWS, it is usage volume. For a B2B analytics product, it might be the number of data sources connected. The axis should correlate with the value the customer receives, not with an arbitrary limit designed to annoy people into upgrading.

Three pricing strategies for market entry

When launching a new product or entering a new market, you are not just setting a price. You are signaling your position.

Penetration pricing: Price low to grab market share fast. The SaaS equivalent of a consumer electronics company launching at half the competitor’s price and eating the short-term losses. Works when you have funding to sustain it, the market is large, and switching costs will keep customers after you raise prices. Dangerous when customers anchor on the low price and revolt when you increase it.

Skimming: Price high at launch, targeting early adopters who will pay a premium. Gradually lower the price to capture more price-sensitive segments. Works for genuinely novel products with no direct competitors. Rare in SaaS — more common in hardware and enterprise AI, where the first customers are large enterprises willing to pay for early access.

Anchoring and bundling: Set a high anchor price for the full product, then offer bundles or tiers that make the mid-range option look like a bargain. The classic “Good, Better, Best” structure where the middle tier is designed to be the most popular. The top tier exists primarily to make the middle tier feel reasonable.

Most Indian SaaS companies default to penetration pricing because competing on price feels safer than competing on value. The long-term cost is that you build a customer base that expects low prices forever and churns the moment you try to monetize properly.

Revisiting pricing: the most neglected PM habit

Pricing is not a launch decision. It is a living system that should be revisited quarterly. Market conditions change. Your product’s value changes. Your competitive landscape changes. A price set 18 months ago may be leaving significant money on the table or driving away customers who would convert at a different point.

The signals that tell you it is time to revisit pricing:

• Conversion rate on your highest tier drops while mid-tier grows — your top tier is overpriced or under-differentiated
• Sales consistently discounts to close deals — your list price is disconnected from perceived value
• A competitor enters at a significantly different price point — the market’s reference price has shifted
• You shipped a major capability that changes the product’s value equation — if you added something that saves customers twice as much, your price should reflect that
• Customer acquisition cost is rising while ARPU is flat — you are paying more to acquire customers who pay you the same

The PM’s pricing checklist

Pricing is cross-functional. But the PM owns the intersection of customer value, product capability, and market positioning. Here is what you should be able to answer before any pricing conversation:

1. What is the unit of value? What does the customer get more of when they pay more? (Seats, usage, features, support level)
2. Who are the segments? Do you have genuinely different customer types with different needs and different willingness to pay?
3. What is the expansion trigger? What natural event in the customer’s growth causes them to need more from your product?
4. What is the competitive anchor? What do customers compare your price to? (It may not be your direct competitor — it may be the manual process they are replacing.)
5. What is the approval threshold? At what price point does the decision go from “individual can decide” to “needs procurement approval”?

If you cannot answer all five, you are guessing. And pricing is too important for guessing.

Test yourself

Where to go next

• PLG vs sales-led — pricing determines the motion: PLG vs Sales-Led — how pricing architecture drives your GTM choice
• Understand how pricing connects to company strategy: Product Vision and Strategy
• Learn to defend pricing decisions with data: Metrics and KPIs
• See how pricing affects competitive positioning: Market Analysis
• Practice the cross-functional pricing conversation: Stakeholder Management