The most common bottleneck across twenty-six founders.

It is not the product. It is not the market. It is not the funding. After two years of advisory work, the bottleneck is something quieter — and it is the same thing almost every time.

What founders bring to the first meeting

Founders bring a hypothesis about their bottleneck. Most of the time, the hypothesis is wrong. The hypothesis is "we need more leads" or "we need to raise" or "we need to ship feature X." These are real problems. They are rarely the binding constraint.

What we usually find

The bottleneck, in twenty-six of twenty-six engagements I am thinking of, is the same: the founder does not have a written, sharp answer to who this is for and why now. Everything downstream — the leads, the raise, the feature roadmap — depends on that answer. When it is unclear, every other system runs at half-speed.

Why it stays hidden

It stays hidden because founders are practitioners. They are doing the work. The work feels like progress. And the unsharpened ICP can produce real revenue for a long time before it stops working. By the time it stops working, the team is already too large for the answer to be cheap.

How we move it

We sit with the founder for a half-day and write the paragraph. Not the deck, not the strategy doc — the paragraph. Two hundred words. Then we test it against the last five customers. Then we test it against the last five no's. The exercise sounds small. It is the one that moves the company.