After you choose · Chapter 19
How to onboard an AI automation agency
You picked an agency. Now the work begins. A strong start decides how the pilot goes.
“Success depends upon previous preparation, and without such preparation there is sure to be failure.”
Set up the pilot for success
Three things decide a pilot's outcome. Agree them before any build starts.
- One metric that defines success.
- A baseline recorded before the work.
- An internal owner who drives it.
You scoped these when planning the pilot. Now lock them in. See the pilot chapter for how to scope them.
The first two weeks
Agree who does what early. It avoids stalls and surprises.
Give the right access
The agency needs access to do the work. Give the least it needs, no more. Grant it on your accounts, not theirs. Keep it within your security and data rules.
Run a kickoff meeting
A kickoff aligns everyone on day one. Cover these in the first meeting.
- The goal and the success metric.
- The scope, timeline and milestones.
- Roles on both sides.
- The comms channel and cadence.
- Risks and how to raise them.
Set a communication cadence
Agree how you will stay in sync. A weekly check-in works for most pilots. Use one channel and one owner. Raise blockers early, not at the end.
Track the pilot metric
Measure against the baseline you set. Check progress at each meeting. Do not wait until the end to look. If it drifts, adjust early.
Onboarding by company size
For small teams
One owner and a weekly call is plenty. Keep access and scope tight.
For enterprises
Line up IT, security and stakeholders early. Agree access and change control before kickoff.
Common onboarding mistakes
Key takeaways
- Set the metric, baseline and owner first.
- Give least-privilege access on your accounts.
- Run a kickoff to align everyone.
- Keep a weekly cadence and track the metric.
Still comparing agencies?
Browse the directory to shortlist and compare before you commit.
Browse the directoryFrequently asked questions
How do I onboard an AI automation agency?+
Start by setting the metric, baseline and internal owner. Give the agency least-privilege access on your accounts. Run a kickoff to align on goals and scope. Agree a weekly cadence and one comms channel. A strong start decides how the pilot goes.
What should happen in a kickoff meeting?+
A kickoff aligns everyone on day one. Confirm the goal and the success metric. Agree the scope, timeline and roles. Set the comms channel and cadence. Surface risks early so nothing stalls later.
What access does an AI automation agency need?+
It needs access to the apps and data in scope. Give the least it needs, no more. Grant it on your accounts, not theirs. Use role-based access where you can. Remove access cleanly when the work ends.
Who should own an AI automation project internally?+
Name one internal owner before you start. They drive decisions, access and feedback. They should know the workflow well. They keep the agency unblocked. Without an owner, most projects stall.
How do I set a baseline for a pilot?+
Measure the current cost before any work starts. Record hours, volume or error rate today. Use the same method you will measure at the end. Keep the number simple and honest. Without a baseline, you cannot prove the result.
How often should I meet the agency during a build?+
A weekly check-in works for most pilots. Keep it short and focused on progress. Use one channel for quick questions between calls. Raise blockers early, not at the end. More critical builds may need more frequent contact.