Skip to content
Anthony Keal Book a 20-minute call
Anthony Keal
Book a 20-minute call

Or contact me here.

Agency Delivery Operations Case Study

Agency delivery operations for a growing team: 3 to 9 people, 20+ projects at once

Three years as digital production lead at a Melbourne agency, building the ClickUp, deployment pipeline and delivery systems behind a team that grew from 3 to 9.

9people in a production team that grew from 3, on the delivery systems I set up
20+concurrent client projects
1core platform: Craft CMS
Role
Digital Production Lead at a Melbourne digital agency (three years, in-house)
Scope
Delivery operations, project management systems, deployment pipeline, platform standardisation

The situation

Agency delivery has a scaling trap. At three people, everything runs on shared context: everyone knows every project, and process is whatever the room agrees over coffee. Somewhere past that, shared context stops scaling. Projects collide over the same resources, estimates drift because nobody owns the method behind them, and the agency's margin quietly leaks into unbilled recovery work.

The agency was winning more work, and the production team grew to match it. My job was making sure the way we delivered could carry that growth.

What I did

Built the delivery systems a growing team needed. Over three years, as the business grew, the production team went from me and two developers to nine people carrying more than twenty concurrent client projects. The hiring was the agency's call. My part was the operating system around the people: project intake, resourcing, estimation discipline, and the reporting that lets an agency see trouble two weeks before the client does.

Rebuilt the project management system from the architecture up. The first job was ClickUp. The tool was in place but the architecture underneath it wasn't right, so the team worked around it instead of through it, and project budgets weren't being tracked at all. I re-architected the workspace to match how work actually flowed through the agency, which turned it from a box-ticking exercise into the operating system the delivery function ran on, with budget tracking built in so every project's margin was visible while it could still be protected, not after.

Set up a deployment pipeline for a bigger team. Developers were deploying changes by hand in the terminal, which was unnecessary work on every release. I set up a pipeline where developers submitted code as a change request, it was reviewed, and only then deployed. Each app ran its build steps automatically on deploy, so nobody had to run them by hand.

Introduced Craft CMS as the agency's core platform. Platform sprawl is an agency margin killer: every project on a different stack means no reusable tooling, no transferable skills, and every estimate starting from zero. I made the case for Craft CMS and led its adoption as the standard build platform, which compounded with every subsequent project: faster estimates, deeper team expertise, and a better product for clients who needed a CMS their editors could actually use.

Ran delivery at leadership level. Twenty concurrent projects means the interesting problems are never inside one project. They're in the portfolio: which client gets the senior developer this fortnight, which fixed-price job is quietly going underwater, and which account needs a hard conversation before it becomes a bad debt.

The results

  • ClickUp and a reviewed deployment pipeline in place for a production team that grew from 3 to 9 as the agency grew
  • 20+ concurrent client projects running through a single, governed delivery function
  • Craft CMS established as the core platform, still central to how the agency builds today
  • Project budgets tracked as standard, giving leadership margin visibility that hadn't existed before

What this shows

Agencies are my other client base, and this is why: I've run delivery inside one at scale. When I work with agencies now on operations and delivery, or when I sit client-side managing an agency, the experience behind the advice is three years of resourcing spreadsheets, estimation post-mortems, and portfolio calls, not a framework from a book.

Anthony Keal

Got more work than people?

Tell me the project and the deadline. I'll tell you straight away whether I can take it.

Book a 20-minute call or send me a message. I answer both myself.

Bigger project? I bring in Keal Collective, vetted people I work with, and stay your lead.