Latest / The Bootstrapped Tech Founder with Fexingo: Profitable Software Companies Without VC / How Bootstrapped Founders Can Afford Hiring
Transcript
- Lucas: There's a question that sits in the back of every bootstrapped founder's mind, and it usually surfaces right after a really good month. It goes something like, 'I made more money than I expected this month — should I finally hire someone?' Luna: And then the fear kicks in, and they talk themselves out of it. Lucas: Exactly. And I get it. When you're bootstrapped, there's no VC cushion. A salary commitment feels like a permanent weight on your cash flow. But here's the thing: not hiring is also a decision, and it has a cost too — opportunity cost, burnout cost, the cost of staying stuck at the same revenue ceiling. Luna: So what's the actual math? Like, when does hiring make sense for a bootstrapped company? Lucas: Let's start with the obvious: the salary. But that's just the tip. You've got payroll taxes, maybe health insurance, equipment, software licenses, and if you're in the US, workers' comp in some states. A $90,000 salary can easily cost you $115,000 to $120,000 once you add it all up. Luna: And that's before you factor in the cost of your own time to train and manage them. Lucas: Right. So a common rule of thumb I've seen in bootstrapped circles is the 'profit-first hiring rule.' You should only hire when your profit — not revenue, but profit — can cover the fully loaded cost of the hire at least one and a half times over, consistently, for about six months. Luna: Why one and a half times? Why not just break-even? Lucas: Because you need a buffer. A new hire doesn't generate revenue on day one. You're paying them to build, fix, or support while you're also still covering your own salary and the business's ups and downs. If you only have just enough to cover them, one bad month and you're in a panic. Luna: That makes sense. So what's a realistic timeline before a new hire starts paying for themselves? Lucas: It depends on the role. A sales person might bring in revenue in a month or two. A developer might take three to six months before they're shipping features that move the needle. A support person can free up your time almost immediately, but you need to convert that time into revenue-generating work. Luna: So it's not just about the money — it's about leverage. Lucas: Exactly. And there's a great way to think about it: revenue per head. If you're a solo founder doing $300K in revenue, that's $300K per head. If you hire someone and your revenue stays flat, your revenue per head drops to $150K. That might actually be fine if your profit per head stays healthy. The key is to track profit per head, not just revenue. Luna: Have you seen a case where a bootstrapped founder hired too early and regretted it? Lucas: Definitely. There's a well-known story of a SaaS founder who hired his first employee — a developer — after a record month, but the next two months were below average. He ended up covering payroll out of his savings, and it created a lot of stress and resentment. He almost shut down. Luna: Ouch. So the buffer is real. Lucas: Yeah. But the opposite mistake is just as common — waiting too long. I've seen founders who've been solo for years, hitting a plateau because they're buried in support tickets and can't build new features. They finally hire, and within six months, revenue jumps 30 percent because they're back to doing what they do best. Luna: So how do you know which camp you're in? Lucas: There's a simple diagnostic: for the last two weeks, track every hour you spend on tasks that are below your pay grade. If you're spending more than 20 percent of your time on support, admin, or things you could hand off, that's a strong signal. Luna: And sometimes it's not a full-time hire, right? Lucas: Exactly. Part-time or contract can be a great first step. There's a founder I know who hired a part-time developer for twelve hundred dollars a month, just to handle bug fixes and small feature requests. That freed him up to focus on sales and marketing, and within a quarter, his revenue was up 40 percent. The hire paid for itself many times over. Luna: That sounds like a low-risk way to test the waters. Lucas: It is. And it lets you build the muscle of managing someone without the full commitment. But you have to be careful — some people are great as contractors, but eventually you need someone who's all in on your mission. There's a tipping point where a contractor is just a band-aid. Luna: Before we go deeper, I just want to say — if you're getting value from these conversations, a couple of dollars a month at buy me a coffee dot com slash fexingo is genuinely what keeps these going. It's a small thing that makes a big difference. Lucas: Yeah, it really does. And it keeps the show ad-free, which we love. So if you can, that's great. But let's get back to the hiring math, because there's a real emotional side to this too. Luna: Oh, absolutely. Letting go of control is hard for most solo founders. Lucas: I've talked to founders who said the hardest part wasn't the money, it was trusting someone else to handle customer emails or write code in their codebase. There's a real identity shift from 'I do everything' to 'I lead a team.' Luna: And that's probably why so many bootstrappers stay solo for way longer than they should. Lucas: Yeah. But there's a practical way to ease into it: hire for a role where the stakes are lower, like customer support. You can write a playbook, and the downside of a mistake is a frustrated customer, not a broken feature. Once you see that the world doesn't end, you can level up to hiring for more critical roles. Luna: So what's the actual decision framework you'd give a founder listening right now? Lucas: First, calculate your fully loaded cost for the role you're thinking about. Second, check your last six months of profit — average it, and make sure it's consistently above that cost. Third, identify the tasks that are eating your time that the hire would take over. And fourth, think about the upside: if you get that time back, what could you do with it that would grow revenue? Luna: And what if the math doesn't quite work yet, but you're drowning? Lucas: Then consider a part-time hire or an independent contractor. You can often get 15 to 20 hours a week for a fraction of a full salary. That's often enough to unblock you. And it's a low-risk way to test the waters before you commit to a full-time hire. Luna: I love that. It's not all-or-nothing. Lucas: Right. And one more thing: think about the type of person you want. For bootstrapped companies, you don't need a superstar. You need someone reliable, coachable, and aligned with your values. You can train on skills, but you can't easily change character. Luna: That's a good note to end on. For our listeners, the key takeaway is: don't let a good month fool you, but also don't let fear hold you back. Run the numbers, start small if you need to, and remember that your time is the most valuable asset you have. Lucas: And if you've made the leap or are wrestling with the decision, we'd love to hear about it. But for now, thanks for listening, and here's to building something that lasts.