पाठशाला Pathshala · वृद्धि Vṛddhi, Growth · Lesson 28 · Scale

Pricing and packaging as a growth lever

Most companies past product-market fit leave more revenue in their packaging than in their list price. Redesign tiers, add-ons and upgrade paths so customers pay for the value they use, and ARPU rises without a price rise.

Pathshala, The Founder Library · 11 October 2026 · 7 min read

Rows of orange terracotta pots arranged closely on the ground. — Photograph: Deepak Maurya · Pexels

A company with five hundred paying customers spends a quarter debating whether to raise its price by 10 per cent. Seventy per cent of those customers are on the cheapest plan, half of whom use a feature that was meant to sit in the middle one. The price is not the problem. The packaging is.

Price is the number on the page. Packaging is everything around it: how many tiers, what each one contains, what is sold separately, what makes a customer move up and when. Two companies with the same list prices can have very different revenue per customer because their packaging sends customers to different places. This lesson is about that second lever: how to redesign tiers, add-ons and upgrade paths so that average revenue per user, ARPU, rises without anyone’s list price changing. Raising prices is a separate decision, covered in [pricing power](/library/pricing-power-raising-prices-without-losing-base), and the choice of what to charge for, seats or usage, is in [the pricing metric lesson](/library/usage-based-seat-based-hybrid-pricing).

ARPU is a packaging number

Write down three numbers from your billing system: the share of paying customers on each tier, the share who buy anything beyond their tier, and the share who moved up a tier in the last twelve months. Most companies that have never redesigned packaging find the same pattern: a large majority on the entry tier, few add-ons and little upward movement. That pattern usually means the entry tier is too generous, the middle tier has nothing a growing customer needs, and nothing prompts the move.

The arithmetic is simple and large. If a tenth of the base moves from a ₹2,000 plan to a ₹6,000 plan, ARPU rises by ₹400 a month across the whole base, with no change to any price and no new customer. Expansion revenue of this kind is what drives [net revenue retention](/library/net-revenue-retention-saas-engine) above 100 per cent, and it costs a fraction of what a new customer costs to acquire.

Tiers that follow segments

A tier should be designed for a kind of customer, not as a slice of the feature list. Look at the pricing pages of companies that have done this for years. Zoho’s CRM pricing page, as it displayed in rupees on 11 October 2026, offered a free edition for three users, then Standard at ₹800, Professional at ₹1,400, marked most popular, and Enterprise at ₹2,400 per user a month. Standard adds email, calling, multiple pipelines and forecasting for a small sales team; Professional adds process management, inventory, CPQ and predictive intelligence for a team that runs its operations on the system; Enterprise adds multi-team management, approval processes, a developer sandbox and field-level encryption for a company with several teams and an IT function. Each tier answers a different buyer.

A vintage metal tiffin carrier with engraved tiers stands on a wooden surface. — A tiffin carrier is packaging at its plainest: each tier holds something different and the buyer chooses how many to carry. Photograph: dof pinhole · Pexels

Freshworks does the same for support software. Its Freshdesk pricing page, as it read on the same date, listed Growth at $19, Pro at $55 and Enterprise at $89 per agent a month on annual billing. Pro adds multilingual support, custom dashboards, intelligent routing and multiple service-level policies, things a growing support team needs; Enterprise adds skill-based routing, a sandbox, audit logs and IP restrictions, things a large company’s IT and compliance teams require. Three tiers, three buyers.

To design your own, start where Madhavan Ramanujam, author of Monetizing Innovation, starts in his conversation on Lenny’s Podcast: segmentation before bundling and packaging. Segment the customers you have by what they value, not by size alone. Interview twenty across the base and ask which capabilities they would miss most and which they would not pay for. The [willingness-to-pay lesson](/library/willingness-to-pay-research-sets-your-price) has the questions. Usually two or three segments appear: a small team that wants the core job done simply; a growing team that wants automation, reporting and integrations; and a large organisation that wants control, security and administration. Those are your tiers.

Fences: what goes in which tier

A fence is a feature or limit that one segment needs and another does not, placed so that the segment that needs it pays for the higher tier. Good fences are things a customer needs more of as they get more value: more users, more records, more automation runs, more integrations, admin roles and permissions, audit logs and single sign-on for companies with an IT function, service-level commitments for companies whose own customers depend on you. Bad fences are features every customer needs to get the basic job done; putting those in a higher tier makes the entry tier feel broken and drives people away rather than up.

Then take things out of the entry tier that only growing customers use. This is the move most companies avoid and the one that moves the mix. If a third of entry-tier customers use reporting that was built for teams of twenty, reporting belongs in the middle tier, and the entry tier should do its own job well without it. Make the change for new customers first.

Add-ons: charging for what only some customers need

An add-on sells something that a minority values highly and the majority would not pay for in a tier price. Capacity is the commonest, extra storage, messages, records or usage. Premium support, implementation, a dedicated manager and compliance features are others. AI features are the newest: Freshdesk listed its Copilot as an add-on at $29 per agent a month on the Pro and Enterprise plans, and sold additional AI agent sessions at $49 per hundred on every plan. The benefit is that customers who do not want the feature do not pay for it, and those who do pay roughly in proportion to what they use.

Keep add-ons few. A pricing page with fifteen add-ons is a negotiation the buyer has to hold with themselves, and many will give up. Two to four add-ons, each with an obvious buyer and a price that is easy to justify, is the usual range. Watch the attach rate of each: an add-on bought by under 2 per cent of eligible customers after two quarters should be folded into a tier or dropped.

The upgrade path

Customers rarely move up because a pricing page told them to. They move when a limit bites while they are getting value. Design the path deliberately. Set limits on the entry tier where growth shows: users, projects, contacts, automation runs. Warn before the limit, show what the next tier unlocks at that moment, and make the upgrade one click. Offer the next tier as a trial inside the product; Freshdesk’s own free trial gives new accounts the Enterprise plan for fourteen days, so the buyer meets the top of the range first. Offer an annual plan with a clear discount, because a customer who commits for a year churns less and pays upfront. And give the sales team a reason to call: an account that hits a limit twice in a month is an expansion lead.

The figure shows what a change in the mix is worth at the same list prices. Set where you think the redesign moves customers and what share buys the add-on, and read the change in ARPU and the annual revenue across your base.

At the defaults, moving the mix from 60, 30 and 10 per cent to 48, 40 and 12 per cent and selling a ₹3,000 add-on to 15 per cent of customers takes ARPU from ₹4,500 to ₹5,610 a month, a rise of about 25 per cent. Across five hundred customers that is about ₹67 lakh a year, with no change to any list price.

A price rise asks every customer to pay more for the same thing. A packaging change asks the customers who get more to pay for it.

Changing packaging for customers you already have

New packaging applies to new customers on the day it launches. Existing customers need more care, because removing something they use from their plan is a price rise in disguise. The usual order is to keep existing customers on their current plan with everything they have for a stated period, often a year or until renewal, while new customers get the new tiers; then move them with notice, a clear explanation and an offer, such as the new middle tier at their old price for a year. The [pricing experiments lesson](/library/pricing-experiments-without-burning-customers) explains how to test changes on new sign-ups before touching the base.

Measure three things in the first ninety days after a packaging change: conversion from trial or free to paid, the tier mix of new customers, and churn among existing customers who were moved. If conversion falls by more than the ARPU rises, the entry tier was cut too far; restore what new customers miss most.

The quarterly packaging review

Once a quarter, the founder, product and whoever owns revenue look at one page: tier mix of the whole base and of new customers this quarter; attach rate of each add-on; upgrades and downgrades by tier, and what triggered each upgrade; the features most used by customers on each tier; and expansion revenue as a share of new revenue. Look for entry-tier customers using middle-tier capabilities, add-ons nobody buys, and limits nobody hits. Make at most one packaging change a quarter, write down what it should move, and check it at the next review.

Prices quoted from Zoho and Freshworks are as their pages showed on 11 October 2026 and change; the figure’s tiers are illustrations. Look at your tier mix this week.