Eidō isn't deployed self-service. Every configuration depends on your structure, your uses and the hosting mode you choose. That's why we build each proposal with you.
Your price depends on three objective parameters. Understanding them is also what lets us support you better.
The number of active licences, the depth of your organisation chart, the volume of users involved in the deployment. A 40-person SME and an 800-person multi-site mid-cap don't have the same needs, and don't pay the same price.
Shared SaaS, dedicated instance, or installation on your own servers: three levels of technical requirement and sovereignty, three price levels. You choose the perimeter your data stays within.
Pilot on one department, progressive deployment in waves, or full organisation rollout: the pace you choose directly influences the sizing of the support.
We recommend starting on a defined perimeter (a department, a BU, a cross-functional project) and letting the results speak.
A 3 to 6 month POC on a real topic gives you what no demonstration can: the certainty that it works in your context, with your teams, on your stakes.
If you choose to extend the deployment to other perimeters, Eidō's architecture is built for it. Adding a department, integrating a new BU, extending to a second site: the structure adapts without reconfiguring what already exists. What you built on the pilot perimeter stays intact and becomes the base for the next rollout.
An Eidō POC usually runs 3 to 6 months. It mobilises 15 to 25 days of support from our teams, spread across the period.
Three modes to choose from, depending on your level of requirement in terms of hosting, customisation and sovereignty.
Every delivery includes what is needed for the tool to be actually used, not just installed.
Your space is configured before your teams step in. Org chart, instances, method, starting objectives: everything is in place the day you start. You don't land on a blank page.
The people who will keep Eidō alive every day are trained on your own cases, not on generic examples. By the end of the training, they know how to pilot. Not just how to navigate.
Our teams stay close until your contributors take ownership of the tool. Human support, not a documentation you read alone on a Sunday evening.
A follow-up checkpoint is planned after the first weeks of use. To adjust what needs to be, before it becomes a habit.
We always start by talking. The time to understand your organisation, your constraints, and what you are really looking for, before proposing anything.
We take the time to understand your organisation: its size, its pilotage stakes, its technical and regulatory constraints. You ask your questions. We ask ours.
We submit a detailed proposal: deployment scope, hosting mode, licence volume, included support.
Your space is configured to fit your real org chart, your methods, your first objectives. Your champions are trained. You don't start from zero.
Your teams step into the tool with a context already in place. The first progress signals surface. You see what's happening, without chasing anyone.
A 30-minute demo, prepared from your context. You leave with a quantified estimate of the time and the cost Eidō can give you back.
