Latest / The Indie Hacker Podcast with Fexingo: Solo Developers, SaaS Side Projects, and Independent Tech / How a Solo Dev Built a SaaS by Solving His Own Problem
Transcript
- Lucas: So there's this solo developer named Marcus Chen. Last year, he was freelancing as a full-stack contractor, hopping between three different project management tools depending on the client. Trello for one, Asana for another, Monday.com for a third. Luna: I've been there. The tool-switching tax is real. Lucas: Exactly. And Marcus realised something: none of these tools were built for someone like him. They're all designed for teams of ten or more, with layers of permissions, boards, timelines, dependencies. He needed something dead simple — a single list of tasks, with basic due dates, and nothing else. Luna: So he built it himself. Lucas: He did. Over a long weekend, he threw together a bare-bones web app using Python on the backend and React on the front end. Hosted it on a $5 DigitalOcean droplet. Called it 'Tally' — because it's just a list you tally through. Luna: What happened next? Lucas: He showed it to a few fellow freelancers in a Discord server. Within a week, twelve people asked if they could use it. He hadn't even built a payment system yet. So he added Stripe, set the price at $75 a month, and figured maybe he'd get twenty users total. Luna: Seventy-five dollars a month for a single-list to-do app? That's bold. Lucas: Right? But here's the thing — his customers weren't price-sensitive. They were paying three or four times that for tools they hated. Seventy-five dollars felt like a bargain for something that actually fit their workflow. Luna: So how did he grow from those twelve Discord users to, what, 200 paying customers? Lucas: He didn't spend a dollar on ads. What he did instead was write a single blog post titled 'I built a project management tool for people who hate project management tools.' It went mildly viral on Hacker News. That drove about 80 percent of his initial signups. Luna: And the rest? Lucas: Word of mouth. He also did something unusual — he made the entire product transparent. There's a public changelog, a public roadmap, even a public revenue dashboard. Customers felt like they were part of the process. Luna: That's smart. It builds trust without a marketing budget. Lucas: Exactly. And it's become his moat. He now has 200 customers paying $75 a month — that's $15,000 in monthly recurring revenue. He works on the product about fifteen hours a week, mostly on weekends. The rest of the time he's still freelancing. Luna: Fifteen hours a week? That's almost passive income. Lucas: Almost. He still does all the customer support himself. But because the product is so simple, support requests are rare. Most weeks he gets fewer than ten emails. Luna: I love that his own problem was the market research. He didn't do surveys, didn't run landing page tests. Just built what he needed. Lucas: That's the indie hacker dream, right? Scratch your own itch. But it only works if your itch is shared by enough people willing to pay. Luna: And Marcus happened to hit that sweet spot. What's the biggest challenge he faces now? Lucas: Deciding whether to stay small or grow. He gets approached by VCs maybe once a month. One firm offered a million-dollar seed round. He turned it down. He says he'd rather have 500 happy customers than 5,000 angry ones. Luna: That's a refreshing take in a world obsessed with hypergrowth. Lucas: It is. And honestly, the numbers work for him. Fifteen thousand a month with minimal costs — almost all of that is profit. He's building wealth on his own terms. Luna: If today's conversation gave you something useful — maybe you're thinking of building your own tool or just appreciate hearing a real indie hacker story — the way this show stays ad-free is through listener support. You can find us at buy me a coffee dot com slash fexingo. Lucas: Yeah, no ads, no sponsors. Just the conversation. And if this episode helped, that link is the way to keep it going. Luna: Alright, back to Marcus. One thing I find interesting is that he used Python and React — pretty standard stack. But he told me he deliberately avoided any fancy architecture. No microservices, no Kubernetes, no CI/CD pipeline. Just a simple monolith. Lucas: That's actually a lesson a lot of solo devs miss. You don't need Netflix-grade infrastructure for a 200-customer app. A $5 server works fine until it doesn't. And by then, you'll have the revenue to scale up. Luna: Right. Premature optimization is the enemy of shipping. Lucas: Exactly. Marcus also shared something else: his pricing strategy wasn't arbitrary. He looked at what his target customer was already spending on project management tools — typically $50 to $100 a month — and priced Tally right in the middle. He says if he priced it at $9, it would have felt like a toy. Luna: That's a great point. Price signals quality. Lucas: He also offers a free tier — a single list with up to ten tasks. That's enough to get a feel for the product, but if you're using it seriously, you hit the limit fast. Conversion rate from free to paid is about 40 percent. Luna: That's incredibly high. Most SaaS products see single-digit conversion. Lucas: It's because the free tier is genuinely useful but deliberately capped. Users get hooked on the simplicity, then they need more lists, more tasks, and they upgrade willingly. No dark patterns, no nag screens. Luna: So what's next for Marcus? Does he have any big features planned? Lucas: He's cautious about adding features. Every new feature is a potential complexity spiral. The only major request he's considering is a shared list for two people — for freelancers who collaborate occasionally. But he's adamant it won't become a team tool. Luna: Interesting. So he's protecting his niche. Lucas: Exactly. He knows his product is for individuals who hate bloat. If he starts adding team features, he'll compete with the very tools his customers fled from. He'd rather lose potential customers than lose his core identity. Luna: That takes a lot of discipline. Most founders chase every feature request. Lucas: It does. But Marcus has a simple filter: 'Does this feature help me get my own work done?' If the answer is no, he doesn't build it. That's the ultimate scratch your own itch approach. Luna: I think that's the key takeaway for any indie hacker listening. Build for yourself first. The market might just follow. Lucas: And if 200 people are willing to pay $75 a month for a tool that took a weekend to build, that's a pretty strong signal. Luna: Absolutely. Marcus Chen and Tally — proof that sometimes the simplest idea is the most powerful. Lucas: And that you don't need a team, a VC, or a marketing budget. Just a problem that won't leave you alone, and the willingness to solve it.