What are the steps in a client onboarding process?
For most service businesses the client onboarding process covers these steps. The client says yes, through an accepted quote or proposal. The engagement letter or agreement is signed. Documents are collected and any identity steps completed. Records are set up in each system. The client is welcomed and told what comes next. Missing items are chased, and the work is handed to the person doing it. A typical checklist covers the signed engagement, the intake form, the documents for that client type, any identity steps, the records to create and what ready means for whoever receives the work. Automation helps most in the gaps between these steps.
What is the difference between client intake and client onboarding?
Intake is the first collection of details and documents, sometimes before a business decides to take the client on. Onboarding covers everything from the yes to the first piece of work: the engagement, documents, records, welcome, chasing and handover. In most businesses intake is one step inside onboarding.
Do we need new onboarding software?
Not always. Many CRM, practice management and job management tools already include forms, checklists or templates, and configuring them may be enough. We start with the tools you already use and connect them where they do not talk to each other. That might be through an integration a tool already offers, or a connector such as n8n, Make or Zapier. A connector may carry its own subscription. If one is needed, it is named in the scope with who pays for it. New software is only suggested when the current tools cannot hold the checklist, the documents or the handover.
Can different clients have different checklists?
Yes. We can scope agreed branches by client, job or service type, for example an individual and a business client, or a residential and a commercial job. Each branch can have its own form, document list and readiness criteria. The rules, and the exceptions to them, need to be written down first, which can be part of the audit.
Can the system chase missing items?
It can prepare or send approved reminders driven by the checklist status. You set the cadence and who is allowed to send, and reminders can go from the address of the person handling the client where agreed. Drafts can wait for approval before anything is sent. A reminder stops once the item is recorded as received, and a client can reply to say they have already sent it, which goes to a person to check.
What happens if a client never sends what we need?
The record stays visibly incomplete. After the agreed number of reminders, a named owner decides the next step, for example a phone call, and the handover does not happen unless that owner accepts the exception. That decision is recorded with the file, so the manager or lead taking the work can see what was missing and who accepted it.
When does the handover happen?
When the agreed readiness criteria are met, or when a named owner accepts the file as an exception and that acceptance is recorded. Open items stay visible to the person receiving the work. The criteria themselves are written down for each client type as part of the audit or the pilot scope.
Can it send engagement letters and request identity documents?
Where your e-signature or practice tool supports it, the workflow can send your approved engagement letter or agreement template and record when it is signed. The wording, scope and fees stay with you. For identity, it can request the documents, route them to the identity service or provider your business already uses and record the result the responsible person confirms. It does not decide whether a client passes or whether an obligation has been met.
Where does AI fit in client onboarding, and where is ordinary automation enough?
In automated client onboarding, most steps are plain rules: send the form, create the record, set the reminder. Ordinary automation, or the features already in your tools, handles those. AI may help where a rule is not enough, reading free-text answers, matching an uploaded document to a checklist item or drafting a welcome summary for a person to review. It works inside the same agreed permissions, and our AI agents page explains how those roles are scoped.
How do you handle private documents?
Access, document location and retention are agreed with your business before anything is built, and the workflow uses the minimum access it needs for its job. Documents are stored where you already approve, such as your practice system or shared drive. Any service that handles them along the way, such as a connector or an AI model used to match a document to a checklist item, is named in the scope with where it processes data, and is used only with your approval. Access and retention rules are yours, set in your storage, and the workflow is built to follow them.
How long does it take and what does it cost?
There is no standard price or duration. The work is priced once we understand the workflow, the tools and the client types involved, and fees and scope are agreed in writing before work begins. It can start with a paid audit to map the process, or a scoped pilot on one client type where the checklist already exists. The free first conversation of 20 to 30 minutes settles which fits. How long the onboarding itself takes depends on how quickly items come back, and the audit measures your current time to handover as the baseline.