Wiring an ai content generator into an agent loop taught me volume was never the constraint

Spent a chunk of this year building a content pipeline for a client as an agent loop. Research step, outline step, an ai content generator producing drafts, a self-review pass, then publish to their CMS. The idea was to go from a few pieces a week to a lot more. It worked, technically. It could produce more drafts than any human could. And that turned out to be the trap. Once the bottleneck moved off "can we produce enough," the real bottleneck showed up and it was quality control and relevance. We could generate 30 drafts. We could not meaningfully review 30 drafts. So either a human became the new choke point, or we published stuff that was fine but forgettable and it did nothing. The version that actually helped the client was slower on purpose. The agent generates three angles, a human picks one, and only then does it draft. The loop went from "make everything" to "make the right one well." Output dropped a lot and results went up, because someone was actually deciding what deserved to exist. I think a lot of agent builders, me included, chase throughput because it's the easy metric to move. But if downstream review can't keep pace, you've just built a faster way to create work nobody reads. Anyone else hit this wall where the agent removed the wrong bottleneck?