Outsourcing BI estate maintenance: what nobody tells you

The decision to outsource BI estate maintenance is never taken lightly. It usually comes after a triggering event: the departure of the one person who "knew everything", a failed upgrade that no one can diagnose, or simply the realisation that maintaining legacy BI in-house costs more than it should.

What’s striking is that most CIOs we speak with don’t question the principle of outsourcing. What they fear is knowledge transfer. And they’re right — because the standard model of knowledge transfer is fundamentally broken.

The problem with oral knowledge transfer

The standard outsourcing model relies on a transition phase where the incoming consultant spends 4-8 weeks paired with the outgoing team. On paper, it’s logical. In practice, it fails more often than it works.

First, the outgoing employee isn’t always motivated to share (especially if they’re leaving due to a disagreement or layoff). Second, even with the best will in the world, nobody can transfer 10 years of accumulated knowledge in 8 weeks.

Finally, oral transfer leaves no trace. If the incoming consultant leaves in turn 18 months later, you’re back to square one. Knowledge, once again, has left with the person.

The alternative: automated audit as the foundation

The approach that works is fundamentally different. Before any pairing phase, a scanner analyses the entire estate through source code reverse-engineering. The result is a complete, objective, permanent map of the estate.

This map serves a dual purpose. On one hand, it constitutes permanent estate documentation — independent of any person, including the maintenance provider. On the other hand, it dramatically accelerates onboarding: the incoming consultant arrives with a complete understanding of the estate.

The real criteria for choosing a maintenance provider

The BI maintenance market in France is dominated by a handful of generalist IT services companies (Capgemini, Accenture, Sopra) and some specialist firms (DeciVision, Keyrus, and independents like Decinova). The evaluation criteria that matter are not the ones you’d expect.

Ask how they handle turnover of their own consultants. A maintenance provider that sends you a different consultant every 12 months is reproducing exactly the problem outsourcing was supposed to solve.

Verify they distinguish between MCO and TMA. MCO (maintaining operational conditions) covers monitoring and incidents. TMA additionally covers enhancements (new reports, new source integration, migration support). A provider that mixes the two is probably underdimensioned.

Test their ability to audit before signing. A provider that offers a free audit of your estate before the maintenance contract proves two things: they have the tools to understand your environment, and they’re confident enough in their value to invest before billing.

The real cost: interne vs. externe

The naïve calculation is to compare the daily rate of an external maintenance consultant with the loaded salary of an internal employee. This calculation always favours in-house — and it’s always wrong.

The real cost of in-house maintenance includes the loaded salary of 1-2 experts (€120-180K/year), the cost of their ongoing training on evolving technologies (SAP publishes a new version every 2 years), the risk of departure (and the 3-6 months of recruitment + onboarding to replace them), and the opportunity cost.

A well-sized maintenance contract covers these risks for 40-70% of the in-house cost, with a contractually guaranteed SLA. The difference funds time freed up for your internal teams to work on higher-value projects.