How a Solo Dev Hit 10K MRR by Tripling Prices Overnight

Lucas: So I came across this solo developer, Alex Chen, who did something that most founders would consider insane: he tripled his prices overnight. Luna: Tripled? Like, from $10 to $30? That's a bold move.

What happened? Lucas: Exactly. His product is called DesignRate - it's a simple time-tracking and invoicing tool built specifically for freelance graphic designers. He launched it in early 2025 at $9 per month, grew to about 400 paying users, and hit around $3,600 MRR.

But he felt stuck. The growth had plateaued. Luna: So instead of adding features or running ads, he just... raised the price?

Lucas: Right. He'd been reading about value-based pricing and came across studies showing that consumers often equate higher prices with higher quality. He decided to test it. In one weekend, he updated his pricing page to $29 per month for new customers.

Existing customers were grandfathered at $9 for a year, then would move to the new price. Luna: Grandfathering seems smart. But still, that's a 222 percent increase. What was the immediate reaction?

Lucas: He published a blog post explaining the rationale - that the tool saved designers hours per week, and that the new price reflected the true value. He also added a $99 per year option. Surprisingly, the conversion rate on the sign-up page actually went up by 20 percent. And churn?

It barely moved. Existing customers stayed, and new customers came in at a higher rate. Luna: Wait - conversion rate went up? That defies the basic law of demand.

Lucas: It does, but there's a psychological explanation. At $9, the product looked cheap, like maybe it wasn't serious. At $29, it signaled quality and professionalism. Plus, Alex updated the messaging to emphasize the time savings and ROI.

He ran a calculator showing that the average designer saves $150 per month in billable hours by using DesignRate. Luna: So he shifted from feature-based to value-based. That's a classic, but rarely executed well. Lucas: Right.

And the numbers bear it out. Within three months, his MRR went from $3,600 to over $10,000. That's a 178 percent increase. And he didn't add a single new feature.

It was purely a pricing and positioning change. Luna: That's remarkable. But I imagine the fear of losing existing customers must have been intense. How did he prepare for that?

Lucas: He sent a personal email to every single existing customer two weeks before the change. He explained why and offered a one-year grace period. He also gave them the option to lock in the $9 forever if they prepaid for two years. Only about 5 percent took that.

Most just stayed on the grandfathered plan. Luna: And the new customers? They had no reference point, so they just saw $29 as the normal price. Lucas: Exactly.

And because his product was already solid, they didn't question it. He also introduced a 14-day free trial, which he didn't have before. That gave users enough time to see the value before committing. Luna: So the free trial was a key part of the strategy.

At the old $9 price, a trial might not have been necessary, but at $29 it builds trust. Lucas: Precisely. And Alex is now experimenting with further segmentation. He's adding a $49 plan for teams of two to three, and a $99 enterprise tier.

He's effectively moving upmarket without any code changes. Luna: It's interesting because so many indie hackers underprice out of fear. They think low prices drive adoption, but sometimes they kill perceived value. Lucas: I agree.

There's a famous study by Dan Ariely on the power of price anchoring. Alex essentially anchored his product at $9, then moved the anchor to $29. But he also added a higher tier, so $29 looked reasonable by comparison. That's a classic decoy effect.

Luna: We're seeing this more in 2026. With inflation still hovering around 3 percent, customers are actually more willing to pay for tools that save them money. Alex's timing was good. Lucas: And he kept his costs low.

He's still the only developer, using a simple stack - React on the front end, Node and Postgres on the back, hosted on a $50 per month VPS. His margins are enormous now. Luna: So the lesson isn't just 'raise your prices.' It's about aligning your pricing with the value you deliver and communicating it clearly.

And having the confidence to charge what you're worth. Lucas: Exactly. And if you're listening and you're stuck at a few hundred MRR, maybe it's time to look at your pricing page before building another feature. You might be leaving money on the table.

Luna: And you know, Lucas, speaking of leaving money on the table - we've never once charged for this podcast. We deliberately keep it ad-free because we think it's better for you, the listener. Lucas: That's true. We want this to be a resource you can trust, not something interrupted by sponsor spots.

If you find value in these episodes and want to support that choice, there's a simple way: buy me a coffee dot com slash fexingo. Luna: Yeah, it's a small gesture that helps us keep the lights on and the content independent. No pressure, but every bit helps. Lucas: So back to Alex - he actually shared some data on his churn post-price-increase.

It dropped to 3 percent for new cohorts, which is incredibly low for a SaaS. He attributes that to the higher price filtering out non-serious users. Luna: That makes sense. When people pay more, they're more committed to using the product and getting value from it.

It's a virtuous cycle. Lucas: Exactly. He's now planning to open-source the core time-tracking engine as a way to build community, but he'll keep the invoicing and reporting features proprietary. That's a smart move for lead generation.

Luna: Alright, so our takeaway: don't be afraid to test pricing. Use grandfathering, improve your messaging, and measure everything. Alex's story shows that the price itself can be a feature. Lucas: I think that's a perfect note to end on.

Thanks for listening, and happy hacking.