Your agency automates everything for clients — except your own pipeline
New business is the only agency work with no deadline attached — so it stops. What it means to automate the pipeline so it runs whether or not you're busy.
For B2B agencies running new business alongside client work
Every agency knows the pattern. Client work is full, so business development stops. Three months later a retainer ends, and suddenly new business is urgent — except the pipeline is empty, because nobody has spoken to a prospect since spring.
It isn't a discipline problem. It's that outreach is the only work in an agency with no deadline attached to it. Client deliverables have dates. Prospecting has good intentions.
Where it actually breaks
Feast and famine, structurally. Outreach happens when there's capacity, and capacity appears exactly when the pipeline is already empty. The result is a pipeline that's always three months out of phase with the need — busy when you have nothing to sell, empty when you do.
The follow-up nobody owns. A prospect replies "interesting, but not this quarter." Everyone agrees to circle back. Nobody puts it anywhere. Next quarter arrives and no one remembers.
Two people emailing the same prospect. Without a shared record, the account director and the founder both reach out to the same contact in the same fortnight with different pitches. It's a bad look, and it's common.
The reply that sat in someone's inbox. A prospect responds with real interest, to the personal inbox of whoever sent the campaign. That person is on a client call, then in a workshop, then on annual leave. The lead goes cold inside a warm inbox.
The campaign that quietly stopped sending. This is the one that actually hurts. A connection expires, or a sync fails, and the outreach simply stops. No alert, no error, no obvious symptom — just a slow decline in replies that gets attributed to the market being quiet. Weeks pass before anyone checks.
What automating it actually means
Agencies are usually good at the creative half of outreach — the positioning, the message, the list. What's missing is the machinery that makes it happen regardless of how busy the studio is.
Sequences that run whether or not you're busy. Multi-step outreach on a schedule, sent through working hours at a sensible pace. New business stops being a thing you find time for and becomes a thing that happens.
One shared view of who's been contacted. Every prospect, every touch, every reply in one place — so nobody double-approaches an account and nobody wonders whether that lead from March was ever followed up.
Replies read, classified and routed. Interested responses surfaced immediately to whoever should handle them. Declines logged and their sequences stopped. Out-of-offices left in the sequence, because they haven't seen it yet.
Sequences that stop the moment a human replies. Nothing damages a new business conversation faster than an automated chaser arriving after someone has already responded.
Opt-outs honoured permanently, across every list. Under PECR this isn't a courtesy — and it needs to be enforced by the system rather than remembered by whoever runs the next campaign.
The CRM accurate without anyone maintaining it. Status reflecting what actually happened, so your pipeline forecast is based on reality rather than on who remembered to update a record.
The uncomfortable bit
Most agencies build this the way they'd build it for a client: connect a sending platform to a scenario builder to a CRM, and wire it together. It's the obvious approach and it usually works — at first.
Then it fails, and it fails quietly. A credential expires and nothing tells you. A step skips records it can't match and swallows the error. An inbox stops being read while every dashboard still shows green. You find out when someone asks why the leads dried up, and the answer is that they dried up a month ago.
There's a cost before that too. Someone has to learn scenario design, figure out how the sending tool talks to the CRM, decide how records map and how replies get categorised. Agencies usually have someone technical enough to attempt it, which is precisely the trap — that person now owns a fragile system on top of their actual job, and when they're busy or they leave, nobody else can fix it.
The argument for building it properly isn't that assembled systems can't work. It's that when they break, they don't tell you — and an agency's pipeline is the last place you want a silent failure.
We build outbound and CRM automation for agencies. If your new business happens in bursts, or you're not certain your last campaign actually reached anyone, it's worth a conversation.
Agile Cookies is a London-based product studio. We build automation systems, mobile and web apps, and the platforms underneath them.
Want to build something?
If this guide has sparked an idea, we'd love to hear it.