Systems, SOPs and healthy margins

0:00 Systems, SOPs and healthy margins

Here's a painful discovery many new agency owners make. Revenue has doubled, the team has grown, everyone's busy, and yet there's less profit than when it was just you. How? Thin margins, hidden rework, projects that overrun, and people who are busy but not billable. In this lecture, you'll learn to run an agency as a system: standard operating procedures with AI steps and quality gates, clear roles, project margins, utilisation and capacity, the tools stack, and a monthly numbers routine that shows you what's really happening.

0:38 Why it matters

Why does this matter? Because an agency's profit lives in the gap between what you charge and what it costs to deliver, and that gap is easy to lose. A project priced well can still lose money through scope creep, inefficient handoffs or rework. And with a team, you can't see everything personally. Here's the key idea. What gets documented gets repeated, and what gets measured gets managed. SOPs make quality repeatable. Margins and utilisation make profit visible.

1:12 The restaurant chain analogy

Here's an analogy. Think of a restaurant chain versus a single brilliant chef. The chef can make a wonderful meal by instinct. A chain needs every branch to serve the same dish at the same quality, at a predictable cost, every day. So it writes recipes, trains staff, weighs ingredients, and tracks food cost as a percentage of the menu price. An agency is closer to the chain than the chef. SOPs are your recipes. Your project margin is your food cost percentage. And utilisation is how much of your kitchen's time goes into dishes customers pay for.

1:55 SOPs

Let's start with SOPs, standard operating procedures. Each one needs an owner, a trigger, a definition of done, and numbered steps. In 2026, add two things. Mark every AI step, with the approved tool, the saved prompt and the inputs allowed, for example aggregated metrics only, no personal data. And put a quality gate straight after each AI step: do the numbers match the source, do the insights make sense, are there any invented causes? Then add metrics for the SOP itself, like on-time rate and hours per run. Start with your five most frequent processes. Don't document everything at once.

2:39 Roles and margin

Next, roles and quality. Even a four-person agency needs clear roles: who owns the client relationship, who delivers, who reviews, who invoices. Use a simple RACI for key processes: who's Responsible, Accountable, Consulted and Informed. And build quality into the process with checklists and peer review, not heroics at midnight. Then the numbers. Gross margin per project is the fee, net of platform and payment fees, minus delivery costs: team hours at an internal cost rate, subcontractors, and tools or AI usage charged to the project. Divide by the fee to get a percentage. Set a target range and track every project against it.

3:24 Worked example 1: project margin (illustrative)

A simple worked example, illustrative, in pounds. A website project with a fee of eight thousand, net of fees. Team time: sixty hours at an internal cost of thirty-five pounds an hour, that's two thousand one hundred. Subcontractors: one thousand five hundred. Tools, AI usage and stock images charged to the project: two hundred. Total delivery cost: three thousand eight hundred. Gross profit: four thousand two hundred. Gross margin: fifty-two and a half percent. Then allocate a share of overheads, say one thousand six hundred, and the project contributes two thousand six hundred to profit. Now, what if the team had spent ninety hours instead of sixty? That's the lesson of the next scene.

4:14 Estimates, utilisation, capacity

Here's the answer. At ninety hours instead of sixty, team cost rises by one thousand and fifty pounds, and gross margin falls to about thirty-nine percent. So the gap between estimated and actual hours is often your biggest margin lever. That's why you track time against estimates on every project. Next, utilisation: billable hours divided by available hours. If a designer has thirty-seven and a half hours available and bills twenty-six, utilisation is about sixty-nine percent. Don't aim for a hundred percent. People need time for sales, learning, rework and illness. Plan capacity four to six weeks ahead by comparing committed hours with available hours.

5:00 Worked example 2: a Dubai agency (illustrative)

Now the realistic scenario, illustrative. A six-person marketing agency in Dubai had strong revenue but thin profit. The founder, Rashid, measured three things for a quarter: estimated versus actual hours per project, utilisation per person, and margin per client. Three findings. Monthly reports took twice the estimated time. One large client had a margin under twenty percent because of constant unbilled requests. And two senior people were only forty percent utilised because they handled all the admin. He fixed it: a report SOP with an AI summary step and QA gate, a change order process and a price review for the large client, and an operations assistant to take admin off the seniors. Margins recovered within two quarters.

5:51 Watch me: a report SOP

Watch me write an SOP for monthly reports, using the lesson template. Owner: account manager. Trigger: the first working day of the month. Definition of done: sent by the fifth working day. Step one: export data from Google Analytics, the ad platforms and the CRM into the report sheet. Step two, the AI step: the approved assistant with the saved prompt, and only aggregated metrics as inputs, no personal data. Step three, the QA gate: numbers match the source, insights make sense, no invented causes. Step four: add three human recommendations and get a manager review. Step five: send it and book the review call. Metrics: on-time rate, client questions per report and hours per report.

6:41 Tools and monthly numbers

A quick word on your tools stack. Choose one tool per category and use it well. Project management, like Notion, ClickUp, Asana or Trello. Time tracking, like Toggl Track, Harvest or Clockify. A CRM, like HubSpot or Pipedrive. Docs and knowledge in Notion, Google Workspace or Microsoft 365. Reporting in Looker Studio or spreadsheet dashboards. Automation with Zapier, Make or n8n. And AI assistants on business plans with data controls appropriate to client work. Then the monthly numbers routine: revenue, gross margin by project and client, utilisation, pipeline, cash and receivables, and estimated versus actual hours. Thirty minutes, every month, without fail.

7:25 Common mistakes

Let's list the common mistakes. Documenting nothing, so quality depends on who's working. Documenting everything at once, so nothing's maintained. AI steps with no quality gate. Pricing projects without knowing your internal cost rate. Never comparing estimated and actual hours. Aiming for a hundred percent utilisation and burning people out. Tolerating a low-margin client because they're big. Too many tools. And looking at revenue instead of margin. Revenue is vanity. Margin is sanity. Cash is reality.

7:58 Recap and try this now

Let's recap. Run your agency as a system. Write SOPs for your top processes, with AI steps marked and a quality gate after each. Define roles. Calculate gross margin on every project from real delivery costs, track estimated versus actual hours, and plan utilisation and capacity with a buffer. Keep a lean tools stack and a monthly numbers routine. Your try this now: calculate the margin on your last three projects with the calculator, write one SOP with an AI step and QA gate, and book thirty minutes a month for your numbers. Next, we'll keep clients longer and grow sustainably.