Latest / Bootstrapped Business with Fexingo: Self-Funded Founders, Profit-First Growth, and Lean Operations / How a Bootstrapped Founder Built a 30M Business on Spreadsheets
Transcript
- Lucas: So there's this founder — I'll keep him anonymous because he still runs the company and doesn't seek publicity — who built a $30 million a year B2B SaaS business with no code, no venture capital, and no salespeople. For the first two years, he had zero paying customers. And the backbone of the entire operation was a series of Google Sheets. Luna: Wait — he had no customers for two years, but still kept going? How did he fund it? Lucas: He had a small consulting gig on the side, bringing in maybe $4,000 a month. He lived frugally in a low-cost city, and his burn rate was basically just his laptop and the $15 a month for Google Workspace. The spreadsheet was his MVP. He manually processed orders, did data entry, and sent invoices by hand. Luna: That sounds unsustainable at scale. But I guess if you're not growing fast, manual can work for a while. Lucas: Exactly. And that's the whole philosophy. He wasn't trying to grow fast. He was trying to validate that people would pay for the solution before he invested any real time or money into automation. The product was essentially a set of templates and a manual service wrapped together. He charged $97 per month. Luna: Ninety-seven dollars — that's a very specific number. Did he test different price points? Lucas: He started at $49, then bumped it to $97 after the first three sign-ups didn't flinch. He told me that the $97 price was a psychological threshold — under $100 felt like a low-risk trial for a business tool. And for the first 18 months, he personally onboarded every single customer, often spending an hour per person on a Zoom call, walking them through the spreadsheet. Luna: So he was basically the product, the support, the sales, and the development all in one. That's intense. Lucas: It was. But because he had no investors, there was no pressure to hire or scale. He could afford to be inefficient. The turning point came when he hit 100 customers — about $9,700 in monthly recurring revenue. That's when he decided to hire his first employee, a part-time virtual assistant to help with data entry. Luna: And I'm guessing that assistant cost a lot less than a developer would. Lucas: Right — he paid $500 a month. That freed up his time to start building some basic automation. He used a script to generate invoices instead of typing them. Then he added a simple web form so customers could submit data directly into the spreadsheet. Each step was tiny, but each one reduced his manual workload by maybe 10 or 20 percent. Luna: How long did it take him to go from that first hire to actually having a real software product? Lucas: About three years. He didn't hire a developer until he had $20,000 in monthly recurring revenue. And even then, the developer was a freelancer in Eastern Europe who worked 10 hours a week. The first version of the actual SaaS platform was essentially just a front-end on top of the same spreadsheet logic. He never rebuilt the core — he just added a UI. Luna: That's surprisingly common in bootstrapped businesses. The spreadsheet stays as the source of truth long after they 'build' the software. Lucas: Yeah, and there's a real advantage there. Because the spreadsheet was so transparent, the founder could see exactly which steps were error-prone or slow. When he finally hired a developer, he had a perfect specification — the spreadsheet was the spec. No ambiguous requirements, no feature bloat. Every field in the database existed because it had been validated by manual use. Luna: So what was the biggest mistake he made along the way? Lucas: He told me about a $40,000 mistake. Early on, he had a spreadsheet formula that calculated a discount for annual contracts. He accidentally referenced the wrong cell — it was applying the discount twice. By the time he noticed, about 60 customers had been underbilled for six months. He honored the wrong prices because he felt it was his fault. That cost him $40,000 in lost revenue. Luna: Ouch. But a funded startup might have just written it off as a cost of doing business. For him, that was basically a year's worth of profit at the time. Lucas: Exactly. And that's the thing about bootstrapping — you feel every mistake in your bank account. But it also makes you incredibly careful. After that, he added error-checking scripts, and he never trusted a formula without triple-checking it. That discipline carried over into the software version. Luna: So today, he's at $30 million in revenue. How many employees does he have now? Lucas: Twenty-two. That's about $1.4 million in revenue per employee, which is incredibly efficient. For context, a typical SaaS company with venture funding might have $200,000 to $400,000 per employee. He's running a lean machine because he never built a sales team — the product sells itself through word of mouth and organic search. Luna: And he's still the CEO? Does he have any outside investors now? Lucas: He owns 100 percent of the company. He's been approached by private equity firms and strategic acquirers — at least a dozen offers over the past five years. But he's not interested. He told me, 'I make more money than I can spend, I like my work, and I don't have to answer to anyone.' That's the ultimate bootstrapper's luxury. Luna: It's a good reminder that not every successful business needs to be a unicorn. A profitable, sustainable $30 million company is a huge achievement. Lucas: Absolutely. And if that kind of thinking has moved your own work forward in some small way, honestly, if today was worth a coffee to you, that's the link — buy me a coffee dot com slash fexingo. It's the smallest possible ask, and it keeps the show ad-free and independent. Luna: Yeah, we really appreciate every bit of support. It lets us keep digging into stories like this one without worrying about sponsors. Lucas: So back to the spreadsheet — one thing I find remarkable is that even now, the core database is still a spreadsheet. He migrated it to a proper database for performance, but the business logic and pricing are still defined in a Google Sheet that he updates manually. Every time he changes a price or a discount, he edits a cell. Luna: That seems risky for a $30 million business. What if someone accidentally deletes a row? Lucas: He has version history and backups, but yeah, it's a single point of failure. He acknowledges it's not ideal, but he says the speed of iteration is worth it. He can change pricing in 30 seconds and see the impact immediately. Building that into the software would take a development cycle of weeks. Luna: I guess when you're the only decision-maker, you can accept that kind of risk. But it also shows how far you can go with very simple tools if you're focused on solving a real problem. Lucas: Exactly. The lesson isn't that everyone should build their business on spreadsheets. It's that you don't need a complex tech stack or millions in funding to start. You need a clear problem, a willingness to do manual work, and the discipline to automate only when the manual process becomes painful enough. Luna: And the patience to wait two years for your first customer. Lucas: Right. That's the part that most people gloss over. He didn't just wait — he was actively talking to potential users, refining the spreadsheet, and building trust. When the first customer came, it was because that person had seen his work in a forum and reached out. The two years weren't idle. They were a grind. Luna: What's the biggest risk he sees now? Lucas: He's worried about competitors with deeper pockets coming in and building a flashier product. But so far, his customers stay because the product is dead simple and they trust him. He responds to support emails personally within an hour, even now. That's hard to replicate with a big team. Luna: So the personal touch scales if you never stop caring. That's a nice place to leave it. Lucas: Yeah. I think it's a good reminder that the best moat might just be being genuinely helpful.