The Host Agency's Guide to Advisor Onboarding

Before the agreement is signed

Onboarding starts before the contract does, and the highest-leverage work is expectation-setting that costs nothing: what the new IC's first week will look like, what the agency provides versus what they own, what a realistic first year of production looks like for someone with their starting network. Advisors don't quit hosts over hard truths; they quit over surprises. The recruit who signs believing leads will be handed to them weekly is a resignation letter with a start date.

This is also the moment to run the intake — one structured pass that collects every decision setup will need: legal name and how their name should appear publicly, bio in their own voice, a usable photo, the niches they actually book, the suppliers they need registrations for, the domain they want if they're having their own site. It feels premature to ask before the ink is dry. It isn't. Every one of these answers is a dependency for something in week one, and collecting them serially, over email, after the start date, is where onboarding months come from.

Day one: accounts and access

Day one has one job: by the end of it, the advisor can log in to every system they'll work in and see their own name there. Their profile exists, their login works, and — this is the detail that separates working from waiting — they know exactly where a lead will appear when one arrives and what they're expected to do with it. An advisor with access is an advisor who can accidentally start working. That's the goal.

Because the intake already happened, day one is execution, not correspondence: create the accounts, load the profile from the intake answers, send the credentials, walk them through the lead flow once. Note what's deliberately absent from this list — supplier registrations that take a week to process, the site going live, business cards. Those proceed in parallel. The mistake that stretches onboarding is treating everything as a chain, when almost nothing actually depends on anything else. Sequence only what must be sequenced.

Getting their site live

The advisor's site matters more to the advisor than almost anything else you'll set up — it's the thing they show their network, and their network is where their first bookings come from. So treat "site live" as a week-one deliverable, not a someday project. The intake already collected the raw material: bio, photo, specialties. Assembled onto the agency's template, that's a real, presentable site in a day — the advisor's face and voice on the front, the agency's brand and lead pipeline underneath.

Resist the perfection trap, in both directions. The advisor will want to polish their bio for two weeks; ship the good-enough version and let them refine it live — if your platform lets them edit their own pages, polish stops being a blocker at all. And the agency shouldn't gate launch on a committee review of every word; the brand layer is fixed by construction, so the review surface is one person's bio, not a whole website. A live site in week one that improves weekly beats a perfect site in month two, because week one is when the advisor is telling everyone they know about their new business.

Their first 90 days

Week one ends with logins and a live site; the next twelve weeks decide whether the advisor makes it. The failure mode is the cliff: intensive attention through setup, then silence, then a check-in at month three that discovers they stalled in week four. The IC economics make this worse than it looks — an advisor who doesn't book early doesn't just earn nothing, they conclude the model doesn't work, and they conclude it privately.

The runway is a plan with dates on it, visible to both sides. A first-booking target — even a modest one, even a friends-and-family one — with a week attached. Supplier trainings scheduled, not suggested. A standing check-in that reviews the pipeline: who they talked to, what's quoted, what's stuck — not "how are you feeling." And one explicit path for the question they'll actually have ("a client asked me something I don't know how to book"), because the speed of that first answer teaches them what support here really means.

Ninety days in, you should both be able to say whether it's working against numbers you agreed on at the start. If it is, the runway ends and normal cadence begins. If it isn't, the conversation is honest because the expectations were — which is where the pre-signing section pays off.

What slows onboarding down

Audit a slow onboarding and you'll find the elapsed time went to four things, none of them work. Serial decision-collection — a dozen questions asked one email round-trip at a time. False dependencies — the site waiting on the contract countersign when only the login legally needed it. Unowned steps — "marketing sets up the profile" meaning no specific person on no specific day. And re-collection — asking the advisor for a photo the recruiter already had, which costs a day and, worse, signals that the machine has no memory.

Every one has the same cure: onboarding is a checklist with an owner and dates, run the same way for every advisor. Not because ceremony is nice, but because a written checklist is the only thing that exposes false dependencies and unowned steps to inspection. Time-to-first-booking is the single number that grades the whole pipeline — track it per advisor, and when it stretches, read the checklist to find which step grew. A host that onboards in a week has a recruiting advantage no split percentage matches, because every advisor's first impression of the operation is the operation working.