Every Layer of Review Makes You 10x Slower

Here's a rule of thumb that will change how you think about building software: every layer of approval makes your process 10x slower.

It sounds extreme. It feels unfathomable. But every time I look for evidence of this pattern, there it is—annoyingly true.

That's not effort—that's wall clock time. Most of it is spent waiting. Sitting idle. Watching your momentum evaporate.

The AI Trap

Now here's where it gets interesting. AI coding agents like Claude and Cursor are incredible. They can write code in 3 minutes instead of 30. That's a 10x improvement on the doing part.

But the review layers? They're still there. They're still slow.

The result? You ship faster, but you wait longer. The bottleneck has just moved downstream.

The "AI Developer's Descent Into Madness"

There's a pattern emerging in teams that go all-in on AI coding:

1. "Whoa, I produced this prototype so fast! I have super powers!"
2. "This prototype is getting buggy. I'll tell the AI to fix the bugs."
3. "Hmm, every change now causes as many new bugs as it fixes."
4. "Aha! But if I have an AI agent also review the code, it can find its own bugs!"
5. "Wait, why am I personally passing data back and forth between agents?"
6. "I need an agent framework."
7. "I can have my agent write an agent framework!"
8. → Return to step 1

It's a spiral. And it's happening to talented engineers right now.

Why We Review (And Why It Hurts)

Let's be clear: reviews exist for a reason. As companies scale, mistakes become more expensive. The average value added by a new feature eventually becomes lower than the average value lost through the bugs it causes.

So we add checks. Controls. Layers. More reviews. More approvals.

The quality goes up monotonically. But so does the latency.

What Indie Hackers Do Differently

Here's the secret: you don't have to play the same game.

As a solo builder or small team, you have something that enterprises desperately try to engineer around: zero approval layers.

The Bottom Line

AI makes you 10x faster at writing code. But if you keep the same approval layers, you've only solved 10% of the problem.

The real unlock is recognizing that velocity is a system design problem, not a tooling problem.

Build your system accordingly.