SaaS onboarding: contract-signed to live

Interviewer: So a deal closes. Somebody signs the contract. From your seat, what actually happens next — walk me through the whole thing, contract to live.

Csm: Yeah, sure. So the moment that opportunity flips to closed-won in the CRM, that's the starting gun for us. And the very first thing — before I ever touch the customer — is the handoff from sales. The AE who closed it has to hand me the context. What did we sell, what did they actually promise, who's the champion, what's the timeline they think they're getting. And I'll just say up front, that handoff is where most of the damage gets done, before I've even said hello.

Interviewer: Damage how?

Csm: Over-promising, mostly. Sales is incentivized to close, right, so sometimes they've told the customer "oh yeah, the product does X" and it doesn't do X, or it does it in phase two, or it needs a custom integration nobody scoped. So part of my job in that handoff is to read between the lines and catch it early. If I smell an over-promise, I'd rather have the awkward reset conversation with the customer before kickoff than discover it during UAT when it's a fire. So sometimes the handoff loops back — I go to sales like, "hey, we need to realign on what we actually committed to."

Interviewer: Okay. Say the handoff's clean. Then what?

Csm: Then I get assigned — or I assign, depending — based on segment and complexity. An SMB self-serve customer gets a lighter touch, an enterprise deal gets the full white-glove treatment with a dedicated implementation manager. Once that's set, I do an internal kickoff first. Just me and whoever's involved internally, reviewing the account, flagging the risks I saw in the handoff, prepping. I don't want to walk into the customer kickoff cold.

Interviewer: And then the customer kickoff.

Csm: Right, the kickoff call. And this is the most important meeting in the whole process, honestly. This is where we align on goals — what does success actually look like for them. The success criteria, the desired outcomes, who the stakeholders are, the timeline. And I cannot stress enough how much everything downstream rides on nailing this. Because if "success" is vague here, then six months from now nobody can agree on whether we're done. We'll talk about that, but — define the win early.

Interviewer: So you've got the goals. Next?

Csm: Discovery. Requirements gathering. I dig into how they actually work today — their workflows, their existing tools, their data, their tech environment. What systems does this need to talk to. And out of that I build the implementation project plan and what we call the mutual action plan, the MAP. Emphasis on mutual. It's a shared plan, dates and owners on both sides. Because here's the thing — a huge amount of onboarding depends on the customer doing their part, and the MAP is how I hold them accountable to that without it feeling like nagging.

Interviewer: Foreshadowing.

Csm: [laughs] Yeah, big time. So with the plan set, we start the actual build. First I provision the account — stand up their tenant, set up the admin users, get the environment ready. That part's on us, it's quick. And then comes the technical setup, which is — the SSO configuration, the integrations, the API connectors, and the data migration. Importing their data in.

Interviewer: And that's the one that stalls.

Csm: That's the one that stalls. Every time. Because almost all of it depends on them. I need their data, I need their IT team to set up the SSO on their side, I need someone with access to flip switches. And customer IT is busy, the data's messier than they said, the champion who was so excited at kickoff suddenly goes quiet. So this step just — sits. And I'm nudging. "Hey, still waiting on that user export." "Hey, can we get thirty minutes with your IT?" I'll re-baseline the dates in the MAP, I'll nudge again, and if it really drags I escalate up to the executive sponsor. It's a loop I'm stuck in until they unblock me, and it is the number one killer of time-to-value. Hands down.

Interviewer: Once you're unblocked?

Csm: Configuration. Now I tailor the product to their workflows — the stuff I learned in discovery. Set it up the way they actually work, not the generic default. And this is where scope creep likes to show up, by the way. They'll go, "oh, can it also do this other thing." And I have to make a call — is that in scope, or is that a phase two. If it's material I'll pull the plan back open and re-scope rather than just silently absorbing it, because silently absorbing scope is how onboarding drags on forever.

Interviewer: Then training, I assume?

Csm: Two flavors of training. First the admins — the people who'll manage the system on their side. Then end-user training, the folks who'll actually use it day to day. And the end-user piece matters way more than people think, because that's what drives adoption later. If the end users never got properly trained, they just don't use the thing, and then we've got an adoption problem down the road.

Interviewer: And before you flip it on — is there a validation step?

Csm: Yeah, UAT. User acceptance testing. The customer validates that what we built actually does what we said it would back at kickoff — against those success criteria. And if they find issues, we loop. Back to configuration, sometimes back to the technical setup if something's broken at that layer. Fix, re-test, until UAT passes clean.

Interviewer: And then live?

Csm: Almost. There's a go-live readiness check first — a go/no-go. It's a joint call: is the build done, is the data in, is everyone trained, is the customer actually ready. And if there's a gap, it's a no-go and we go fix whatever's missing. But assuming we're green — then we go live. Cut over to production. Real users, real work.

Interviewer: Champagne?

Csm: [laughs] Not yet. Go-live triggers hypercare. That's a period of heightened, hands-on support right after launch — I'm watching closely, responding fast, because the first couple weeks are when problems surface and you want to squash them before they sour the whole thing. After hypercare settles down, I move into adoption monitoring. I'm watching the usage data, the health score — are they actually logging in, are they using the features that map to their goals.

Interviewer: And if they're not?

Csm: Then I intervene. If adoption's stalling — low logins, key features untouched — I don't just sit there and watch the number. I re-engage. Maybe re-train a team, maybe re-engage the champion, maybe troubleshoot a workflow that's clunky. It loops back into training or even config sometimes. Because a customer who's not using it is a customer who's going to churn, full stop.

Interviewer: Say adoption's healthy. Now what?

Csm: Now the payoff. We do the first business review — the QBR — and this is where I tie everything back to the success criteria we set at kickoff. "You said you wanted to cut process time by thirty percent, here's the data, here's what you got." That's value realization. And when you defined the win clearly at the start, this meeting is a victory lap. When you didn't, it's an awkward "so... are you happy?" conversation where nobody can point to anything.

Interviewer: And then you hand it off.

Csm: Then I transition the account. Implementation hands off to the ongoing renewal CSM — the person who owns the steady-state relationship and eventually the renewal. And once that handoff's done and the success criteria are met, I mark onboarding complete. Done. Closed out in the tracker.

Interviewer: So last question — the one I always ask. What do people get wrong about this?

Csm: The definition of done. Everybody thinks onboarding ends at go-live. The product's live, ticket closed, on to the next one. And that's completely wrong, and it's expensive. Going live is not value. A customer can be fully live and getting zero value — logged in twice, using ten percent of what they bought, quietly deciding not to renew. "Done" isn't when the software turns on, it's when they're actually getting the outcome they signed up for. And the reason teams get this wrong is there's usually no clear definition of done in the first place, because they rushed the kickoff and never pinned down the success criteria. So onboarding just... drags. There's no finish line, the customer's frustrated they're not getting value, time-to-value balloons, and by the time the renewal comes up they've got nothing good to point to. The whole game is: define the win on day one, and don't call it done until you've actually delivered that win. Everything else is just steps.

Interviewer: That's the beat. Thanks.

Csm: Anytime.