Latest / The Indie Hacker Podcast with Fexingo: Solo Developers, SaaS Side Projects, and Independent Tech / How a Solo Dev Built a SaaS for a Single YouTube Channel
Transcript
- Lucas: So there's a solo developer I've been following named Ryan. He built a SaaS product that does exactly one thing: it tracks real-time merch inventory for a single YouTube channel with about five million subscribers. That's it. One client. And it's making twelve thousand dollars a month in MRR. Luna: Wait — one client? As in, he built a whole product for one customer? Lucas: Exactly one. The YouTuber in question has a massive merch operation — hoodies, hats, limited drops, all that. But they kept running into the problem of overselling: they'd announce a drop, fans would rush to buy, and then the backend would show items out of stock that still had orders coming in. Ryan offered to build a real-time sync tool that connected the YouTube live chat to their Shopify backend, showing exact inventory counts on screen during streams. Luna: That's actually brilliant — it solves a very specific pain point. But isn't it risky to have all your revenue tied to one client? Lucas: Huge risk, and we'll get to that. But first, think about the economics here. Ryan's pricing is a flat twelve hundred dollars a month retainer, plus a two percent revenue share on every piece of merch sold through his integration. The YouTuber does about six hundred thousand dollars a year in merch sales. So Ryan's take is about fourteen thousand a month from the rev share alone, plus the retainer. Total around fifteen K a month gross. He's running this on a single VPS and a few API calls — his hosting costs are maybe fifty bucks a month. Luna: So margins are absurdly high. But the real question: can he ever scale this to more clients? Lucas: And that's exactly where the conversation gets interesting. Ryan actually tried to generalize the product — he built a dashboard that any creator could plug into. But he quickly realized that each creator's setup is different: different e-commerce platforms, different streaming tools, different inventory logic. The first client took him three months to custom-build. The second would take another two months. At that point, he'd be trading custom work for recurring revenue — which is basically consulting dressed up as SaaS. Luna: So he's leaning into the hyper-niche. One client, deep integration, maximum value. It's almost like a co-founder relationship. Lucas: Right. And if today's tech conversation gave you something usable — maybe you're thinking about a niche of your own — listener support is what keeps this show independent and ad-free. If you find value here, you can buy me a coffee at buy me a coffee dot com slash fexingo. No pressure, genuinely. Just a way to keep the episodes coming. Luna: Yeah, it's a small gesture that goes a long way. And we appreciate everyone who's already done it. Lucas: So back to Ryan. The interesting thing is, he didn't start with the intention of building a SaaS. He was a fan of the YouTuber, saw the merch problem in the live chat, and just built a simple script for himself to track inventory. He tweeted a screenshot of it, the YouTuber saw it, and reached out. That's how the whole thing started. Luna: So it was almost accidental. He wasn't trying to start a business — he was scratching his own itch as a fan. Lucas: Exactly. And that's a pattern you see a lot in indie hacking. The best products often come from someone solving their own problem, then realizing others have the same problem. But here, the 'other' was just one person with a massive audience. Ryan's tech stack is worth noting too: he used no-code tools for the front end — it's a Retool app — and a simple Node.js backend that polls the YouTube API and the Shopify API every few seconds. No database, just in-memory state. He's running it on a single DigitalOcean droplet. Luna: So the whole thing costs maybe a hundred bucks a month to run, and he's pulling in fifteen grand. That's the dream, right? Lucas: It is, until you consider the nightmare scenario. If that YouTuber decides to switch platforms, or fires Ryan, or just stops making merch — his revenue goes to zero overnight. There's zero diversification. And that's the trade-off with hyper-niche: you get incredible economics per customer, but you're one relationship away from bankruptcy. Luna: So how does he mitigate that? Does he have a plan? Lucas: He's building a generalized version in the background — a productized version that works with any creator who uses Shopify and YouTube. He's been slowly abstracting the custom logic into configurable modules. But he's careful not to spend too much time on it because his paying client is demanding feature requests. It's a classic innovator's dilemma at the micro scale. Luna: I can see why he's cautious. The existing client is paying the bills. If he neglects them to build a general product, he might lose the bird in hand. Lucas: Right. And there's another angle here: the rev share model. Most SaaS businesses charge a flat monthly fee or per-seat pricing. Ryan's model aligns his incentives directly with the YouTuber's success. If merch sales go up, both win. That's a powerful dynamic for a small developer — it makes the client see you as a partner, not a vendor. Luna: Have you seen other indie hackers using similar rev share models? I feel like it's rare. Lucas: It's becoming more common in the creator economy. There are tools for newsletter writers that take a percentage of subscription revenue, or for course creators that take a cut of sales. But for a B2B SaaS serving a single business, it's unusual. Ryan told me he actually proposed the rev share himself — he wanted to keep the retainer low to make it a no-brainer for the YouTuber, and bet on the upside. Luna: That's smart sales psychology. Low monthly commitment, high potential upside for both sides. Lucas: And it worked. The YouTuber didn't even negotiate. They signed a one-year contract. Ryan's been running it for eight months now, and the relationship is strong. He messages the YouTuber's merch manager daily. He's basically embedded in their operations. Luna: So what's the biggest lesson for other indie hackers listening? Is it 'build for one person'? Lucas: I think the lesson is more nuanced. It's not just 'build for one person' — it's 'find one person with a painful, specific, high-value problem and solve it so well that they pay you a lot.' Then, if you want to scale, you can productize what you learned from that one relationship. Ryan's approach is essentially a consulting to product pivot, but he's doing it in slow motion. Luna: But not everyone can land a client with five million subscribers. How does a solo dev without an existing audience find that first customer? Lucas: Ryan's advice was simple: go to where the problems are visible. He found the problem in a YouTube live chat. You can find them in subreddits, in Discord servers, in Twitter threads. Look for people complaining about the same thing repeatedly. Then offer to build a solution for free or cheap, just to get your foot in the door. Once you deliver, you have a case study and a reference. Luna: So it's basically the classic 'door to door' sales of software, but done in public. Lucas: Exactly. And the beauty of this approach is that you don't need venture capital or a fancy launch. You just need one person who trusts you enough to pay. Ryan's entire business came from a single tweet screenshot. No landing page, no marketing, no SEO. Luna: It's almost like a return to the old-school software model: build for one customer, then sell the same thing to others. But modernized with APIs and no-code. Lucas: Right. The difference is that today's tools let you build something functional in a weekend. Ryan's initial prototype took him two days. That's incredibly low risk. If the YouTuber had said no, he would have spent a weekend learning — not a huge loss. Luna: So what's next for him? Will he ever try to get a second client? Lucas: He's torn. On one hand, the current client keeps him busy with feature requests. On the other, he knows he's one contract renewal away from zero. He told me he's saving aggressively and planning to hire a part-time developer to help with the generalized product. If he can get that to a point where onboarding a new creator takes a week instead of months, he'll start selling it. Luna: It's a smart hedge. Keep the golden goose happy while quietly building the next thing. Lucas: And that's the indie hacker way. You don't have to choose between stability and growth. You can do both, just not at the same time. Ryan is using his current revenue to fund his future product. It's bootstrapping in its purest form. Luna: Makes me wonder how many other solo devs are out there with similar stories — one big client, huge margins, but a ticking clock. Lucas: A lot more than you'd think. I've talked to several who are in the same boat. They don't talk about it because it doesn't sound as glamorous as a high-growth startup. But the financial reality is often better. I'd rather have fifteen K a month with one client than a million-dollar ARR with fifty angry customers. Luna: Fair point. And there's something to be said for the simplicity. One client, one product, one relationship to manage. It's almost zen. Lucas: Right up until they leave. But until then, it's a pretty good life. Luna: So if someone listening wants to try this approach, what's your one piece of advice? Lucas: Find a creator or a small business that clearly has a manual process they hate. Offer to automate it for free, with the understanding that if they like it, you'll work out a pricing model. Most people will say yes to free. And once they see the value, they'll pay to keep it. Luna: It's the classic 'give away the razor, sell the blades' strategy. Lucas: Exactly. And with today's tools, you can build that razor in a weekend. The hardest part is just finding the right person to shave.