Your shop floor tool depends on one person.
We take over maintenance after reading the code: the knowledge comes out of one person’s head, and changes start moving again.
“The costing tool was written by someone who used to be in the engineering department. He’s gone now.”
A shop floor or costing tool written in-house always ends up untouchable: changes get put off, incidents depend on one person, and workarounds take hold.
The risk isn’t a breakdown, it’s changes grinding to a halt — the day the tool no longer keeps up with the product range, it becomes the problem it once solved.
- A documented takeover phase, before any commitment
- Corrective and evolutive maintenance taken over by us
- An included volume of changes, directed by you
- An open door to modernisation, if the takeover shows what needs rebuilding
- Developers supplied on a time-and-materials basis
- A takeover without reading the code first
- A service-level commitment on software whose condition hasn’t been assessed
- A foot in the door to sell you something else
We read the code and its history, talk to the people who use it, and come away with what can be taken over, what must be rebuilt first, and the takeover timeline.
The takeover runs over an initial year, with a volume of changes that you direct. If scoping concludes that a rebuild is needed, modernisation is handled separately, priced before it starts.
