Customer Operations
Onboarding: nobody should have to chase a checklist
Onboarding is mostly chasing
Taking on a new account means collecting a dozen things from people who are busy: forms, contacts, documents, approvals, instructions. Most of the effort isn't the work itself; it's remembering what's missing and asking again, by email, from someone's memory.
An onboarding system keeps the checklist as the record. Each item knows who completes it, who chases it and when. The customer fills in what they can through a portal, approvals go straight to the person who gives them, reminders go out on their own, and when reminders stop working, a person is told with exactly what's missing.
Today, and with an onboarding system
Today
- 01A welcome email with a list of attachments to send back.
- 02Replies arrive in pieces, in different inboxes.
- 03Someone keeps the checklist in their head or a spreadsheet.
- 04Credit terms wait in an approver's inbox.
- 05The first visit is booked before access details are complete.
Accounts stall quietly, and the first anyone hears is a technician standing outside a locked unit.
With an onboarding system
- 01The customer gets a portal link with exactly what's needed.
- 02Each item updates the account record as it arrives.
- 03Credit terms go to finance as an approval with the evidence.
- 04Reminders go out by themselves; stalls go to the account owner.
- 05The first visit is booked only when the checklist allows it.
Everyone can see where the account stands, so nobody has to ask.
One account, day by day
Events
Account · Acme Properties
- Status
- onboarding
- Details
- complete
- Billing
- accounts payable contact
- Units
- —
- Credit
- —
- Agreement
- —
- Access
- —
- First visit
- —
Event 1 of 8: onboarding.started
The checklist, with owners
The parts it's built from
What changes from one business to the next
A common starting point is a customer portal on your existing CRM or job system, n8n or Trigger.dev for the checklist workflows, PostgreSQL for onboarding state, and e-signature through a tool you already use. These are starting candidates, not requirements.
Is an onboarding system the right fit?
Good fit
- New accounts need several things from several people before work starts.
- Someone spends their week chasing forms and approvals.
- Accounts stall and nobody notices until something goes wrong.
Avoid when
- New customers need nothing beyond a booking.
- You take on a handful of accounts a year and one person handles each from start to finish.
How we'd approach it
01
Understand
As much as the problem needs
We map how the work runs today: who does what, which systems hold the records, and where it breaks.
02
Design
Decided before it's built
Ownership, rules, integrations and exceptions, agreed with you and written down with acceptance criteria.
03
Build
Connected to what you use
We build the scoped system, connect it to the tools you already run, and test it on the cases that matter.
Questions about onboarding systems
Do customers have to use a portal?
It's the easiest way, but not the only one. Items can also arrive by email or through the office, and they update the same checklist.
Can different customers have different checklists?
Yes. Each account type has its own list, and items can depend on answers, such as access details only for units with locked entry.
What stops the first visit being booked too early?
A go-live rule. The visit can only be booked once the items you mark as required are complete.
Where does the account end up?
In the systems you already run: the CRM, billing and job software. The onboarding system holds the checklist, not a second copy of the customer.
Have every new account ready before the first visit
Tell us what a new account needs today and who chases it. We'll show you how the chasing would run itself.