Build for one job title: the vertical wedge that beats a generic tool
Generic AI tools are commoditizing weekly. The products holding their ground solve one job, for one role, in one industry — and charge accordingly.

The short version
- A thin layer over a model anyone can call has a moat measured in weeks — the answer is narrower, not more ambitious.
- Name your customer by job title, company size and industry. "Marketers" is not a customer; "head of marketing at a twenty-person dental group" is.
- Vertical knowledge is the moat generative tools cannot copy, because it lives in customers rather than in code.
- Earn the right to widen: dominate a niche, absorb the adjacent workflow, then expand with revenue and references behind you.
The uncomfortable arithmetic of the current cycle: if your product is a thin layer over a model that anyone can call, your moat is the month before someone notices. The response is not to build something more technically ambitious. It is to build something narrower than feels comfortable.
Narrow until the pitch writes itself
A useful test: can you name your customer by job title, company size, and industry? "Marketers" is not a customer. "Head of marketing at a twenty-person dental group" is. The second one tells you which words to use, which integrations matter, where they gather, and what they already pay for — four answers you cannot buy at any price.
- Narrow markets are not small markets. They are reachable markets, which is the constraint that actually binds early on.
- Vertical knowledge is the moat that generative tools cannot copy, because it lives in customers rather than code.
- The workflow around the AI feature is the product. The model call is a component, not a company.
Earn the right to widen
Every widely used product started as a specific one. The sequence is always the same: dominate a niche small enough to serve properly, absorb the adjacent workflow your customers keep asking about, then widen with revenue and reference customers behind you. Reversing the order is how a product ends up with a vague market and a flat chart.
Building got cheap. Choosing did not. The constraint moved from execution to judgment, and judgment is now the scarce input.
Put this article to work
Ask it a question, or turn it into a to-do list for your own project. Both answer strictly from this article — nothing invented.
Answers are generated from this article only and are a working draft, not advice.
Questions this answers
How do you build a moat against AI competitors?
By being narrower than feels comfortable. Feature moats are copied in weeks now, but vertical knowledge — the workflow, vocabulary, integrations and edge cases of one role in one industry — lives in customer relationships rather than in code, and cannot be regenerated from a prompt.
Is a niche market too small to build a business on?
Narrow markets are not small markets; they are reachable ones, which is the constraint that actually binds early on. Knowing the exact job title, company size and industry tells you which words to use, which integrations matter, where those people gather and what they already pay for — four answers you cannot buy at any price.
When should a startup expand beyond its niche?
After it dominates one, and by absorbing the adjacent workflow customers keep asking for. Every widely used product started as a specific one; reversing the order produces a vague market and a flat chart.
Building something?
Put it in front of founders who read this — free listing, community-voted, reviewed before it goes live.


