Latest / The Bootstrapped Tech Founder with Fexingo: Profitable Software Companies Without VC / How Bootstrapped Founders Use Pricing to Double Revenue Without Raising Prices
Transcript
- Lucas: You know, one of the biggest levers a bootstrapped founder has that doesn't cost a dime in development is pricing. And I'm not talking about raising prices — I mean restructuring how you charge. Luna: Because if you just raise the number, you might lose customers. But if you change the model, you can increase what each customer pays without them feeling a sting. Lucas: Exactly. There's a great example from a project management SaaS called — let's call it 'Planly', not the real name — that was charging $19 per user per month. They had about 500 customers, mostly small teams. Average contract value was about 4 users, so $76 a month. Luna: That's pretty standard per-user pricing for that category. Lucas: Right. But they realized that per-user pricing actually punishes growth. When a team adds a member, they pay more. So there's friction. They switched to per-project pricing: $49 for up to 5 projects, $99 for up to 20, and $199 for unlimited. Luna: And what happened? Did customers revolt? Lucas: Surprisingly, no. Existing customers on the old plan were grandfathered in for six months, then gently nudged to the new tiers. Within six months, average contract value went from $76 to about $150. Same product, same customers, just a different packaging structure. Luna: So they doubled revenue without adding a single feature. That's the dream for a bootstrapped company with a small dev team. Lucas: And the psychology is key. Per-project pricing feels like you're paying for value — the output — not for headcount. Teams don't feel penalized for bringing on a new intern or contractor. Luna: It also makes the product seem more valuable because you're paying for the work itself. I've seen this work well for agencies and consultancies that use the tool. Lucas: Another approach is usage-based pricing, like charging per API call or per storage gigabyte. That works for infrastructure plays — think AWS or Twilio — but for a bootstrapped SaaS, it can be dangerous because usage is unpredictable. A customer might have a spike and then get a huge bill, leading to churn. Luna: So you'd rather have predictable revenue as a bootstrapped founder, not surprises. Lucas: Exactly. That's why the 'good-better-best' tiered model is so popular. Mailchimp did it beautifully. They had a free tier for very small users, then standard, then premium. Each tier unlocked more value — more audience, more automation, more advanced reporting. The jump from free to paid is the hardest conversion, but once a customer is paying, they tend to upgrade over time. Luna: It's like a natural upsell path. Customers grow into the next tier as their needs expand. Lucas: And for bootstrapped companies, you don't need a sales team to do that. The product itself should guide the upgrade. You want the 'aha' moment where a user hits the limit of their current tier and thinks, 'I need the next one.' Luna: That's a lot more sustainable than cold calling. And it aligns with the bootstrapped ethos of building product-led growth. Lucas: Right. So the takeaway is: before you even think about raising your prices, look at your pricing model. Are you charging per user? Per project? Per feature tier? Each model sends a different signal to the customer about what they're buying. Luna: And if you're a bootstrapped founder, you can test a new pricing model on a subset of new customers without touching existing ones. That's low risk. Lucas: By the way, conversations like this — where we dig into real operational tactics for bootstrapped businesses — that's exactly what keeps this show going. And if you find value in it, one way to support is at buy me a coffee dot com slash fexingo. It helps us stay ad-free and focused on the content that matters to founders. Luna: Yeah, it's a simple way to keep these episodes coming without any corporate sponsorship. Appreciate anyone who chips in. Lucas: Alright, back to pricing. One more model I want to mention: value-based pricing. That's where you charge based on the value the customer gets, not your cost. A classic example is a CRM that charges per deal closed, not per user. Luna: That aligns your revenue with their success. If they close more deals, you make more. That's a powerful incentive to keep improving the product. Lucas: But it requires trust. The customer has to believe your tool actually drives more deals. For a bootstrapped company, you might start with a simpler model and evolve to value-based as you build case studies. Luna: So the key is to pick a model that matches your product's maturity. Early stage: per-user or flat fee. Later: performance-based. Lucas: And always, always test. You can run a pricing experiment on your landing page — show different pricing to different segments and measure conversion. Tools like ProfitWell or Baremetrics can help track the metrics. Luna: What about the risk of complexity? Too many tiers can confuse customers. Lucas: That's real. Three tiers is the sweet spot. More than four and you get analysis paralysis. Less than three and you don't have a clear upgrade path. And make sure the features in each tier are distinct enough that the middle tier feels like a clear step up. Luna: So we've got per-project, tiered, usage-based, value-based. Any other models worth mentioning for bootstrapped founders? Lucas: There's also the 'pay what you want' model, but that's risky for recurring revenue. Some open-source tools use it for donations. For a bootstrapped SaaS, it's usually better to have clear, predictable pricing. Luna: Makes sense. So the big lesson: pricing is a product feature. Spend time on it like you would on any feature. Lucas: Absolutely. And if you can double your average revenue per customer without changing your product, that's pure profit. Which is the whole point of being bootstrapped.