The contract comes back signed, and the win turns into a setup list with your name on every line.
Case Study 07 / 09
The Onboarding Rail
Delivery was one of the four workflows I removed myself from, and onboarding was its front door. The week after a contract got signed used to be all me: forms, access, folders, the kickoff agenda, a setup list I rebuilt from the last client's thread every time. Now the signed contract is the trigger. Four agents pick it up and the rail runs to the kickoff. The only thing left on my calendar is the call itself.
You hunt down the intake questions from the last client's thread, send them again, and chase the answers yourself.
Logins and permissions trickle in over a week of back-and-forth you have to keep alive. There's always one login nobody at the client remembers owning.
You rebuild the folders and channels by hand, from memory of how the last one looked.
The kickoff agenda gets written the night before, from a contract you haven't reread.
Kickoff happens whenever the setup finally finishes, and the client's excitement cools in the gap.
The signed contract starts the rail. Every step below begins on its own.
The intake goes out on its own, and unanswered questions get chased without you.
Access requests go out as one checklist, tracked until every box is green.
Folders, channels, and docs build themselves from the same template every time.
The agenda drafts itself from the contract and the intake answers.
You walk into the kickoff with everything in place, and the first impression is yours to make.
The Hand-Off · The rail runs signed to kickoff. You just walk in
-
You
The kickoff. Setup is plumbing. The first call is the relationship, and it's yours.
-
You
The exceptions. When a client needs something the template didn't see coming, that's your call.
-
You
The tone. How week one feels gets set by a person, not a checklist.
In a session, this workflow gets one of three verdicts: automate it now, fix it manually first, or leave it alone.
Onboarding earns "automate it now" when clients start the same way every time and the setup steps already exist as a list somewhere, even a messy one. If every engagement starts differently, it's "fix it manually first": you run the next few by hand, write down what repeated, and the rail gets built on that. And if you sign a handful of clients a year, leave it alone. A rail needs traffic to be worth laying.
Sixty minutes. The spec for this, written live.
Book the session