
The Next Hire Is a Workflow. Not a Headcount.
Before you write the job description, count the hours. Most agencies at capacity are not short of people — they are short of the hours they already pay for.
The subscription line is the cheap half of what a scattered stack costs. Here is how to price the other half, and the rule that decides what survives the audit.

Once a year somebody in your agency opens the card statement, sorts it by vendor, and discovers a $49 line item nobody has logged into since March. It gets canceled. Everyone feels efficient. The stack is exactly as expensive as it was the day before.
That is the shape of most tool audits: they find the dead subscriptions and miss the expensive ones. The $49 tool nobody uses costs you $588 a year. The $200 tool two people use badly, that nothing else talks to, and that produces the report a client argues with every month — that one costs multiples more, and it never shows up as a line worth canceling because somebody is clearly using it.
Agencies are unusually exposed here. According to Basis’s 2026 Advertising Agency Report, 36.8% of full-service and media agencies now manage ten or more tools — more than double the 17.3% recorded two years earlier. The pattern is not agency-specific either: Zylo’s 2026 SaaS Management Index puts the average organization at 305 applications, up from 275 the year before, including 9.9 project management apps and 9.5 team collaboration apps running side by side.
Nobody chose that. Stacks are not designed, they are accumulated — one tool per crisis, one per client demand, one per new hire who brought a favorite with them. This is how you take the accumulation apart.
A tool bills you once and charges you three times. Only the first charge appears on a statement.
The visible one. Easy to count, easy to negotiate, and almost always the smallest of the three. Note that seat-priced tools have a second-order cost: they tax you for growing. Any tool where adding a junior designer adds a line to the invoice is a tool that quietly argues against hiring.
The work a human does purely because two systems do not talk. Exporting a CSV from the ad platform to paste into the reporting deck. Re-typing a lead from the form tool into the CRM. Copying an approved caption from the doc into the scheduler. None of it is billable, none of it is skilled, and all of it is invisible until you count it.
Price it honestly: minutes per week × 52 × the loaded hourly cost of whoever actually does it. Not your rate — the rate of the account coordinator who really does it at 5:40 on a Friday.
The most expensive and the least measured. When four tools each hold a version of the truth, your monthly client report is a reconciliation, not a readout. Sessions in one place, conversions in another, spend in a third, and a number in the deck that matches none of them exactly. The cost is not the hour spent reconciling. The cost is the client call where a number is questioned and you cannot immediately defend it.
A tool is not expensive because of what it charges. It is expensive because of what it forces a person to do at the seam between it and the next tool.
One row per tool. One hour, one spreadsheet, the whole team in the room because nobody knows the whole stack alone. The columns matter more than the precision — you are looking for shape, not accounting.
| Column | What goes in it | Why it earns its place |
|---|---|---|
| Tool | Name, and the one person who owns the relationship | A tool with no owner is already a cancellation candidate |
| Seats / billing | Flat or per-seat, and the real seat count | Separates fixed cost from the cost of growing |
| Monthly | What it actually bills, not the list price | Annual prepays and legacy discounts hide here |
| Only it does… | The one job no other tool in the stack performs | If the cell is empty or duplicated, you have found an overlap |
| Feeds / fed by | Which tools it exchanges data with, and how | “Manually” in this cell is the swivel-chair cost |
| Client-facing? | Does a client ever see its output or log into it | Client-facing tools carry switching risk the others do not |
Two columns do the real work. Only it does… is where overlap becomes undeniable — when three rows all say “schedules social posts,” the argument is over. Feeds / fed by is where the hidden labor surfaces; every “manually” is a person, a recurring calendar block, and a place where numbers drift apart.
With the sheet filled in, every row resolves into one of three buckets. Work them in this order, because cutting is free and consolidating is not.
Consolidation is sold as pure upside. It is not, and going in clear-eyed is the difference between a migration that sticks and one that quietly reverts within two months.
Most platforms import current records well and historical activity badly. Three years of notes attached to a lead, the thread where a client approved something contentious, the audit trail from a campaign that went sideways — assume it does not move. Export it, store it somewhere you control, and do that before you cancel anything.
Every specialist tool has a depth the generalist does not match. That is a real trade, not a marketing objection. The question is whether that depth is load-bearing for client work or a preference. Ask the person who will lose it, in writing, what they use it for — you will get a straight answer and occasionally a genuine blocker.
Budget for sixty to ninety days of running both. A migration that also has to hit a cancellation date is a migration that will cut corners on exactly the data you needed.
A twelve-person web design studio runs eleven tools. The audit finds four rows whose only it does… cells overlap and four whose feeds / fed by cells say “manually.”
| Row | Verdict | Reasoning |
|---|---|---|
| Project management | Keep | Single owner, no overlap, delivery depends on it |
| Client portal | Consolidate | Overlaps file sharing and approvals; clients log in twice |
| File sharing | Consolidate | Duplicates the portal; “manually” in the feeds column |
| Rank tracker | Consolidate | Data re-keyed into the report deck every month |
| Report builder | Consolidate | Exists only because nothing else reports |
| Design tool | Keep | Best-in-class, load-bearing, nothing comparable |
| Form tool | Consolidate | Leads re-typed into the CRM by hand |
| CRM | Consolidate | Per-seat, half-adopted, fed manually from two places |
| Invoicing | Keep | Bookkeeper depends on it; financial system of record |
| Social scheduler | Cut | Bought for a client who churned in January |
| Screen recorder | Cut | No named owner; last login predates the last invoice |
Two cuts, three keeps, six consolidations. The interesting number is not the subscription saving — it is that six rows shared one failure mode. Every one of them existed because something upstream would not hand its data to something downstream. The studio was not paying for six tools. It was paying for six seams.
None of this requires a decision yet. It requires the sheet.
When you are ready to act on the consolidate column, the shortlist writes itself: the replacement has to cover every overlapping row, close the manual seams between them, and not reintroduce per-seat billing on the way in. That is the brief the nine modules behind one login are built to answer, and what seven client-facing surfaces on one workspace looks like in practice. If the seams you counted are mostly integrations with tools you intend to keep, start at the live integration directory instead — consolidation and connection solve the same problem from different ends.
Then run the other half of the audit. This one prices the money going out; the hours audit prices the capacity going out, and agencies at capacity usually find the second number is the one holding them back.