← All Field Notes

Client onboarding: good kickoffs are boring on purpose

Your client signed because of the pitch. They'll stay, refer you, and forgive your mistakes because of what happens in the first thirty days. That window teaches them who you actually are, and most companies teach the wrong lesson without knowing it.

Here's the pattern I've seen inside growing service companies for fifteen years. Every new client gets onboarded a little differently, depending on who sold the deal, who's running the work, and how busy everyone happened to be that week. One kickoff has an agenda and a plan. The next one is a get-to-know-you call where nobody writes anything down. Everyone means well. Nothing is standard.

And it mostly works, until it doesn't. A handoff gets skipped and the delivery team learns the scope from the client instead of from sales. Week two arrives and the client asks a reasonable question nobody assigned an owner to. Small stuff. But the client is keeping score in those first weeks, and every improvised moment quietly moves you from "these people have a system" to "I need to stay on top of these people."

Improvisation is a cost you chose

When onboarding lives in people's heads, you pay for it three ways. You pay in rework, because things missed in week one get rebuilt in week six. You pay in margin, because scope that was never restated clearly has a way of growing. And you pay in trust, which is the expensive one, because a client who feels dropped in week two shops the renewal in month ten.

The fix is not heroics or better memory. It's a path. The same path, every time, no matter who sold it or who runs it.

The five pieces of a real onboarding path

An internal handoff that actually happens. Sales hands delivery the full picture in a structured way: what was promised, what was priced, what the client is worried about, and anything odd about the deal. Fifteen minutes with a checklist beats a forwarded email chain every single time. Most onboarding failures I've untangled started here, before the client ever noticed.

A welcome the client doesn't have to ask for. Within a couple of days of signing: who's on their team, how communication works, what happens next, and real dates on a calendar. Silence between signature and kickoff is where buyer's remorse grows.

A kickoff that runs on a template. Same agenda every time. Confirm the goal in the client's words, restate scope and what's not in scope, name who owns what on both sides, and set the rhythm for updates. If your best kickoffs depend on your best people having a good day, you don't have a kickoff, you have a performance.

A first thirty days the client can see. A short, written plan with milestones. Not a project plan for your team, a visible one for the client, so they always know what's happening and what's next. Clients don't ask for status when status walks in the door on its own.

One home for everything. The scope, the contacts, the plan, the decisions. One place both sides can point to. If the answer to "where does that live" is a person's inbox, it doesn't live anywhere.

The test

Here's how you know whether you have a process or a habit. Could someone you hired last month run your next client kickoff from the written path alone, without pulling a veteran into the room? If yes, you've built something that scales. If no, your onboarding is really just your most experienced people compensating, and it will break exactly when you grow enough to need it most.

Boring is the goal here. Predictable kickoffs, predictable first months, no surprises. Clients experience that consistency as professionalism, because that's what professionalism is.

This note is the first in a series working through the twelve questions on my operations readiness assessment, one honest look at a time. Client onboarding is one of the twelve for a reason: it's where operations stops being an internal concern and becomes something your customers can feel. If the systems side of this is where your company gets stuck, that's exactly the work I do as a fractional COO.