Your business application depends on a single person.
We take over maintenance after reading the code: the knowledge comes out of one person’s head, and changes start moving again.
“The guy who wrote it retires in a year. Nobody else ever opens that code.”
Software that runs but that nobody wants to touch costs you three times over: every change is overestimated, every incident depends on one person, and nothing gets decided without them.
This isn’t an IT risk, it’s an operational one — and it materialises the day that person leaves.
- 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 release history, talk to the people who maintain 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 as a separate project, priced before it starts.
