Focus Strategy

A company with few resources that meets a large one head-on in the same arena usually loses. The trouble was that this observation never said what to do instead. One piece of advice was to spend carefully because money is tight; another was to be different or die. Both left the scope untouched and simply asked the team to execute better, which changed nothing in practice.

What filled the gap was a third option: cut the scope. Alongside how cheaply you build and how differently you build sits a third axis — who you sell to and, just as importantly, who you don't. Only once that axis was named explicitly did a sentence like "we sell to customers in one industry only" start reading as a strategy rather than as giving up.

Pagedeck passed through the same moment in its first year. Grace described the product to an investor as "a collaboration doc tool for every team," and the question that came back was which team can't do its job without this today. She had no answer. Digging into actual usage, the accounts that renewed clustered in engineering teams at software companies, while every other industry signed up and left inside two months. A product built for everyone was in fact working for exactly one industry.

Pick the axis you'll cut along, then win inside the narrow slice either by selling cheaper than anyone else or by solving a problem nobody else bothers to solve. The axis is usually one of four: customer type, industry, geography, or use case. Sometimes it's a single cut — software companies only, this country only, meeting notes only — and sometimes two cuts are layered.

Execution comes in four steps.

1. Set the axis and the width. "Engineering teams at domestic software companies" fits in one sentence, and everyone who hears it should picture the same thing. "Growing businesses" is not an axis.
2. Check whether the slice is the right size to be number one in. The judgment is three percent of the whole doc-tool market versus forty percent of the slice, and you take the second — but if the slice is too small, forty percent of it still won't keep the company running.
3. Write down what you're giving up. Name the customers you won't take, the features you won't build, the channels you won't enter. Skip this step and the first two remain announcements.
4. Move people and budget across. A strategic priority is one of the few things a company commits to for the period, and under a focus strategy that list must not wander outside the slice.

Winning inside the narrow slice splits two ways again: give the same thing for less, or go deeper into that customer's specific problem than anyone else will. The second is more common, because a narrow slice means the customers all do similar work — the same engineering effort reaches ten percent of a broad market and ninety percent of a narrow one.

That gap becomes a competitive advantage, the point where you are clearly better than the alternatives. A large company that wanted to take the position would have to spend on features most of its own customers don't need, so it tends to leave the slice alone even after noticing it.

It appears first in the direction document of an early company. With few people and a fixed amount of money, writing down what you won't do is the strategy. A beachhead market is the foothold you take first and expand sideways from, and the slice chosen by a focus strategy often becomes exactly that foothold.

It comes up in investor meetings too. Investors don't only ask how large a market is; they ask which part of it you intend to take first, which is where a company that never cut its scope stalls. A broadly written target market makes the number look big without explaining how you win.

In roadmap meetings the term shows up as grounds for saying no. Whether a feature request gets built is decided not by how many people asked but by whether the customers inside the slice asked. Sales screens leads by the same rule. Take a customer from outside the slice and you gain one contract, but that customer's specific demands work their way into the roadmap, and a few quarters later the product satisfies neither side.

"Our focus strategy says engineering teams, and two HR features just landed on this quarter's roadmap."

The declared scope and the actual allocation have drifted apart, and one of the two needs to change.

"This isn't abandoning the focus strategy, it's widening the beachhead."

A proposal to move to the next adjacent slice now that this one is held — not a proposal to drop scope entirely.

"We should pass on that account. Taking it means the roadmap gets pulled around."

How turning down revenue gets justified at a company that has chosen a focus strategy.

Pagedeck narrowed to engineering teams at software companies that quarter. Grace made the call, Mia pulled four features built for other industries off the roadmap, and Sofia deleted manufacturing and retail accounts from the sales list. Ravi re-aimed advertising at developer communities only; signups dropped on the same budget, but paid conversion rose enough that revenue went up.

The argument ran in the other direction too. A manufacturing customer offered a contract worth about $23,000 a year, and it took two leadership meetings to settle. The refusal came down not to the amount but to the approval-chain feature the customer wanted, which would be useless to every engineering-team account.

The most common misreading is that a focus strategy means staying in a small market. Narrowing scope sounds like surrendering scale, so the reaction is understandable. But what gets narrowed is where you stand now, not where you end up. Once a slice is held, the path into an adjacent one opens, and you walk in carrying customers and references rather than nothing at all. Reverse that order and start broad, and no area uses the product enough to recommend it, so the platform for expanding never forms.

The other mistake is reading focus and diversification — spreading into several lines of business — as a difference in company size. The assumption is that a company naturally graduates to diversification as it grows, but the two differ in how resources are allocated, not in what stage they suit. Diversification spreads risk so the company survives when one business wobbles; focus concentrates everything in one place to raise the odds of winning there. A 45-person company that splits into three businesses to spread risk ends up short-staffed in all three, and the risk triples instead of falling.