Assisted Onboarding

Letting screens and automated email carry the first setup works fine for a customer who needs to create one document. A $38,000-a-year contract has a different starting list. A hundred accounts get created at once, material moves over from whatever tool they used before, and visibility has to be split by department. Tooltips don't finish that work, and nothing in the product can chase down a person who has not replied.

A month after Pagedeck signed its first enterprise contract, Sofia opened the usage report. Four people had logged in out of the 80 the contract covered. All that had gone out was the automated email sent the day after signup. The reason wasn't that the product was hard. The person who could export the old material, the person who knew the department structure, and the person who could clear the security review were three different people on the customer's side, and none of them moved first.

Four stages, usually three to six weeks.

1. The opening meeting. A kickoff that settles goals and roles. Write down in one sentence how many people should be able to do what by when, and name the counterpart on the customer's side.
2. Setup. Create the accounts, migrate the old material, design the per-department permissions. An onboarding specialist, whose job is exactly this early setup and training, walks the screens with them.
3. Training. Departments use the product differently, so this gets split rather than run as one session for everyone, and the split usually follows whoever owns which documents.
4. A check a month later. Confirm it's actually being used, and go back only to the departments that aren't.

What stalls here is rarely how the product works; it's what the customer has to prepare. Three weeks becomes six because the person who exports the data and the person who runs the security review can't line up their calendars. So when measuring time to value — how long from signup to feeling the benefit — assisted onboarding is worth splitting into days your side moved and days the customer sat still.

"This contract goes assisted. The customer can't create a hundred accounts alone."

The size of the account is what decided that a person gets attached.

"Kickoff is Tuesday, and the data migration is waiting on their IT schedule."

Our side is ready; the remaining schedule sits with the customer.

"We planned three weeks, but the security review hasn't cleared, so call it six."

The completion date is being reset because of a process inside the customer.

Sofia now writes the onboarding schedule into the contract itself. With the four dates listed and each stage naming what the customer has to supply, the situation where four people logged in after a month doesn't repeat.