Latest / The Indie Hacker Podcast with Fexingo: Solo Developers, SaaS Side Projects, and Independent Tech / How a Solo Dev Used a Chrome Extension to Hit 10K MRR
Transcript
- Lucas: There's this assumption in the indie hacker world that building a proper SaaS means spinning up a full stack—database, authentication, payment processing, the works. But one developer I came across recently built a business doing nearly ten thousand dollars in monthly recurring revenue using a single Chrome extension, and his backend is essentially a Firebase collection. Luna: I love that. So he skipped the server entirely? Just a frontend that talks to a cloud database? Lucas: Exactly. The extension is called Thread Saver, and it does one thing—it lets you save Twitter threads and organize them into folders. That's it. No login screen within the extension; it uses your Google account through Chrome's identity API, and stores everything in Firestore. The entire business logic lives in the browser. Luna: And people pay for that? I mean, I can see the utility, but ten grand a month for saving threads? Lucas: That was my first reaction too. But look at the numbers. The extension launched on Product Hunt in October 2024 and hit number two product of the day. That drove about fifteen thousand installs in the first forty-eight hours. The free tier lets you save fifty threads. The paid tier is three dollars a month for unlimited saves and folders. Within a week, he had two hundred paying users—six hundred dollars MRR from a single launch. Luna: Six hundred dollars from a weekend project. That's the dream. Lucas: Right. But what I find more interesting is how he grew from six hundred to nine thousand MRR over the next eighteen months. No paid ads, no content marketing—just the Product Hunt spike and then steady organic growth from the Chrome Web Store search. The extension ranks for keywords like 'save twitter threads' and 'thread organizer,' which get about five thousand combined searches per month. That converts to about a hundred new installs per day, and roughly one percent of those convert to paid. Luna: So the SEO is basically built into the store. You just need a good description and ratings. Lucas: He focused heavily on ratings early on. After the Product Hunt launch, he put a small popup inside the extension asking users to rate it on the Chrome Web Store if they found it useful. Within three months, he had over a thousand ratings with an average of four point seven stars. That's a huge signal to Google's algorithm. The store surfaces high-rated extensions more prominently. His ranking for the core keywords improved significantly, and that drove the organic growth loop. Luna: I've heard Chrome extensions are a tough market because the store is crowded and the margins are thin. What's the economics here? He's charging three bucks a month, so at nine thousand MRR, that's three thousand paying users. Lucas: Close. About three thousand two hundred. After the thirty percent cut Chrome takes, his net is around six thousand three hundred per month. That's still a solid solo income, especially considering his only cost is the Firestore database—maybe fifty dollars a month. He's running a seventy percent margin after platform fees. Luna: But thirty percent to Chrome. That's the same as Apple's App Store cut. Do you think extensions are a better entry point than a full web app? Lucas: In some ways, yes. The development cost is lower—you're just writing JavaScript and HTML. You don't need to build a separate backend for authentication or payments; Chrome handles identity and the store handles billing. The downside is the platform risk. If Google changes the store policies or the API, your business can disappear. But for a solo developer with limited capital, it's a very efficient way to validate an idea. You can have a working extension up in a weekend and see if people install it. Luna: What about customer support? I imagine with a simple tool like this, support load might be low. Lucas: That's another deliberate design choice. The extension is so straightforward that most issues are self-resolving. He has a FAQ page and an automated email for billing questions, but he told me he averages fewer than ten support tickets per month. He spends maybe an hour a week on support. That's part of why the margin is so high—he's not burning time on customer service. Luna: So the product is inherently self-serve. That's a lesson in itself: build something whose complexity is hidden from the user. Lucas: Exactly. And he's kept the feature set intentionally small. He hasn't added sharing, collaboration, or AI summarization—all the things you'd think a thread saver should have. He told me that every time he considered a new feature, he asked himself whether it would increase conversion or reduce churn. Most ideas didn't pass that test. The result is a product that's basically unchanged from its launch version, with steady growth. Luna: That's a hard discipline. Most of us would try to add features to justify a higher price or attract more users. But he's proving that a minimal product, well-positioned, can generate a decent income. Lucas: It also makes you think about the Chrome extension market more broadly. There are thousands of extensions with millions of users, but very few are monetized. The ones that succeed tend to solve a very specific, recurring pain point—like saving threads, managing tabs, or automating form fills. If you can find a pain point that's small enough to build in a week but persistent enough that people will pay a few dollars a month to solve it, you have a viable business model. Luna: And if today's conversation gave you something usable, the way we keep this show ad-free is listener support. You can find us at buy me a coffee dot com slash fexingo. It's a simple way to say this episode was worth your time. Lucas: Yeah, we don't run sponsors or sell your data. If you find value in episodes like this one, that link is how you keep it going. Appreciate anyone who throws a coffee our way. Luna: Now, let's get back to the business. What's the long-term ceiling for a Chrome extension? Can Thread Saver ever hit fifty thousand MRR? Lucas: That's the question. The addressable market is limited to people who use Twitter heavily and save threads. Worldwide, that's maybe a few hundred thousand potential users. At a one percent conversion rate, he could theoretically get to thirty thousand MRR before saturating the market. But he's also considering expanding to other platforms—saving threads from LinkedIn or Reddit. That would open up a much larger audience without changing the core mechanics of the extension. Luna: So the same architecture could serve multiple platforms. That's a smart leverage point. Lucas: Exactly. He's already built a prototype for Reddit, but he's holding off until the Twitter version plateaus. The key insight for me is that he's not trying to force growth. He's letting the product find its natural audience and only expanding when the current channel shows diminishing returns. That's the opposite of the growth-at-all-costs mentality we see in vc backed startups. Luna: And it's a great example for any indie hacker thinking about their next project. Sometimes the simplest idea, executed well and distributed through the right channel, is all you need. Lucas: Absolutely. Thread Saver isn't going to be a unicorn, but it's a profitable, low-stress business that gives its creator financial independence. And that's a pretty good outcome for a weekend project.