From scoping to the first signed order.
A business application is not rolled out by handing round logins. Here is the path we follow, what we expect from you, and what stays with you once the platform is live.
A pilot first, wider deployment afterwards.
We never start across a whole company. One region, one team, one trade: long enough to check that the configuration holds up against reality, and that technicians use it without being watched.
-
Scoping 1 to 2 weeks
We look at your operation as it is: your statuses, your types of work, your contractual deadlines, your clients, your report formats. We settle the scope of the pilot and which modules are switched on.
-
Configuration 1 to 2 weeks
Statuses and the deadline-pausing rule, procedure sets, equipment classes, roles and scopes, order and invoice templates under your letterhead. This is the stage that decides the quality of your figures.
-
Data migration 1 week
Import of your customers, your sites with their coordinates and access instructions, your teams and your parts reference, from your existing files. Past intervention history can be brought over if it is usable.
-
Training 2 to 3 days
Three audiences, three separate sessions: technicians on field mode, dispatch on qualification and assignment, the administrator on configuration. The aim of the last one is that you no longer need us.
-
Pilot 4 to 6 weeks
One team, in real conditions, with a weekly review. This is where the gaps between the written procedure and the real one surface, and this is the moment to fix them, not afterwards.
-
Wider deployment
The other teams, the other branches, the other countries, with configuration that has already been proven. Each new entity means a data migration and training, not a full scoping exercise.
These durations are indicative. They depend above all on the state of your existing data and on how available your teams are during scoping. We would rather announce a realistic path than a pleasant deadline that will not be met.
Three things, and they matter more than the rest.
Someone who can decide
A person on your side who knows the operation and can settle a question. Without one, configuration bogs down in approval meetings.
Your data, imperfect as it is
Your files of sites, customers and teams as they exist. We take care of cleaning them; we cannot invent them.
Technicians during the pilot
A real team, on real jobs. A pilot played out by managers in a meeting room never reveals what goes wrong up a tower.
Running the platform
Support
On the channel your teams already use, during your hours. Blocking incidents come before change requests, always.
Backups and monitoring
Daily backup, tested restoration, availability monitoring. Detailed on the security and data page.
Changes
What is configuration, you do. What needs development is quoted and scheduled, then folded into the platform’s later releases.
Reversibility
Your data belongs to you and is handed back on request, with no exit fee. The clause is in the contract.
See the platform run on your own cases
An hour is enough: you open a request, assign it, close it and print the signed work order. Then we look at how your operation fits in: your customers, your sites, your contractual deadlines.