SaaS Customer Onboarding

Where the time went

Every new account went through twelve steps before anyone could log in: a contract to countersign, a workspace to provision, seed data to load, a welcome call to book, and a handful of internal records to update. Each step was owned by a different person, and each handover cost a day.

• New customers waited between four and nine days to reach their first useful screen.
• Two of the twelve steps were regularly missed, which support only discovered when the customer complained.
• Nobody could say, at a glance, where any given account had stalled.

What we built

We rebuilt onboarding as one sequence with a single source of truth.

1. Signature to record. A signed contract writes the account into the CRM and opens an onboarding record.
2. Provisioning. The workspace, the seed dataset and the admin invitation are created together, in that order, with a retry on each.
3. Scheduling. The welcome call is offered as a booking link inside the first email rather than negotiated over three replies.
4. Escalation. A step that has not completed within its window notifies the owner, and then the owner’s manager.

The point was never to remove people from onboarding. It was to stop them being the transport layer between two systems.

What made it stick

• A visible board. Every account’s position is on one screen, so a stall is obvious.
• Idempotent steps. Every step can be safely re-run, which is what makes an automated retry trustworthy.
• A written runbook. The team can change the sequence themselves; we handed over the canvas, not a black box.

Results

• Time to first login fell from an average of 6.4 days to under 4 hours
• Missed steps fell to zero across the first quarter
• Onboarding capacity roughly tripled without a new hire

What we would do again

Start with the board. Making the process visible produced half the improvement before a single step was automated, and it made the case for the rest.