Onboarding Specialist

Companies were slow to notice that signing is the start of the work. For a long time a deal was considered finished the moment sales closed it. But in a subscription business the real result is next year's renewal rather than the first month's invoice, and accounts nobody attended to after signing kept going quiet a few months in.

The reason they left was rarely the product. The account existed, but the buyer didn't know how to invite their team and was using it alone. Or the records from the previous tool never got moved, so both tools stayed open side by side. Or only the decision maker had a login while the people who do the actual work had never signed in. When the renewal call arrives and someone says they barely used it, there's no time left to change the answer.

So a role appeared that covers only those first weeks. The whole process of helping a new user settle into a product is called onboarding, and for business customers it doesn't end with a few tooltips. There is data to move, a permission structure to design, and dozens of people to train, which takes a person driving a schedule.

The day starts by checking which stage each of five or six assigned accounts is stuck at. The work runs in the same order for every customer, and one account typically takes four to eight weeks.

1. Run the opening meeting. The session where goals and roles get aligned is the kickoff, and it ends with numbers written down: by what date, how many people, doing what. Without those numbers, nobody can later judge whether onboarding finished.
2. Build accounts and permissions. Split people to match the org structure, decide who can see what, and connect the company login so everyone gets in with one set of credentials.
3. Move the data. Transferring what accumulated in the old tool is migration, and this is where things stall most often. Mapping three thousand documents onto a new folder structure with matching sharing settings looks different every time, and the counterpart on the customer's side is fitting it around their actual job, so replies come slowly.
4. Train. Split a single all-hands session from smaller sessions for the teams that will use the product daily. Recurring questions don't get answered once and dropped — they go into the knowledge base as written articles.
5. Watch usage. Check weekly how many of the invited people have actually signed in and which teams have tried the core features, then reach out wherever things stopped.
6. Hand off. Once the agreed thresholds are met, the account transfers and the specialist steps away.

Performance in this role is measured in speed. The time from signup to the customer first feeling the value is time to value, and an onboarding specialist exists to shorten it. Two accounts on the identical product — one with thirty people working in it after two weeks, one with five after three months — have completely different years ahead of them.

There is a handoff on each side of the role, and three working relationships in between.

The front handoff is sales. Once the contract closes, the specialist collects what was actually promised. A thin handoff here means the customer hears one story during the sale and a different one during onboarding. That's why the conversation starts with what the customer was trying to solve rather than with a feature list.

The back handoff is the customer success manager (CSM). An onboarded account moves into a relationship measured in years, and the CSM picks it up there. What transfers isn't just the account's settings but everything that didn't go well. If the data migration was only half finished when the window closed, that fact needs to be written down for whoever comes next.

In between, three relationships. Tickets that arrive during the onboarding window get reviewed together with the support agent handling them — the same question arriving repeatedly means the training material is thin, which changes what gets covered next. Anything that jams while connecting accounts to another system goes to technical support. And the product team hears where new customers get stuck in their first days. Somebody starting ten accounts a month is the first to notice the same screen producing the same misunderstanding every time.

"When does onboarding close on this account? I want to schedule the handoff next week."

Asking whether the agreed thresholds are met and the account can transfer.

"Three weeks past kickoff and they still have two active users."

Reporting that invitations went out but real usage never started, so the schedule has stalled.

"Let's set the bar for assigning a specialist at fifty seats and up."

Proposing the contract size at which a dedicated person pays for themselves.

At Pagedeck, deals Sofia closes move into onboarding right after signing. The handoff meeting runs thirty minutes and opens with what the customer wanted to change, not with the contract. One account last quarter had four thousand documents to move, and their internal owner couldn't reply for two weeks because of their regular job, which pushed the whole schedule. Since then the migration gets scheduled for the week right after kickoff, and anything over two thousand documents comes with a request that the customer name one dedicated person on their side.

The most common reading is that the role is training. Standing in front of a screen explaining features is the visible part, so that's what sticks. In practice the hours go to data migration and permission design, and training sits on top of those as the last step. Left uncorrected, this assumption leads to schedules built around training dates, which produces the session where forty people gather to watch someone explain an empty workspace because the data never arrived.

The other one is treating the end of the window as success. A four-week plan that finished in four weeks looks like a win. But this role is judged on state, not on dates: how many of the forty invited people sign in every week, and whether everything that was supposed to move actually moved. Cut it off by the calendar instead and an account with poor customer health transfers as-is to the next owner, where the problem surfaces at the renewal six months later.