Latest / The Indie Hacker Podcast with Fexingo: Solo Developers, SaaS Side Projects, and Independent Tech / How a Solo Dev Pivoted From $0 to 400K ARR in 18 Months
Transcript
- Lucas: Simon Chen spent fourteen months building a web scraper that zero people would pay for. That's not the part that makes this story interesting — the interesting part is what he did next. Luna: He pivoted, and the pivot turned a dead side project into four hundred thousand dollars in annual recurring revenue inside eighteen months. I love stories like this because they're so counterintuitive. Lucas: Completely. Most indie hackers I talk to treat a pivot like a failure — like the code they wrote was wasted. But Simon's case shows that the code isn't wasted if you redirect it into a problem people actually have. Luna: So let's rewind. What was he building originally, and why did nobody buy it? Lucas: Simon built what he called 'ScrapeHub' — a generic no-code web scraping tool aimed at small businesses. You point it at any website, it pulls structured data. The problem was there are already a dozen tools like that, many of them free or backed by VC money. He launched on Product Hunt, got a few hundred sign-ups, but conversion to paid was maybe half a percent. Luna: Right — generic tool in a crowded space. But he kept building features for fourteen months? That's a lot of sunk cost. Lucas: It is. And he admits he was in denial for most of that time. He kept thinking, 'If I just add one more integration, if I just improve the export, they'll come.' They didn't. The turning point was a support ticket from a user who wasn't even a customer — just a free-tier user — asking if the tool could handle a very specific compliance check for e-commerce brands. Luna: That's the kind of signal that's easy to ignore when you're obsessed with your original vision. Lucas: Exactly. But Simon followed the thread. He started doing discovery calls — five, then ten, then twenty — with e-commerce compliance managers. What he found was a massive pain point: brands selling on Amazon and Walmart and Shopify needed to monitor their resellers for MAP violations, unauthorized sellers, counterfeit listings. They were doing it manually or paying agencies thousands per month. Luna: So his generic scraper had a very specific, high-value use case hiding inside it. Lucas: That's the whole story. He didn't start over. He took the scraping engine, built a thin compliance layer on top, and rebranded as 'BrandShield Lite' — a name I'm not sure I love, but the product worked. He charged four hundred ninety-nine dollars a month, which is about ten times what he'd been planning to charge for ScrapeHub. Luna: And people paid it. Because the pain was real and the alternative was either hiring a person or doing nothing. Lucas: If today's tech conversation gave you something usable — maybe you're building something yourself, or you're thinking about a pivot — the way these episodes stay ad-free and independent is through listener support. If you got value, you can find us at buy me a coffee dot com slash fexingo. That's one word, lowercase. It helps us keep doing deep dives like this without sponsors. Luna: Yeah, and we really mean that — every bit of support lets us spend more time on the stories that actually teach you something. So back to Simon's pivot. Lucas: The first month after the pivot, he got three paying customers. That's not a lot, but it was more than he'd had in fourteen months. And he started charging annually — five thousand nine hundred eighty-eight dollars upfront. That gave him cash flow to actually hire a part-time customer success person. Luna: Annual upfront billing is a smart move for a solo dev. It de-risks the churn problem while you're still figuring out retention. Lucas: Absolutely. By month six he was at seventy-two thousand dollars ARR — all from less than fifteen customers. That's when he knew the niche was real. The compliance managers were telling their peers at other brands. He didn't spend a dollar on marketing; it was all word of mouth. Luna: So the growth was organic, but the trigger was the pivot itself. What specifically did he change besides the pricing and the positioning? Lucas: He added three features that the compliance people specifically asked for: automated MAP monitoring — that's minimum advertised price — a dashboard that flagged violations by seller, and a weekly email report. That was it. He didn't build a CRM, didn't add a hundred integrations. Just those three things, layered on the existing scraper. Luna: That's a great example of the 80-20 rule. Twenty percent of the feature work delivered eighty percent of the value. Lucas: Exactly. And here's a detail I love: he actually removed features from the original ScrapeHub. He killed the CSV export customization, killed the webhook builder — things that added complexity but no value for compliance users. That's hard for a solo dev to do because you feel like you're deleting your own work. Luna: It's like pruning a plant. You have to cut healthy branches to let the main stem grow stronger. So where did he end up at the eighteen-month mark? Lucas: Four hundred thousand dollars ARR, about eighty customers, and he was still the only developer. He had a part-time support person and a freelance designer for the dashboard. His net profit margin was around seventy percent because his only real costs were servers and the occasional contractor. Luna: That's a solo dev's dream. But it also raises the question — could he have gotten there faster if he'd pivoted earlier? Lucas: Possibly. He wasted about eight months building generic features. But I'd argue that the scraper itself was necessary — he needed that foundation to be able to pivot quickly. If he'd tried to build the compliance product from scratch, it would have taken him another six months at least. Luna: So the 'wasted' time wasn't really wasted. It was R&D that happened to be misdirected. Lucas: That's exactly how Simon frames it. He says the scraper was the price of admission to discover the real problem. And I think that's a healthy way for any indie hacker to think about early product work. Luna: What about competitors? Once he found the niche, did bigger players try to copy him? Lucas: A few. There are established compliance platforms like BrandVerity and MAPtracker, but they're enterprise-focused — think twenty thousand dollars a year minimum. Simon's product is simpler and cheaper, and the smaller brands that couldn't afford those platforms became his core market. The big guys aren't interested in sub-thousand-dollar monthly contracts. Luna: So he found a gap at the low end of an existing market. That's classic disruption theory — start with the undershot customers. Lucas: Exactly right. And the key was that he wasn't trying to compete on features. He competed on simplicity and price. The compliance managers he talked to didn't want a Swiss Army knife. They wanted a screwdriver that always worked. Luna: There's a broader lesson here about listening to market signals. Simon had a support ticket from a free user — that's a very weak signal — but he followed it. How many indie hackers get those tickets and just answer the question and move on? Lucas: Most of them. I've done it myself. The difference is Simon treated that ticket like a hypothesis: 'Maybe there's a market here.' And then he went and tested it with real conversations. He didn't build anything new until he'd talked to twenty people. Luna: Twenty discovery calls is a low bar, but most founders never do even five. They build from their own assumptions. Lucas: And that's the trap. Simon's story is so instructive because it shows how close he was to giving up. He said in an interview that if that support ticket had come a week later, he might have shut down the project and gone back to freelancing. The timing was that narrow. Luna: So luck played a role, but he created the conditions for luck by having a product in the market and being open to redirection. Lucas: That's a perfect summary. One other thing I want to highlight: his pricing strategy after the pivot. He charged four hundred ninety-nine dollars a month, but he also offered a 'lite' plan at one hundred ninety-nine that only monitored one marketplace. That created an upgrade path. About forty percent of customers started on lite and moved up within three months. Luna: So the lite plan was really a lead generation tool disguised as a product tier. Lucas: Exactly. And he didn't offer a free tier at all after the pivot. He learned from ScrapeHub that free users generate support tickets but rarely convert. So for BrandShield Lite, he did a fourteen-day free trial with no credit card required, but that was it. His conversion rate from trial to paid was about eighteen percent, which is healthy for B2B SaaS. Luna: Let's talk about the emotional side. Simon spent over a year building something nobody wanted. Most people would have quit. How did he keep going? Lucas: He had a day job as a freelance developer, so the project wasn't his only income. That gave him runway. But he also says he's stubborn — maybe to a fault. The pivot wasn't a rational decision at first; it was desperation. He was about to shut it down, so he tried one last thing. Luna: That desperation can be a powerful motivator. It strips away the attachment to your original idea. Lucas: It does. And the interesting thing is, once he pivoted, he says building felt fun again. Because he was solving a real problem for real people who were grateful. That's a totally different energy from building into the void. Luna: So for indie hackers listening who are stuck on a project that's going nowhere, what's the one concrete takeaway from Simon's story? Lucas: Talk to the people who almost pay you. Anyone who signs up for a free trial or sends a support ticket is telling you they have a problem. Your job is to figure out if that problem is widespread and painful enough to build a business around. Don't ask them what features they want — ask them what they're currently doing to solve the problem, and how much it costs them in time or money. Luna: That's excellent. And if you do that, you might find that the product you've already built is closer to something valuable than you think. Lucas: Exactly. Simon's scraper was never the product. The product was the compliance layer. But without the scraper, he couldn't have delivered the compliance layer in a week. So build something, put it out there, and then listen harder than you build. That's the indie hacker way. Luna: And sometimes the pivot is just a rebrand and a pricing change away. Lucas: Right. Four hundred thousand dollars ARR, one developer, eighteen months. Not bad for a pivot that started with a support ticket from a free user.