Picking a SaaS Niche When You're Solo: Hard Lessons
Most SaaS advice tells you to pick a big market and build defensibility. That's written for teams. When you're solo, the math is different: a small niche with a real problem and a customer who will pay beats a large market where you'll drown in feature requests and support debt.
Why Market Size Advice Fails for Solo Builders
The standard SaaS playbook says: find a large, growing market, build a simple MVP, and scale. That advice assumes you have a team. When there's only you, every customer interaction, every feature request, every integration, and every support ticket is your time. The math inverts. A large market is actually a liability if it means you'll get pulled in ten directions at once.
A solo founder in a large market faces a cruel trade-off: either you say no to customers (killing growth) or you keep saying yes and burn out. You can't hire for two years because the product isn't mature enough to justify it. So you either build a narrow wedge into that large market and defend it fiercely, or you pick a genuinely small niche from the start. Both work. The mistake is picking a large market and expecting to operate it alone.
The niche doesn't have to be tiny; it just has to be defensible by one person's effort. That means the problem is specific enough that solutions don't sprawl, the customer base is coherent (you can reach them without spending a fortune on ads), and the support burden is manageable.
Niche Selection Criteria for the Solo Operator
Start with these three filters. First: can you reach the customer without massive marketing spend? If your customer is a CTO at a Fortune 500 company, you'll spend months on sales. If your customer is a solo consultant or small-business owner in a specific field, you can find them through communities, newsletters, and word of mouth. Second: is the problem specific enough that it doesn't demand endless feature variation? A tool for freelance bookkeepers is more bounded than a general accounting tool. Bookkeepers face similar workflows; they have similar compliance needs. Third: will they pay? Don't pick niches that traditionally resist pricing, such as free communities, hobbyists, or students, unless you genuinely enjoy operating at the margin.
The best solo-founder niches have three things in common. They're usually vertical, serving a specific profession or industry rather than a horizontal workflow. They're usually B2B or B2B2C, because small businesses and freelancers have budgets and tolerate imperfection; consumers expect polish and demand features. And they usually solve a back-office or efficiency problem, not a core offering: a tool that saves time, not a tool that runs the whole business.
- Vertical niche: pool cleaners, real-estate photographers, bookkeepers, golf clubs, poker sites, niche agencies
- Horizontal but bounded: scheduling for a specific type of service, CRM for a specific workflow, analytics for a specific platform
- Buyers with budgets include professionals, small businesses, and agencies, not consumers, students, or volunteers.
- Problem stays the same: the workflow doesn't change drastically quarter to quarter, so feature creep is manageable
The Coherence Test: Can You Talk to All Your Customers?
Consider this thought experiment: if you can't reasonably have dinner with every paying customer in a year, the niche is too large for one person. This doesn't mean you should stay tiny forever. It means that in year one, you should be able to know your customers by name, to understand their exact workflow, and to iterate based on their real feedback rather than aggregate data or speculation.
This test serves two purposes. First, it keeps you honest about scope: if you start talking to ten customers and realize they're solving completely different problems with your tool, your niche is too broad. Second, it keeps you close to the signal. Your first customers are your best product managers. If you're serving five funeral homes, ten real-estate brokers, and fifteen personal trainers simultaneously, you're serving no one well. Pick one.
When you pass this test, something shifts. You stop building features and start solving a specific customer's problem repeatedly, for money. You can turn down feature requests that don't fit. You can charge more because you're not competing on feature count, you're competing on understanding. That's the advantage of the solo operator in a tight niche: depth over breadth.
Adjacency: How to Expand Without Sprawl
After six months or a year in a niche, you'll start seeing adjacent niches that share the same buyer or workflow. A tool for golf clubs might expand to golf resorts. A tool for freelance designers might expand to small design agencies. The expansion should share the same customer base or a very similar workflow, not requiring re-learning the domain.
This is how you grow without hiring immediately. You expand horizontally into similar customers in similar verticals rather than building your product into a platform. Horizontal expansion is a one-person job; vertical integration is not. You add another niche after proving the first one works, not before.
The key is to share as much code, infrastructure, and expertise as possible across niches. If your first niche is Chilean real estate, do not expand to home-improvement contractors next because they are a different workflow and a different buyer. Expand to Chilean luxury real-estate, or Chilean commercial real-estate, or real-estate across the Andean region. You're leveraging what you already know.
Red Flags: Niches That Look Good but Aren't
Watch for these traps. First: picking a niche because it's crowded means it's validated, without asking whether you can win a slice. A crowded niche means customers have options and high expectations. You need a genuine differentiation or a slice of the market that's being ignored. Second: picking a niche you don't understand. You'll make wrong assumptions about the workflow, the buyer, and the budget. Talk to customers before you code. Third: pick a niche with structural resistance to pricing, such as open-source communities, non-profits, or hobbyists. You can serve them, but plan for that in your business model.
Fourth: picking a niche where the buyer isn't a solo decision-maker. If buying your tool requires a committee meeting, a budget cycle, and IT approval, you've picked something that won't work at a solo company's pace. Fifth: picking a niche where the workflow is in flux. If the industry is being disrupted or the tools your customers use are changing, your niche is moving faster than you can react. Sixth: picking a niche that's geographically scattered and expensive to reach. If your customers are one per country and you need to fly to sell, you've picked wrong.
When to Abandon Your Niche
You'll know within three to six months of talking to customers. If you can't find more than five or ten who will pay, the niche is too small or the problem isn't real enough. If every conversation reveals a completely different workflow or need, you've picked a cohort, not a niche. If the customer base is shrinking or the workflow is being disrupted by a new tool or platform, you're chasing a moving target.
The hard part is knowing when to pivot rather than persist. A real niche will yield customers who are relieved you exist because they've been solving this problem manually, with a spreadsheet, or with a tool that doesn't fit. If you're getting blank stares or indifference, that's a signal. So is hearing 'you should add this feature' in every conversation, which means the problem is too varied for a focused tool.
Abandoning early is not failure; it's data. You learned something about the market, the customer, or the problem. Persist is the temptation. But for a solo operator, persistence in the wrong niche is just slow failure. Pick a new one and start again.
Starting Lean in Your Niche
Once you've picked, move fast and sell before you build. Find ten potential customers in your niche and talk to them. Learn their exact workflow. Don't pitch your solution; listen to their problem. Then, build only the smallest version that solves that problem for them. Your MVP for a vertical SaaS may need less than you first expect because you are solving one specific step in a workflow, not the whole workflow.
Charge from day one. Not a lot, maybe $50 to $200 a month, but charge something. Paid customers are honest customers. They'll tell you what's broken and what matters. Free users will use your tool occasionally and forget it. Paid users will complain if the invoice doesn't arrive, if the tool is slow, or if a feature breaks. That complaint is gold.
As a solo operator in a focused niche, your advantage isn't features, speed, or brand. It's understanding. You know your customer better than a larger platform will ever care to. You know their pain in detail. You can ship a tool that fits their workflow because you've lived in it. That understanding compounds over time. After a year, you're not fighting feature creep; you're extending a tool that already works. That's when you can finally slow down and hire, if you want.
Common questions
how do I know if a niche is too small to build a SaaS
A niche can be too thin when the people with the problem are difficult to reach and the revenue they could support does not cover delivery and support. Estimate the reachable market, willingness to pay, and costs using evidence from customer conversations. A small market can work, but there is no universal customer-count or conversion threshold.
should I pick a niche with high pain or high willingness to pay
High willingness to pay. A customer in pain but broke will never sign up. A customer with a genuine workflow problem and a budget will. This is why vertical SaaS aimed at professionals (real-estate agents, tradespeople, niche marketers) tends to work better for solo builders than horizontal tools aimed at consumers.
what if my niche is too crowded or too small
Too crowded: pick an underserved segment within it, such as rural real-estate agents or agents in a specific region, rather than targeting all real-estate agents. Too small: either expand to adjacent niches that share the same customer base, or consider whether you've misidentified the real buyer (maybe it's not individuals but agencies or platforms serving those individuals).
Every property in the Don Gastón portfolio is independently live; it is built, deployed, and operated by one person.
See what's live in the portfolio