Latest / The Bootstrapped Tech Founder with Fexingo: Profitable Software Companies Without VC / How Bootstrapped Founders Use Customer Pain Audits
Transcript
- Lucas: Luna, I want to start with a number. I recently spoke with a founder running a logistics software company — bootstrapped, about four million in annual recurring revenue. He told me that every quarter, he picks up the phone and calls five customers who just renewed. Not to upsell, not to check satisfaction — he calls them to ask about their biggest pain points that his software does not solve. Luna: That sounds like it could backfire. You just renewed them, and now you're asking what's broken? Lucas: That's exactly what I thought. But he explained that renewal is actually the perfect moment. The customer has just voted with their wallet — they see value. So they're more willing to be honest about what's missing because they trust you enough to keep paying. He calls it a customer pain audit, and he's been doing it for three years. Luna: Okay, so how does it work? Is it just a free-form conversation or does he have a script? Lucas: He has exactly three questions. Question one: 'What is the one thing our software does that you could not live without?' That's the anchor — it confirms your core value. Question two: 'What is the one thing you wish our software did that it currently doesn't?' That's the pain inventory. And question three: 'If we built that, how much more would you be willing to pay?' Luna: That third question is bold. Most founders are terrified to ask that directly. Lucas: Absolutely. And he told me the answers are surprisingly specific. One customer said they'd pay twenty percent more if the software could automatically reconcile invoices from three different carriers. Another said they'd pay an extra thirty percent for a real-time dashboard that showed driver delays before the customer calls to complain. He actually built both features, and those customers upgraded without hesitation. Luna: So the audit doubles as a pricing discovery tool. But I wonder — is this really different from standard customer development interviews? Most founders talk to customers already. Lucas: I think the difference is in the framing and the timing. Standard customer development usually happens before you build, or when you're trying to find product-market fit. This happens after you already have a paying relationship. The question isn't 'what problem should we solve?' — it's 'what problem are you already feeling acutely enough to pay more for?' Luna: Right, so it's less about discovery and more about prioritisation. You're not looking for a new market — you're looking for the next feature that has a direct price tag attached. Lucas: Exactly. And that's incredibly valuable for a bootstrapped company where every engineering hour counts. He told me that before he started doing these audits, his product roadmap was driven by whatever customer complained the loudest that week. Now he has a queue of features ranked by willingness to pay, not by volume of complaints. Luna: But doesn't asking about price create awkwardness? Like, 'Hey, I'll charge you more if I build this' — that feels like it could strain the relationship. Lucas: He said it's actually the opposite. He frames it as: 'We want to invest in the features that matter most to you. To do that responsibly, we need to know what you value.' Most customers appreciate the transparency. They'd rather pay more for something they actually want than get free features they don't care about. And he never builds a feature unless at least two customers have named it in their audits and given a concrete price point. Luna: That's a pretty rigorous filter. Two customers, named price — that's a high bar. It forces you to stay lean. Lucas: It does. And it also reveals something interesting. He told me that about forty percent of the time, the feature a customer says they want is actually a workaround for something his software already does, but they just don't know about it. So the audit also becomes a training opportunity. He can say, 'Actually, you can already do that — let me show you.' And that reduces churn risk. Luna: So the audit serves three purposes: roadmap prioritisation, pricing discovery, and retention through education. That's a lot of leverage from five phone calls a quarter. Lucas: Exactly. And he doesn't just call the happy customers. He also calls customers who renewed but had a rough year — maybe they submitted a lot of support tickets or downgraded their plan. He wants to understand the pain on both ends. The ones who struggled often have the clearest picture of what's missing because they've been hitting the wall repeatedly. Luna: That takes guts. Calling a customer who almost churned and asking 'what do you wish we did better?' — you have to be ready for honest answers. Lucas: You do. But he said those conversations are where he's gotten his best ideas. One customer told him their biggest frustration was that the software didn't integrate with a specific accounting platform that ninety percent of their clients used. He built that integration, and within six months, that customer had referred three new clients because of it. Luna: So the audit doesn't just help you keep existing customers — it turns them into advocates because they feel heard. Lucas: That's the real magic. And it's a tactic that costs nothing but time. You don't need a customer success platform, you don't need a survey tool — just a phone and three questions. Luna: I'm going to try this with my own consulting clients. I've been relying on annual feedback forms, but that's so passive. Lucas: I think you'll be surprised at how willing people are to tell you exactly what they'd pay for. And speaking of paying for things you value — if you're finding these conversations useful for what you're building or running, listener support is what keeps this show ad-free and independent. It's a small thing, but it makes a big difference for us. Luna: Yeah, if you've gotten even one concrete idea from this episode, that's exactly the kind of value we're trying to deliver. And if that's worth a coffee to you, you can find us at buy me a coffee dot com slash fexingo. Lucas: That's it. No pressure, no upsell. Now back to the audit — one thing I didn't mention is that he documents every call in a shared note that the whole team can see. So the support team knows what customers are struggling with, the engineering team sees the feature requests with price tags, and the sales team can reference the specific pain points in their conversations. Luna: So it becomes a company-wide signal. That's smart. It prevents the classic problem where customer feedback lives in one person's head and never gets acted on. Lucas: Exactly. And he has a rule: within a week of the audit, he sends the customer a personal note summarising what he heard and what the company plans to do about it. Even if the answer is 'we're not building that right now,' the customer gets a candid explanation. He said that follow-up alone improved his net promoter score by ten points. Luna: That makes sense. Customers don't expect you to build everything — they just want to know you listened. And if you explain your reasoning, they respect it. Lucas: Right. And over time, those audit conversations create a feedback loop. The customers who participate start feeling like they're part of the product's evolution. One of his early customers has been in every audit for three years, and that customer has never even considered switching. They feel invested. Luna: So the audit essentially builds a community of power users who shape the product. That's a form of retention that's hard to replicate with any tool. Lucas: Absolutely. And it's scalable even for a solo founder. Five calls per quarter — that's about two hours a month. Compare that to the cost of building a feature nobody asked for, or losing a customer because you didn't know they were frustrated. Luna: Two hours a month versus months of wasted development. The ROI is ridiculous. Lucas: It really is. And I think the reason more founders don't do this is that it feels vulnerable. You have to be willing to hear that your baby has warts. But the founder I spoke with said the most painful calls were the ones that taught him the most. One customer essentially told him that his onboarding process was confusing and cost them a week of productivity. He fixed it, and that customer's lifetime value doubled. Luna: So the audit doesn't just surface feature requests — it also uncovers friction points in the core experience. That's a whole other layer of value. Lucas: Exactly. And that's why he asks about pain, not just features. The question 'what do you wish we did differently?' can reveal process issues, documentation gaps, or even pricing confusion. One customer said they wished the billing page showed the exact amount instead of an estimate. That was a two-line code change, but it removed a source of anxiety every month. Luna: Small things that compound. I love that he doesn't let perfect be the enemy of good — he'll act on a two-line fix just as readily as a six-month project. Lucas: That's the bootstrapper mindset. Every improvement is measured by its impact on customer happiness and willingness to pay, not by its engineering complexity. And because he's the one making the calls, he has direct empathy for the customer that can get lost in a larger organisation. Luna: So if someone wants to start doing this tomorrow, what's the one piece of advice you'd give them from this conversation? Lucas: Start with the customers who just renewed. They're the most likely to be honest and the least likely to feel attacked. Call them, ask those three questions, and actually write down what they say. Don't try to fix anything during the call — just listen. Then, within a week, follow up with what you heard. The first audit will feel awkward. The second one will feel like the most productive hour of your quarter. Luna: I'm going to try it. And I'll report back on how it goes. Lucas: Please do. I have a feeling you'll find at least one thing that makes you rethink your roadmap.