The hardest thing about competing in a saturated SaaS market is not the competition. It is the temptation to position your product against the competition. The moment your landing page says "the affordable alternative to [incumbent]", you have positioned yourself as a discount version of the leader. You will lose. The teams that win in saturated markets do not compete on the same axis. They find a sub-niche where the incumbent's general-purpose product is mediocre and they build something specific. Niche SaaS strategy is the discipline of being indispensable to a small group instead of mediocre to a big one.
We run five SaaS products, all in markets with established competitors. None of them compete head-on with the leaders. Here is the framework.
What "saturated" actually means
A market is saturated when:
- There are at least 3 well-known general-purpose tools.
- The category is well-understood (buyers know what to ask for).
- Free trials, demos, and content marketing all assume a category-aware buyer.
Lesson planning, retirement-advisory tools, scheduling, CRM, helpdesk, project management. All saturated. All have multi-billion dollar incumbents.
The mistake is concluding "I cannot enter this market". The market is saturated for the average buyer. It is rarely saturated for the specific buyer.
The wedge framework
A sub-niche is a wedge into a saturated market. The wedge has three parts:
- A specific buyer profile with needs the general tool serves badly.
- A specific feature or workflow the general tool does not prioritize.
- A specific channel where the general tool does not show up.
If you have all three, you have a wedge. If you have two, you have a struggle. If you have one, you have nothing.
The buyer
Specific does not mean small. It means definable. "Solo accountants who do French tax returns" is specific. "Accountants" is not.
For Carriva, the buyer is "retirement-advisory firms (CGP, CGPI) in France with 1 to 20 advisors". Specific. The general retirement-planning tools do not target this profile; they target enterprise insurance companies or consumers directly.
For the lesson-planning monorepo, the buyer is "K-12 teachers in France, English-speaking countries, and Poland who plan lessons weekly". Specific. The general lesson-planning tools target school administrators or curriculum publishers.
The buyer profile should be specific enough that you can describe a single representative person. If you cannot, you have not narrowed enough.
The feature
The feature is the thing the incumbent could build but has not. Usually because their general-purpose product has 47 priorities and yours has 1.
For Carriva, the feature is the audit of the RIS document (Relevé Individuel de Situation). The incumbent retirement-planning tools do simulation (projection of future pension). Carriva does audit (verification of past contributions). It is a different problem with a different workflow.
That distinction is the wedge. We covered it in detail in our why we built Carriva writeup. The audit-vs-simulation framing is not a feature checkbox; it is a different product.
The channel
The third axis. Where do you reach the buyer that the incumbent does not?
For Carriva, the channel is direct outreach to CGP cabinets and content in French specifically tuned to the audit terminology. The incumbents advertise to consumers. The CGPs are a niche that does not see those ads.
For the lesson-planning monorepo, the channels are language-specific (preparemescours.fr for France, draftmylesson.com for English, przygotujlekcje.pl for Poland). Each language site is positioned for the specific market. The incumbents are largely Anglophone and serve the French and Polish markets through translated marketing, badly.
Channels are often hidden in plain sight. Industry forums, language-specific sites, regional events, niche newsletters. The incumbent cannot economically reach all of them. You can reach a few, deeply.
The questions to ask
Three questions to validate a niche idea.
"Who is being served badly today?"
Not "who has problem X?" Everyone has problems. The question is who has problem X and is currently being served by a tool that handles their case poorly.
The answer comes from interviews. We covered the interview discipline in our customer interview questions writeup. The signal is when interviewees say "we use [incumbent] but it does not really fit because..."
That sentence is a wedge.
"Why has the incumbent not built this?"
Important question. The honest answers:
- The market is too small for the incumbent. Their existing customers do not ask for it. Building it would dilute their general-purpose roadmap.
- The feature requires domain expertise the incumbent lacks. A tax-return tool needs a tax expert. A pension-audit tool needs a retirement expert.
- The feature requires a different go-to-market. The incumbent's sales motion does not reach this segment.
If the answer is "I do not know why they have not built this", you may be missing something. Maybe they have built it and you have not seen it. Maybe the demand is not real.
If the answer is one of the three above, you have a structural reason the incumbent will not catch up to you quickly.
"Can a small team build this?"
A small team has different math than an incumbent. We need to ship a product that one or two people can build and maintain. If the niche requires hundreds of integrations or a 24/7 enterprise support team, we are the wrong shape for it.
Carriva is buildable by a small team because the workflow is bounded (audit a document, produce a report). The lesson-planning monorepo is buildable by a small team because the core unit of work (a lesson plan) is small.
A niche that requires the operational footprint of a 50-person team is not the right niche for a solo founder, no matter how clean the wedge.
Examples of wedges that work
A few real patterns.
Geographic wedge
The incumbent is Anglophone. You build for a non-English market. The localization is not just translation; it includes domain-specific concepts, regulatory specifics, and market vocabulary.
PrepareMesCours competes against a category dominated by English-language tools. The French market has different curriculum frameworks, different vocabulary ("séquence pédagogique" not "lesson sequence"), different exam structures. The geographic wedge is real.
The Polish version (PrzygotujLekcje) is a similar wedge for the Polish market. The Spanish multi-country fork (Creaclases) targets 10 LATAM countries with the same mechanic.
Vertical wedge
The incumbent serves all industries. You serve one. You learn the vertical's workflows, vocabulary, regulations, and integrations.
We covered the broader vertical-AI-SaaS thesis in our vertical AI SaaS writeup. The wedge mechanism is the same: incumbent's generality is your specificity.
Workflow wedge
The incumbent builds for one user role. You build for an adjacent role with a different workflow. CRM for sales reps is saturated. CRM for customer success or for partnerships is less saturated, with different mechanics.
Carriva is a workflow wedge inside retirement-advisory: audit instead of simulation, advisor instead of consumer.
Compliance wedge
The incumbent treats regulated industries as a footnote. You build with the regulation as a first-class concern.
Healthcare, finance, education in some countries, all have compliance constraints that off-the-shelf tools handle poorly. Building with compliance as a starting point is a wedge that incumbents struggle to retrofit.
The pricing implication
A niche product can charge more per user than a horizontal tool because the value is more specific. We covered the pricing axis in our SaaS pricing models 2026 writeup; in a niche, hybrid pricing with a meaningful entry tier captures the value of being specific.
The corollary: do not undercut the incumbent. If the incumbent charges 30 EUR per seat, your niche product can charge 50 to 100 EUR per seat. The buyer is paying for fit, not for the cheapest option.
We see new founders pricing too low because they are afraid the buyer will pick the cheaper general-purpose tool. The buyer who is shopping on price is not your customer. The buyer who is shopping on fit will pay a premium for a tool that fits.
What we did wrong
Honest reporting from our own products.
We picked too broad a niche
Early in the lesson-planning project, we tried to serve "all teachers globally". Too broad. We pivoted to country-specific forks, which gave us specific marketing channels and tighter product-market fit.
We pitched against the incumbent
For one product (not a Drafted By product, an earlier project), we positioned as "the open-source alternative to [closed-source incumbent]". We competed on the incumbent's axis. We lost. The buyer who came to evaluate us was already committed to the incumbent's mental model.
The lesson: do not let the incumbent define your category. Define your own.
We launched without enough interviews
Two of our products shipped after a handful of interviews. The first six months were a series of corrections we could have made before launch with 20 more interviews. The math is brutal: every customer interview is 45 minutes. Every wrong assumption that ships is several weeks of building plus several weeks of unwinding.
Pre-launch interviews are the cheapest insurance you can buy.
The niche SaaS strategy is not "be smaller than the incumbent". It is "be more specific to a buyer the incumbent does not know exists".
The defense moats
Once you have a niche, the defenses against incumbent attention are real.
- Domain knowledge. You learn the niche's specifics. The incumbent does not.
- Customer relationships. Niche customers talk to each other. Word of mouth is concentrated.
- Integrations specific to the niche. A pension tool integrated with French regulator portals is hard for an Anglophone incumbent to replicate.
- Brand association. When buyers in the niche think of the problem, they think of you first. That is the most underrated moat.
These defenses compound over time. After 18 months in a niche, your accumulated knowledge is a real moat. The incumbent could try to enter your niche but they would have to spend 18 months learning what you already know.
The exit problem
A real concern: niche SaaS has a smaller addressable market. Your TAM might be 50 EUR million instead of 50 EUR billion. That changes the exit math.
The honest framing:
- A niche SaaS at 5 EUR million ARR is a great business. Sustainable, profitable, owned outright.
- A niche SaaS at 5 EUR million ARR is rarely a venture-scale outcome. VCs need 100x returns; niches do not deliver that.
If you are building for a venture-scale exit, niche may not be the right strategy. If you are building to own a profitable, sustainable business, niche is exactly right.
We are building for the second outcome at Drafted By. The niche strategy is aligned with our goal. If your goal is different, evaluate accordingly.
The expansion paths
A niche SaaS can expand in several directions.
Adjacent niches
After dominating one niche, expand to a similar one. Carriva starting with French CGPs could expand to Belgian CGPs. Same product mechanic, similar market, smaller incremental cost.
Vertical depth
Stay in the same niche but go deeper. Add features the niche specifically wants but the incumbent never will. Each added feature widens the moat.
Horizontal expansion (cautiously)
Eventually, after years in a niche, expand to a horizontal product. This is the riskiest expansion because you give up the wedge. We have not done this on any product yet.
The default for a small team is the first two. Horizontal expansion is a phase 3 problem.
How niches stack across products
If you are running multiple SaaS products like we are, the niches can reinforce each other. The lesson-planning monorepo's three forks share infrastructure, share content, share product mechanics. The incremental cost of adding a fourth and fifth is small. The aggregate revenue is higher than any single niche could generate.
This is the studio model. Each individual product is a niche. The portfolio is meaningful. We covered the practical mechanics of running multiple products in parallel in our shipping four SaaS in parallel writeup.
What we would test first
If you are evaluating a niche right now:
- Define the buyer in one specific sentence. If you cannot, you are not specific enough.
- Identify the feature or workflow the incumbent serves badly. Not "AI"; an actual workflow.
- List three channels where you can reach the buyer. If you cannot list three, the niche is not addressable.
- Run 10 interviews with people matching the buyer profile. The pattern will tell you if the wedge is real.
- Estimate the niche size at scale. Is 5 EUR million ARR enough for you? If yes, proceed. If no, find a bigger niche or reset expectations.
A niche that survives all five tests is worth building. A niche that fails any of them is worth re-examining before you spend a year building.
TL;DR
Saturated markets have niches that the incumbents do not serve. The wedge is buyer + feature + channel. Specificity beats scope. Pricing reflects fit, not category cost. The niche SaaS strategy in 2026 is the small team's structural advantage; you are not competing on the incumbent's axis. You are building a different product for a different person. That is the whole game.
