Onboarding a Docebo client: a 5-stage SME playbook
A Spanish SME signing its first Docebo deal often discovers that the gap between contract and go-live is not technical. It is procedural: nobody on either side has agreed on what “ready to launch” means, which fields HR will hand over by which date, and who signs off on the SSO test. This piece walks through a 5-stage onboarding playbook we run for European SMEs every month, with the checklist items that prevent the usual two-week slip.
Why onboarding slips by two weeks
The pattern is consistent enough to be predictable. Week 1 is the kick-off — everyone is keen, decisions get made, branches get sketched. Weeks 2 and 3 disappear into “waiting on HR for the user list” and “waiting on IT for the SSO certificate.” Week 4 is when someone realises the original launch date assumed all of that was already done.
The fix is not motivational — nobody is being lazy — it is procedural. The five stages below name the artifacts each side owes the other, with explicit hand-off points. A Docebo onboarding done this way ships in 4-6 weeks for a typical 50-200 user SME. Done without it, the same project takes 8-12 weeks and burns goodwill on both sides before the first user has logged in.
For SMEs claiming a Kit Digital voucher up to €12,000 under the LMS adoption category, the procedural rigour also has a documentation purpose: the digitising agent needs evidence that each stage was completed before invoicing, and a stage-by-stage checklist produces that evidence as a side effect.
The 5 stages and what each one delivers
| Stage | Duration | Client owes | Vendor owes | Exit criteria |
|---|---|---|---|---|
| Discovery | 3-5 days | Org chart, user count, training goals | Onboarding questionnaire, branch map proposal | Both sides agree the scope is buildable |
| Configuration | 5-10 days | SSO IdP details, branding assets | Branch + power-user setup, SSO test instance | Test login works for one pilot user |
| Content load | 5-10 days | Course library or content brief | LMS content import, enrolment-rule wiring | First course assigned to first user successfully |
| Pilot | 5-7 days | 5-10 pilot users committed | Support channel + bug-tracker | Pilot users complete one course, no P1 bugs open |
| Go-live | 1-2 days | Comms to full user base | Cut-over plan, rollback plan | All users provisioned, first day of usage logged |
Discovery is where most slip-ups originate. The onboarding questionnaire we send asks for current user count, expected user count at month 3, branch structure, role-based access requirements, language preferences, training compliance deadlines, and the data fields HR is willing to push to the LMS. Half of those answers do not exist on day one — but writing the questionnaire forces the client to find out, and that is the actual purpose.
Configuration is where SSO usually causes the slip. A clean SSO test against a sandbox tenant, run during this stage with the IT contact in the room, removes 80% of the go-live risk. Postponing the SSO test until the end of pilot is the single most common scheduling mistake we see and the easiest one to avoid.
Content load is where the client’s content team has to actually deliver — and where the stage exits the moment one real user receives one real assignment, end-to-end. That milestone catches enrolment-rule bugs, course-visibility bugs, and notification-template bugs in one pass instead of three separate fire drills during pilot.
The minimum-viable governance package
For European SMEs, onboarding is also the moment the GDPR posture for the LMS gets set. Three artifacts live in the onboarding pack and travel with the client to the next audit:
- A list of personal data fields the LMS will store, mapped to the lawful basis under GDPR Article 6.
- A sub-processor disclosure naming Docebo and any third-party connectors used (the Docebo product list is the source for this).
- A retention schedule — how long completion records, certificates, and login history are kept after a user leaves.
These three documents take a half-day to assemble and save weeks of back-and-forth when a procurement team or an auditor asks. Spanish SMEs serving public-sector clients also need to add the ENS classification of the LMS hosting tier; Docebo’s EU multi-tenant on AWS Ireland qualifies for ENS Medio with the right compensating controls, but the classification claim has to be in writing and produced before, not after, the contract is signed.
When to deviate from the playbook
Three situations justify changing the standard 5-stage flow. First, an SME with under 25 users can collapse Discovery and Configuration into a single 5-day sprint — the questionnaire still gets sent, but the answers come back in a single working session. Second, an SME inheriting a partial Docebo install from a previous vendor needs a Migration stage between Discovery and Configuration; the data audit there is non-trivial and skipping it produces silent record loss. Third, an SME adding Docebo Connect integrations alongside the core LMS rollout should sequence the integrations after Pilot, not before — a broken integration discovered before pilot is a launch blocker; after pilot it is just a backlog item.
The thing that does not change: every stage produces a written exit-criterion confirmation. No verbal sign-offs. The 4-week win-rate depends on it.
Ready to get started?
Working on this yourself? J4SGON S.L. delivers Docebo Connect, HRIS, SSO and migration work for European organisations — see what a scoped engagement covers or describe your project and we will reply with a written scope.
Tell us what you are integrating or migrating
Send the platform, the systems involved and where you are stuck. You get a written scope back — phases, deliverables and what is out of scope — before anything is billed.