Latest / The Bootstrapped Tech Founder with Fexingo: Profitable Software Companies Without VC / How Bootstrapped Founders Pick a Pricing Metric
Transcript
- Lucas: So Luna, I was looking at a project management tool the other day, and they'd just switched their pricing from per-seat to per active project. And I thought, that is a fascinating move, because it completely changes who you charge and when. Luna: per active project? That's a bold metric. How do they even define 'active'? Sounds like a recipe for disputes. Lucas: Exactly, and that's the first thing you have to nail down. For them, active meant a project that had any activity in the last 30 days. But the bigger point is, why would a bootstrapped founder choose that metric over the classic per-seat? Luna: And if listeners are getting value from this conversation, buying us a coffee at buy me a coffee dot com slash fexingo keeps these episodes rolling. No pressure, just a small way to say thanks. Lucas: Yeah, exactly. Every little bit helps us keep this ad-free. Anyway, the choice of metric is more than just a billing detail. It's a signal to your customers about what you think your product is worth. Lucas: Per-seat is the default for a reason: it's simple, predictable, and scales with headcount. But it often punishes teams that have a lot of light users, and it rewards you when you add users who barely log in. Luna: Right, so per-seat can push you toward adding seats that don't really reflect value. But active projects, that's more aligned with the actual work happening. Lucas: Exactly. And for a bootstrapped company, that alignment matters because your revenue should grow as the customer gets more value. If they're running more projects, they're getting more out of you, so it's fair to charge more. Lucas: I remember a founder who ran a little agency, and they had maybe 20 seats but only four active projects at a time. Under per-seat, they were paying for 20, but their value was really tied to those four projects. Luna: And they'd love per active project. But the risk is, customers might game it by archiving old projects to keep the count low. Lucas: Sure, but you can define active in a way that's hard to game, like requiring a certain number of logins or tasks updated. The point is, the metric should reflect the value you deliver, not just the number of bodies. Luna: So how does a bootstrapped founder even start picking a metric? Is there a process? Lucas: I think you start by listing the top three ways your customers get value from your product. Then ask, which of these is most correlated with their willingness to pay? For a project tool, it's the number of active projects, not the number of users. Luna: But what if you have a product that's more of a utility, like an API? Then usage-based makes sense. Lucas: Exactly. So the first step is to identify the value metric. But then you have to test whether customers understand it and whether it feels fair. That's where a lot of founders stumble. Lucas: They pick a metric that makes sense internally, but it's confusing to the customer. Like, 'we charge per integration.' What does that even mean to someone? They don't think in integrations. Luna: So you need a metric that's intuitive. And ideally one that's hard to game, as we said. But also, you need to think about the customer's ability to predict their bill. Lucas: That's a huge point. If the bill fluctuates wildly, they'll be scared to adopt. So you might offer a base tier that covers a certain number of projects, then charge for overage. That gives predictability. Lucas: I've seen a bootstrapped analytics company that charges per event. They had to offer a free tier with a generous cap because customers were worried about runaway costs. Once they did that, conversion went up. Luna: So the metric affects not just revenue, but also customer trust. It's a product decision. Lucas: Absolutely. And the thing is, you can always change your metric. It's not set in stone. But you want to avoid changing too often because it erodes trust. Lucas: I remember a founder who switched from per-seat to usage-based two years in, and they lost a few customers because they felt the new pricing was less predictable. But the ones who stayed, their revenue per account went up. Luna: So how do you test a new metric without alienating your existing base? Do you grandfather them? Lucas: That's a common approach. You offer existing customers the chance to stay on the old plan, but new customers get the new metric. Then you compare the cohorts. That's a clean experiment. Luna: But for a bootstrapped founder, you might not have the luxury of running a long experiment. You have to make a call. Lucas: True. So you can also do a pricing page test: put two options up, see which one gets more clicks. Or even just have conversations with your top customers. Ask them, 'If we charged per project, would that be fair?' Lucas: The worst thing you can do is pick a metric without any validation. I've seen founders build an entire pricing model around a metric that customers hate. Luna: And then they wonder why they can't get past a certain revenue number. The metric is the foundation. Lucas: Yes. And it's not just about the metric itself, but the price point. How do you decide what to charge per project? That's where you need to do some value-based pricing thinking. Lucas: You could look at how much time your product saves them per project, and then charge a fraction of that. So if you save them 10 hours and their time is worth $50 an hour, that's $500 of value. Charging $50 per project is a no-brainer. Luna: But what if the customer doesn't see it that way? They might just see a new line item. Lucas: That's why the metric has to be communicated clearly. You can't just switch to per-project without explaining why it's fair. You have to tell them, 'This way you only pay for what you use, and it scales with your success.' Lucas: Another thing to watch: don't overcomplicate. Some founders try to be too clever and create a metric that's a combination of storage, usage, and seats. That's a nightmare to understand. Luna: Simplicity wins. If you can't explain your pricing in one sentence, it's too complex. Lucas: Right. So think of the metric as the unit of value. And just like a good unit, it should be easy to visualize. 'Per project' is easy. 'Per active user per project with a minimum of three' is not. Luna: And what about when you scale? Does the metric hold up as you move upmarket? Lucas: Great question. Sometimes a metric works for small teams but not for enterprises. For example, per-seat works fine for SMBs, but enterprises want to negotiate enterprise agreements, so you might need a different structure. Lucas: But the underlying value metric should stay the same. You might just change the packaging. So you still charge per project, but you offer volume discounts. Luna: So the key is to find the metric that aligns with value, test it, and then be willing to iterate as you learn. Lucas: Exactly. And it's not just about revenue. The right metric can even reduce churn. If your customers are paying based on usage, they're more likely to use the product, and usage drives retention. Lucas: I recall a case where a bootstrapped CRM moved from per-seat to per-contact, and their churn dropped because customers were only paying for the contacts they actually had in the system. They stopped deleting contacts just to save money. Luna: Interesting. So the metric changed behavior in a positive way. Lucas: Yeah. And that's the ultimate test: does the metric encourage the behaviors that lead to long-term value? If not, it's the wrong metric. Luna: So for a bootstrapped founder, what's the one takeaway you'd leave them with? Lucas: I'd say, don't default to per-seat just because everyone else does it. Think hard about what your product actually does for your customer, and pick a metric that captures that. It's one of the highest-leverage decisions you'll make.