The fragmented-stack margin tax: how to measure it

Most agency owners feel the stack tax. Few can put a number on it. This note gives you a working model you can run on the back of an envelope, and a way to read what the number is telling you.

What the stack tax actually is

Every additional tool in your delivery stack adds a small per-week cost in three places: the time to keep records in sync, the time to pull data back out for reporting, and the senior time spent reconciling when the records disagree. None of these line items show up on an invoice. They show up as margin you cannot find at the end of the quarter.

The simple model

Pick a representative week. For each of the seven workflows below, write down the number of hours your team spent and who did them. Multiply by 50 weeks and by a fully loaded hourly cost. The total is your annual stack tax.

• Reporting assembly across tools
• Status updates and client comms
• Approvals routing and chase
• Data reconciliation between PM, time, and billing
• Onboarding a new client into all systems
• Tracking deliverables across freelancers or specialists
• QA before anything goes out the door

Reading the number

A number under five percent of agency revenue is normal and not worth restructuring for. Between five and ten percent is the band most agencies sit in. Above ten percent is where the stack tax starts paying for a full agent team on its own.

What to do with it

Do not buy more tools. Tools add line items. Consolidate the work onto one shared record and have one accountable owner of the operating metric. That is the only intervention that moves this number.