Latest / The Bootstrapped Tech Founder with Fexingo: Profitable Software Companies Without VC / How Bootstrapped Founders Use Usage-Based Pricing Without Scaring Customers
Transcript
- Lucas: One of the trickiest decisions a bootstrapped founder faces is how to price their software. Charge too much upfront and you scare off early adopters. Charge too little and you leave money on the table. But there's this middle ground that's been gaining traction: usage-based pricing. Luna: pay as you go, like your electric bill. I think a lot of founders are drawn to it because it feels fair — customers only pay for what they use. Lucas: Exactly. And it's worked wonders for companies like Twilio and Snowflake. Twilio's whole business is built on metering every API call, every SMS sent. Snowflake charges by the compute credit, by storage. Both are multi-billion dollar companies now. Luna: But Twilio and Snowflake are not bootstrapped. They raised enormous amounts of VC money. For a bootstrapped founder, usage-based pricing can create a whole different set of problems. Lucas: Right. The biggest one is unpredictability. If your customers get a surprise bill — say their API usage spikes and they owe three times what they expected — they're going to churn. Fast. I've heard horror stories of startups getting a $20,000 monthly bill from a data API provider because a test script went rogue. Luna: I've heard that one too. The company cut their API key and never came back. That's the worst outcome for a bootstrapped business: losing a customer because of your own pricing model. Lucas: So the question is: can a bootstrapped founder use usage-based pricing without creating that fear? I think the answer is yes, but you have to be smart about it. The key is a hybrid model: a low base fee that covers core features, plus usage-based billing for variable services. Luna: Like a cell phone plan with a data cap. You pay a flat rate for the first few gigabytes, then overage charges kick in. Lucas: Precisely. And you set that base fee high enough to cover your fixed costs — server infrastructure, support, development — but low enough that it's a no-brainer for the customer. Then the usage component is gravy. But you need caps and alerts. Luna: Let's talk specifics. What kind of caps work for bootstrapped founders? Lucas: I like the idea of a hard monthly cap. The customer agrees to a maximum spend. If they hit that cap, the service either shuts off or they have to manually approve more. That eliminates the surprise bill entirely. Zapier does this for their premium plans — you buy a certain number of tasks per month, and if you need more, you upgrade. Luna: But doesn't that cap your revenue? If a customer happily uses ten times their base allotment, you're leaving money on the table. Lucas: That's where tiered billing comes in. You offer multiple tiers with higher caps and higher base fees. The customer self-selects into the tier that matches their usage pattern. And you make it easy to upgrade mid-cycle with prorated billing. Founders should think of the base fee as a floor, not a ceiling. Luna: What about the psychology? I've heard that when customers see a usage meter ticking up, they get anxious. They start second-guessing every API call. Lucas: That's a real risk. The counter-argument is that usage-based pricing aligns your revenue with the value you deliver. If a customer is using a lot, they're getting a lot of value, so paying more feels fair. But you have to earn that trust. One way is to provide proactive usage alerts — 'You've used 50% of your monthly credits' — rather than making them log in to check. Luna: I know a bootstrapped project management tool that does this well. They charge a flat fee per user, plus a small per-project fee for active projects. But they send a weekly summary email showing how many projects are active and what the cost will be. No surprises. Lucas: That's a great example. The per-project fee is usage-based, but it's predictable because the customer controls how many projects they start. And the weekly summary builds trust. I also like the model used by some data API companies: they sell prepaid credits that expire in 30 or 90 days. The customer pays upfront, so there's no bill shock, and they have an incentive to use what they bought. Luna: But then you're holding unearned revenue. If a customer buys $500 in credits and only uses $100, you've got $400 in deferred revenue — and potential refund requests. Lucas: That's the trade-off. But for bootstrapped founders, cash flow is everything. Prepaid credits give you cash upfront, which you can invest in development. And you can structure the credits as 'use it or lose it' to minimize refunds — as long as you're transparent about the expiration policy. Luna: Speaking of transparency, what about showing customers their usage in real time? Some founders worry that if customers see a spike, they'll freak out and throttle their usage. Lucas: I think real-time dashboards are essential. If you hide the meter, customers will assume the worst. But if they can see exactly what each action costs, they feel in control. The best usage-based companies I know have a dashboard that shows: 'You've used X of Y credits this month. Your estimated bill is $Z.' No math required. Luna: So the customer can budget. That's key for small businesses that use your tool. They need to know what they'll owe. Lucas: Exactly. And for bootstrapped founders, there's another benefit: usage data tells you which features are most valuable. If 80% of your API calls are for one endpoint, that endpoint is your core value. You can optimize it, market it, maybe even build a separate pricing tier around it. Luna: I've seen that happen with a bootstrapped image processing API. They noticed that most usage was for resizing images — not the fancy filters they had built. So they introduced a 'resize-only' tier at half the price, and it became their best-selling plan. Lucas: That's a perfect example of usage-based pricing revealing customer behavior. The data was right there in the meter. And the founder was smart enough to act on it. The hybrid model — base fee plus usage — gives you that visibility while keeping revenue predictable. Luna: Let's talk about the base fee itself. How do you set it? If it's too high, customers won't even try your product. If it's too low, you're not covering costs. Lucas: I suggest starting with your own costs. Calculate your server costs per active user, your support cost per ticket, your development overhead. Then add a margin. For many bootstrapped SaaS companies, a base fee of $15 to $30 per month is a sweet spot — low enough to be an impulse buy for a small business, high enough to cover a typical user's costs. Luna: And then the usage component? How do you price each unit? Lucas: This is where you have to think about value, not cost. If your API call saves a customer $10 in manual labor, charging $0.10 per call is a steal. But you also need to be aware of the customer's total bill. If a small business has 10 users and each makes 1000 calls a month, that's $1000 — more than they probably expect. So you tier the pricing: first 5000 calls included in the base fee, then $0.05 per call after that. Luna: That tiered structure also encourages usage. Customers feel like they're getting something for free, so they're more likely to integrate your tool deeply. Lucas: Right. And once they've integrated deeply, switching costs go up. That's the lock-in effect that usage-based pricing can create — but only if the pricing is fair. If it's not, they'll rip out the integration as soon as they get a big bill. Luna: One thing I've noticed: a lot of bootstrapped founders are afraid to raise prices. They worry about losing customers. But with usage-based pricing, you can increase the per-unit price without shocking existing customers, because their bill only goes up if they use more. Lucas: That's a subtle but powerful advantage. You can grandfather in existing customers at the old rate for a while, then gradually phase it out. Or you can introduce a new, higher tier with more features. Usage-based pricing gives you flexibility that a fixed monthly subscription doesn't. Luna: I want to get concrete. Can you give me an example of a bootstrapped company that nailed this? Lucas: Sure. There's a bootstrapped email validation API called Kickbox. They charge $0.005 per verification — half a cent per email. That's tiny. But they also have a $15 per month plan that includes 5,000 verifications, plus a dashboard and analytics. Most small businesses buy the $15 plan and never hit the cap. Larger companies buy prepaid credit packs. It's simple, transparent, and they've been profitable for years. Luna: Half a cent per email. That's so low it's almost frictionless. But for Kickbox, the margin is huge because the cost per verification is negligible. Lucas: Exactly. And they've built trust by being upfront about the pricing. There's no fine print, no minimum commitment. That's the gold standard for bootstrapped usage-based pricing. If these conversations are useful for what you're building or running, listener support is what keeps this show ad-free. A couple of dollars a month is genuinely what keeps these going — buy me a coffee dot com slash fexingo. Luna: Seconded. It's a small way to say 'I got something out of this' and it really does make a difference. Now back to usage models — I'm curious about the flip side. What happens when a customer's usage drops off a cliff? Lucas: That's a real risk with pure usage-based pricing. If a customer stops using your product, your revenue goes to zero. But with a hybrid model, the base fee keeps some revenue flowing. You can also use the usage data to reach out: 'Hey, we noticed you haven't used X feature in a while. Can we help?' That's a retention opportunity. Luna: So the base fee is like a retainer. It keeps the relationship alive even during low-usage periods. Lucas: Exactly. And for bootstrapped founders, predictable base revenue is what pays the bills. The usage revenue is upside. I think the ideal ratio is something like 60% base, 40% usage on average. That way, even if usage dips, you're still covering costs. Luna: What about customers who are heavy users but low value? Like, they cost you more in support than they pay in fees. Lucas: Usage-based pricing actually solves that problem. If a customer costs you $5 per month in server resources but only pays $3 in usage fees, you're losing money. But with a hybrid model, you can set the base fee high enough to cover the average support cost. And if a customer is exceptionally high-maintenance, you can move them to a custom plan or a higher tier. Luna: That's a good argument for not making the base fee too low. You need to cover the cost of serving the customer, not just the infrastructure. Lucas: Right. And the beauty of usage data is that you can segment customers by profitability. You can see which ones are in the top quartile of usage and lowest quartile of support tickets. Those are your ideal customers. You can build marketing campaigns around them. Luna: So usage-based pricing isn't just a billing model — it's a data source for your entire business. Lucas: Exactly. And for bootstrapped founders who don't have a data science team, the billing system is your best source of customer intelligence. The key is to implement it thoughtfully, with transparency, caps, and alerts. If you do that, usage-based pricing can be a win-win: customers feel they're paying for value, and founders get revenue that scales with success. Luna: I think the biggest takeaway is that surprise bills are the enemy. As long as you eliminate those, usage-based pricing is a powerful tool for bootstrapped founders. Lucas: Couldn't agree more. And on that note, I'm curious: next episode, should we talk about how to handle customers who abuse your usage limits — like someone running a bot that makes a million API calls a day? Luna: Absolutely. That's a whole other can of worms. Let's save it for next time.