The agency client lifecycle, stage by stage
An agency client moves through six stages: inquiry, proposal and signature, kickoff and onboarding, delivery and client approvals, monthly reporting, then renewal or wind-down. Each stage hands off to the next, and each handoff needs one owner. The stalls that cost the most margin come after kickoff, in work waiting on client approval, the monthly report and retainer setup.
Most agency owners can describe how a lead turns into a signed client. Ask about the rest of that client's time with the agency, from the day they sign to the day they renew, and the answer gets vaguer, because that part runs on habit and on whoever is on the account. It's also where the margin on the account is made or lost, and where the client decides whether to stay.
- Inquiry
- Proposal and signature
- Kickoff and onboarding
- Delivery and client approvals
- Monthly reporting
- Renewal or wind-down
Six stages, who owns them, and where they stall
Every stage ends in a handoff, where the client or the work moves from one person to the next. A stage on its own usually works. Work stalls at a handoff nobody owns, or at a step that repeats every month and gets done by hand each time.
| Stage | Who owns it | The handoff out of it | Where it stalls |
|---|---|---|---|
| Inquiry | The owner, or whoever answers new leads | A first reply sent and a call booked | New leads wait for a reply, or land in a mailbox nobody else can see |
| Proposal and signature | The owner, because scope and price sit with them | A signed proposal passed to whoever runs delivery | What was promised on the call stays in the owner's head and never reaches the project |
| Kickoff and onboarding | Whoever runs delivery | A set-up project and a kickoff call on the calendar | Folders, tasks and the client's channel are built by hand from the proposal |
| Delivery and client approvals | The account lead | Approved work, or a requested change logged against scope | Finished work waits days on a client's yes, and small extras get done without anyone logging them |
| Monthly reporting | The account lead | A report with a written summary of what changed and why | The summary gets written the night before the call, and it's the first thing to go thin in a busy month |
| Renewal or wind-down | The owner | A plan for the next term, or a clean handover of files and access | An unhappy client shows up for the first time at renewal |
Inquiry to kickoff, in brief
The stretch from a new lead to a signed proposal has its own guide, How a lead becomes revenue, which times each handoff with a spreadsheet. Carry one document out of it into everything below: the signed proposal. It says what the client is paying for, and every later stage leans on it, from the task plan at kickoff to the question of whether a requested change is extra.
Kickoff and onboarding: one form from the signed proposal
Kickoff is the stage I built a system for. It's called client launch, and it takes one form with the client's details and the signed proposal, and sets up the client's folder, a task list drafted from the proposal, a chat channel for the team and the welcome email. In one run on a test workspace I own, it turned one signed proposal into 21 tasks. A later run on a test workspace I own planned 30 tasks and created 30 of 30.
On 2026-08-07 and 2026-08-08, full runs on my test workspaces took about one to two minutes each. Every run so far has been on test workspaces I own, and no client has used it yet.
Kickoff happens once per client, though, and when agency people describe what slows their week down, it rarely comes up. The stages after it repeat every week or every month for every account, and that's where the hours add up.
Delivery: finished work waiting on the client
Delivery is the longest stage, and the slowest part of it is often the client's yes. Campaign creative, a month of content and a page of the new site each go to the client for a yes, and the yes comes back late, vague, or with a new request attached. Nobody owns the wait, so it shows up as a launch date that moved.
I'd send every piece with one clear question and a due date. When the date passes, a reminder is drafted for the account lead to send or edit, and any change the client asks for is approved as part of the work or logged against scope. That last step matters for margin, because requests that ride in with an approval are how scope creep gets into an account. The client-approval queue page walks through the whole loop.
Monthly reporting: the numbers are the easy part
Reporting tools already pull the numbers together. What still takes an evening per client is the few lines on what changed this month and why, and every client's report is due in the same few days. When those lines go thin, the client reads the charts and fills in the story themselves, and a report that should build trust becomes a call spent defending one number.
A draft written from the report's own numbers, with anything the data can't show marked as a guess, leaves the account lead to confirm the why and sign off. The reporting bottleneck page covers how that works.
Retainers: the same setup, every month
A retainer client gets a similar month again and again: a content plan, a report, a strategy call. Project tools assume a project starts and ends, so at the start of each month someone copies last month's board, moves the dates and reassigns the work, for every retainer. That's retainer re-setup, and it grows with every retainer you sign, in hours nobody bills.
It's the kickoff setup on a monthly cadence: one template per kind of retainer, a short record per client of what's in their plan, and the month's tasks created from both for the account lead to check. Client launch runs once per signed proposal. I haven't built or tested the monthly version, so treat this as the shape I'd start from.
Renewal: decided in the months before it
Renewal looks like one conversation at the end of a term. The client makes up their mind across the months before it: how long their approvals sat, whether the reports explained what changed, whether extras were raised with them or absorbed into the fee without a word. An owner who looks at an account only at renewal hears about trouble last.
The early signs are already in the stages above. Approvals running past their dates, a report that went out thin, and extra requests piling up against scope all show before the renewal call. Reading them every month gives you time to fix the account, or to plan a clean wind-down with the files and access handed over properly.
Which stage to work on first
Start where the work repeats most. Kickoff happens once per client. Approvals happen every week on every account, reports every month for every client, and re-setup every month for every retainer. A fix at a stage that repeats is used every cycle, on every account.
The coordination cost calculator takes the projects you have running and the hours of coordination each one needs a month, and shows what that time costs across a year.
Questions
Where does the client lifecycle usually break in an agency?
After kickoff, in the stages that repeat. Work waits on client approvals every week, the report summary gets written in a rush every month, and retainers get set up again by hand. Each one looks small. They repeat for every account, so they add up over a year.
Who should own each stage?
One named person per stage, and one per handoff between stages. The owner usually holds inquiry, the proposal and renewal. Whoever runs delivery holds kickoff. The account lead holds delivery, approvals and reporting. Work handed to a group waits until someone picks it up, so every stage gets a person's name.
Is this the same as the customer lifecycle in marketing?
They share a name. The marketing version is about how a business moves its own customers from first touch to repeat purchase. This guide is about how an agency runs its client work: how a client is signed, set up, served, reported to and renewed.
Do retainer clients go through the whole lifecycle every month?
They loop through the middle of it. Each month repeats setup, delivery with its approvals, and reporting, and renewal comes at the end of the term. That monthly loop is why retainer setup done by hand keeps adding hours for as long as the account runs.
Do I need a system for every stage?
Start with one. Pick the stage that repeats most and stalls most, put a named owner on its handoff, and fix that before anything else. Some stages, like renewal, stay mostly human, and a system's job there is to put the early signs in front of you.
Related
- How a lead becomes revenue: an owner's mapMap the six steps from a new lead to a kicked-off project, time each handoff with a timestamp column, and fix the slowest one first.
- Bottlenecks in a service businessWhere work stalls between a new lead and a renewal, found by the symptom you notice, with the system that fixes each one.
- From signed deal to running projectClient onboarding automation I built. One form with the signed proposal sets up the Drive folder, ClickUp tasks, Slack channel and welcome email.
- Closed-won to kickoffClosed-won to kickoff is the gap between a client signing and the project starting. What has to happen in it, where it breaks, and how a system runs it.
- Retainer re-setupRetainer re-setup is rebuilding the same project every month for each retainer client. Why it costs margin and how a system sets up each month from a template.
- The client-approval queue: finished work waiting on a client's yesFinished work sits with a client for days and nobody owns the chase. Send each piece with one clear question and a due date, and draft the reminder.
- The reporting bottleneck: writing what changed, every monthSomeone still writes what changed and why, every month. Draft it from the report's own numbers, mark the guesses, and let the account lead sign off.
- What does coordination cost your business each year?Turn your leads, proposals and active projects into the hours your people spend coordinating each month, and what that time costs you in a year.