Blog

We recently audited an entire Salesforce delivery stream — 149 merge requests across a single client engagement, start to finish — and asked one question the usual retrospective never asks. Not what shipped, but where a later change had to revert, re-cut, or re-baseline what an earlier one got wrong. About a quarter of the merge requests were rework. And when we grouped that rework by root cause, one pattern sat underneath almost all of it, surfacing in cluster after unrelated cluster.

Most companies that experiment with AI agents discover the same uncomfortable truth: building them in-house is substantially harder than the demos suggest. The technology works — when context is fresh, tasks are narrow, and someone is watching. The problems surface at scale: agents that hallucinate midway through a workflow, token budgets that spiral, scope that drifts the moment you try to generalize a working prototype into production. Managed AI services solve these problems structurally, not through heroics — and that structural difference is the argument this piece makes.

Rework rarely announces itself. It shows up disguised as productivity — a revert here, a "fix:" follow-up there, a branch quietly closed and re-cut on a new base. Each looks like a small course correction. In aggregate, they are the single largest tax on a delivery stream, and in an agentic one — where an AI author ships fast and there is no default human reviewer standing between the model and the merge button — they compound faster than anyone expects.

Every services firm runs on the same hidden equation, whether or not anyone has written it down: revenue is a function of headcount. To grow, you hire. To take on more work, you staff up. To protect margin, you push utilization. The whole apparatus of an agency, a consultancy, or a professional-services firm is a machine for converting human time into invoices, and the better you run it, the more cleanly that conversion happens.