What a custom agent looks like inside an agency — the ten roles in your language, and what each plugs into in a shop running a project system, time tracking and a dozen client platforms.
last reviewed
An agency's economics come down to one number nobody has in front of them: what each client actually costs to serve against what they pay. Everything that erodes it is administrative — scope creep nobody logged, time nobody recorded, reports assembled by hand every month, and approvals that sit for a week. The project system holds the work. What it does not hold is the client's own platforms, where the results live, or the conversation where the scope quietly changed.
The honest version of "does it integrate with my software." These are the systems this industry actually runs on, and what each one means for a build.
The system of record for work in progress. All integrate readily, which makes them the anchor for status, assignment and anything about what is stuck.
The input that makes profitability visible, and the one people skip. Anything that captures time without asking for it changes the economics of the firm.
Google Ads, Meta, GA4, LinkedIn and the rest. Where reporting data lives, across as many accounts as you have clients, each requiring its own access.
Where leads land for clients who track them. The bridge between what you spent and what it produced, and usually the hardest data to assemble.
Figma, Adobe and shared drives. Version confusion and approval chasing are the recurring costs here.
Either a dedicated tool or email. Where deadlines quietly slip while everyone waits on one person.
Retainers, project billing and pass-through media spend, which is the number most likely to be reconciled badly.
Each of these is a real build, not a feature of a product you already pay for. Follow one through to see how it works in general.
Nothing you are owed gets dropped.
Whatever arrives, in whatever format, becomes a clean record.
Writes the recurring document from your own past work.
Knows what expires, renews or comes due — and says so first.
Answers from your own records, not from the internet.
The conversation becomes the record, without anyone typing it up.
Assembles the recurring report from systems that do not talk.
Matches two sets of records and queues only the exceptions.
Two systems that do not talk, now talking.
Applies your rules, escalates only what needs judgment.
If that is a job in your business, the next step is half an hour on a call. Bring whatever you know about the volume — how many a month, who owns it now, which systems it touches. That is enough to scope it properly and quote it flat before anything starts.
Everything in this library is built to order rather than bought off a shelf — and whatever I build, I host and maintain. The rest of the library is here.