Home›AI Agency Academy›Lesson 33
Module 09 · Lesson 33

Onboard a client without losing context

Collect the people, evidence, access, policy, baseline, and approvals required for a controlled build.

Last updated August 5, 2026•15–25 minutes•Free AI agent course
What you will learn

Complete the onboarding checklist

You will be able to run a client kickoff that creates a usable delivery starting point instead of a long list of disconnected credentials and wishes.

Why this matters

Good agent work is useful before it is impressive.

A rushed onboarding creates predictable rework: wrong policy source, missing operator, unclear sign-off, and a build that no one feels safe launching. The goal is to create one shared picture of the first pilot.

Core concepts

The language that keeps the work clear.

Stakeholder mapBuyer, operating owner, policy expert, technical contact, reviewer, and escalation contact.
BaselineA documented view of the workflow before change.
Access checklistThe exact, least-privilege access needed for the stated scope.
Approval pathWho signs off discovery, content, tests, launch, and changes.
The practical method

How to complete the onboarding checklist

Meet the operating owner

Confirm the person who lives with the workflow and can validate whether it helps.

Collect only needed access

Request systems, samples, policies, and credentials by job—not a broad login collection.

Capture the baseline

Record current volume, delay, quality, exceptions, and examples before any automation changes.

Agree milestones

Set dates and approvers for discovery, first test, pilot, review, and the decision to expand or stop.

Worked example

Worked case: onboard a client without losing context

A white-label partner onboards a local-services client for after-hours lead intake. The owner provides brand language, service-area rules, the emergency policy, CRM access scoped to the pilot, and two frontline staff for testing.

The partner records the current average response delay and examples of incomplete requests. It does not request access to unrelated financial systems or assume the owner can approve clinical or safety language.

The kickoff finishes with a clear pilot owner, weekly review time, and sign-off steps. Everyone knows what evidence is needed before the workflow reaches real customers.

Build it in practice

Complete the working artifact

Business owner: [role]. Operating owner: [role]. Policy owner: [role]. Required access: [scoped list]. Baseline: [metrics/examples]. Milestones + approvers: [table].
Practice

Before you move on

  • Create an onboarding checklist for one offer.
  • Run it with a mock client and remove unnecessary access requests.
  • Confirm who can approve each launch decision.
  • The operating owner participates.
  • Access is least-privilege.
  • A baseline exists.
  • Approval and escalation paths are specific.

Lesson progress

Finished this lesson?

Save your place on this device so it is easy to pick up where you left off.

Not marked complete yet.