Latest / The Bootstrapped Tech Founder with Fexingo: Profitable Software Companies Without VC / How Bootstrapped Founders Can Support Customers Without a Help Desk
Transcript
- Lucas: So there's this solo founder I've been following—she runs a project management tool for small agencies, about two thousand paying customers, and she handles all support herself using nothing but a shared inbox and a well-stuffed help document. Luna: Wait, no help desk software at all? How does she keep track of everything? Lucas: That's exactly what I wanted to dig into, because the conventional wisdom says you need a proper ticketing system once you pass a certain scale. But she's been doing it for three years, and her response times are actually better than the industry average—median first reply under two hours. Luna: That's impressive. So what's her secret? Is it just discipline? Lucas: Partly, but it's more about systems. She uses email labels and filters to separate support from everything else, and she has a set of email templates for the fifty most common questions she gets. The templates aren't canned—she personalizes each one—but they save her the mental overhead of starting from scratch every time. Luna: I like that. It's like having a cheat sheet for your own product. But what about the harder, more complicated questions that don't fit a template? Lucas: That's where the help document comes in. She treats her knowledge base as a living thing. Whenever she gets a question that isn't already covered, she writes a short answer in the doc, then links to it in her reply. Over time, the doc handles more and more of the load—she says about seventy percent of her replies now just point to a specific page. Luna: So she's essentially outsourcing to her own documentation. That's clever. But isn't there a risk that customers get annoyed when you just send them a link? Lucas: She's careful about that. The link is always accompanied by a one-sentence summary of the answer, so the customer gets the info even if they never click. And she's found that most people actually appreciate it because they can refer back to it later. It's not about deflecting—it's about giving them a resource. Luna: That makes sense. So what's the cost savings? I'm guessing she's avoiding a monthly subscription that could be a hundred bucks or more. Lucas: Yeah, she told me she'd be paying at least a hundred and fifty dollars a month for a decent help desk with two seats. That's eighteen hundred a year, which for a bootstrapped company is real money—especially at her stage where she's reinvesting everything into development. And she says the shared inbox approach actually feels more personal, because customers get a reply from a human, not a ticket number. Luna: I can see that. It's like the difference between emailing a friend and submitting a form. But I'm curious—what happens when she's on vacation or gets sick? Doesn't the whole thing fall apart? Lucas: That's the biggest vulnerability, and she knows it. She sets clear expectations by having an autoresponder that says responses might take up to forty-eight hours during holidays. And she has a network of other solo founders she can tap for emergencies—she's actually exchanged access with a couple of them, so they can cover for each other if something urgent comes up. It's not perfect, but it works for her. Luna: A support co-op among founders—that's a neat idea. But I bet it only works if you keep things simple. So what's her rule for when she'd finally switch to a real help desk? Lucas: She says the moment she finds herself losing track of a customer request, or when she starts getting duplicate emails from the same person because they didn't get a response, that's the signal. She's also keeping an eye on her response time—if it creeps above six hours on a regular basis, she'll know she's outgrown the system. Luna: That's a smart threshold. It's all about the customer experience, not just the tool. And speaking of which, I think it's worth mentioning that we're able to have these conversations without any ads interrupting because of listener support. If you find value in what we're doing, you can help keep it that way at buy me a coffee dot com slash fexingo. Lucas: Yeah, we really appreciate that. It keeps Fexingo free of sponsors, so we can focus on what's useful for you. Anyway—back to the shared inbox. There's another piece of her system that I think is brilliant. Luna: What's that? Lucas: She tracks a simple metric every week: how many support emails she received, and how many of those were already answered by an existing help doc. That tells her whether her knowledge base is actually reducing her load, or if she's just writing new answers all the time. Luna: So she's measuring the effectiveness of her documentation. That's something a lot of founders skip—they just write a few articles and never look back. Lucas: Right. And she's been able to see that number improve over time. When she started, maybe thirty percent of questions were covered by existing docs. Now it's up to seventy. That's a massive reduction in the amount of repetitive typing she has to do. Luna: I love that. It's like she's building a little machine that learns. But what about the emotional side? Doesn't doing all support yourself get exhausting? Lucas: She admits it can be, especially during launch weeks. But she says it's also the best way to stay close to customers—she hears their problems directly, which fuels her product roadmap. She told me that some of her best features came from support emails where a customer described a workaround they'd built because the tool didn't do what they needed. Luna: That's support-led growth in action. You're not just solving problems—you're discovering opportunities. So for a founder who's thinking about trying this, what's the first step? Just set up a shared inbox? Lucas: The first step is actually to write down the ten most common questions you get. If you don't know those off the top of your head, scroll through your email history and count. Then create a simple doc with answers to those ten, and next time someone asks, you link to it. That alone will cut your response time in half. Luna: And what about the shared inbox itself? Are there any free tools that work well for this? Lucas: Absolutely. You can use something like Google Workspace or even a free email provider, but the key is to set up labels and filters so support emails don't get buried. There are also free tools like Zoho's shared inbox or Help Scout's free tier—though those might be overkill. The point is to keep it simple and manual until you're at a point where the system breaks. Luna: So it's not about being cheap for the sake of it—it's about avoiding unnecessary complexity early on. That fits with the whole bootstrapped philosophy. Lucas: Exactly. Too many founders buy a help desk before they even have customers, just because they think they're supposed to. But if you're a solo founder or a tiny team, a shared inbox can actually give you a competitive advantage because you're so close to your users. Luna: And you can always graduate to a dedicated tool later. It's not like you're locked in forever. So what's your takeaway for our listeners who are maybe at that tipping point? Lucas: My takeaway is: measure first, and only buy when you have the numbers to justify it. If you're missing emails or response times are slipping, that's a clear signal. But if you're managing fine and your customers are happy, there's no shame in keeping it lean. The money you save can go into building a better product, which ultimately reduces support needs even more. Luna: That's a nice virtuous cycle. Any final advice on the help doc itself? How do you make it good enough that customers actually use it? Lucas: She has a simple rule: write each article as if you're explaining it to a colleague who's never seen the product. Use screenshots generously, and keep the language plain. And don't bury the answer—put the solution in the first paragraph, not the third. Customers are scanning, not reading. Luna: That's practical. And I guess it also helps with SEO—people can find your help docs on Google and solve their problem before they even email you. Lucas: Exactly. She's actually seen a steady trickle of sign-ups from people who land on her help docs via search. So it's not just a cost-saving measure—it's a marketing asset in disguise. Luna: That's a win-win. So to sum up: start with a shared inbox, build a living knowledge base, track your metrics, and only switch when the numbers tell you to. Sounds like a solid plan. Lucas: And remember, the goal isn't to avoid spending money—it's to spend it where it matters most. For a bootstrapped founder, that's usually product development, not support infrastructure. But when the time comes to scale up, you'll know, because your customers will tell you—one way or another. Luna: Well said. Thanks for breaking this down, Lucas. I think our listeners have a lot to chew on. And if you've got your own support hacks, we'd love to hear them—maybe we'll feature them in a future episode. Lucas: Absolutely. Send us a note, and who knows, you might be the case study we talk about next time.