/services/odoo-training
Your team owns the system after we leave.
Role-based sessions on your own configuration and your own data, recorded and written up — not a generic Odoo course delivered to a room.
- Per role not per module
- Recorded every session, kept by you
- SOPs a deliverable, not a follow-up
Facts. - Per role · not per module - Recorded · every session, kept by you - SOPs · a deliverable, not a follow-up
/the-problem
Training is the deliverable most often quietly dropped.
It sits at the end of the plan, which is where the time goes when a project runs late. So it becomes a two-hour walkthrough the week of go-live, delivered to whoever was free, on a demo database, covering every module rather than the four screens each person actually uses.
Three months later the symptoms are consistent. One person has become the unofficial system expert and is now a bottleneck. Data quality drifts because nobody was taught why a field matters, only where it is. And a new joiner is trained by a colleague who was themselves trained badly.
So we train by role, on your configuration, with your data, and we record it. The recording matters more than the session — it's what the fourth hire watches in a year's time, when everyone who attended has forgotten there was a session.
/what-it-changes
What it changes
- A session per role, scoped to what that role actually does
- Delivered on your configuration with your master data
- Every session recorded and handed over
- Written SOPs per role, in your document store
- Key-user sessions for the people who'll answer questions internally
- A UAT script your team runs, so you find out whether the training worked
- A refresher after go-live, once real use has surfaced real questions
- No single person becomes the system's only expert
- New joiners onboard from a recording, not a colleague's memory
- Data quality holds, because people know why a field exists
- Support tickets fall to genuine issues rather than how-do-I questions
- Process changes get made in the system rather than around it
- You can replace your ERP partner without replacing your knowledge
/how-we-run-it
Five stages, run alongside the build rather than after it.
Training that starts at go-live is already late. We schedule it against configuration milestones, so people learn on a system that's real.
-
01
Role mapping
Who does what, and which screens each role actually touches. Usually fewer than anyone expects.
1–2 days
-
02
Key users first
The people who'll answer internal questions, trained deeper and earlier.
1 week
-
03
Role sessions
Each role, on your configuration, recorded. Small groups; a room of thirty is a presentation, not training.
1–2 weeks
-
04
UAT
Your team runs the scripts. If they can't complete a task, that's a training gap found before go-live.
1 week
-
05
Post-go-live refresher
Four to six weeks in, when the real questions have surfaced.
0.5 day
/what-you-get
Four artefacts you keep.
Training is worthless if it exists only in the memory of the people who attended. Everything below outlives them.
Session recordings
every role session, in your document store. The onboarding material for every hire after this one.
/02Written SOPs
step by step, per role, screenshotted from your system rather than a generic one.
/03UAT scripts and results
what was tested, by whom, and what failed the first time.
/04Key-user notes
the deeper material for whoever answers questions internally.
/where-this-fits
What comes before this, and what comes after.
Training runs alongside implementation and migration, not after them. It's also the cheapest thing you can add to a system somebody else built badly — often the fastest way to make an unloved Odoo instance usable.
/questions
Asked on every first call.
-
Yes, and it's one of the more effective things we do. It starts with a short configuration review, because we need to know why the system was built the way it was before teaching anyone to use it — and occasionally that review finds the training gap is really a configuration problem.
-
Small groups, by role. Beyond about eight it stops being training and becomes a presentation, and the difference shows up three months later. We'd rather run the same session twice.
-
For general Odoo capability, it's good and we'll point you at it. But it teaches Odoo, not your Odoo — and the gap between those is where most training fails. Our sessions are on your configuration, with your data and your process names.
-
It's the most common reason training under-delivers, and it's why we record everything and schedule against configuration milestones rather than the week of go-live. But someone on your side has to protect the time. We'll tell you early if attendance suggests that isn't happening.
-
Yes — role-based training and written SOPs are deliverables of a phase-one implementation, not extras. This page is for teams who need more than that, or who have a system already and never got it.
/next
Tell us who the bottleneck is.
Thirty minutes, no slides. We will tell you straight if Odoo is not the answer.