Comparisons

AI tools for agencies: what actually saves time

Two hours a week each across a hypothetical 12-person agency is 1,104 hours a year. Saved hours only become money if you can sell or reclaim them — here's how to tell which tools do that.

·5 min read

The useful question about AI in an agency isn't which tools are best. It's which parts of agency work are actually shaped like something a model does well — and then whether the time saved turns into money or just evaporates.

Both halves matter, and the second one gets skipped.

Saved hours are not saved money

Take a hypothetical 12-person agency where every person saves two hours a week. Over 46 working weeks that's 1,104 hours a year.

That number means nothing on its own. It becomes money in exactly three ways:

  1. You sell the capacity. More projects with the same headcount. Requires demand you don't currently have.
  2. You avoid a hire. Real, but only if the saved hours are concentrated enough to remove an actual role rather than spread thinly across twelve calendars.
  3. You deliver fixed-price work for less cost. The most reliable one. On fixed price, cost reduction goes straight to margin.

If none of those applies, the time is absorbed. Work expands, meetings fill the gap, and you have paid for subscriptions and got a slightly more pleasant week. That's not nothing, but don't put it in a business case.

Before adopting anything, name which of the three you're chasing. It changes what you should adopt.

Where the time genuinely is

Sorted by how reliably agencies see a return.

First drafts of structured writing. Proposal boilerplate, scope descriptions, case study outlines, status updates, meeting notes into actions. The work is real, it's largely non-billable, and a mediocre first draft that takes ninety seconds beats a blank page that takes forty minutes. Requires editing, always.

Research and synthesis. Competitor scans, market context for a pitch, reading a long RFP and pulling out the requirements and dates. Verification is non-optional — this is where fabricated detail slips into client-facing work.

Code and technical scaffolding. Boilerplate, test cases, refactors, unfamiliar API syntax. Reliable in the hands of someone who could have written it themselves and can therefore spot when it's wrong. Much less reliable otherwise.

Volume creative variation. Fifteen ad headline variants, resizing a concept across formats, alt text. Not the idea — the permutations around the idea.

Transcription and summarisation. Client calls into notes and action items. Small per instance, constant across the week, low risk.

Where it's thinner than the marketing suggests: original strategic thinking, anything where the value is your specific judgement about this specific client, and anything the client is paying you personally to have an opinion about.

Choosing between the shapes of tool

ShapeStrengthWatch for
General assistants (Claude, ChatGPT and similar)Flexible, cheap to try, cover most of the drafting and research casesNo workflow context; output quality depends heavily on the person prompting
AI features inside tools you already ownZero adoption friction, has your data in contextDepth varies enormously; easy to overrate because it's convenient
Specialist point toolsDeep at one job, often the best result for that jobSubscription sprawl, and the job may be absorbed into general tools next year
Custom internal workflowsFits your process exactly, compounding advantageReal build and maintenance cost; needs an owner

Capabilities in this category change faster than in any other software market. Anything specific written about a given product today may be wrong in six months, so treat vendor claims — and comparison articles — as perishable and check current documentation before committing.

The two rules that keep this safe

Client data. Know what you're allowed to put into which tool. Some client contracts prohibit third-party processing outright; others require disclosure. Check before, not after. A single breach of a confidentiality clause costs more than every subscription you were considering.

Verification. Models produce plausible wrong things — a statistic that doesn't exist, a legal detail that's subtly off, a citation that was never written. Anything leaving the building gets read by a human who is accountable for it. That review time is part of the cost, and if a task needs so much verification that you'd rather have written it yourself, the tool is losing money on that task.

Pricing is the harder question

If AI genuinely halves the effort on a service line, hourly billing quietly converts your productivity gain into a revenue cut. The same job, honestly tracked, invoices for less.

There's no clean answer, but the direction is clear enough: the more work becomes cheap to produce, the more pricing has to attach to the outcome and the judgement rather than the hours. That's a commercial redesign, not a tooling decision, and it's slower and more uncomfortable than buying subscriptions.

Note also what stays expensive. Deciding what to build, knowing which client request is a trap, reading the room in a stakeholder meeting, being accountable when it goes wrong. Those don't get cheaper, and they're increasingly what clients are actually paying for.

Adopt narrowly, then measure

The failure pattern is buying six tools, mandating none, and finding a year later that two people use one of them.

A better sequence:

  1. Pick the single most repetitive non-billable task in the agency. Usually proposal drafting, status reporting, or turning calls into notes.
  2. Give it to two people for a month. Not everyone. Two people who want to.
  3. Have them write down the before and after time for that one task. Rough numbers are fine; consistency matters more than precision.
  4. If it holds up, document how they did it — the actual prompts, the review step, the rule about client data — and roll that out.
  5. Then pick the next task.

This is slower than it sounds like it should be, and it's the only version that produces a change you can still see six months later.

The measurement that matters

Whatever you adopt, watch utilisation and margin rather than a subjective sense of speed.

If AI is genuinely working, one of two things shows in the numbers: non-billable hours fall while billable hours hold, or delivery cost on fixed-price projects drops while the quoted value stays the same. If neither moves after a quarter, the time saved is being absorbed somewhere — and finding out where is more valuable than adding another tool.

Start by writing down the one repetitive task you'd hand over first. If you can't name it, that's the finding.

Keep reading

All articles