Latest / The Bootstrapped Tech Founder with Fexingo: Profitable Software Companies Without VC / How Bootstrapped Founders Use Time Blocking to Protect Deep Work
Transcript
- Lucas: So there's this solo founder I've been following, runs a profitable little SaaS for agencies, and she recently posted her calendar for the week. It wasn't a wall of meetings. It was literally three blocks: product, support, marketing. And that was it. Luna: That sounds both incredibly simple and almost impossible to pull off. What was her revenue, if you don't mind sharing? Lucas: She's around sixty thousand a month, profitable, no outside money. And she told me the calendar isn't decorative. It's the whole system. She time blocks everything, including the buffer for when things blow up. And I think that's a genuinely underrated bootstrapper superpower. Luna: That's really interesting because a lot of founders I talk to say they can't time block because everything is urgent all the time. How does she handle that? Lucas: She said the trick is you don't block the exact minute the fire starts. You block the recovery time. Like, she expects to lose a day a week to emergencies, so she schedules it. That's the part that feels counterintuitive but works. Luna: Okay, so she's basically planning for chaos. That's a mindset shift. And before we go deeper, I just want to say, if this conversation is useful for what you're building or running, the reason we can keep it ad-free is listener support. You can buy me a coffee at buy me a coffee dot com slash fexingo. It genuinely helps keep these conversations going. Lucas: Yeah, that's the whole model. And it means we don't have to shill for anyone. So back to this founder. She calls it 'the three-block week.' Product on Monday and Tuesday, support on Wednesday, marketing on Thursday and Friday. Luna: And she just sticks to that? No meetings, no calls? Lucas: She has one two-hour window on Thursday afternoon for external calls. Everything else goes to async. She says if someone wants a call, they can send a Loom and she'll reply with a Loom. That's it. Luna: That's a bold line to draw. But I feel like a lot of founders would say, 'I can't do that, my clients expect a call.' How does she get away with it? Lucas: She got away with it because she set the expectation from day one. Her clients know she's a solo shop. And honestly, they're paying for the software, not for her to be on standby. She replaced real-time support with a really good knowledge base and a 24-hour response SLA. Luna: So it's not just about the calendar. It's about the systems that make the calendar possible. What does she do on her support day, then? Lucas: Support day is her favorite. She works through the inbox in batches, answers everything from the last 24 hours, and then she spends the rest of the day turning the top three questions into help-doc articles or small UX tweaks. So support becomes product research. Luna: That's clever. She's not just doing support, she's doing product discovery at the same time. And then marketing on Friday? What does that look like? Lucas: She writes two long-form posts, records a short demo video, and sends a newsletter. All in one day. She says it's the most draining day of the week, but she protects it because if she doesn't do it, the pipeline dries up in about eight weeks. Luna: So the message is: protect your deep work like it's your only revenue line. Because for a bootstrapper, it kind of is. Lucas: Exactly. And there's a specific technique she uses that I think is worth stealing. She doesn't just block 'product.' She blocks a theme for each product day. Monday is 'build new features.' Tuesday is 'fix bugs and refactor.' That way her brain doesn't have to switch context every time she sits down. Luna: That aligns with the research on context switching. Every time you switch, you lose maybe twenty minutes of focus. So batching similar tasks is like getting an extra hour a day for free. Lucas: Right. And she applies the same logic to her inbox. She only checks email at 10 a.m., 2 p.m., and 5 p.m. Not because she's rigid for the sake of it, but because she knows that every time she peeks, she loses the thread of what she was doing. Luna: I love that. It's like a mental firewall. You don't wait for the dopamine hit of a new message; you schedule the hits. Lucas: And it works. She's been doing this for three years, and her churn is under one percent. She told me the biggest change wasn't the calendar itself. It was giving herself permission to say no to things that don't fit the blocks. Luna: Say no to what, exactly? Like feature requests? Lucas: Sure, but also the stuff that feels productive but isn't. Like, she used to do a weekly 'state of the business' spreadsheet update that took three hours. Now she does it once a quarter. She realized the numbers didn't move that much week to week, so she was just procrastinating. Luna: That's painful because I bet every founder has at least one ritual like that. Something that feels operational but is actually just busywork. How do you catch it? Lucas: Her rule is simple: if a task doesn't directly move revenue, product, or customer happiness, it doesn't get a block. If it doesn't get a block, it doesn't happen. She literally has a list of 'things I don't do anymore' on her wall. Luna: A physical list? That's commitment. What's on it? Lucas: She showed me a photo once. It says: no unscheduled calls, no same-day replies, no feature requests from the top of my head, no comparing myself to funded startups, no working after 6 p.m. on weekdays, and no work at all on weekends except for emergencies. Luna: No weekend work at all. That's rare for a bootstrapper. How does she keep that boundary when a server goes down or a client is freaking out? Lucas: She has a simple rule for that too. If something takes less than ten minutes on a weekend, she does it. If it takes longer, she schedules it for Monday and sends a quick 'got it, will handle it Monday' message. She says nine times out of ten, it can wait. Luna: That's a great heuristic. And it probably keeps the client calm because they know you've seen it. You're not ignoring them, you're just setting a boundary. Lucas: Exactly. And the other thing she does is she blocks a two-hour buffer every Friday afternoon. She calls it 'slack time.' She doesn't plan anything for it. If nothing comes up, she goes for a walk or reads. If something breaks, she has a place to put it. Luna: So instead of over-scheduling herself and setting up for failure, she builds in the inevitability of chaos. That feels almost zen. Lucas: It is. And it's the reason she's been able to do this for years without burning out. She told me the turning point was when she realized that working more hours doesn't make a better product. It just makes a tired founder. Luna: That's a line I might have to steal. Tired founders make bad decisions. So what's the one thing a listener should try this week if they want to start time blocking? Lucas: I'd say start with a theme day. Pick one day next week and designate it as 'deep work only.' No meetings, no email until lunch. Just one project for the whole day. See what happens. Luna: And if they're scared they'll miss something urgent? Lucas: Check your phone twice a day. That's it. If the world is going to end, you'll find out soon enough. And if it doesn't end, you might just ship something that matters. Luna: I think that's the real gift here. Time blocking isn't just about productivity. It's about building a company that doesn't depend on your burnout. Lucas: Exactly. And for a bootstrapped founder, that's the whole game. You're not racing a clock set by investors. You're building something that can last. Luna: Well said. I'm definitely going to try a theme day next week. Maybe I'll even put it on the calendar. Lucas: Do it. And if you find yourself reaching for your phone at 9 a.m., just remember: the email will still be there at 10.