When onboarding a new client runs six to eight weeks, the time is rarely going where people assume.
Where the weeks go
Waiting for access. Credentials, approvals, finding someone on the client side who can actually grant things. This is usually the largest single block, and it is administrative rather than technical.
Documenting an environment nobody documented. Real work, and it is discovery, not setup. Naming it as discovery changes how it is scoped and how it is sold.
Exceptions handled as one offs. Every client has three things that are different. If each is solved from scratch and lives in somebody's memory, the process never gets faster no matter how many clients you onboard.
What to standardise
The sequence of steps. The artifacts produced. The definition of onboarded. The verification that runs at the end.
None of these depend on the client. If two technicians onboard two clients in different orders and produce different documents, you do not have a process, you have two people being competent independently.
What is genuinely variable
The environment. Which systems, which versions, which oddities.
Keep that as configuration: a record per client holding the systems in scope, the approver, the naming conventions, the exceptions and the access status. Adding a client becomes filling in that record.
The single biggest lever
Send the access checklist before day one.
Names, systems, what you need, who can grant it, and a date. Half the elapsed time in most onboardings is waiting for something that could have been requested the week the contract was signed.
Make the definition of onboarded verifiable
Not a feeling and not the day the last ticket closed. A list a second person can check: monitoring is live, documentation exists at this location, these accounts are provisioned, this verification passed.
Without that, onboarding ends when everyone gets tired of it, which is why nobody can quote a duration honestly.
Measure it from signature
From contract signature to the verifiable definition. Not from kickoff, which hides the access delay, and not to the last ticket, which hides the tail.
Once you measure it that way, the variable part becomes obvious, and it is almost always the two things at the top of this page.
What good looks like
The fixed part is genuinely fixed and takes the same time every client. The variable part is discovery, scoped and named. And you can tell a prospect a range without guessing, which is worth something commercially on its own.