Latest / The Indie Hacker Podcast with Fexingo: Solo Developers, SaaS Side Projects, and Independent Tech / How a Solo Dev Hit 10K MRR With a Product That Ships Every Week
Transcript
- Lucas: Alright, episode 100. I wanted to do something a little different today — not just another solo dev hitting ten thousand in monthly recurring revenue, but a story that actually ties back to why we keep doing this show. Luna: I was wondering if you'd acknowledge the milestone. So what's the angle? Lucas: A developer named Marcus runs a newsletter called 'Version One.' Every Friday for two years he's shipped a new feature or improvement to his SaaS product — a simple project management tool for freelancers. No Product Hunt launch, no ads, no referrals. Just the newsletter and the product. Luna: Two years of weekly shipping? That's over a hundred releases. How did he even get initial users? Lucas: He started the newsletter six months before he had a product. Wrote about building in public — his struggles, his decisions. By the time he launched the beta, he had about 800 subscribers. He let them in for free and told them: every Friday, you get a new version. The price would go up with each release. Luna: So early adopters got a deal, and latecomers paid more. That's essentially a reverse pre-order. Lucas: Exactly. The pricing started at five dollars a month for the first hundred subscribers. After the tenth release, it went to ten. After the twentieth, fifteen. Now it's at thirty dollars a month for new users, but the original hundred still pay five. Luna: That builds incredible loyalty. But also — how do you sustain a weekly release cadence solo? That's brutal. Lucas: Marcus is very disciplined. He keeps a public roadmap on a simple Trello board. Each week he picks one thing — a feature, a bug fix, a UI improvement. The rule is it has to be shippable by Friday. He says the constraint forces him to scope tiny. Some weeks it's just a button color change. Other weeks it's a whole new integration. Luna: And the newsletter is the marketing. He writes about what he shipped, why, and what's next. That's the entire funnel. Lucas: Right. He's not selling a product — he's selling a process. People subscribe to the newsletter to watch the product evolve. The SaaS is almost secondary. But the MRR hit ten thousand last month, with just over four hundred paying users. Luna: Four hundred users at an average of twenty-five bucks a month. That's a healthy base. But here's my question: does the weekly shipping ever become noise? Like, do users get tired of constant updates? Lucas: Marcus addressed that in his latest post. He said the key is that every update is optional — nothing breaks, nothing forces a change in workflow. He also surveys users every quarter. The last survey showed 92 percent of respondents said the weekly updates are a net positive. They like feeling the product is alive. Luna: That's a remarkable stat. Most SaaS products ship quarterly at best. He's shipping fifty times a year. Lucas: And that rhythm becomes a competitive moat. New entrants can't easily copy the pace because it's built into his audience's expectations. The newsletter subscribers are basically beta testers who pay for the privilege. Luna: I want to talk about the economics of this approach, but first — Lucas, we've done a hundred episodes of these stories. Do you think we've missed a pattern? Lucas: Maybe that the best indie hackers don't just build products — they build engines of attention. Marcus's engine is the newsletter and the weekly ship. Others use Twitter threads, or YouTube, or a podcast. But the common thread is that the product is almost a byproduct of the audience relationship. Luna: It reminds me of something we hear often: 'build an audience, then build a product.' But Marcus flipped it — he built the audience with the promise of a product that would keep getting better. Lucas: And that promise is what people pay for. They're not paying for a static tool — they're paying for a ticket on a journey. That's a different value proposition than most SaaS. Luna: It's also a lot more work. But for a solo dev, it might be sustainable because the work is incremental. You're never facing a massive rewrite. Lucas: Right. And the revenue grows incrementally too. Marcus's MRR chart is almost a straight line up — no big spikes, just steady climbs after each price increase and each new subscriber. Luna: This is actually a really concrete example of something we've talked about abstractly: compounding effort. Each newsletter builds on the last, each feature adds value, each price increase locks in more revenue. Lucas: And you know, this is exactly the kind of thing that listener support helps us keep exploring. A couple of dollars a month from people who find these stories useful genuinely makes a difference — it keeps the show ad-free and lets us dig into cases like Marcus's. If you've gotten something out of these episodes, you can find us at buy me a coffee dot com slash fexingo. Luna: Yeah, it's a small gesture that adds up. And we're grateful for every bit. So back to Marcus — what's his biggest risk now? Lucas: Burnout. He's been shipping every Friday for two years. He says he takes one week off per quarter, but that's it. The pressure to keep the streak going is real. If he misses a week, the newsletter feels empty, and the community notices. Luna: Has he considered automating parts of it? Lucas: He's started outsourcing some UI work to a part-time designer, but he still does all the coding himself. He told me he's thinking about moving to a bi-weekly ship cycle after he hits fifteen K MRR. He wants to get there first. Luna: That's a milestone-driven approach. I can see the logic — give yourself a concrete target before you change the formula. Lucas: Exactly. And fifteen K MRR at his current trajectory is maybe six months away. So the weekly ship has another twenty-six episodes left, if you will. Luna: I love that you called them episodes. Do you think we could learn something from Marcus for our own show? Lucas: I think we already have. We've been doing a hundred episodes at a consistent clip. That's a kind of weekly ship too. And like Marcus, we're building a relationship with an audience that cares about this niche. The content is the product. Luna: So for episode 200, should we have a public roadmap and a pricing tier? Lucas: Maybe we just keep shipping. But it's worth remembering that the value we offer — these concrete stories — is what keeps people listening. And if listeners find them useful, the coffee support helps us keep doing it. Luna: Alright, let's wrap with a forward look. What's the one thing you'd tell a solo dev starting today, based on Marcus's story? Lucas: Pick a cadence you can sustain, tie it to a communication channel, and make the product a living thing that your audience watches grow. The revenue follows the relationship. Luna: That's a good note for episode one hundred. Thanks, Lucas. Lucas: Thanks, Luna. And thanks to everyone who's been along for the ride. See you next week.