Latest / The Indie Hacker Podcast with Fexingo: Solo Developers, SaaS Side Projects, and Independent Tech / How a Solo Dev Built a SaaS With No Employees
Transcript
- Lucas: So there's this one-person company called Pulsetic — a website monitoring tool — that as of early 2026 has over 10,000 paying customers and is north of a million dollars in annual recurring revenue run rate. Luna: Wait — one person? No co-founders, no employees, no contractors? Lucas: Not a single employee. The founder, a solo developer named Alex, built the entire product himself, handles customer support, does the marketing — everything. Luna: Okay, I have so many questions. How does one person support 10,000 customers? That seems like a full-time job just answering tickets. Lucas: That's the key insight: he automated almost all of it. Customer support is handled by a sophisticated AI chatbot that he built and trained on his own knowledge base. It can resolve about 85 percent of inquiries without human intervention. Luna: Eighty-five percent? That's impressive. What about the other fifteen percent? Lucas: Those get escalated to him, and he answers them personally — usually within a few hours. He's said that the chatbot actually makes the remaining tickets easier because it's already collected context and tried to solve the problem. Luna: So the AI doesn't just deflect — it actually pre-qualifies the hard cases. That's smart. Lucas: Exactly. And he's applied that same automation mindset to other parts of the business. Onboarding is fully automated — users sign up, get a trial, and the product guides them through setup with in-app tutorials. No onboarding calls. Luna: But at a million ARR, that's about a hundred bucks per customer per year on average. That's a pretty reasonable price for website monitoring. Lucas: Right — it's a commodity-ish product, but he's carved out a niche with simplicity and reliability. He focuses on uptime monitoring, SSL certificate checks, and basic performance alerts — nothing fancy. No dashboards with fifty metrics. Luna: So he's deliberately avoiding feature creep. That's a discipline a lot of founders lose once they see competitors adding more stuff. Lucas: That's the thing — he's said that every new feature request is evaluated against one question: 'Does this make the product better for our core use case, or does it just make it more complicated?' If it's the latter, he says no. And because he's solo, there's no team to lobby for pet features. Luna: That must also keep his codebase lean. Less maintenance, fewer bugs. Lucas: Absolutely. He can deploy changes in minutes because the codebase is small and he knows every line. Compare that to a team of five where a simple change might need code review, testing, and coordination. Luna: But what about the downside? Burnout seems like a real risk when you're the only person who can fix a critical outage at 3 AM. Lucas: He's addressed that with redundancy — the monitoring infrastructure itself is fully automated with failover alerts sent to his phone, but he also has a pact with another solo founder: if one of them is unreachable, the other can step in as a backup. It's an informal arrangement. Luna: That's clever. A buddy system for emergencies. Lucas: And he's also disciplined about working hours. He blocks out deep work in the morning, handles customer issues in the afternoon, and — this is key — he doesn't check dashboards on weekends. The product either works or it doesn't, and he trusts the automation. Luna: Trusting automation is easier said than done. I think a lot of founders would be refreshing their revenue dashboard every Sunday night. Lucas: No doubt. But he's built a business that doesn't need constant attention. And that's actually a competitive advantage — he can offer reliability at a lower price because his costs are just his own time and server bills. Luna: Speaking of costs — what's his stack look like? He must be using a lot of managed services to keep ops minimal. Lucas: Yeah, he's all-in on cloud. He uses a combination of AWS Lambda for compute, DynamoDB for storage, and a third-party monitoring API for uptime checks. The whole thing costs him about two thousand dollars a month in infrastructure. Luna: So at a million ARR, that's a 98 percent gross margin. That's absurdly good. Lucas: It's insane. The only other costs are his own salary — he pays himself about a hundred fifty thousand — and some software subscriptions. He's basically printing money. Luna: But here's the thing I keep coming back to: is this scalable? Can he get to two million ARR alone? Five million? Lucas: He's thought about that. He believes the ceiling is probably around three to four million ARR before he'd need to hire. At that point, customer support alone would overwhelm the chatbot, and he'd need someone to handle the fifteen percent that require a human. Luna: So eventually he'd need to become a manager. And that changes the whole dynamic of the business. Lucas: Right — and he's not sure he wants to. He enjoys building software, not managing people. So he's actually considering keeping the business at its current size and just letting it generate cash flow indefinitely. Luna: That's a valid strategy. Not every business needs to be a unicorn. A million-dollar solo company that runs itself is a pretty sweet gig. Lucas: And that's the indie hacker dream for a lot of people. Speaking of which — and this is totally unrelated — but you know, we're able to make these episodes without any ad breaks or sponsors because a small group of listeners supports us through Buy Me a Coffee. Luna: Yeah, it's literally at buy me a coffee dot com slash fexingo. And those contributions go directly toward covering hosting costs and the time we put into research. It's not a big ask — just if you find value in the show. Lucas: Exactly. And it keeps the podcast exactly the way we want it — no ads, no sponsorships, just honest conversations. So thank you to everyone who's already chipped in. Luna: So back to Pulsetic — do you think this model could work for other types of SaaS? Or is website monitoring a uniquely well-suited niche? Lucas: I think the principles apply broadly. The secret sauce is picking a product that's simple enough to be handled by one person, automating aggressively, and being extremely disciplined about scope. You could do this with a calendar booking tool, a simple invoicing app, or a password manager. Luna: What about customer onboarding? If you're selling to businesses, there's often a need for demos and setup calls. Lucas: That's true, but you can design around it. Pulsetic uses a self-serve model with a generous free tier. Users can get value without ever talking to a human. If you're targeting tech-savvy customers, that's totally feasible. Luna: So the key is to build for the customer who wants to figure it out themselves. That's a specific persona. Lucas: Exactly. And you have to be willing to lose the customers who need hand-holding. But if you can serve the self-sufficient ones well, you can run a very lean operation. Luna: I wonder how many other solo founders are quietly running million-dollar businesses like this. We hear about the big vc backed stories, but there must be thousands of these. Lucas: Probably more than we think. Pulsetic isn't famous — it doesn't have a blog or a Twitter following. It just quietly solves a problem and collects revenue. That's the ultimate indie hacker move. Luna: Alright, I'm going to go audit my own stack now and see where I can add a chatbot.