Latest / The Indie Hacker Podcast with Fexingo: Solo Developers, SaaS Side Projects, and Independent Tech / How a Solo Dev Used a Launch Week to Hit 10K MRR
Transcript
- Lucas: There's this idea in indie hacker circles that you should launch fast and iterate, but a lot of people misinterpret 'fast' as 'quietly' — they push a product live on Product Hunt, send a tweet, and then wonder why revenue trickles in over months. Luna: Right, the 'slow drip' approach. But I've seen some devs do the opposite — they concentrate everything into one week and hit five figures in MRR right out of the gate. Lucas: That's exactly what we're talking about today. Episode 63 — the launch week playbook. I came across a solo developer named Alex who built a tool for freelancers to automate their invoicing and expense tracking. Nothing revolutionary on the surface. But his launch strategy was anything but ordinary. Luna: What did he do differently? Most invoicing tools are a saturated space. Lucas: He spent three months building a waitlist before he had a finished product. Not a landing page with a 'coming soon' — he built a bare-bones prototype, showed it to freelancers in Facebook groups, and got 1,200 email addresses. Then he did something specific: he announced that the product would launch on the first day of a major freelance conference — FreelanceCon — and that the first 500 people to sign up during launch week would get lifetime access at $29 per month instead of the planned $49. Luna: So he created scarcity and a clear deadline. That's textbook — but did it work? Lucas: It worked better than textbook. On launch day, he sent an email to the waitlist at 9 AM Eastern — time zone aligned with the conference's keynote — and by midnight he had 410 paid sign-ups. That's about 35 percent conversion from waitlist to paying customer in a single day. By the end of the week, he was at 590 subscribers, which at $29 per month is roughly $17,100 monthly recurring revenue. Luna: Seventeen thousand MRR in a week — that's remarkable. But 35 percent conversion from a warm list is way above average. What was his secret sauce? Lucas: I think a few things. First, the waitlist wasn't just emails — he'd been sending a weekly newsletter with tips about freelancer finances. So by launch day, those 1,200 people already trusted him. Second, the lifetime discount at $29 was genuinely a good deal — the product was solid, and he showed detailed feature comparisons on the pricing page. But the third factor is the one I find most interesting: he timed the launch to a moment when his target audience was already thinking about upgrading their business tools. Luna: The conference. So he piggybacked on an existing event's momentum rather than trying to manufacture his own. Lucas: Exactly. FreelanceCon had maybe 10,000 attendees that year. Alex wasn't a speaker, but he posted in the conference's Slack community and had a few attendees tweet about his tool during a session on 'financial hygiene for freelancers.' The conference organisers even linked to his product in their resource roundup email on day two. That endorsement from a trusted third party — the conference — was essentially free marketing to a highly targeted audience. Luna: So he didn't just launch a product; he launched into an existing conversation. That's a smart way to overcome the cold-start problem. Lucas: Right. And the concentrated launch window created a feedback loop. Because 350 people signed up on day one, the Slack community and Twitter were buzzing about it — 'did you see the new invoicing tool?' — which drove more sign-ups on day two and three. By Friday, he had enough users that he could send a 'week one update' email showcasing testimonials and usage stats, which converted another batch of late deciders. Luna: That's the network effect of a launch week. But I wonder — what happened after the week ended? Did the momentum sustain? Lucas: This is the part that doesn't make the Twitter threads. After launch week, new sign-ups dropped to about 10 per day — nothing like the spike. But here's the thing: Alex had 590 paying customers within seven days. That's a base that most solo devs take a year to build. He spent the next month improving the product based on feedback from those early users, and churn in the first 90 days was only 6 percent — very low for a new SaaS. So the launch week bought him time and breathing room. Luna: Low churn suggests he priced it right and delivered value. But 17K MRR from launch week also means he had to handle 590 new customers all at once. That's a support nightmare for a solo dev. Lucas: It was. He admitted in a blog post that he slept maybe four hours a night for the first three days. He had automated onboarding emails and a knowledge base ready, but he still answered over 200 support tickets personally that week. He also used a simple chatbot to handle basic questions like 'how do I connect my bank account?' — that deflected maybe 30 percent of queries. But the key point is he planned for the deluge. He didn't expect launch week to be quiet. Luna: So he front-loaded the work. Built the waitlist, the automated sequences, the knowledge base, the chatbot — all before he sent that first email. That's what separates a launch week from a launch day. Lucas: Exactly. A lot of developers treat launch as 'push the code and pray.' Alex treated it as a product in itself — the launch was engineered. He even A/B tested his launch email subject line two weeks before. The winner, by the way, was 'Your invoicing is about to get easier' — outperformed 'New tool for freelancers' by 40 percent open rate. Luna: That's a great detail. So if someone listening wants to replicate this, what are the concrete steps they should take? Lucas: I'd say three things. One: start building a waitlist at least 90 days before launch, and don't just collect emails — send useful content that builds trust. Two: find an existing event or community where your target audience is already gathered, and time your launch to coincide. Three: create a genuine scarcity mechanism — not fake urgency, but a real limited-time offer that rewards early adopters. In Alex's case, the lifetime discount at $29 was a real sacrifice on his part, but it drove the conversion. Luna: I'd add a fourth: prepare for success. Have your support system, your FAQ, your automated emails ready before you hit send. Lucas: Absolutely. And one more thing — Alex kept pricing simple. No tiers, no annual vs monthly confusion. Just one plan at $29 per month for launch week, then $49 after. That clarity probably helped conversion too. Luna: It also meant he could focus on building rather than configuring Stripe. Speaking of building — I know this is a technology show, but I think it's worth mentioning that listener support is what keeps these deep-dive episodes ad-free and independent. If today's conversation gave you something you can use — maybe a tactic for your own launch — a couple of dollars a month genuinely helps keep the lights on. It's buy me a coffee dot com slash fexingo, and it makes a real difference for a small show like this. Lucas: Yeah, absolutely. Every bit helps us keep bringing these specific, actionable case studies. So thanks to anyone who chips in. Luna: Alright, back to Alex. You mentioned after launch week he focused on improving the product. Did he ever release a post-mortem with numbers? Lucas: He did — a detailed one on his blog. He shared that his total cost for the launch was about $2,000: $500 for the conference Slack membership and some small ads in niche newsletters, $1,200 for his time building the waitlist and automation, and $300 for the chatbot subscription. So he essentially spent $2,000 to acquire 590 customers, which is a customer acquisition cost of about $3.40. That's absurdly low for SaaS. Luna: $3.40 per customer — and at $29 per month, he recouped that in about four days. That's a fantastic unit economics story. Lucas: Exactly. And eighteen months later, he's still solo, MRR is around $45,000, and he's hired a part-time support person. He attributes most of his early traction to that launch week. Without it, he says he would have grinded for two years to get the same revenue. Luna: So the launch week compressed the growth timeline. That's the real takeaway — not just the revenue number, but the time saved. Lucas: Right. And that's why I wanted to cover this angle. There are plenty of 'how I got my first 100 customers' stories, but the launch week strategy is less discussed. It's higher risk, higher reward — but if you prepare properly, it can be a rocket ship. Luna: I think the key is that it forces you to do the hard work upfront. Most people want to launch fast and figure it out later. Alex launched fast but he also prepared fast. Lucas: Yeah, that's a good way to put it. The preparation phase is non-negotiable. If you're going to do a launch week, you need to have the product stable, the support ready, the pricing set. You can't iterate on launch day. Luna: Do you think the launch week model works for B2B SaaS that's more complex than an invoicing tool? Lucas: It depends on the sales cycle. If you're selling to enterprise with a long evaluation process, a launch week probably won't convert. But for self-serve, low-ticket SaaS — under $50 per month — it absolutely works. The key is that the buyer can make the decision alone. Alex's freelancers could pull out a credit card and sign up. No procurement, no manager approval. Luna: That's a good point. The launch week is really for products where the user is also the buyer. Lucas: And where the audience already has a pain point. Alex's audience — freelancers — they all hate invoicing. So the product solved an obvious problem. If you're building something that creates a new category, a launch week is much harder because you have to educate first. Luna: So the advice is: pick a known pain point, build a waitlist, find a conference, and go all-in for seven days. Lucas: That's the playbook. And if you do it right, you might just skip the first year of grind.