Client Onboarding: The Two Weeks That Decide How the Project Goes
Most agency projects that go badly went wrong before any work started. A kickoff process that prevents the usual failures.
Think about your worst project of the last two years. Not the one with the difficult client — the one that ran long, lost money, and ended awkwardly.
Trace it back and the cause is almost never in the build. It's in the first fortnight: an assumption nobody checked, a decision-maker who wasn't in the room, content that was promised and never arrived.
Onboarding is the cheapest place to fix a project, and most agencies treat it as paperwork.
What onboarding is for
Three jobs, in order of importance:
- Find out what's actually true, as opposed to what the sales conversation implied
- Set the rules — who decides, how fast, what happens when things slip
- Make the client feel they made a good decision, because buyer's remorse in week one poisons everything after
Most agency onboarding does the third badly and skips the first two entirely.
Find the real decision-maker immediately
The single most expensive onboarding failure is discovering in week five that the person you've been working with can't approve anything.
You present, they love it, and then it goes to someone who wasn't in any of the conversations and has entirely different opinions. Now you're redoing work you already did, unpaid.
Ask directly, in the kickoff: "Who else needs to approve this before it's final? Can they join the review calls?"
If the answer is a name you haven't met, get them in the room or accept that every milestone carries hidden risk. Write it into the scope if you must — approval by a named individual, within a stated window.
Get the content commitment in writing
Client-supplied content is the most common cause of agency overrun, by a wide margin. Copy, images, logins, brand assets, product data.
The pattern is always the same. They agree enthusiastically at kickoff. Three weeks later you're building with placeholder text and the timeline is quietly gone — and because you never wrote down what they owed you, the delay becomes your problem.
Handle it explicitly:
- List every item you need from them, with a date attached to each
- State what happens if it's late — the timeline moves, and it moves by more than the delay because your team gets rescheduled
- Ask what they don't have. Many clients don't realise they have no usable photography until you ask. Better to find out now and sell them a solution than to discover it in week four.
The questions worth asking
Beyond the obvious brief, the questions that actually predict problems:
"What's happened before?" Have they worked with an agency on this before, and how did it go? A client who's been burned will behave differently, and it's better to know why.
"What does success look like in six months?" Not deliverables — outcomes. If their answer doesn't match what you're building, you found the mismatch before it cost anyone anything.
"What would make this a failure?" People are often clearer about what they're afraid of than what they want.
"Who internally is sceptical about this project?" There's usually someone. Knowing who, early, saves you a surprise in the review.
"What's the real deadline, and what's driving it?" A date tied to a trade show is real. A date someone picked because it sounded good is negotiable, and knowing which is which changes how you plan.
Set the communication rules
Agree these on day one, before they get set by accident:
- Where work is discussed. One place. Decisions made in a Slack DM or a hallway conversation don't exist, and you'll be held to them anyway if you don't say otherwise.
- How often you meet, and who attends.
- Your response time, and theirs. Both directions.
- What "approved" means. In writing, from a named person. "Looks good!" in a thread is not approval, and pretending it is causes the week-nine argument.
Whatever tool you use, use one. Requirements scattered across email, Slack, and call notes is how scope creeps invisibly.
The kickoff meeting itself
An hour, with the right people, structured:
- Introductions and roles. Who does what on both sides, including who approves.
- Restate the scope out loud. Including the out-of-scope list. Watch faces during that part — surprise here is enormously valuable information, and it's the last cheap moment to find it.
- Walk the timeline, with client obligations marked as milestones on it, not as footnotes.
- Agree the communication rules.
- Confirm what happens next, and who does it by when.
Send a written recap within 24 hours. That document is your reference for the rest of the project, and it costs twenty minutes.
Make them feel good about it
The commercial part matters, but so does the human one. A client who's quietly anxious in week one is a client who micromanages in week four.
Small things that work: a fast first deliverable, even something minor, in the first few days. A named person they can reach. A clear statement of what happens next, so the silence between milestones doesn't feel like nothing is happening.
Silence is the enemy in early-stage projects. Clients fill it with worry.
Red flags to catch at onboarding
If these show up now, they get worse:
- Can't answer who approves. Organisational confusion that becomes your problem.
- Won't commit to content dates. They already know they can't deliver.
- The deadline is immovable and unexplained. Usually someone promised something upstream.
- They mention the previous agency a lot, negatively. Sometimes the previous agency was bad. Sometimes it's a pattern.
- They want to renegotiate scope before starting. This will not be the last time.
None of these are automatic disqualifiers. All of them should change your contingency, your payment terms, or your willingness to take the work.
The one thing to change if you change nothing else
Write down what the client owes you and when, and get them to acknowledge it.
That single artefact prevents the most common, most expensive agency failure — absorbing the cost of a delay that wasn't yours, because nobody ever wrote down whose it was.
We onboard into your process and your project tool, under your brand. See how the partnership works.