Latest / The Bootstrapped Tech Founder with Fexingo: Profitable Software Companies Without VC / Why Bootstrapped Founders Use Async Communication
Transcript
- Lucas: If these conversations are useful for what you're building or running, there's a small, sincere way to keep them coming. We deliberately don't run ads on these shows. No sponsors, no pre-rolls, no mid-roll interruptions. Luna: Yeah, that's a choice we made early on and it still feels right. If you want to support that choice, the link is buy me a coffee dot com slash fexingo. Lucas: Exactly. And now to today's topic. I want to talk about something that I think is quietly transforming how bootstrapped founders operate: async communication. Luna: Async communication — you mean no meetings, delayed replies, that sort of thing? Lucas: Right, but it's more deliberate than just ignoring your calendar. It's a structural choice to move most internal communication out of real-time channels — Slack DMs, Zoom calls, ad hoc syncs — and into written, recorded, or documented formats that people can engage with on their own schedule. Luna: And this matters more for bootstrapped founders because…? Lucas: Because bootstrapped teams are usually lean. We're talking maybe 5 to 15 people. Every hour spent in a status meeting or waiting for a Slack reply is an hour not spent building, selling, or supporting customers. And unlike vc funded startups, they can't just hire more people to cover the overhead. Luna: So the opportunity cost of sync is higher. I've seen this firsthand. There's a company I follow called Plane — it's a project management tool, bootstrapped, about 12 people. They publish their internal async practices openly. One stat stood out: after they went async-first, they cut meeting time by 80 percent. Lucas: Eighty percent. That's massive. And the kicker is their revenue per employee climbed about 35 percent year-over-year during that same period. Now correlation isn't causation, but it's hard to argue that reclaiming that time didn't help. Luna: Right. So what does async-first actually look like in practice? I think people hear 'async' and imagine just sending emails into a void. Lucas: It's more structured than that. One pattern I've seen is the daily written update. Instead of a stand-up meeting, each person posts a short written or Loom video update in a shared channel: what I did yesterday, what I'm doing today, any blockers. Takes 5 minutes to write, 10 minutes to read everyone else's. No scheduling required. Luna: And that replaces what would be a 30-minute stand-up for a team of 12. You save 20 minutes per person per day. Over a month that's hours. Lucas: Exactly. Then there's decision logs. Instead of hashing out a decision in a real-time meeting, someone writes a proposal document — one page, background, options, recommendation. People comment asynchronously over 24 to 48 hours. Then the decision maker reviews the comments and makes a call. It gets documented permanently. Luna: I love that. Because in a synchronous meeting, the decision often goes to the loudest voice or whoever speaks first. Async gives introverts and deep thinkers a chance to contribute thoughtfully. Lucas: And it creates a record. Six months later you can go back and see why a decision was made. That's invaluable for onboarding new team members too. Luna: But there must be downsides. What about the serendipity of a quick huddle? Sometimes you need to riff off someone's idea in real time. Lucas: Sure. Async doesn't mean zero sync. Most async-first teams carve out specific windows for real-time collaboration. Maybe Tuesday and Thursday afternoons are 'office hours' where anyone can jump on a video call. Or they do a single weekly all-hands sync. The key is that sync becomes the exception, not the default. Luna: So you're preserving the benefits of real-time interaction but containing it. Another practice I've seen is 'no-meeting Wednesdays.' That's a full day of deep work, no internal meetings allowed. Some companies extend it to no-meeting mornings. Lucas: That works well. But I think the more radical shift is moving away from instant messaging as the primary communication tool. Slack is great for urgent stuff, but when every message expects a reply within minutes, it fragments attention. Async-first teams often use Slack more as a broadcast channel: announcements, kudos, links to docs. The actual work conversations happen in project management tools or shared documents. Luna: There's a framework called 'write it down' that a bootstrapped company called Basecamp has been preaching for years. They argue that writing forces clarity. If you can't explain your idea in a paragraph, you probably don't understand it well enough. Lucas: Basecamp is a great example. They've been profitable and remote for over two decades. They famously refused VC money. And their entire culture is built around async communication. They have a book about it — 'Remote' — but the practice goes deeper. They use internal blogs, not chat rooms, for most discussions. Luna: And they're not alone. There's a newer bootstrapped SaaS called Beeper. They started as a messaging aggregator, but internally they're almost entirely async. Their CEO, Eric Migicovsky, has said that they treat Slack like email: you check it a few times a day, not constantly. Lucas: That's a healthy mindset. Because the real enemy isn't meetings per se — it's context switching. Studies show it takes about 23 minutes to refocus after an interruption. If you're getting pinged every 10 minutes, you're essentially never in deep work mode. Luna: And for a bootstrapped founder who is also the lead developer or the main salesperson, deep work is where the leverage is. You can't afford to be in reactive mode all day. Lucas: So what's the practical first step for a founder listening right now who wants to move toward async? I'd say start with one meeting. Pick the most redundant recurring meeting on your calendar — maybe the daily stand-up or the weekly status update — and replace it with a written or recorded update for two weeks. Measure whether things get worse or better. Luna: And if you're the only one pushing for this on a team that's used to sync, how do you get buy-in? Lucas: Lead by example. Start posting your own async updates. When people see that you're getting more done, they'll be curious. And frame it as an experiment, not a permanent change. 'Let's try this for two weeks and see what happens.' That lowers the resistance. Luna: I think there's also a customer-facing angle. Some bootstrapped founders use async communication with customers too — like sending Loom videos explaining a feature instead of scheduling a call. It's more scalable. Lucas: Absolutely. And it builds trust because customers see you're being transparent and thorough. Of course, when a customer is upset or there's a sensitive escalation, sync is better. But for routine support or feature explanations, async can be more efficient for both sides. Luna: So async isn't a dogma. It's a tool. Use it where it fits. Lucas: Exactly. And the teams that do it well tend to be more profitable, less burned out, and more resilient. Which, for a bootstrapped founder, is pretty much the whole game.