The Agency Project Management Workflow, Mapped End to End

Ask ten agency owners to draw their project management workflow and you'll get ten different diagrams, but the failure points are almost always the same three: the sales handoff, the client review loop, and the close. I've mapped this workflow for dozens of agencies now, from two-person shops to 40-person firms, and the version that actually holds up isn't more complex than what most teams already do — it's just explicit about the handoffs nobody usually writes down.

Mapping the seven stages

1. Sale

The deal closes. What matters for delivery: what was actually promised (not just what's in the contract), the client's real priority, and any verbal commitments made during the sales process. If sales doesn't capture this somewhere delivery can see it, it's gone the moment the account manager changes hands.

2. Handoff

The single most under-invested stage in agency delivery. A written summary loses tone, priority and the things the client said but didn't put in writing. Run this as a live call — sales, the new project lead, and the client if possible — within a day or two of signing. I go into this in more depth in how to run a client onboarding project.

3. Kickoff

The client-facing start. Introduce the team, confirm the plan and milestones, set the cadence for updates, and get the first round of information or access moving. This is also where you set expectations for the review process in stage 6 — how many revision rounds, what "approved" means.

4. Scoping and planning

Turn the sold scope into a real plan: tasks, owners, dependencies, and dated milestones. For anything beyond a small project, this deserves its own short internal meeting before work starts, not an assumption that everyone read the SOW the same way.

5. Active delivery

The work itself, with a regular status cadence — see project status report template for the format. This is the longest stage and the one most tools are built around, but it's not where most agencies actually lose money or trust; the handoffs on either side of it are.

6. Review

Client feedback rounds. Define the number of rounds up front — two is typical for creative work — and track each round's scope explicitly. Undefined review loops are how a "quick tweak" becomes six weeks of unbilled revisions.

7. Close

Formal sign-off, final invoice, and a short internal retrospective: what took longer than estimated, what the client asked for that wasn't in scope, what you'd change next time. Skipped constantly, and cheap to add back — 30 minutes, once, per project.

Where the workflow actually breaks

McKinsey's work on service delivery operating models makes a broader version of this same point: most delivery failures trace back to handoffs between functions, not to the quality of work within any single function.

Sizing the workflow to the project

A $3,000 one-week project doesn't need a formal scoping meeting and a seven-stage Gantt chart — it needs the same seven stages compressed into a checklist, some of them combined into a single conversation. A $150,000 six-month engagement needs each stage to be a real milestone with its own owner and date. The mistake is either applying heavyweight process to small projects (killing margin on light work) or applying no process to large ones (guaranteeing scope disputes). Template the stage sequence once, and flex the depth per project size.

The review loop specifically

This deserves its own callout because it's the single biggest source of scope creep I see. Define at kickoff: how many rounds of feedback are included, what counts as a "round" (a batch of consolidated feedback, not five separate emails over two weeks), and what happens beyond that limit (a change order, additional hours, or a straightforward no). Put this in writing in the kickoff materials, not just verbally on the call — verbal agreements are the first thing forgotten when a client asks for "just one more small thing."

Closing projects properly

A retrospective doesn't need to be formal. Fifteen minutes with the delivery team, three questions: what took longer than we estimated, what did the client ask for that wasn't in the original scope, what would we template differently next time. Feed the answers back into your scoping template so the next project of that type is quoted and planned more accurately. Agencies that skip this step re-learn the same lessons project after project, because nothing captured them the first time.

Putting the workflow in one system

This entire sequence, sale through close, tends to work better when it lives on top of one client record rather than a CRM for the sale and a separate tool for delivery. The handoff stage specifically is much easier when the delivery lead can open the same client record the salesperson used, rather than reconstructing context from a summary email. That's the case for project management with a built-in CRM and, more broadly, for an all-in-one CRM and project management setup — see also a project management tool built for agencies specifically.

The workflow itself isn't the hard part; most agencies already do something close to these seven stages informally. The discipline that separates smooth delivery from constant fire-fighting is making the handoffs explicit — especially the two nobody wants to spend time on, handoff and close — and templating the sequence so it scales without becoming bureaucracy.