Latest / The Founder's Journey with Fexingo: First-Time Entrepreneurs, Failures, and Lessons Learned / How a Founder Used a Burned Down Office to Build a 20M Business
Transcript
- Lucas: So there's this founder — we'll call him Mark, not his real name — who launched a software company in 2010 out of a rented office in downtown Austin. He had maybe eight employees. Six weeks after launch, a fire started in the building's electrical room at 2 AM. By dawn, his entire office was gutted. No servers survived, no paper records, no nothing. Luna: That's the kind of thing that kills a startup before it's even started. I can't imagine trying to recover from that at six weeks. Lucas: Right. Most businesses that experience a total property loss never reopen. But Mark did. And within three years, that company was doing twenty million dollars in annual recurring revenue. Today it's closer to fifty. Luna: Okay, I have to hear how. Was there some insurance jackpot that gave them a ton of cash to rebuild? Lucas: Partially. They had a decent business interruption policy. The insurance paid out about three hundred thousand dollars for lost equipment and about six months of payroll. But here's the thing — they didn't use most of that money to rebuild the office. Luna: What did they do instead? Lucas: They went fully remote. In 2010. Before remote work was a thing outside of a few tech companies. Mark told me that standing in the ashes, he realized they didn't actually need the office. They needed the people and the code. And the code was backed up off-site — he had a personal habit of pushing to a GitHub private repo every night. So the code was safe. Luna: So all they lost was furniture and maybe some hardware. But they still had to get everyone set up at home, right? That's not cheap. Lucas: It was cheap compared to Austin office rent. They gave each employee a two-thousand-dollar stipend to buy a desk, chair, monitor, whatever. Total one-time cost: sixteen thousand dollars. Their monthly rent had been fourteen thousand. So after month one, they were cash-flow positive on the real estate alone. And they had a three-hundred-thousand-dollar insurance check sitting in the bank. Luna: So the fire actually improved their unit economics. That's wild. But I imagine customer trust was a bigger issue. If you're a six-week-old startup and your office burns down, don't your clients think you're about to go under? Lucas: That was Mark's biggest fear. So he did something that I think is the real reason the business survived. He called every single customer personally — there were about forty of them at that point — and told them exactly what happened. No spin. He said 'Our office burned down. We're okay, your data is safe, but I wanted you to hear it from me before you heard it anywhere else.' Luna: That's counterintuitive. Most founders would try to hide it or downplay it. But the honesty probably built more trust than any marketing could have. Lucas: Exactly. And he followed up every call with a personal email that included his cell phone number and said 'If you're worried, call me anytime, day or night.' A few customers did call — at 3 AM, but he answered. That level of transparency turned the disaster into a brand story. Customers started rooting for them. Luna: I love that. But I want to push back a little on the 'blessing in disguise' narrative. A lot of companies go remote and fail. A lot of founders call customers and it doesn't save them. Isn't this just survivorship bias? Lucas: It is, partially. But I think there's a real lesson in how constraints forced better decisions. Before the fire, Mark was spending a lot of time and energy on the office — decorating it, managing the internet, worrying about whether the air conditioning was working. After the fire, all that mental bandwidth went into product and customers. Luna: So the fire was a forcing function. It stripped away everything non-essential. Lucas: Exactly. And that's a principle that applies even if you never have a fire. What can you deliberately strip away from your business that's eating up time and money without adding real value? Luna: Maybe that's the real story here. Not the fire itself, but the clarity it created. Lucas: Yeah. And it's worth noting that Mark didn't plan to go remote. He was a pretty traditional manager. The fire made the decision for him. But once he was forced into it, he realized he preferred it. His team was happier, productivity didn't drop, and they saved a ton of money. Luna: So what happened to the insurance money they didn't spend on the office? Lucas: They invested it in customer acquisition. They ran a targeted ad campaign on LinkedIn — which was still pretty new in 2010 — and used the cash to hire a part-time salesperson. That was the turning point. Within six months, they had tripled their customer base. Luna: So the fire indirectly funded their growth. That's a hell of a story. Lucas: It is. And it's one of those cases where the obstacle really was the way. But I think the key takeaway isn't 'hope your office burns down.' It's that when a crisis hits, your response to it can define your company's trajectory more than the crisis itself. Luna: I want to linger on that customer call strategy. Because I think a lot of founders hear 'call your customers' and they think it's too simple or too scary. But Mark did it and it worked. Is there a specific script he used? Lucas: He didn't have a script. He just said what he would want to hear if he were a customer. 'Here's what happened, here's what it means for you — which is nothing — and here's my personal number if you're worried.' No jargon, no spin. Just honesty. Luna: And he answered the phone at 3 AM. That's the part that's hard to replicate. Lucas: Agreed. But you don't have to answer at 3 AM to show you care. You can set expectations. Say 'I'll respond within two hours during business hours, and within 24 hours on weekends.' The point is to signal that you're reachable and you take their concern seriously. Luna: Okay, so let's talk about the remote transition. In 2010, there wasn't Slack, there wasn't Zoom as we know it. How did they actually coordinate? Lucas: They used a combination of IRC — yeah, Internet Relay Chat, very old school — and Skype for voice calls. They also had a daily fifteen-minute stand-up call at 9 AM. Everyone had to be on. No exceptions. That created a rhythm. Luna: And they didn't miss the office? The water cooler conversations? Lucas: Mark said some people did. But they replicated that by having a dedicated Slack channel — well, IRC channel — called 'random' where people posted funny links or talked about non-work stuff. It was intentional. They didn't just work; they built social space online. Luna: That's a good lesson for any remote team, even now in 2026. You have to be intentional about culture. Lucas: Exactly. So Mark's story is really about three things: radical transparency with customers, using constraints to focus on what matters, and being willing to abandon your own assumptions about how work should happen. Luna: I think there's also a fourth thing: luck. The fire happened at night, no one was hurt, the code was backed up. If it had happened during the day with injuries, or if the backup had failed, the story would be very different. Lucas: That's a fair point. But I'd argue that luck played a role, but so did preparation. Backing up code off-site was a choice. Having insurance was a choice. Answering the phone at 3 AM was a choice. Luna: Yeah, that's true. You make your own luck, to some degree. Lucas: And if these kinds of conversations — about real decisions, real numbers, real crises — move your work forward in some small way, that's exactly why we make this show. We deliberately don't run ads on it. If you want to support that choice and keep it ad-free, the link is buy me a coffee dot com slash fexingo. No pressure, just an option for those who find value here. Luna: Yeah, it's a small gesture that goes a long way in keeping these episodes independent and honest. Lucas: Alright, back to the fire. One more detail I love: after they went remote, Mark started a weekly all-hands video call, not for work updates, but just to check in. He'd ask 'What's one thing you're excited about this week?' It sounds cheesy, but it built a lot of cohesion. Luna: That's actually a practice I've seen in a lot of successful remote companies. It's about maintaining human connection when you're not sharing a physical space. Lucas: Right. And Mark's company still does that call, every Monday, fifteen years later. The fire is a distant memory, but the practices it forced into existence are still part of the culture. Luna: So if a founder listening right now is facing a crisis — maybe not a fire, but a big setback — what's the one thing you'd tell them to do that Mark did? Lucas: Call your customers. Not email. Not a blog post. Pick up the phone. Tell them the truth. And then listen to what they're worried about. That single action can turn a disaster into a deeper relationship. Luna: I think that's a good note to end on. Thanks, Lucas. Lucas: Thanks, Luna. And if you've got a founder story you think we should cover, you know where to find us.