Latest / The Bootstrapped Tech Founder with Fexingo: Profitable Software Companies Without VC / How Bootstrapped Founders Use Financial Modeling Without a Finance Background
Transcript
- Lucas: So there's this assumption floating around bootstrapped circles that financial models are for fundraisers—something you build when you're pitching VCs, not when you're running a profitable little SaaS business on your own terms. Luna: Right, and I think a lot of founders hear 'model' and imagine complex Excel workbooks with macros and sensitivity tables. Lucas: Exactly. But the most useful financial model I've seen recently from a bootstrapped company came from a founder who explicitly said, 'I have zero finance background, I barely know what a P&L is.' And he built a one-page spreadsheet that drove his pricing overhaul and saved him roughly forty thousand dollars a year. Luna: Forty thousand dollars? From a one-page model? I want the details. Lucas: The company is called Planify—it's a project planning tool for small creative agencies. About two point four million in annual recurring revenue, entirely bootstrapped. Founder's name is Marcus Chen. He started it as a side project in 2019, and for the first three years he priced purely by gut feel. Flat monthly fee, one plan, one price. Luna: And gut feel was working well enough to get to two point four million ARR, so when did he realize he needed a model? Lucas: He told me that his churn rate started creeping up in early 2024, and he couldn't figure out why. Customers were leaving, but satisfaction scores were high. So he sat down and built a model to understand the unit economics of a single customer. Luna: And what did the model look like? Did he use any fancy software? Lucas: Just Google Sheets. Three tabs. First tab: revenue drivers—number of new customers per month, average revenue per user, expansion revenue from upgrades. Second tab: expense burn—his fixed costs, variable costs like customer support and hosting, and his own salary. Third tab: cash flow timing—when money actually hits the bank versus when bills are due. Luna: So the classic three-tab structure. But what did he learn that saved him forty thousand? Lucas: He discovered that his largest customers—the ones paying the flat monthly fee of one hundred ninety-nine dollars—were actually unprofitable. They used so much customer support and consumed so much storage that his gross margin on those accounts was negative. Meanwhile, his mid-tier customers at ninety-nine dollars a month were his most profitable segment. Luna: Wait, the higher-paying customers were losing him money? That's a classic pricing problem. Lucas: Exactly. He was essentially subsidizing power users with the revenue from his core customers. So he introduced a usage-based component for storage and support hours above a certain threshold. That change alone added about forty thousand dollars to his bottom line in the first year. Luna: And he never would have caught that without the model. Lucas: Right. And this is the thing—bootstrapped founders often avoid financial modeling because they think it's complicated, or they think they don't have enough data. But Marcus started with just three months of historical data and a few assumptions. He updated the model monthly, and within six months he had enough data to make confident pricing decisions. Luna: It's also a way to test scenarios without risking real money. Like, 'what happens if I raise prices by twenty percent and lose ten percent of customers?' Lucas: That's exactly how Marcus used it. He ran a scenario where he increased the base plan from ninety-nine to one hundred nineteen dollars. The model showed that even with a twelve percent drop in new sign-ups, his overall revenue would still increase by about eight percent. He made the change, and the actual results were within two percent of the model's prediction. Luna: Two percent accuracy from a three-tab Google Sheet? That's impressive. But I'm wondering—if this is so powerful, why aren't more bootstrapped founders doing it? Is it fear of numbers? Lucas: Partly. But also, I think there's a cultural thing. Bootstrapped founders pride themselves on being lean and action-oriented. Modeling feels like planning, and planning feels like something corporates do. But Marcus told me that building the model actually saved him time because he stopped making gut-feel decisions that led to costly mistakes. Luna: And I've noticed that when you model something, you also model your own assumptions. You have to write down what you believe about your business. That alone can reveal blind spots. Lucas: Absolutely. One thing Marcus included in his model that I thought was clever: a 'bad assumptions' tab. He listed every assumption he was making—like customer lifetime, churn rate, support cost per ticket—and flagged the ones he had the least confidence in. That forced him to prioritize which data to collect next. Luna: That's a great habit. And it ties into something we've talked about before—bootstrapped founders don't need perfect data, they need directional data that helps them make better decisions. Lucas: Right. The model doesn't have to be right; it has to be useful. Marcus's first version had a placeholder for customer acquisition cost that he just guessed at—he put in two hundred dollars based on a gut feel. Six months later, he had actual data showing it was closer to three hundred fifty. But even that rough model was good enough to catch the pricing issue. Luna: It's interesting that you mention gut feel versus data. Because I think a lot of solo founders rely on gut feel precisely because they don't have a finance person. But a simple model can actually augment that intuition. Lucas: And if today's conversation is useful for what you're building or running, it's worth mentioning that the way we keep these episodes ad-free and focused on practical operator knowledge is listener support. If you found value in hearing how Marcus's model saved him real dollars, you can support the show at buy me a coffee dot com slash fexingo. Luna: Yeah, it's a small way to keep the conversations going without sponsorships or ads. And we really appreciate it. Lucas: So back to models. Another bootstrapped founder I spoke with—Sarah at a niche HR compliance SaaS—uses a similar approach but with a twist. She built her model around cash flow timing because she operates in a market where clients pay net sixty. Luna: Net sixty is brutal for a bootstrapped company. You need to forecast when the money actually arrives. Lucas: Exactly. Sarah's model includes a timing buffer. She runs a 'cash runway scenario' that assumes a thirty percent delay in payments. That forced her to maintain a larger cash reserve than she would have otherwise, and it saved her when two large clients paid three weeks late last quarter. Luna: So the model isn't just about profit; it's about survival. For bootstrapped companies, cash flow is everything. Lucas: Right. And Sarah's model is even simpler than Marcus's. Two tabs: one for cash inflows based on signed contracts with payment terms, and one for all outflows including her own draw. She updates it every Friday afternoon. Takes her about fifteen minutes. Luna: Fifteen minutes a week to avoid a cash crisis? That seems like a no-brainer. Lucas: It is. But again, the barrier is often psychological. People think modeling is a big undertaking. Marcus and Sarah both started small. Marcus's original model was literally a single sheet with ten rows. He added complexity only when he needed it. Luna: I think that's the key takeaway: start with a skeleton. What's the minimum viable model for a bootstrapped founder who's never done this before? Lucas: I'd say five rows. Row one: monthly recurring revenue. Row two: new customers. Row three: average revenue per customer. Row four: fixed costs. Row five: cash in the bank. Project that out twelve months. That's it. You'll immediately see if your current trajectory is sustainable. Luna: And if it's not, you have time to adjust before you hit the wall. Lucas: Exactly. Marcus told me that before he built his model, he was operating in a fog. He knew the business was growing, but he didn't know which customers were profitable or whether his pricing was leaving money on the table. After the model, he could answer both questions in thirty seconds. Luna: And that's the kind of clarity that lets a bootstrapped founder sleep better at night. Lucas: For sure. So if you're a bootstrapped founder who's been avoiding financial modeling, start with a five-row spreadsheet in Google Sheets. Pick one key metric to track—revenue per customer, churn rate, or cash runway—and build from there. You don't need an MBA, just a willingness to write down what you think is happening and then compare it to what actually happens. Luna: And if you want to see how Marcus's model evolved over time, we'll link to a template he shared on his blog. It's a great starting point. Lucas: Next episode, we're going to look at how bootstrapped founders handle hiring their first employee—specifically, the financial model for making that leap without blowing up your runway. Until then, keep building.