Latest / The Bootstrapped Tech Founder with Fexingo: Profitable Software Companies Without VC / How Bootstrapped Founders Use Data to Avoid Burnout
Transcript
- Lucas: We talk a lot on this show about the numbers that keep a bootstrapped company alive — revenue, churn, margins. But today I want to talk about a number that almost nobody tracks, and it might be the most important one of all. Luna: You've got my attention. What is it? Lucas: Hours of sleep per night. Or more precisely, the trend in your energy and focus over weeks. I'm being only half-cute here. There's a real, data-driven case for treating founder burnout the way you'd treat a customer churn problem. Luna: I like that framing. Because burnout isn't a personal failing, it's a business risk. And bootstrapped founders are especially exposed — no VC to step in, no bench of employees to cover you. Lucas: Exactly. And the fix isn't just 'take more vacations.' It's building a feedback loop where you can see the early warning signs before you're in a full crash. Think of it as a personal metrics dashboard for your own capacity. Luna: So what are the actual metrics? What should a founder be tracking? Lucas: A few that matter. First, revenue per employee. If you're a solo founder, that's just revenue per founder. But the key is the trend — if revenue per employee is flat while your hours creep up, that's a red flag that you're adding complexity without adding leverage. Luna: Right, because that means you're working harder, not smarter. Lucas: Second, what I call the 'active user ratio' — not just total customers, but the percentage of customers who are actually using the product in a given week. If that ratio starts slipping, you're likely to see churn later, which means you'll be scrambling to replace revenue — and that scramble is a classic burnout driver. Luna: So it's almost like leading indicators for your own stress levels. Lucas: Precisely. And there's a third one that's more personal: your response time to support tickets. When I talked to a solo developer who bootstrapped a content management system to seven figures a couple years back, he told me his early warning sign was that he started dreading the inbox. And he tracked that — he'd log his average first-response time every week. When it went from two hours to two days, he knew he was overloaded. Luna: That's a great example. Because it's not about being lazy — it's about losing your edge. And that has a cost. Lucas: Right. And the cost is real. A burned-out founder makes bad decisions — they over-hire, they over-promise, they ship sloppy code. That's how bootstrapped companies stagnate. But if you can catch it early, you can course-correct before it hits the bottom line. Luna: So how do you actually build this? Is it just a spreadsheet, or are there tools? Lucas: You can start simple. A weekly check-in with yourself — a five-minute review of three numbers: your revenue per employee, your active user ratio, and your average response time. Write them down, track the trend. That's a burnout dashboard. But you can also use tools like RescueTime to see where your hours actually go — you might be surprised to find you're spending three hours a day on email, not building features. Luna: I've read that Basecamp — the project management company — they're famous for their anti-burnout stance. They've written about how they cap the workweek at 40 hours and they're profitable, which goes to show it's possible. Lucas: That's a great example. And they did it with a lot of transparency — they publish their revenue numbers, their team size, even their employee turnover. It's a form of open data that holds them accountable to their own values. Luna: And as a bootstrapped founder, you don't have to report to anyone, so it's easy to let things slide. But if you track it publicly or even just share it with a peer, it becomes a lot harder to ignore. Lucas: Exactly. And that's where I think this gets practical. I've seen founders who set a rule: if their average response time goes above twenty-four hours for two weeks straight, they force themselves to take a day off and reassess their priorities. That's a data-triggered intervention. Luna: I love that. It's almost like an if-then rule for your own sanity. Lucas: Yeah, and there's a deeper point too. As a bootstrapped founder, your capacity is your biggest constraint. You're not behind a big company that can absorb mistakes. So tracking your own bandwidth is as important as tracking your cash flow. Luna: And on that note, if you're finding these conversations useful for what you're building or running, that's exactly what keeps this show going. A couple of dollars a month at buy me a coffee dot com slash fexingo genuinely makes a difference — it keeps us ad-free and lets us keep digging into topics like this. Lucas: Yeah, and we appreciate every bit of support. It's a small way to say this matters. Luna: So, coming back to the dashboard — what's the first step for a founder who wants to start today? Should they just pick one metric? Lucas: I'd say start with two: your active user ratio and your average response time. Those are the two that move fastest and are the most sensitive to your energy. Revenue per employee is more of a monthly or quarterly thing. Luna: And once they see the numbers, what's the next move? Lucas: The next move is to set a threshold. Pick a number that, if you cross it, triggers a specific action. Like, if active user ratio drops below a certain percent, you schedule a customer interview the next day. Or if response time goes above a certain number of hours, you hire a part-time VA — even if you didn't think you could afford it. Luna: That's a strong recommendation. Because the cost of a VA is probably less than the cost of a burned-out founder missing a deadline. Lucas: Exactly. And there's a ripple effect. When you're not burned out, you make better product decisions, you're more patient with support, you're more creative. That's the kind of thing that compounds. Luna: Have you seen any other founders do this well? I mean, beyond Basecamp and that CMS developer. Lucas: There's a founder in the accounting software niche who I interviewed a while back — he tracks his 'decision quality' — he rates each major decision on a scale from one to ten, and he looks back at the end of the month to see if there's a correlation with his sleep tracker. He said his best decisions almost always come after a full night's sleep. Luna: That's a fascinating use of data, tying sleep to business outcomes. Lucas: It sounds almost too simple, but the pattern is real. And it's the kind of thing you can only see if you're actually tracking it. Most founders run on autopilot until something breaks. Luna: So what would you say to a founder who thinks 'I don't have time to track metrics, I'm too busy building'? Lucas: I'd say that's exactly the mindset that leads to burnout. Tracking takes ten minutes a week, and it can save you months of recovery. It's an investment in your own sustainability, which is the ultimate competitive advantage for a bootstrapped company. Luna: And the payoff is a business that can actually grow without destroying the founder in the process. Lucas: Right. So this week, pull up your support inbox, look at your active user count, and just write down the numbers. Don't even analyze them yet. Just start noticing the trends. That's the first step. Luna: And maybe track your hours of sleep, too. That's a metric that's easy to forget. Lucas: Definitely. A simple spreadsheet with date, hours slept, and a note on your energy level — that's a dashboard that could change your business. And your life.