Latest / The Bootstrapped Tech Founder with Fexingo: Profitable Software Companies Without VC / How Bootstrapped Founders Use Founder-Led Sales Pre-Launch
Transcript
- Lucas: So there's this story that keeps rattling around my head, about a solo developer who built a niche project management tool for architecture firms, and he didn't write a line of code until he had twelve pre-orders in the bank. Not commitments, not 'sounds interesting' emails — actual invoices paid. Luna: Wait, he invoiced people before the product existed? How does that even work? Lucas: That's exactly what I want to dig into. It's a playbook that a lot of bootstrapped founders use but rarely talk about publicly — founder-led sales as a pre-launch strategy. And it's not about some slick demo or a landing page with a countdown timer. It's about picking up the phone, doing the uncomfortable outreach, and asking for money early. Luna: Okay, but most people would hear 'sell before you build' and think, 'sure, if you're a famous founder with a following.' This guy was nobody, right? Lucas: Right, complete nobody. No newsletter, no Twitter following, no prior startup. What he had was a very specific pain point he'd seen firsthand while working as a project architect. He knew the tools out there were overkill or misaligned. So he built a one-page mockup — not even a prototype — and started calling architecture firms that fit a very narrow profile. Luna: What was the profile? Small firms, big firms? Lucas: Firms with between ten and forty people, because that's the sweet spot where coordination breaks down but they're too small for enterprise software. He found these firms through public project directories, LinkedIn, and even old-school professional association membership lists. Luna: So what did the pitch sound like? 'Hey, I have an idea for software, want to give me money?' Lucas: It was more refined than that, but not by a ton. He framed it as a problem he'd lived himself. He'd say something like, 'When I was at my last firm, we lost two weeks on a project because the BIM data and the spec sheets weren't synced. I'm building a tool that fixes that, and I'm looking for a few design partners who get early access at a discount.' Luna: So he wasn't selling features, he was selling the problem. Lucas: Exactly. And he asked for a one-time pre-payment of five hundred dollars, which would be credited toward a year of the full product. That was the ask. He wasn't charging for a finished tool — he was charging to be part of the process. And around twelve percent of the people he called actually said yes. Luna: Twelve percent on cold calls is huge. What was the secret sauce? Lucas: I think part of it was the specificity. He wasn't trying to boil the ocean. He had a one-page mockup, a clear use case, and a deadline: 'We start development in two weeks, first cohort gets in at this price.' That scarcity wasn't manufactured — it was real, because he needed the money to quit his job and build it. Luna: So the pressure was actually financial. He needed those pre-orders to survive. Lucas: Right. And that urgency came through in the calls. He wasn't desperate, but he was honest: 'I'm doing this full-time, and I need a few committed partners to make it happen.' That's a very different energy from 'we're disrupting the construction industry.' Luna: Did he run into pushback? Like people saying, 'What am I paying for if the product doesn't even exist yet?' Lucas: All the time. He said the most common objection was, 'I've been burned by half-finished software before.' So he built in a safety net: full refund if they didn't like the first stable release, no questions asked. That took away the risk, and only one person actually asked for their money back. Luna: And the other eleven stuck around through the development process? Lucas: They did, and that's where it gets interesting. He set up a private Slack group with those eleven customers, and they became his de facto product team. They'd send screenshots, report bugs, suggest features. One customer even roped in a former colleague who ran a forty-person firm, and that became his first enterprise-size deal. Luna: So the pre-orders weren't just revenue — they were a built-in feedback loop. Lucas: Exactly. And this is the part I want to stress for anyone listening who thinks sales is a dirty word. For a bootstrapped founder, sales isn't something you do after you build a great product. It's how you figure out what 'great' even means. Those early calls were essentially structured interviews where every objection became a feature requirement. Luna: But how do you know which objections are real and which are just noise? I mean, every prospect has a pet peeve. Lucas: That's the art. He told me he kept a simple spreadsheet — every call, every objection, every question. Patterns started to emerge after the first twenty calls. 'Does it integrate with Revit?' came up five times, so he added that to the roadmap. 'Can we self-host?' came up once, from a guy who ended up not buying — so he ignored it. Luna: So the rule is, don't build for the people who don't pay. Lucas: Exactly. And that's the discipline. It's tempting to chase every feature request, but if only one person asks and they're not even a customer, that's not a market. Luna: I guess the big question is, how do you structure the actual pre-sale without feeling like you're taking advantage of people? Because some would say it's a bit sketchy. Lucas: It can be, if you're not transparent. But he was very clear about what they were getting: a significant discount off the eventual price, direct access to the founder, and a say in the roadmap. There was no deception. He even put a line in the invoice that said 'early access license — product in development, final features may vary.' Luna: That's a good example of managing expectations. Did he ever feel the pressure of having taken people's money before the product was ready? Lucas: He said it was the best motivation he ever had. Every time he was tempted to slack off, he remembered those eleven invoices. And it forced him to ship a usable version within six weeks, which is way faster than most solo developers would move without that external commitment. Luna: So the money wasn't just revenue — it was accountability. Lucas: Exactly. And that's a powerful dynamic. The customer is invested, so they're more forgiving, but they also hold you to a standard because they've put their reputation on the line by betting on you. Luna: It's like the customer becomes a co-founder in their own way. Lucas: In a very real sense, yeah. And that's why this model can be such a strong alternative to waiting for perfect product-market fit before ever talking to a buyer. Luna: You know, Lucas, this whole conversation is a good reminder of why we do this show. We get to talk to founders who have figured out practical, often counterintuitive ways to build a business — and we get to share that with people who are doing the same thing in their own corners. Lucas: And that's the only reason this podcast exists, honestly. If you're one of those builders or operators who finds this kind of conversation useful, there's a small way to keep the lights on: if today's episode was worth a coffee to you, that's the link — buy me a coffee dot com slash fexingo. That's it. No tier, no perks, just the simple act of saying 'this should exist.' Luna: And it genuinely helps. We're an independent show, no corporate sugar daddy, so every little bit goes toward keeping the feed ad-free. Okay, back to the pre-launch sales. Lucas: Right, so we've talked about the initial calls and the pre-orders. But there's a second phase that I think is even more telling — what happened after he launched. Luna: Did he keep using that founder-led approach? Lucas: He did, but it evolved. Once he had a product and a dozen case studies, he could switch from 'I'm validating an idea' to 'here's how we saved this specific firm two weeks on a project.' That's when he could start raising prices. The first cohort paid five hundred; the next group paid seven fifty, then a thousand. Luna: So the early customers basically subsidized his learning curve. Lucas: In a way, yes. They took a risk on him, and he rewarded them with a lifetime discount. But for everyone after, the price reflected the proven value. Luna: What about the people who said no at the start? Did he ever go back to them? Lucas: He did, about seven months later. A few of them had already found a different solution, but two of them signed up at the full price because they had seen the firm down the street using it. So the 'no' wasn't permanent — it was just a 'not yet.' Lucas: And that's a key lesson for founders who get discouraged by early rejection. The people who say no today might become your best customers tomorrow — if you keep the door open and have something worth coming back to. Luna: So what's the takeaway for our listeners? If they're thinking about trying this pre-sales approach, what's the first step? Lucas: The first step is to write down the one problem your software solves, and who specifically has that problem — not 'small businesses' but 'landscaping companies with ten to twenty trucks that need to schedule crews across multiple jobs.' Then find ten of those people and have a conversation. Not a pitch, a conversation about their workflow. Luna: And then what? When do you actually ask for money? Lucas: You ask when you've heard the same problem three times without prompting. That's the signal that it's not just your intuition. Then you can say, 'I'm working on a fix for that, and I'm offering a founder's price for the first handful of customers.' If nobody bites, you've saved yourself months of building into the void. Luna: I love that this whole approach is so lean. No big launch, no ads — just a bunch of honest conversations and a product that actually fits. Lucas: And that's the bootstrapped way. Every dollar you raise from customers is a vote of confidence, and every 'no' is a free market research call. It's not glamorous, but it's real. Luna: So the next time someone tells you 'just launch and see what happens,' maybe you're better off picking up the phone first. Lucas: Exactly. The product will be better for it, and so will your bank account.