Do Not Hand a New Advisor a Book of Business on Day One

A book of business is the last thing to transfer

Small advisory firms tend to make one of two onboarding mistakes. They keep a capable new hire on internal work for months because nobody knows when the person is ready. Or they assign accounts immediately and tell the new advisor to ask questions as they come up.

The first approach wastes capacity. The second makes the client part of your training program.

New advisors need real work, but account ownership should move in stages. Give them a defined set of records, decisions, and client interactions. Watch the work. Expand the boundary when the evidence supports it.

That is more useful than a generic 30, 60, and 90-day checklist. Time in the seat matters less than what the advisor can now do without losing context, making an unsupported promise, or waiting for the founder to rescue the conversation.

Define the role before you build the ramp

"Help with clients" is not a role. Neither is "take some accounts off my plate." Decide what you are hiring the person to own during the first six months.

Will the advisor qualify new opportunities, manage existing accounts, coordinate implementations, prepare renewals, build proposals, manage supplier work, or do some mix of those jobs? Each path requires different client context and a different authority boundary.

The U.S. Office of Personnel Management's supervisor onboarding toolkit tells managers to be clear about performance objectives, timelines, roles, and responsibilities, then use milestones to check progress. That guidance is basic, but small firms still skip it. They introduce the tools before they define the work.

Write the first operating boundary in plain language. For example: "During the first month, the advisor can prepare account updates, document client decisions, and own routine supplier follow-up. Pricing changes, contract recommendations, escalations, and new client commitments require review."

Now the new advisor knows where to move and where to stop.

Choose the first accounts on purpose

Do not start with whichever clients the founder likes least. A difficult account with poor records, an active escalation, and three overdue promises is not a training assignment. It is a recovery project.

Pick a small first group using the current state of the account, not just revenue. Look at relationship health, record quality, stakeholder complexity, active projects, upcoming renewals, supplier dependencies, open commitments, and the downside of a missed decision.

A useful first account has enough activity to teach the operating model, but the next thirty days are visible and manageable. The client history is reasonably current. Another advisor can supervise without taking every task back. The new advisor can make a useful contribution before being asked to own a difficult commercial decision.

Keep strategic accounts, active disputes, sensitive executive relationships, and material contract decisions supervised until the person has shown the judgment required for them. Seniority from another company does not replace context inside yours.

Build an account brief that leads to action

Do not send the new advisor into six years of email and call it context. Build a brief around the next decisions.

For each first-wave account, capture:

• The client's current priorities and the evidence behind them
• The stakeholders, their roles, and who can approve a decision
• Active services, suppliers, contracts, projects, deals, and renewal dates
• Open client promises, supplier commitments, owners, and due dates
• Commercial exceptions, relationship risks, and escalation history
• The next account decision and what must happen before it is ready

This overlaps with a good 90-day account plan because it should. Onboarding is not a separate pile of training documents. The new advisor should learn from the same current account record the firm uses to run the relationship.

Ask the person to explain the account back to the current owner. If the recap becomes a biography of the client instead of a view of current decisions, the brief is not ready.

Move through four levels of client responsibility

A new advisor can be useful before owning the whole relationship. Use four levels so everybody knows what has changed.

1. Observe: Review the account record, join selected meetings, and document the decisions, promises, and next actions.
2. Prepare: Build meeting briefs, draft follow-up, update account records, and prepare options for the relationship owner to review.
3. Lead within a boundary: Run routine client calls, own supplier follow-up, and complete approved work while escalating named exceptions.
4. Own the account: Hold the relationship, advance client decisions, coordinate the internal team, and bring senior judgment in when the situation crosses an agreed line.

Do not advance every account at the same speed. Somebody may lead a stable account review while still preparing the work on a larger client with an active renewal. That is a sensible ramp, not a lack of trust.

Your existing delegation levels should carry into onboarding. The difference is that the boundary expands as the new advisor proves they can use the account context and escalate before the client feels the gap.

Use readiness evidence instead of calendar dates

A ninety-day anniversary does not prove readiness. Neither does sitting through ten calls.

Before expanding responsibility, review work the person actually completed. Can the advisor find the current contract and renewal timing? Can they identify the client decision maker and the daily contact? Did their meeting recap separate facts, open questions, commitments, and next actions? Did they update the system without being chased? Did they escalate a scope, supplier, or commercial issue at the right point?

Client communication also matters. The advisor should be able to explain what was decided, what remains open, who owns the next move, and when the client will hear back. Polished talk with a weak operating record is not readiness.

Have the manager approve one of three outcomes for each account: keep the current boundary, expand it, or pull it back and repair a specific gap. Do not leave the person in permanent shadow mode because the manager never made the decision.

Make the client introduction match the authority

Clients get confused when a new advisor is introduced as their contact but still needs the founder to approve every normal step. They also notice when an unfamiliar person starts sending directions without an introduction.

Tell the client exactly what the new advisor owns. "Jordan is preparing your September account review and will own supplier follow-up. I remain the relationship owner and will lead the renewal decision" is clear. Later, send a separate update when account ownership changes.

If full ownership is moving, use the more formal client ownership transition. Confirm the effective date, current priorities, open work, supplier routes, and next scheduled decision. Onboarding the employee and transferring the client are connected, but they are not the same event.

Audit one new-advisor ramp before the next hire

Pick the last person who joined your client team. Review the first accounts they touched, the context they received, the authority they were given, and the evidence used to expand that authority.

If the answer is mostly memory, rebuild the ramp for one account. Define the role boundary, choose the account, create the brief, set the responsibility level, name the supervising owner, and schedule the readiness review. Then run the process before adding more accounts.

Advisor OS CRM connects client and contact records with activities, tasks, deals, suppliers, contracts, reminders, and reporting. That gives a new advisor one operating record to learn from and gives the manager visibility without asking for another private recap.

Use the free Advisor OS agency scorecard if client context and ownership still depend on the founder's memory.