Delivery
Deploy in your environment, through to real use
We do not deliver a demo and then go silent. Diagnosis, design, setup, team training: delivery holds until the gesture has become daily.
Start through the right door
A useful exchange starts with the object: training, a solution, someone to intervene. A question — information, not a need to frame — belongs on the contact page.
General entry
You know you have a need, not yet in which form. One page, then you choose.
OpenA solution to deploy
A flow that costs, a tool that does not hold: describe what slows the work, and the expected result.
OpenTraining to run
Audience, objective, date constraints. The catalogue can serve as a starting point.
OpenWrite to us
Information, a partnership, a message that is not a need to frame: contact, not the request path.
Open
Course of a mission
Qualify
Understand the flow, the people, the tools already there, what is blocking. An Unlock request stays a solicitation until it is accepted.
Design
Target a priority process, draw the assistance, the documents, the access rights. We do not extend before we have seen the first use hold.
Set up
Integrate in the real environment — not in a demo copy. Your teams see the gesture in their day, not in an isolated workshop.
Train and stay
The people who do the work learn the new gesture. Unlock stays until the use no longer needs to be explained each time.
What “delivery” means here
It means a contact person, a file, documents, a plan. It does not mean a permanent on-site presence, nor a contractual deadline that this page would not display.
Deadlines, prices and terms of a mission appear in the proposal and the contract, not on the site. The terms of sale set the frame.
For recurring questions — response times, training, data, collective — see the frequent questions.
