Latest / The Bootstrapped Tech Founder with Fexingo: Profitable Software Companies Without VC / How Bootstrapped Founders Use Asynchronous Communication to Scale
Transcript
- Lucas: When you're bootstrapped, every hour you spend in a meeting is an hour you could have spent building or talking to customers. And that's led a lot of founders to rethink how they communicate internally. One of the most interesting examples is Sahil Lavingia at Gumroad. Luna: Right, Gumroad — the digital products platform. Sahil has been vocal about how he runs the company with a fully asynchronous approach. Lucas: Exactly. And the numbers here are stark. In a recent public doc, Sahil shared that Gumroad's team of roughly fifteen people across ten time zones only holds one optional weekly call. Everything else — product decisions, customer support, strategy — happens in writing. Luna: So no standups, no all-hands, no daily syncs? Lucas: None. And the reasoning is specific: they calculate that a one-hour meeting with fifteen people costs the company fifteen hours of productive time. Over a year, cutting a daily standup saves thousands of hours. For a bootstrapped company where cash flow matters, that's significant. Luna: That's the kind of trade-off a vc backed company might not think about — they've got the burn to cover inefficiency. Lucas: Right. And Sahil has written that async communication forces better writing. When you can't talk it out in real time, you have to articulate your thoughts clearly, which reduces misunderstandings. He even says he judges candidates by their ability to write a thoughtful proposal. Luna: But doesn't that slow things down? If you need a decision fast, waiting twenty-four hours for a response can be painful. Lucas: It does shift the pace. But bootstrapped founders are often building for the long haul, not sprinting to a quarterly growth target. And they compensate with rapid async loops — like setting expectations for response times within four hours during business hours. Gumroad uses a tool called Twist for threaded discussions. Luna: Twist, developed by the Basecamp team. Also built by bootstrapped founders. Lucas: Exactly. And the key insight is that async doesn't mean no communication. It means deliberate communication. You write a thoughtful update, tag a few people, and they respond when they have a coherent thought. No interruption of deep work. Luna: I've heard founders say that a single thirty-minute meeting can derail an entire morning of coding. So this might actually be faster overall. Lucas: That's the argument. Sahil says he gets more done in a four-hour writing block than in an eight-hour day of back to back meetings. And because Gumroad is profitable and growing, the model speaks for itself. Luna: Nathan Barry at ConvertKit has a similar philosophy. He wrote about using a 'no-meeting Wednesdays' policy originally, and then expanded it to almost no recurring meetings at all. Lucas: Right. And ConvertKit grew to over thirty million dollars in annual revenue with a fully remote team. That's a strong signal that async works for bootstrapped businesses. Luna: Are there any downsides? I mean, human connection — don't you lose some of that? Lucas: Sure. Both Sahil and Nathan acknowledge that async can feel isolating if you don't invest in intentional connection. They do things like virtual co-working sessions or annual retreats. But the trade-off is autonomy. For many bootstrapped founders, the freedom to focus without interruptions outweighs the occasional loneliness. Luna: And async communication also forces documentation. Every decision is recorded in writing, which becomes a knowledge base for new hires. Lucas: Huge point. At ConvertKit, they use Notion extensively for everything from strategy docs to onboarding guides. Because everything is written, new team members can catch up without pulling senior people into meetings. That scales really well. Luna: And customer support also benefits. A thoughtful, written response is often better than a rushed phone call. Plus, it can be reused as a help article. Lucas: Exactly. Gumroad's support is entirely async — they use email and a knowledge base. Their response times are actually better than industry average because they batch replies during focus blocks. Luna: So the whole business becomes more efficient and more resilient. It's not just about meetings. Lucas: These are the kinds of operational details that I love digging into because they're practical, not theoretical. Luna: Yeah, and that's exactly why we keep this show ad-free — we want to share these specifics without any sponsor interference. Lucas: Absolutely. A couple of dollars a month from listeners who find value in it really helps. If you've gotten something from this episode or any of our previous ones, consider tossing a few bucks at buy me a coffee dot com slash fexingo. Luna: Yeah, even just a coffee keeps the servers running and lets us keep talking to founders who are building sustainably. Lucas: And speaking of building sustainably, let's talk about how bootstrapped founders handle customer support without a large team — another area where async communication plays a role. Many use a combination of public knowledge bases, forum threads, and email templates that they refine over time. Luna: That's actually a great lead into something I read about — Buffer uses a similar async support model. They have a tiny team but respond to thousands of tickets. Lucas: Buffer's another good example. They've always been transparent about their internal processes. Their support team uses Slack in a limited way, but mostly relies on email and a public help center. They've found that customers actually prefer getting a clear, written answer they can refer back to. Luna: So async isn't just about internal operations — it can improve the customer experience, too. Lucas: Exactly. And for bootstrapped founders, where every dollar and every hour count, that dual benefit is huge. You reduce the cost of support while increasing satisfaction. Luna: I think one of the underappreciated benefits is that async forces you to prioritize. If you can't just jump on a call to resolve confusion, you have to make your product and documentation clearer from the start. Lucas: That's a great insight. Sahil has said that living async actually made Gumroad's product better — because every customer interaction had to be self-service friendly. They invested heavily in their knowledge base and in-app guidance. Luna: It's like a flywheel — async operations lead to better documentation, which leads to fewer support tickets, which leads to more time for product improvements. Lucas: Right. And that's the kind of compound effect that bootstrapped companies live on. Slow, deliberate improvements that stack over years. Not the VC playbook of growth at all costs. Luna: So if a founder is listening and wants to start transitioning to async, what's the first step? Lucas: Start by auditing your meetings. Write down every recurring meeting, its duration, and its purpose. Then ask: could this be solved with a written update or a shared doc? Often, the answer is yes. Sahil started by canceling all regular meetings and told his team to only schedule one if absolutely necessary. Luna: Radical, but it worked. And I'd add: pick one tool and stick with it. Twist or Basecamp or even just email. The tool matters less than the discipline of writing clearly. Lucas: Exactly. The shift is mental more than technical. You're trading synchronous comfort for asynchronous rigor. But once you get used to it, it's hard to go back. Luna: And the results speak for themselves — profitable, growing companies with happy teams. Lucas: That's the bootstrapper's definition of success. No meetings, more building.