The week you should have stopped building

A founder books the call because 'traction is slow'. They describe the product roadmap. Three features shipping this sprint. A fourth lined up for next month. Customer feedback is 'mostly positive'. The team is 'shipping well'. And the pipeline hasn't moved in two months.

I can usually tell within five minutes of that conversation that the problem is not the product. The founder has been building, the team has been delivering, the velocity chart is healthy. But the growth curve is flat. The product team has answers. The distribution team — where there is one — has questions.

The asymmetric diagnosis

Most pre-Series A companies have either a distribution problem or a product problem. Rarely both at full intensity at the same time. The uncomfortable heuristic I've started using:

• If users who try it keep using it, but new users don't arrive — distribution problem
• If new users arrive, try it once, and never come back — product problem
• If neither — then yes, both. Usually in Series A territory this is more common.

The founder almost always knows which category they're in. They also almost always keep working on the other one, because it's the one the team is set up to solve.

Why the wrong one is the comfortable one

Engineering teams know how to build features. Shipping features feels like progress. It's legible — there are commits, standups, release notes. Distribution work is messier. Cold outbound, content, partnerships, pricing experiments, positioning rewrites. The feedback loop is longer and the wins are harder to attribute.

So the team keeps building. The pipeline keeps not moving. The runway keeps shortening. Everyone feels busy.

What stopping looks like

I'm not saying shut the product team down. I'm saying: when you're six to nine months in and the chart's flat, it's worth spending one sprint — one — where the team does zero feature work and the founder and one engineer do nothing but distribution. Cold email campaigns. Pricing tests. New positioning on the homepage. A partnership conversation.

If the pipeline moves, the diagnosis was distribution and the next three sprints follow that. If it doesn't, the product team goes back to work and the founder now has proof that the constraint isn't where they thought.

Every founder thinks their problem is the complicated one. Usually it's the boring one they've been avoiding.