1
0 Comments

AI didn't remove your bottleneck. It moved it — and I think most of us are optimizing the wrong station

I have a folder of repos that all got to about 80%. Auth works. Core loop works. There's a deploy with a real URL somewhere. And then nothing — no launch, no users, no Stripe key in prod. Four or five of them, sitting next to each other.

For years I blamed time, skill, or the stack. Then AI removed all three excuses at once. The folder kept growing. That's the part I can't stop thinking about.

The question going around is "is AI making me obsolete?" — and I think that's the wrong question. The one that actually stings is: why am I not finishing anything, now that building got easy?

Goldratt's Theory of Constraints has a useful answer. Every system has exactly one bottleneck. And when you lift it, it doesn't vanish — it relocates to the next station. "Writing the code" was the constraint for most of us for a long time. AI lifted that ceiling. So building throughput shot up, and the constraint quietly slid one station down the line.

It landed on follow-through.

Theory of Constraints diagram on a dark background. A horizontal pipeline runs IDEA → BUILD → FINISH → SHIP. A gold arrow curves from BUILD, labeled "AI lifted the ceiling," to FINISH, labeled "the new constraint." Headline: "The bottleneck does

Here's the part I want to put up for discussion, because it's counterintuitive: better build tools make the gap wider, not narrower. Agentic coding, one-shot generators, AI pair-programmers — they 10x a station that's no longer the bottleneck. Through the TOC lens, that doesn't raise throughput; it just stacks a bigger pile of half-built work in front of the real constraint. A faster builder pointed at an unmoved finishing problem generates a larger graveyard, faster.

Which means finishing isn't the chore you do after the differentiation. Finishing is the differentiation now — it's the one part of the pipeline this cycle didn't commoditize.

The way I frame it for myself: AI makes you a builder. The work makes you a finisher. That shift happens somewhere no tool reaches — in the boring, repeated act of returning to the same unfinished thing until it's actually out.

I'm a solo dev with a full-time job building toward exactly this problem in the open, so I'm not neutral. But I'm genuinely curious where the IH crowd lands:

- What's your repo-to-shipped ratio honestly?

- Has AI made you ship more, or just start more?

If you'd rather see what I'm building than take my word for it, it's here: https://mvpbuilder.io/?utm_source=indiehackers&utm_medium=post&utm_campaign=cohort2&utm_content=bottleneck — but the question stands on its own whether or not you click it.

posted toAvatar for product MVP Builder
MVP Builder