Brendan ElgieSoftware & Systems Consultant

Product · For media agencies

Budget pacing that catches drift before month end.

One screen that answers one question: which accounts need me today. Deployed into your own infrastructure, not rented from mine.

  • 12Agencies running it
  • $1M+Monthly spend per deployment
  • YoursCode, hosting and data
The pacing dashboard: total monthly budget, spend to date, days complete, and a table of client accounts with a pacing bar and a status pill. One account is flagged as needing attention.
A live month. Client names replaced with sector labels, figures real. Sixteen accounts, roughly a million dollars of spend, and on this day exactly one of them needed a person.
02

Pacing is the number that has to be right every day.

It is also the one that gets checked when somebody has time. A spreadsheet holds up until you have sixteen accounts, several channels each, and a month that ends on a Tuesday.

The failure is never a wrong number. It is a number nobody looked at until it was too late to correct.

03
  • 01

    Pace, not spend

    Every account is measured against where it should be given how much of the month has elapsed. 73% spent is not good or bad until you know it is day 28.

  • 02

    Exception first

    Anything off pace sorts to the top. On a normal day the useful part of the page is the first two rows, and most days it is empty.

  • 03

    Per channel, not just per client

    Accounts expand to their individual channels, so a book that looks fine in aggregate still surfaces the one channel that stalled.

  • 04

    Alerts on the exception

    Notifications fire when something is actually wrong. A daily digest that says everything is fine trains people to delete it unread.

04

You are not buying a seat.

Most tools in this category want your spend data on their servers and your team on their pricing page. This one gets installed into your account and signed over to you.

HostingYour Cloudflare account. Your Workers, your database, your domain. Nothing runs on infrastructure I control.
CodeYour GitHub organisation. You get the repository, not a licence. Any developer you hire can read it, change it, or fork it.
DataSpend and channel data goes from the ad platforms into your account and stops there. It never passes through a vendor, mine included.
AccessYour team, your identity provider, your access rules. No seats to buy and nobody outside your org with a login.
Running costCloudflare’s free tier covers a typical agency book. There is no per-seat or per-account pricing to grow into.
ExitThere is nothing to negotiate. It is already yours, on your infrastructure, in your repository.
05

Live in about two weeks.

It is a template, so you are paying for the setup and the fit to your book, not for someone to build a dashboard from scratch.

Read the original build: the agency it was made for.

Week 1Connect the ad platforms, map your accounts and channels, deploy into your Cloudflare account.
Week 2Pods and teams configured to match how your account managers are actually organised. Alerting tuned.
HandoverRepository transferred, walkthrough session, and written documentation for whoever maintains it next.
AfterOptional support, or nothing at all. The handover assumes you might not want me involved.

Next step

See it with your own numbers.

Send me the shape of your book, how many accounts and which channels, and I will show you what the first screen would look like for you.