A firm may spend months winning a client through tailored proposals, prepared meetings and prompt follow-up. After signature, the experience can narrow to a welcome email, several document requests and portal credentials sent without context.
The source article called this the “signing cliff”: the transition from a choreographed pitch to an improvised relationship. The phrase is memorable because it locates the problem at a handoff, rather than assuming the delivery team lacks care.
Onboarding is the first operational evidence of the promises made during selection. It should help the client understand what happens next, what the firm needs, who is responsible and how to get help. The exact journey will vary by service and client. Its basic quality should not depend entirely on a partner remembering each step.
Map the promise before mapping the process
Collect the proposal, pitch notes, engagement terms and any commitments made during selection. Identify the expectations they create about team, communication, access, timing, reporting and billing.
Then map what a recent client actually experienced from signature to settled delivery. Include:
- communications and document requests;
- legal, regulatory and commercial acceptance steps;
- team introductions;
- portal or system access;
- the first working session;
- initial deliverables and decisions;
- billing explanation; and
- routes for questions, concerns and accessibility needs.
Compare the two. A pitch may have implied immediate access to a senior partner while the operating model assigns day-to-day work elsewhere. That can be perfectly appropriate if the roles are explained. Surprise creates the gap.
Use client evidence as well as the internal process. Employees know what they sent. Clients can explain what they understood, repeated, waited for or had to chase.
Keep a consistent scaffold and purposeful variation
Partners sometimes resist standardisation because every relationship is different. They are right about the difference and may be wrong about the consequence.
Standardise the questions and minimum assurances, not every sentence or interaction. A transactional matter, an audit and a long-term advisory relationship will need different timing and depth. Each client can still receive:
- a coordinated start;
- a named relationship and delivery structure;
- clear requests and reasons;
- an explanation of communication and billing;
- supported access to any digital service; and
- an early opportunity to correct friction.
Design exception routes. A standard online process may be inappropriate for a client with an accessibility need, limited digital access, an urgent matter or a complex authority structure. Good onboarding makes variation deliberate and visible.
The first 30 days, viewed from the client side
At signature: confirm the transition
The welcome should do more than express enthusiasm. Confirm the immediate next action, the person coordinating it and when the client will hear from the firm again.
Where acceptance remains subject to conflicts, identity, credit, engagement or other controls, explain the status accurately. Do not imply that work has formally begun before the firm can make that commitment.
Create one owned list of information required. Some items will emerge later, though avoid several teams asking independently for the same material. Explain why sensitive information is needed and provide an appropriate secure route.
Before delivery begins: introduce roles through use
Names and titles are insufficient. Tell the client what each person owns, which questions belong where and how the senior relationship partner remains involved.
For example:
Sarah coordinates the work and is your first contact for timing and documents. Arun leads the technical analysis. I remain responsible for the relationship and will join the monthly decision review.
Check internal capacity before making the introduction. A named contact who is unavailable for the first two weeks makes the process feel less reliable.
Set a communication rhythm with room for client preference. Explain routine updates, urgent escalation, response expectations and the channel used for formal decisions. Subject these promises to the obligations and realities of the service.
At portal activation: begin with a real task
Sending credentials and inviting the client to explore asks them to discover the value unaided. Connect first use to a necessary, useful task: review the agreed scope, provide a document, approve a step or see the initial timeline.
Do not assume that a purposeful introduction guarantees adoption. Test the journey with the clients and tasks the portal is intended to serve.
Measure successful activation, completion of the first task, repeat use, access problems and support. Ensure the portal contains the promised material before the invitation arrives. Provide a human route for help and an alternative where the portal is unsuitable.
Designing for adoption: why “build it and they will come” never works explores the wider adoption pattern.
Before the first invoice: explain what the client will see
Confirm billing cycle, format, scope treatment, approval and the contact for questions. Where estimates or assumptions may change, explain how and when the client will be told.
Finance, relationship and delivery teams should agree the explanation. A correct invoice can still cause friction if its categories bear little resemblance to the way the work was described.
Around day 30: ask about joining the firm
Separate onboarding feedback from a general update on the work. Ask:
- Which part of getting started worked well?
- Where were you unsure what would happen or who to contact?
- Did you have to repeat information, wait unexpectedly or use a workaround?
- What should we change for the next client?
The timing should suit the engagement. Some clients reach settled delivery sooner; others remain in onboarding for longer. The important point is to ask while the details are recent and the firm can still recover the experience.
Record themes and actions with appropriate confidentiality and permissions. Do not turn one client’s preference into a universal rule.
Automation should support ownership
A CRM can trigger reminders, prepare communications and show incomplete steps. Automation is useful when it prevents silence or duplication. It can also send an inappropriate message, expose an internal status or create a generic sequence that contradicts the personal pitch.
For each automated step, define:
- the event that starts it;
- the data used;
- the person who reviews or owns it;
- suppression and exception rules;
- what happens if the underlying record is wrong; and
- the service measure it supports.
Templates should contain required information and leave room for client context. Personalisation means more than inserting a name. If a partner cannot explain why the message is relevant, the trigger needs revision.
Legal, compliance, privacy, security and professional requirements apply to onboarding data and communications. Build them into the process rather than adding approval after the sequence is finished.
Find the operational cause
Onboarding gaps persist because ownership crosses business development, the partner, delivery, operations, finance and technology. Each can complete its own task while the combined journey fails.
Name one journey owner with authority to maintain the standard, review evidence and coordinate changes. Individual relationship partners remain accountable for client judgement within the service. The journey owner protects the shared scaffold.
Review incentives and capacity. If partner contribution to onboarding is expected and invisible in workload planning, reminders will have limited effect. If the delivery team learns about a new client only after signature, the pitch-to-delivery handoff needs attention before the email sequence.
The source article also described Distinction’s own experience appointing an external firm: a strong pitch followed by several weeks of weak coordination. The work was acceptable, and no second engagement followed. That is one experience rather than proof of a general retention law. It usefully shows how operational friction can alter a commercial decision even when the core work is competent.
Our broader article on the experience gap between winning and keeping a client covers onboarding alongside communication, portals, billing and between-matter relationships.
Improve one real journey
Select a recent engagement and walk through it as an observer. Find one avoidable point of uncertainty, duplication or unsupported access. Change the process, test it with the next appropriate clients and review the result after a defined period.
Distinction offers an onboarding experience audit, so we have a commercial interest in facilitated work. The one-page onboarding experience audit checklist available below covers five components and can also support an internal review.
The aim is not an elaborate welcome campaign. It is a reliable transition from being chosen to becoming a client, with enough structure that personal service no longer depends on memory.
