Training
Capability that stays in-house after we leave.
When this fits
A system was handed over and the team is operating it cautiously rather than confidently.
Knowledge sits with one or two people and everyone knows it.
You are building an internal capability rather than outsourcing it.
How we work within it
On your systems, not a lab
Training against the estate the team actually operates. Generic courseware teaches the product; this teaches your configuration of it.
Role-based rather than one-size
What an operator needs is not what an architect needs. Sessions are shaped by what each role has to be able to do unaided.
Demonstrated, not attended
The exit criterion is your team performing the operation, not a completed attendance list. If they cannot, the training is not finished.
What you get it on
Training, across these domains
A delivery model is not a product. These are the technology domains we work in through it — start from the one your problem sits in.
Engagement and pricing model
Per programme, sized by roles and systems covered. Where it follows one of our implementations it is normally scoped into the engagement, because handover without enablement is not handover.
What we commit to, and what we measure
Operations your team can perform unaided afterwards, tested rather than surveyed.
Escalations to us for tasks the training covered — the honest measure of whether it worked.
Coverage: how many people can perform each critical operation, not just whether one can.
Targets are set per engagement and written into the agreement. We do not publish a number here, because a service level that is not attached to a specific scope is not a commitment.
Questions we are asked
Is this vendor certification training?
No. Certification courses teach a product in general; this teaches your systems as configured. The two complement each other and only one of them prepares somebody for your three-in-the-morning.
Can it be delivered in Arabic?
Yes. Technical training in the language the team works in is not a courtesy — comprehension under pressure is the whole point.
How many people can attend?
Small enough that everyone gets hands on the system. A session where most people watch is a presentation, and it should be priced and described as one.
What if the team turns over afterwards?
That is why documentation and recordings are deliverables, and why coverage is measured across people rather than concentrated in one. Turnover is a known condition, not an excuse.
Do you train on systems you did not build?
Yes, after learning them well enough to teach them. That assessment is part of the engagement and it is honest about what it finds.
Start with an assessment
The fastest way to a useful answer is a short, scoped look at what you already have.