Onboarding a client is onboarding a team

When a new hire joins a team, everyone agrees they need onboarding. Accounts get provisioned, introductions get made, someone explains why the conference rooms are named after mountains. Nobody expects the new person to be useful on day two.

Then a company hires an agency, and all of that common sense evaporates. The agency is expected to produce from a standing start, and the agency, wanting to look confident, plays along. Both sides skip the joining part and go straight to the working part, and then everyone acts surprised in week five when the work keeps missing in ways nobody can quite name.

We treat the first two weeks of an engagement as exactly what they are: onboarding. Not a discovery phase with a fancier invoice. Onboarding, in the ordinary employee sense, because we’re joining a team, and joining is a skill with actual components. Four of them, mostly.

The tools

Every company has an official stack and a real one. The official stack is in the IT documentation. Decisions happen in the real one, and it’s usually some unholy braid of one Slack channel with a misleading name, a spreadsheet called FINAL_v7 that three departments quietly depend on, and one person’s memory. Week one, we map the real stack. Where do requests come in, where do approvals live, which notifications does everyone ignore. Asking these questions early looks slightly naive. Guessing wrong in week six looks much worse, because posting a deliverable where nobody looks is functionally the same as not delivering it.

The names

Org charts tell you who reports to whom, which is the least useful fact about a company. What we’re actually learning in the first two weeks is the informal directory: who answers fast, who needs a day, whose one-line reply means enthusiasm and whose means the opposite. Which developer knows where the legacy bodies are buried. Which marketer has been there eleven years and functions as the institutional memory no wiki ever captured. Every company has three or four people who make everything move, and their names are almost never at the top of anything.

The politics

This word makes clients flinch, so let’s be precise. We don’t mean gossip and we’re not choosing sides. Politics, in the useful sense, is just the map of what’s sensitive and why: which project got cancelled last year and left a bruise, which two departments are polite in meetings and at war in email, which topic makes the room go quiet. You cannot navigate what you refuse to see. An agency that ignores this map will eventually park a well-meaning recommendation directly on a landmine, and the recommendation will die for reasons that have nothing to do with its quality, and the agency will conclude the client “wasn’t ready” when the truth is the agency never learned the terrain.

The vocabulary

Every organization speaks a dialect. Words mean specific things in specific buildings: “launch” might mean the press release or the actual release, “the platform” might be a product or a grudge, and an acronym can carry six years of history that no glossary will surrender. In week one somebody on our side keeps a running list of terms and what they seem to mean, then checks it. Half the entries turn out to be slightly wrong, and each correction is a small flood of context about how the company actually thinks. The list isn’t the point. Being corrected is.

By osmosis, or on purpose

Here’s the thing: every agency learns all of this eventually. Osmosis works. Give it five or six months and the tools, names, politics, and vocabulary soak in through sheer exposure, one small misunderstanding at a time.

But look at what that sentence actually says. It says the learning gets funded by mistakes. The misdirected deliverable, the stakeholder discovered too late, the word used wrong in a big meeting: that’s osmosis collecting its tuition, spread across the exact months when trust is newest and most flammable.

Doing it deliberately just means paying the same tuition up front, at a steep discount. So we schedule the unglamorous parts. Sitting in on meetings we’re not strictly needed in. Reading a year of decision threads nobody assigned us. Interviewing the people who never appear on a project plan. To a certain kind of accounting this looks like two slow weeks.

It’s the fastest thing we do all year.

A new hire who skips onboarding isn’t impressive, they’re a liability with confidence. The same is true of an agency, and week one is when you find out which one you hired.