Field Notes

Where your agency invoice actually goes

May 18, 2026 5 min

We’re allowed to write this article because we ran the thing we’re describing. A digital agency group: 1,000+ people, 19 countries, 25 agencies. This isn’t an outsider throwing stones. It’s an autopsy by the surgeon.

The anatomy of an invoice

Take a €100,000 agency project. Roughly speaking — and yes, it varies, but not as much as agencies claim — here’s what the money buys:

Account and project management layers. The account director, the account manager, the project manager, the traffic manager. None of them produce the work. All of them are necessary — in that model. When fifteen people across four departments touch a project, someone has to keep the plates spinning. You pay for the plate-spinning.

Internal coordination. The status meetings, the internal reviews before the client review, the alignment calls before the status meetings. A creative team of six spends a documented, depressing share of its week talking about the work instead of doing it.

Handover loss. Strategy hands to creative. Creative hands to production. Production hands to development. Development hands to QA. At every border, information evaporates and gets expensively rediscovered. The wireframe said X, the design shows Y, the developer built Z — you’ve lived this.

Overhead and margin. Offices in good neighborhoods, group management fees, and margin on all of the above — including margin on the coordination. You pay a markup on the meetings.

The actual work. What’s left. The strategy thinking, the design craft, the code, the copy. The part you wanted.

None of this was a scam

Here’s what outsiders get wrong: this structure wasn’t parasitic. It was load-bearing. Large teams genuinely cannot function without coordination layers. We didn’t build that machinery because we liked it; we built it because at 100+ people there is no alternative. The model was honest. It was just expensive by necessity.

The question was never “why do agencies charge so much?” The answer was visible to anyone who worked inside one. The question was always: “what would make the structure unnecessary?”

What changed

Agentic AI didn’t make designers faster at Figma. That’s the shallow version.

What it actually did: it made small teams capable of large-team output. One senior person directing agents produces what used to require a pod of five — plus the pod’s project manager, plus a slice of the account team above them. When the team is two people and a fleet of agents, there is nothing to coordinate. The layers don’t get optimized. They get deleted.

Remove the structure and you remove the cost. Not 15% removed — the category removed.

The uncomfortable math

That’s why “up to 20× less cost” is not a marketing number. When 70–80% of an invoice was structure, and the structure goes away, and the remaining work is amplified by agents — the multiplication is just arithmetic.

The old model isn’t dying because it was wrong. It’s dying because its reason to exist — the coordination problem of large teams — stopped existing first.

If you’re still buying from the old model, you’re paying for a solution to a problem your vendor no longer needs to have.

Try the quote translator with a real number from your inbox.



Tell us what you want to build.

We'll tell you if we should work together.
A short conversation. No theatre. No deck. No delay.