Client Onboarding

Client onboarding is not SaaS product onboarding. There are no activation steps, no in-app walkthroughs, no feature tours. For agencies, onboarding is the structured process of setting up a new client relationship before it drifts into chaos. It starts the day the contract is signed and closes around the 60-day mark, when the engagement transitions into steady-state management.

The goal of onboarding is to establish norms, not just kick off the work. How the client communicates, who approves deliverables, how feedback is given, how fast they expect responses: these patterns are set in the first 30 days and they persist for the entire engagement. The norms you allow in week two become the expectations you are managing in month six.

Agencies that wing the first 30 days spend the rest of the engagement managing consequences: scattered feedback channels, unclear approval chains, scope requests that should have been change orders. A well-run discovery call feeds into onboarding. Onboarding feeds into long-term client relationship management. The sequence matters.

Seven things to complete before the kick-off call. These are not bureaucratic boxes. They are the inputs that make the kick-off meeting substantive rather than introductory. Agencies that skip this prep spend the kick-off gathering information they should have had before walking in.

A standard agenda: introductions (5 min), objectives and success metrics (10 min), SOW walkthrough (15 min), communication setup (10 min), approval process (10 min), first milestone (5 min), open questions (5 min). Sixty minutes. Every item serves a purpose.

The most important agenda item is the approval process. Who approves? What format? What is the turnaround window? This conversation is awkward to have later. Do it now, in the meeting, with the person who has authority in the room. If that person is not present, postpone the kick-off until they can attend.

Send a written meeting summary within 24 hours. This is the first reference document for the engagement. Include: who attended, decisions made, next steps with owner and deadline, the communication channel agreed on, the approval process, and the first milestone date. Store it in the client portal.

Channel discipline: pick one primary channel for all project communication. Email plus Slack plus DMs creates fragmented feedback that nobody can act on. Set the channel in the kick-off, confirm it in the summary, and redirect any out-of-channel messages from day one.

Feedback format: define how feedback should be given. Consolidated in writing, not verbal on a call. Verbal feedback during a demo is for questions. Written feedback is for changes. Verbal-only feedback does not get actioned until it is confirmed in writing.

The first deliverable sets the standard for the engagement: quality, format, presentation, and how you handle feedback. A polished first output signals that the rest of the project will run this way. A rough first output trains the client to expect iterations as the default.

Do not just send a link. Present the deliverable with context: what you were trying to achieve, the decisions you made, and what you are asking the client to respond to. Give them a clear brief for their review, not an open-ended "let us know what you think."

Handle the first round of feedback carefully. This is where the approval norms are established in practice, not just in the kick-off meeting. If the client routes feedback through multiple people or gives verbal-only feedback on a call, correct the pattern immediately and calmly. It is easier to reset at round one than at round four.

The 30-day check-in is a brief structured conversation (15 to 20 minutes). Is the communication working? Is the scope still accurate? Are there early concerns on either side? This is a health check, not a status meeting. Run it even if everything seems fine. Issues that feel small at 30 days become expensive at 90.

The 60-day review is more substantial (45 to 60 minutes). Review against the original objectives: are you still solving the right problem? What needs to change about how you work together? Has anything shifted on the client side (team, priorities, budget) that affects the engagement?

After the 60-day review, the engagement transitions from onboarding into steady-state client relationship management. Onboarding is closed. The norms are set. From here, you manage to them.

Three patterns that consistently predict engagement problems. None of them mean the client is difficult or the engagement is broken. They mean the norms from onboarding did not fully land. Fix them early rather than managing their consequences for months.