Pricing

How to Raise Prices When Your Team Says No

The Framework

In late 2022, Render's margins were too low. Anurag Goel decided to add a fee for every team member on top of compute. A bunch of people inside the company didn't want to do it. They'd spent years thinking from the customer's side, and charging just for membership felt unfair.

That's the usual way a price rise dies. Someone says you'll lose customers, and nobody can prove otherwise, so nothing changes.

Anurag's answer was to stop arguing about feelings and run it as a test with a clear read. His advice for founders stuck in the same spot: "if you're thinking about it," he said, "you're probably not charging enough right now."

The 4 Steps

  1. Know your category's margins. "Every industry has a different margin structure." Yours should be around the average for your category. Common mistake: comparing yourself to the cheapest competitor instead.
  2. Find what's actually driving your margin. For Render, part of it was architecture. Running on both GCP and AWS meant paying "a lot of money for the traffic between those two clouds." So they fixed the architecture and the pricing. Common mistake: raising prices to cover a cost you could cut.
  3. Ask customers before you change anything. Render tested the seat fee "just sort of verbally" with some customers. The answer they kept hearing: "Well, I'm not gonna be happy, but I'll pay it." Anurag's read: when you hear that, you know you're onto something.
  4. Make one change and read the result. It was "probably the only big change we made." Anurag framed it plainly: "Either it would work or it wouldn't." If people stayed, they'd been getting value Render wasn't capturing.

You don't have to fix everything at once, either. You "don't have to get there tomorrow," he said, "but you should have a path to it."

Real Numbers

Render's numbers here aren't percentages. They're decisions:

  • Lowest web service tier: $7 a month, unchanged since the 2019 launch
  • Pricing change: seat fees added after the late-2022 margin squeeze
  • Customer reaction: "Turns out it was fine." Customers paid, "although they were never happy about it."
  • Seat fees: removed completely in 2026

That last one matters. The seat fee did its job, then stopped fitting. Once AI agents became team members too, "you really can't be charging twenty dollars per month per agent." A price is a test you keep running, not a decision you make once.

When It Fails

This breaks if customers aren't getting much value to begin with. The verbal test is your early warning. If people say they'd leave rather than grumble and pay, stop. Fix the product or the cost first. And if your only reason for the increase is to look like a competitor, that's not a reason. Anurag's whole case started with Render's own margins.

Your First Move

This week, pick five of your best customers. Tell each one the new price and what's changing. Write down their exact words. If most of them grumble but say they'll pay, you have your answer. If they push back hard, you've learned that before a single customer left.

Ready to build your SaaS with founders who get it?

Join thousands of SaaS founders getting weekly insights and proven strategies from real founder conversations.

Free weekly newsletter · No spam