n o ren
Building & Strategy

Your Niche Can Kill Your Scale

Jeff Bezos owned relentless.com and incorporated as Cadabra before landing on Amazon, and not one of those names says books.

Jeff Bezos incorporated his company as Cadabra in 1994, bought the domain relentless.com, and renamed the business Amazon in 1995 — after the world's largest river, not after anything on the shelves. The bookstore was the wedge, never the identity. That distinction sounds like branding trivia until you notice what it bought: when the catalog expanded to music, then electronics, then nearly everything, nobody inside the company had to argue that the new category betrayed the story, because the story had never been about books. Relentless.com still points at Amazon today, a small monument to a name deliberately built too big for its first product.

Most founders do the opposite, and the reason they do is that the opposite works first. A sharp niche story is what earns the first hundred customers: early adopters are buying a change, they tolerate rough edges, and they want to hear the product was built for exactly them. Geoffrey Moore named the problem in Crossing the Chasm in 1991 — the early majority that follows is not a larger version of that first group. They are buying a productivity improvement rather than a revolution, they want references from people who look like themselves, and the enthusiasts you spent a year courting are precisely the wrong references.

What turns this into a lock rather than a phase is that the narrow story quietly acquires enforcers. Sales quotes it, the roadmap inherits it, and every request from outside the niche arrives pre-labeled as scope creep — so the evidence that the fence is costing money gets filtered out by the fence itself. Breaking it rarely means abandoning the first market. It means demoting the founding feature from identity back to feature, which costs a team far more in ego than in engineering.

Early adopters and the early majority buy different things, so the reference customers you built are the wrong ones for the market you want next.
A founding feature has become an identity once the org rejects ideas for violating it rather than for losing money.
Naming and positioning choices made in year one quietly set the width of the roadmap in year five.

The positioning that recruited your first hundred customers is the same positioning that disqualifies you with the next ten thousand.

The fence filters its own evidence: demand from outside the niche gets logged as off-strategy noise rather than as a market you are declining.

1
Pull every deal marked closed-lost last quarter and count how many were lost to "not a fit" rather than to a named competitor; a fit-loss majority means you are turning down a market, not losing one.
2
Take your last ten roadmap rejections and write the actual reason next to each; count how many amount to "not what we're for" with no revenue number attached.

Crossing the Chasm (1991) remains the sharpest treatment of this, and its central claim is narrower than the popular summary: the gap is not between small and large customers but between buyers with fundamentally different reasons to buy. Moore's advice was not to widen the story but to pick a single beachhead segment inside the mainstream and dominate it, then use it as the reference base for the next one. Most teams reach for "broaden the story" when the actual fix is choosing a second, deliberate niche.

There is a naming version of this problem that costs nothing to avoid at the start and a fortune to fix later. A company named after its first product — one with the category sitting in the wordmark — pays a tax every time it enters a second category, because the name argues against the pitch before the salesperson opens their mouth. That is why the cheapest positioning decision you will ever make is the one made before you have any customers, and why it was rational for Bezos to spend real time on a name at a moment when he had nothing to sell.