How do you increase average revenue per user?

Increasing average revenue per user (ARPU) comes down to three levers: charging more for what you already deliver, expanding what you deliver so customers willingly pay more, and reducing the friction that keeps users from upgrading. Most founders underuse all three because they confuse low prices with user love—but real user love comes from solving problems so well that price becomes a secondary concern.

Start by understanding what users actually value, not what you assume they value

The most common reason ARPU stays low is that pricing was set arbitrarily at launch and never revisited. Founders pick a round number, watch it not cause churn, and assume it's correct. It almost never is. Before you touch your pricing page, run structured conversations with your best customers—the ones who'd be genuinely upset if your product disappeared tomorrow. Ask them to walk you through the last time your product saved them money, won them a deal, or saved significant time. When customers start describing impact in dollar terms, you're hearing the real ceiling of your value.

This matters because most SaaS and consumer products are priced on cost-plus intuition rather than on value delivered. A tool that saves a sales team four hours a week has a calculable dollar value to that team—and that number is almost always far above what you're charging. The gap between what you charge and what you're worth is your pricing headroom. Closing that gap is the most direct path to higher ARPU without acquiring a single new customer.

Tactically: segment your current users by how much value they extract. Power users who hit usage limits, integrate your product with other tools, or bring in teammates are telling you something. They're showing you where the next pricing tier belongs. Build the tier around what they're already doing, not around artificial feature gates that annoy rather than delight.

Build product depth that justifies higher prices rather than manufactured differentiation

Paul Graham's argument in his writing on branding is that genuine quality—not surface-level distinctiveness—is what earns premium pricing. The implication for product strategy is direct: cosmetic differentiation (a unique color scheme, a quirky brand voice, a 'distinctive style') doesn't hold up under pressure. What holds up is a product that solves the problem better than anything else a user can find.

This means your path to higher ARPU runs through product investment, not marketing investment. Every time you add a feature that a power user specifically needed, you create an anchor for a higher pricing tier. Every integration that makes your product stickier inside a workflow raises switching costs and justifies price increases. Every reliability or performance improvement that users stop noticing because it's invisible and flawless—that's compounding trust that makes renewals and upsells frictionless.

A practical signal that your product depth is insufficient: users describe your product as 'nice to have' rather than 'mission critical.' If your tool is optional, your price is always under pressure from budget cuts and competitive alternatives. The strategic goal is to become load-bearing infrastructure in your users' daily workflow. That's not achieved through positioning language—it's achieved by being genuinely difficult to remove without breaking something your users care about.

Use packaging and tiers to let users self-select into higher value

Flat pricing is a tax on your best customers. If everyone pays the same amount, your highest-value users—who extract the most from your product—are massively undercharged, while your lowest-value users may be overcharged and churning silently. Tiered packaging exists to solve this mismatch by letting usage, outcomes, or team size determine what someone pays.

Effective tier design isn't about locking features behind paywalls to frustrate free users into upgrading. It's about identifying the natural expansion vectors in your product: seat count, usage volume, API calls, projects, data storage, or access to higher-leverage capabilities. Your free or entry tier should deliver real value and get users to the moment where they need more. Your middle tier should serve the median business user doing real work. Your top tier should exist for the companies where your product is genuinely critical infrastructure.

One underused approach: usage-based or outcome-based pricing components layered on top of a base subscription. If your product helps users achieve something measurable—more revenue, faster deployments, fewer support tickets—you can structure a component of pricing around that output. This aligns your revenue with customer success in a way that flat subscriptions don't, and it naturally grows ARPU as customers grow without requiring a sales conversation every time.

Expand revenue from existing users through adjacent value, not upsell pressure

Expansion revenue—charging existing users more over time—is the highest-margin revenue path available to any software business. The cost of acquiring an existing customer's next dollar is a fraction of what it costs to acquire a new customer's first dollar. Yet most startups treat their existing customer base as a fixed line item rather than a growth engine.

The most durable expansion happens when you solve adjacent problems the user is already experiencing. If you run a project management tool and users are pasting data into spreadsheets for reporting, that's an adjacent problem you can solve—and charge for. If users are exporting data to email to their managers, that's a workflow gap you can close. The pattern is: watch what users do immediately before and after using your product, because those are the expansion opportunities. The worst expansion attempts happen when companies add features nobody asked for and then send an email announcing a price increase.

Non-pushy upsell mechanics work best when they're triggered by the user's own behavior. If a user hits a usage limit, show them what they'd unlock by upgrading—at the exact moment they feel the constraint. If a user invites a fifth teammate, that's the moment to surface your team plan, not in a quarterly check-in call. Behavioral triggers convert at dramatically higher rates than calendar-based outreach because the user is experiencing the problem right now.

Don't let pricing anxiety keep you at the wrong price forever

Most founders are afraid to raise prices because they conflate price resistance with product rejection. These are different things. A user who says 'that's expensive' and buys anyway has given you signal that you're near the right price. A user who churns and cites price as the reason is worth examining—but only if that user matches your target customer profile. Price-sensitive users who don't extract much value are not your best customers, and optimizing your pricing to retain them is a mistake.

The mechanics of testing a price increase are straightforward: raise the price for new users only, measure conversion rate and churn over 60-90 days, compare lifetime value against the previous cohort. A 20% price increase that causes a 10% drop in new user conversion is almost certainly a net win on a per-user revenue basis, because your LTV goes up faster than your acquisition rate goes down. Most founders never run this test because they fear the conversion drop without doing the math.

Paul Graham's observation that 'the real test is revenue'—not fundraising metrics, not vanity metrics—applies directly here. ARPU is one of the cleanest measures of whether you're building something people genuinely value at the price you're asking. If it's low and stagnant, that's a signal worth treating as urgently as a drop in retention. Raising ARPU by 30% is equivalent to acquiring 30% more users with zero additional marketing spend. It deserves that level of strategic attention.

“The real test is revenue. Fundraising is just a means to that end.”

— Paul Graham, source

The one thing to do

Call your ten most engaged users this week, ask them to quantify the value your product creates for them, and use that number to set your next pricing tier.

Frequently asked questions

How do I raise prices without losing existing customers?

Grandfather existing customers at their current rate while raising prices for new customers. After 90 days, you'll have data on whether the new price converts well, and you can migrate existing customers with advance notice and a clear explanation of added value. Most customers accept increases when they trust the product and receive fair notice.

What's the fastest way to increase ARPU right now?

Find your top 10% of users by engagement or outcomes achieved, call them, and ask what they'd pay for a version of your product that solved their next biggest problem. You'll discover both a price ceiling and a product roadmap in the same conversation.

Is it better to add features or raise prices to grow ARPU?

Neither alone is the answer. Features without price changes leave revenue on the table. Price increases without additional value creation accelerate churn. The winning combination is adding depth that power users specifically need and pricing that new tier so it captures the value delivered.

When should a startup focus on ARPU vs. user growth?

Focus on ARPU first when your retention is solid but your unit economics don't work—you're burning too much to acquire each customer relative to what they pay. Focus on user growth when ARPU is healthy and your main constraint is market penetration. Most early-stage startups benefit from improving ARPU before scaling acquisition.

Sources

More playbook answers · Growth Prophet home