Latest / The Founder's Journey with Fexingo: First-Time Entrepreneurs, Failures, and Lessons Learned / How a Founder Used a Single Page to Land 3000 Waitlist Signups
Transcript
- Lucas: Before you write a single line of code, before you build a prototype, before you even name your product — what if you could prove people would pay for it with just one web page and a few dozen emails? Luna: That sounds almost too good to be true. But I know exactly what you're getting at — the classic landing page as mvp move. Lucas: Exactly. And today I want to look at a specific case. A first-time founder named Sarah Chen. She had an idea for a B2B SaaS tool that helps remote teams manage async standups. Nothing revolutionary, but she was stuck in analysis paralysis — building features, tweaking the UI, all before anyone had even seen it. Luna: Classic trap. I've done it myself. Lucas: So she forced herself to stop. She spent exactly one hundred twenty-seven dollars — that's the number she tracked — on a Carrd page and a domain. The page had three things: a headline describing the problem, a screenshot of a very rough mockup, and an email signup form with the words 'Join the waitlist.' Luna: No pricing, no demo video, no case studies? Lucas: Nothing. Just the promise that if enough people signed up, she'd build it. Then she went to a Slack community for remote team leads — about fifteen thousand members — and posted a short message: 'I'm building a tool to fix async standups. Would anyone use this? Drop your email and I'll keep you posted.' Luna: And how did people respond? Lucas: Within seventy-two hours, she had over three thousand signups. Three thousand people gave her their email addresses based on a one-paragraph pitch and a sketch. She had never talked to most of them before. She had zero audience. Luna: Wait — three thousand from a single Slack post? That's not just a good response, that's viral. Lucas: It was shared within the community. A few team leads posted it in other channels. But here's the thing — she didn't just get lucky. She targeted a very specific pain point in a community that already felt that pain. Remote team leads hate standup meetings that drag on, and async updates are a known alternative. She basically said 'I'll solve this for you' and they raised their hands. Luna: So the validation wasn't really about the product — it was about the problem. She confirmed the problem existed before she confirmed the solution. Lucas: Exactly. And that's the key insight. Most founders try to validate their solution — 'Will people buy my app?' — when they should validate the problem first: 'Is this pain real and widespread enough?' Sarah's approach answers that second question for basically zero cost. Luna: But three thousand signups — is that a high bar? I mean, some founders try this and get thirty emails. What made her different? Lucas: Great question. I think it comes down to three things. First, she picked a community that was already talking about the problem. She didn't cold-email random people. She went where the conversation was happening. Second, her pitch was almost aggressively simple. No features, no roadmap, no 'we're disrupting the industry.' Just 'I see this problem, I'm building a fix, want in?' Luna: That low-pressure framing probably helped. It's not a sales pitch, it's an invitation. Lucas: Right. And third, she followed up. Within a week, she sent a personal email to every single signup — not a blast, but a segmented list based on what role they mentioned in the Slack thread. She asked each person one question: 'What's the biggest frustration with your current standup process?' That gave her dozens of detailed replies that later shaped her product. Luna: So she turned a waitlist into a customer discovery engine. That's smart. Lucas: And it's something any founder can do. The total cost was a hundred twenty-seven dollars and about ten hours of work. Compare that to spending six months building a full MVP, only to launch and hear crickets. Luna: You know, it reminds me of something — a couple of dollars a month is genuinely what keeps these shows going. If you've gotten something out of these conversations, buy me a coffee dot com slash fexingo helps us keep them ad-free and focused on practical stories like this one. Lucas: Yeah, it's a small thing that makes a real difference. We don't run ads, so listener support is what keeps the lights on. Anyway — back to Sarah. She eventually built the product, of course, and those three thousand signups converted to about four hundred paying users in the first month. Luna: Four hundred from three thousand — that's about thirteen percent. That's actually a solid conversion rate for a pre-launch waitlist. Lucas: It is. And it gave her enough revenue to quit her job and work on it full-time. But I want to dig into a potential counterargument here. Some people say this method only works for certain types of products — B2B tools with clear, existing pain points. Would a consumer product or a luxury good get the same response? Luna: That's a fair point. If Sarah had been building a meditation app or a new kind of sneaker, a Slack post and a landing page might not cut it. Consumer products often need visual appeal, brand trust, social proof. Lucas: Right. And even within B2B, some problems are more urgent than others. Her tool solved a daily annoyance that team leads were already actively seeking solutions for. If the pain is more diffuse or seasonal, the same approach might fall flat. Luna: So the lesson isn't 'build a landing page and wait for the magic' — it's 'find a community that's already frustrated, and offer them a way to signal that frustration.' Lucas: Exactly. And the landing page is just a tool to capture that signal. The real work is identifying where your target users are already complaining, and positioning yourself as the person who's going to fix it. Luna: I've also seen founders mess this up by making the page too polished. When it looks like a real product, people get suspicious. They think 'this is a scam' or 'they're going to spam me.' Sarah's rough mockup actually helped — it signaled that she was a real person, early stage, and honest. Lucas: That's a great point. There's an authenticity to the rough sketch that a high-fidelity prototype doesn't have. It says 'I'm in the trenches with you, not a corporation trying to sell you something.' Luna: So if someone listening wants to try this next week, what's the one thing they should do first? Lucas: Don't build anything yet. Spend a few hours just listening. Go to three online communities — Slack groups, Reddit, LinkedIn groups — where your target users hang out. Read what they're frustrated about. If you see the same complaint five times, that's your opening. Then write a one-paragraph description of how you'd solve it, and ask them to join a waitlist. That's it. Luna: And if nobody signs up? Lucas: Then you've saved yourself months of building something nobody wants. That's not a failure — that's the cheapest market research you'll ever do. Luna: I love that framing. It takes the ego out of it. Lucas: Sarah's story is a great example, but it's also replicable. She didn't have a special network or a famous background. She was just willing to take the smallest possible step before committing to the big one. Luna: And that's really the core of the lean startup philosophy, right? Test your riskiest assumption first. For Sarah, the riskiest assumption was that anyone cared about async standups. She tested that for a hundred twenty-seven dollars. Lucas: Exactly. And once she had the signal, she could build with confidence. I think that's a lesson every first-time founder should internalize: the cost of asking is almost always lower than the cost of assuming. Luna: Alright, so for our listeners who want to try this — go find your community, write your one paragraph, and see what happens. And if you get stuck, you know where to find us. Lucas: Next time, we'll look at what happened after Sarah launched — the early churn, the feature requests that nearly derailed her, and how she handled the pressure of four hundred paying users expecting updates. That's a whole different kind of founder challenge. Luna: Looking forward to it.