There's a default assumption in bootstrapper circles that services are a stepping stone. You do client work until you figure out what to productize, then you build the SaaS. The service phase is something you graduate from.
I've been thinking about why that framing is so persistent, and I think it mostly comes from survivorship bias. The founders who escaped services into SaaS write about it. The ones who built a quietly profitable service business and stayed there don't make for as dramatic a story. But that second group exists, and the mechanics of what they built are worth understanding.
Here's what usually happens when a service business stays broad: sales conversations are long, pricing is always up for debate, and the portfolio is too mixed to tell a coherent story.
A generalist agency can do good work. But every new client is a different problem, and different problems don't produce the kind of patterns you can systematize. You end up doing great work that you can't reuse. The knowledge stays in people's heads instead of in the process.
Word of mouth also gets weird. When a happy client refers you, what exactly do they say you do? "They're great at, uh, design and marketing and some strategy stuff." That doesn't send you a stream of warm, ready-to-buy prospects. It sends you people who need to figure out whether you're even relevant to their problem.
The first thing that changes is who reaches out. When your positioning is specific enough — not "we do visual content for ecommerce" but "we do 3D rendering for furniture brands" — you start getting inbound from people who already know they need exactly that.
The second thing is that your portfolio starts pulling weight. Every past project is relevant to the next conversation. You're not explaining from scratch why your work in one industry translates to another. The prospective client sees themselves in what you've already done.
And pricing gets simpler. When you've done the same type of project thirty times, you know your costs, your timeline, and what can go wrong. You can quote confidently. You don't need to say "it depends" as often, because for your specific thing, it mostly doesn't.
The mistake I see service founders make is thinking the business is their expertise. It's not. Expertise gets you the first few clients. Repeatability is what turns it into a business.
What repeatability looks like in practice: you have a documented process for onboarding a new client. You have a checklist for delivering the core service. You have templates for the most common output formats. New projects don't start from a blank page — they start from a system that's been calibrated by the last twenty projects.
This matters because capacity stops being the bottleneck. When everything lives in your head, you're the bottleneck. When it lives in documented process, you can bring in a contractor for part of the work, or eventually a hire, without the quality dropping.
"Productized service" gets thrown around a lot, and it mostly just means: stop selling time, start selling an outcome at a fixed price.
That shift sounds simple. It's harder than it sounds. You have to narrow your scope enough that you can actually predict what's involved in delivering it. Which means saying no to custom work that falls outside the package. Which means some clients won't be a fit. Which feels like leaving money on the table until you realize you're leaving chaos on the table too.
A niche studio like CGI Furniture is a useful example here — the kind of specialized service business that can grow through positioning, repeatable delivery, and a tight ICP rather than trying to become a generic agency or chase a SaaS pivot. The scope is specific. The output is predictable enough to systematize. The client base is narrow enough that the portfolio speaks directly to every inbound lead.
That's the model. Not software. Not a broad agency. A very specific thing, done reliably, for a specific kind of customer.
Repeatability handles delivery. You still have to get customers.
The honest breakdown of what works for niche service businesses at different stages looks something like this: Early on, most business comes from direct outreach and the founder's existing network. The founder is the salesperson. That's not a problem — it's how it works.
What develops over time, if the positioning is right: referrals get more targeted. Past clients send you people who look like themselves. Your portfolio starts ranking in search, or at least gives you content to point people at. You build some kind of visible presence in the community where your clients spend time — a newsletter, a blog, speaking at an industry event.
None of this happens automatically. But unlike SaaS distribution, which requires either significant content investment or paid acquisition from day one, a well-positioned service business can run on referrals and outbound for years and be genuinely profitable.
Hiring before the system is built. If delivery still depends on the founder's judgment on every project, you can't delegate. Adding headcount just spreads the chaos.
Staying custom because custom feels premium. There's a version of this that's true — some clients will pay more for custom work. But custom work doesn't compound. You end up busier without getting more leverage.
Chasing every type of customer who expresses interest. The temptation is real, especially early. A client outside your niche shows up, the money is good, and you say yes. Then you do a mediocre job because you're outside your system, and the referrals they might have sent don't come because you weren't remarkable to them.
The Indie Hackers assumption is that a services business is where you figure out the idea for the real thing. But I think that framing is doing some founders a disservice.
A niche service business with documented delivery, a tight ICP, reliable referrals, and reasonable margins is not a consolation prize. It's a profitable small business with low overhead, optionality on when or whether to grow, and no VC to answer to. You can run it with a small team. You can stay in it for ten years. You can sell it eventually if you want to.
The SaaS might make sense later, or it might not. But getting there shouldn't be the goal by default. The goal is a business that works. Some of those are SaaS. Some of them are specialized service businesses that just got really good at the thing they do.