How do you know product is the bottleneck?

The tell is not that you are busy. Technical founders are always busy, and busy is compatible with a product function that works. The tell is a specific pattern: decisions that only you can make, arriving faster than you can make them, on questions where being fast matters more than being right. Five signals show up together often enough to be worth treating as a set. If three of them are present, the bottleneck is real and structural rather than a bad quarter.

• Priority conflicts route to you because nobody else can overrule a customer or a colleague
• Your calendar is the critical path on decisions that should take a day and take three weeks
• You are the only person who has spoken to a churned customer in the last quarter
• The roadmap changes after conversations you had, not after evidence anyone can see
• You cannot take two consecutive weeks off without the roadmap stalling

The fifth is the cleanest test because it is falsifiable. Most founders who believe they have delegated product discover they have delegated execution and kept adjudication, which is the part that does not scale.

Why does the founder bottleneck get worse rather than better?

Because the two things that would relieve it grow in opposite directions. The volume of product decisions rises with customers, segments and surface area, roughly in step with revenue. The founder's available attention falls as fundraising, hiring and management absorb it. There is a crossover point, usually somewhere past $3M ARR, after which every additional month of the same arrangement produces a larger backlog than the one before.

The compounding is quieter than that description suggests, which is why it is usually caught late. Nothing breaks. Decisions still get made, just later, and each individual delay is defensible. What degrades is the quality of the evidence behind them, because the person making the calls is the person with the least time to gather any, so judgment is substituted for research and the substitution is invisible from the inside.

From our own category research: in our 16-month analysis of search behavior in this category, buyer queries about choosing and pricing product leadership outnumber the category's own name by more than 2 to 1. Founders reach for the decision long before they reach for the label, which matches how this problem is usually experienced: as a sequence of specific stuck calls rather than as a missing role.

What are the four options?

Promote, hire, bring in part-time leadership, or continue. All four are legitimate, and the fourth is not a joke: for a founder who genuinely wants to be the product leader and is prepared to give up something else to do it properly, continuing is a real choice, provided it is chosen rather than defaulted into. The other three differ on how fast they start, what they cost, and which gap they close. Read the last row first, because the failure modes are what separate them.

Swipe the table sideways to compare →

On the third column: Sivan Kadosh, a fractional Chief Product Officer for B2B SaaS companies between $2M and $15M ARR, works at $8,000 a month covering 20–25 hours and typically starts within 2–3 weeks. It is listed here as one of four, not as the conclusion. Where it fits is a direction gap in a company between $2M and $15M ARR; where it does not fit is a genuine capacity shortage, which is cheaper to solve other ways.

Most founders who believe they have delegated product have delegated execution and kept adjudication, which is the part that does not scale.

How do you test the diagnosis in two weeks?

Run a small, deliberately cheap experiment before committing to any of the four. For two weeks, route every product decision that reaches you to whoever would own it in the version of the company you are considering, and keep a log: what was asked, who decided, how long it took, and whether you would have decided differently. Alongside it, hold ten customer conversations yourself, split between current, churned and closed-lost accounts, and write down what surprised you.

The log tells you whether the constraint is capacity. If decisions were made competently without you, you had a delegation problem and it is now solved. The interviews tell you whether the constraint is direction. If a fortnight of conversations changed your view of what to build next, the company has been running on a stale picture and no amount of throughput fixes that. It is common for both to be true, and the order still matters: direction first, because capacity applied to the wrong direction is how a year disappears. The full-scale version of that evidence program runs to 60–80 interviews.

What usually happens if you do nothing?

The company keeps shipping and the numbers flatten. That combination is the signature of this specific failure, and it is why the problem is so often mistaken for a go-to-market issue: output is visible, direction is not, and the board conversation goes to the visible thing. Meanwhile the founder's own leverage falls, because the hours available for the decisions only they can make are exactly the hours everything else is competing for. The transition out of this pattern is covered in the guide to handing off product as a founder, and the timing question is in when to hire your first product leader.

Four options, one diagnosis. Promotion closes a capacity gap, a VP hire closes a management gap over a search that commonly runs 4–6 months, part-time senior leadership closes a direction gap in weeks, and continuing is defensible if it is chosen deliberately. Run the two-week test before deciding, because the diagnosis is what most technical founders get wrong, not the arithmetic.