Agency Operations

Automation for
Agencies

Lead capture, reporting and internal tooling for agencies. Stop paying three people to copy data between tools. You own the code.

Sound familiar?

  • Someone on your team spends a day a week assembling client reports by hand.
  • Leads arrive in four places and get worked twice, or not at all.
  • Your CRM costs more per seat than the junior using it, and you still export to a spreadsheet.
  • The clever process lives in one person’s head, and they are on holiday.

What I do about it

Internal tooling

The CRM or tracker your process actually needs, instead of bending your process around someone else’s product.

Client reporting

Generated from the source data on a schedule. Nobody assembles a deck by hand.

Lead routing

One inbox, scored and assigned, so nothing is worked twice or dropped.

Delivery pipelines

The repetitive part of shipping client sites, done the same way every time.

A job I actually did

Anonymised. Sector, size and region only, never a client name. The work and the numbers are real.

Who: A UK agency running outbound at volume alongside a delivery team building client sites.

Before: Prospect data lived in spreadsheets, audit reports were assembled by hand, and the tools between sales and delivery did not talk to each other. The reporting alone was consuming most of a full-time role.

Built:
  • A Flask and SQLite operations CRM for prospect tracking and campaigns, owned outright rather than rented per seat.
  • Automated PDF audit report generation straight from website audit data.
  • Lead-scoring loops that route qualified prospects instead of leaving them in a queue.
  • Delivery pipelines behind 100+ client sites across Shopify, WordPress and React.

After: Over 34,000 leads processed and more than 19,000 audit reports generated without anyone assembling them. The manual reporting workload dropped by roughly 94%, which is a role’s worth of time returned to work that bills.

What went wrong: An SMS notification step quietly burned through credit far faster than budgeted. The messages had grown past the 160-character limit, so every send was silently billing as three segments rather than one. Nothing errored, the sends all succeeded, and the only symptom was the bill. Message length is now capped before send and the spend is checked against expected volume, because a system that fails by costing money rather than by breaking is the kind you find late.

Questions

Should we build internal tools or buy them?

Buy, until the per-seat cost passes what the tool saves, or until you are exporting to a spreadsheet to do the actual work. Both of those are signals the product does not fit your process. Below that line, buying is the right call and I will say so.

What does agency automation actually cost?

A one-off build fee, then hosting, which is usually single-digit pounds a month because these systems are small. The comparison worth making is against the salaried hours currently spent on the manual version, not against a SaaS subscription.

Will this replace our CRM?

Sometimes. More often it sits alongside it and removes the copying between systems. Ripping out a working CRM is rarely the cheapest fix, whatever the demo suggests.

What happens if you disappear?

The code is in a repository you own, in ordinary Python and JavaScript, documented. Any competent developer can pick it up. That is the point of not building on a platform you rent.

How long does it take?

A single automation is usually days. A full operations tool is weeks. I would rather ship the one process costing you the most time and let you judge the result before committing to more.

Tell me what you need

No pitch deck, no discovery call to book another discovery call. Describe the job and I will tell you what it takes, or tell you that you do not need me.

Or see what I have built and the free tooling.

BareBOT

Mountain guide for the stack.

BareBOT online. Ask about BareStackOS, self-hosting, docs, or what kind of custom system fits your workflow.

Free CRM guideDocs