Latest / The Bootstrapped Tech Founder with Fexingo: Profitable Software Companies Without VC / How Bootstrapped Founders Use Tiered Pricing Without Feature Gating
Transcript
- Lucas: You know, I was looking at pricing pages for about forty bootstrapped SaaS companies this week — just as a random research project — and I noticed something strange. Luna: I'm almost afraid to ask what constitutes a 'random research project' for you, but go on. Lucas: Almost every single one of them gates features behind tiers. You know the drill: Free plan has basic reporting, Pro plan has advanced analytics, Enterprise has everything plus a dedicated account manager. It's the standard playbook. Luna: Right, that's basically the industry default. Feature-based tiering has been around since the dawn of SaaS. Lucas: But I found a small handful doing something different. They give every tier the full product — all features unlocked — and they differentiate purely on usage limits, support response times, and data retention. So the free tier gets the same dashboard, same reports, same integrations as the paid tiers, but maybe it's capped at five hundred records and you get email support within 48 hours. Luna: Wait, so no feature gating at all? That seems almost counterintuitive. Why would anyone pay if they can get the full product for free? Lucas: That's exactly the question I wanted to dig into. Because the data from these companies suggests it actually works better. One company I looked at — a bootstrapped project management tool called Plane — switched from feature-gated tiers to usage-based, feature-unlocked tiers about 18 months ago. Their conversion rate from free to paid went from roughly 3 percent to over 8 percent. Luna: That's a massive jump. But why? If you're not holding back features, what's the incentive to upgrade? Lucas: The theory is that when users experience the full product from day one, they build deeper habits around it. They integrate it into their workflow, they invite teammates, they start relying on it. Then when they hit the usage cap, they're already hooked — upgrading feels like a natural next step, not a ransom note. Luna: So it's about reducing friction and building trust. The classic 'give before you ask' approach. Lucas: Exactly. And there's a psychological element too. With feature-gated tiers, users often feel manipulated. They see a feature they need behind a paywall and it creates resentment. With feature-unlocked tiers, the limit feels fair — you're using a lot, so you pay more. It's usage-based, not arbitrary. Luna: I remember when Mailchimp used to do this. Before they got acquired by Intuit, their free tier was famously generous — full feature set, just limited on list size and sends per month. And they built a massive user base that way. Lucas: Mailchimp's a great example. They had no feature gating for years. The free plan had all the automation, all the templates, all the reporting. The limit was purely on contacts and monthly sends. And they grew to hundreds of thousands of paying customers without ever locking a feature. Luna: But isn't that harder to implement? Feature gating is straightforward — you just flip a switch in your code. Usage-based pricing requires tracking usage, setting limits, and handling overages gracefully. Lucas: It is more complex on the backend, no question. But for bootstrapped founders, the trade-off might be worth it. One founder I spoke with said that his billing infrastructure is actually simpler because he doesn't have to maintain multiple feature configurations. Every user runs the same code. The only thing that changes is the rate limits and support queue. Luna: That's a good point. Fewer code paths means fewer bugs. And if your product is solid, you're not shooting yourself in the foot by hiding features that could convert users. Lucas: There's also the support angle. With feature-unlocked tiers, support becomes a differentiator. The free tier might get email support within 48 hours, the Pro tier gets within 4 hours, and the Business tier gets priority phone support. That's a lot easier to scale than trying to support a feature that only exists on one tier. Luna: Data retention is another lever. I've seen companies where the free tier keeps data for 30 days, the mid tier for a year, and the top tier indefinitely. That's a strong incentive to upgrade without ever touching the feature set. Lucas: Right. And it aligns with customer value — if you have more data, you're getting more value from the product, so paying more makes sense. It's a classic value-based pricing approach, just applied to the tier structure. Luna: But what about the risk of cannibalization? If the free tier is too good, won't some customers just stay on it forever? Lucas: That's the fear, but the data suggests otherwise. The company I mentioned — Plane — found that only about 2 percent of free users stayed past the point where they clearly should have upgraded. Most either upgraded or churned. And the ones who stayed on free were typically very small teams who cost almost nothing to serve. So it's a manageable overhead. Luna: So the key is setting those limits intelligently. You want them to be generous enough that users get real value, but tight enough that growing teams naturally outgrow them. Lucas: Exactly. And there's an art to it. You need to know your unit economics cold — what does a free user cost you in server and support resources? What's the average time to conversion? What's the lifetime value of a converted user? Once you have those numbers, you can calibrate the limits to maximize the conversion rate. Luna: It reminds me of how Basecamp does pricing. They have a free tier for personal use and a paid tier for businesses, and the difference is just on number of projects and storage. Full feature set on both. And they've been profitable for years. Lucas: Basecamp's a great example of the philosophy in practice. Jason Fried has written about how they deliberately avoid feature gating because it creates a 'good version/bad version' dynamic that erodes trust. They want customers to use the best product possible and then pay when it's clearly valuable to them. Luna: There's something almost old-school about that approach. It's like paying for a software license based on how many users you have, not which features you can unlock. Lucas: And I think for bootstrapped founders especially, it's a way to compete against well-funded competitors who can afford to give away features for free to build market share. If you're bootstrapped, you can't out-spend them, but you can out-trust them. Feature-unlocked pricing is a trust signal. Luna: That's a powerful positioning. 'We trust you to pay when you see the value.' It flips the usual dynamic on its head. Lucas: And it works especially well for products that have network effects or team collaboration. Because if one user on the free tier invites their team, pretty soon the team hits the usage cap and the whole company upgrades. It's a natural growth loop. Luna: I want to talk about the practical implementation. For a bootstrapped founder today, June 2026, what would you recommend as a starting point? Lucas: Start by auditing your current usage data. Look at how free users are using your product — what's the median usage of your key metrics? Number of projects, records, API calls, whatever. Then set your free tier limit at around the 80th percentile of current free users. That way, most users won't hit the limit immediately, but the heaviest users will naturally need to upgrade. Luna: So you're basically drawing the line where the power users start. That's smart. Lucas: Then for the paid tiers, set limits that correspond to different team sizes or usage patterns. And make sure the limits are communicated clearly on the pricing page. No hidden caps. Transparency is part of the trust-building. Luna: And what about the transition period? If you're switching from feature-gated to feature-unlocked, you might have existing customers on different tiers. Lucas: That's a delicate process. The safest approach is to grandfather existing customers on their current plans, but offer them the option to switch to the new structure. Some might want to downgrade to a lower tier if they get more features, but that's okay — it's a net positive for customer satisfaction. Luna: So the new customers get the full product from day one, and existing customers get upgraded automatically. That seems like a win-win. Lucas: One more thing — don't forget about the support cost. If you're giving every user access to all features, you might get more support tickets from free users asking questions about advanced features. That's why support tiering is so important. You can use a tool like Intercom or Crisp to route free users to a knowledge base first, and only escalate to email after they've tried self-serve. Luna: That's a good call. It keeps the support costs manageable while still offering a great experience. Lucas: And if you're building a bootstrapped company and these kinds of practical conversations are useful — about pricing, product strategy, operations — we keep this show free and ad-supported because of listeners who chip in. If you find value in it, you can support the show at buy me a coffee dot com slash fexingo. It helps us keep doing deep dives like this without any sponsor interruptions. Luna: Yeah, it's a small way to keep the content independent. And we genuinely appreciate everyone who does. Lucas: Alright, back to pricing. So once you've set your limits, the next step is to monitor the conversion funnel closely. Look at where users are hitting the limit — are they upgrading immediately, or are they dropping off? That tells you if your limits are set right. Luna: And if you see a lot of drop-offs at the limit, you might need to adjust the limit or add a grace period. Maybe give users a 7-day overage window before forcing an upgrade. Lucas: Exactly. Some companies do a soft limit — you can exceed it, but you get a notification and a prompt to upgrade. And if you don't upgrade within a week, the product starts degrading. That's more forgiving than a hard cut-off. Luna: I like that. It respects the user's time while still creating a natural incentive. Lucas: At the end of the day, the core insight is this: pricing is a communication tool. Feature-gated pricing says 'We have things you want, and you have to pay to get them.' Feature-unlocked pricing says 'Here's everything we have. Use it, love it, and when it's time, we'll have a plan that fits.' For bootstrapped founders, that second message can be a real competitive advantage. Luna: It's about building a relationship, not just closing a transaction. I think that's a great note to end on.