What does a customer onboarding RACI look like?

Last updated 19 August 2026

A customer onboarding RACI covers both sides of the relationship, not just yours. The two roles teams most often leave undefined are the customer's internal project owner and whoever accepts that onboarding is finished — and those two omissions cause most of the disputes about whether it was.

What does the RACI actually look like?

Responsible does the work; Accountable owns the outcome and is the single name against it; Consulted is asked before a decision; Informed is told after. The version below is a starting point for a typical B2B SaaS onboarding — the value is in adapting it, not adopting it.

Activity	Vendor	Customer
Handoff from sales	Responsible & Accountable	Informed
Onboarding plan & dates	Responsible	Accountable for their dependencies
Access, credentials, data	Consulted	Responsible & Accountable
Security & procurement review	Responsible for answering	Accountable for completing
Configuration	Responsible & Accountable	Consulted
Training & enablement	Responsible	Accountable for attendance
Internal rollout & comms	Consulted	Responsible & Accountable
Declaring onboarding complete	Consulted	Accountable

Why does the customer own the last row?

Because if the vendor decides when onboarding is finished, “finished” means “we completed our tasks”, and that is a claim the customer never agreed to. Any dispute about whether onboarding succeeded is really a dispute about who held that definition.

Making the customer accountable for it has a second effect worth having: it forces the acceptance criteria to be agreed early, because someone now has to sign against them. Teams that adopt this usually discover their definition of complete was never written down.

Which roles get left undefined?

Two, reliably. The customer’s internal project owner — not the economic buyer and not the end user, but whoever is accountable inside their organisation for the rollout actually happening. Without that person, every customer-side dependency is chased by you, from outside, with no authority.

And whoever accepts completion, as above. Both omissions are invisible at kickoff and expensive at the end, which is why they are worth five minutes in week one.

How do you use it without it becoming paperwork?

Fill it in during the kickoff conversation rather than before it, and keep it on the account rather than in a document. The point is not the grid — it is that the names get said out loud while both sides are present, which is when a missing owner becomes obvious.

Revisit it only when someone leaves. Personnel change is the event that silently invalidates a RACI, and it is also the moment nobody thinks to look at one.

Common questions

Is a RACI worth the effort for a small onboarding?

The document usually is not; the conversation always is. For a short onboarding, ask the two questions that matter — who owns this on your side, and who decides we are done — and write the answers on the account. That captures most of the value in ten minutes.

Can the same person be accountable and responsible?

Yes, and in small teams they usually are. The distinction earns its keep when they differ: it stops an escalation landing on someone doing the work who has no authority to change the plan, which is the most common way an escalation goes nowhere.

What if the customer will not name an owner?

Treat that as a risk finding rather than an administrative gap. An onboarding with no named owner on the customer’s side typically slips, because every decision has to be routed by whoever is available, and no one internally is accountable for the date.

Who should be accountable for the go-live date?

Jointly, in practice — which is why it works better to make each side accountable for its own dependencies and agree the date as a consequence. A date owned by the vendor alone is a date the vendor will be blamed for and cannot control.

How does a RACI relate to the handoff?

The handoff supplies the names and the RACI assigns them roles. If the handoff recorded the buying committee properly, most of the customer-side column is already answered — which is one of the practical reasons a good handoff pays off later.