Digital and AI

IT master plan: a three-year roadmap for mid-sized companies

Stacked-up applications, forgotten contracts, untested backups: an IT master plan restores order and sets three years of priorities, with a budget attached.

By Benjamin Forte · 19 October 2026 · 7-minute read

In a company of 50 to 250 people, IT tends to build up in layers: accounting software chosen ten years ago, a business tool added for one client, spreadsheets bridging the gap between the two. Each decision made sense at the time. Together, they become expensive and fragile.

An IT master plan, sometimes called an information systems master plan, is how you take back control. It is a short document that says where you stand, where you want to be in three years, in what order and at what cost. Here is how to build one in New Caledonia in 2026, where every franc invested has to be justified.

Signs you need an IT master plan

You start an IT master plan when IT begins to hold the business back. The same warning signs come up again and again:

the same data is keyed in two or three times, into tools that do not talk to each other;
nobody can say what IT costs each year, subscriptions and providers included;
only one person, in-house or external, really understands the system;
a new software project, an ERP for instance, is on the table without anyone knowing what it should replace;
management is unsure about artificial intelligence, without knowing whether its data could support it.

That last point is not theoretical. In France, 31% of companies with 50 to 249 employees used AI in 2025, up from 15% a year earlier, according to INSEE, the French national statistics institute. Among non-users of that size, 66% cite a lack of expertise; across all sizes, 38% of non-users point to incompatibility with their existing equipment, software or systems.

There are no equivalent figures for New Caledonia, but the lesson holds here too: without a clean foundation, new uses stay out of reach.

The inventory: applications, data, contracts, skills

An IT master plan starts with an honest picture of where you are. Not a 200-page technical audit, but a snapshot a management committee can read. Four lists are enough.

Applications: for each one, who uses it, for which process, who maintains it, what it costs and when support ends.
Data: where customer, stock, payroll and document data live; who is responsible for them; where the backups are and when a restore was last tested.
Contracts: licences, hosting, maintenance and telecoms, with renewal dates, notice periods and reversibility clauses, meaning your ability to recover your data and switch provider.
Skills: who does what in-house, what depends on a provider, and which tasks nobody really owns.

Add a fifth column, the most useful one: what your teams think. Half a day of interviews with department heads often reveals more than any analysis of the servers.

Risk and continuity: lessons from 2024

2024 was a reminder that IT continuity is not an abstract topic in New Caledonia. On 18 August, the operator Lagoon was hit by a ransomware attack. According to the daily Les Nouvelles Calédoniennes, internet access was cut for nearly 48 hours for about 40% of its subscribers, email was down for two weeks, and hosted servers were unreachable for three weeks for 1% of its business customers.

Three weeks without servers means three weeks without invoicing, without customer files, sometimes without payroll. The crisis that began in May 2024 raised another question: could your business keep running if its premises became inaccessible? Our founder created and ran a New Caledonian cloud operator: the real question is not whether an incident will happen, but how long the business can cope with it.

Your plan should therefore rank each application on two criteria: the impact of an outage on the business, and the downtime you can accept. The first project often follows from that ranking: tested off-site backups, fallback hosting, a written recovery plan. The same article notes that the EU’s NIS 2 directive does not yet apply in New Caledonia. No rule forces you to act; your own interest does.

The target and the three-year roadmap

Once you know where you stand, the target should come from the company’s priorities, not from vendors’ catalogues. If your challenge is tracking margins per project, the target is not “a new ERP” but “reliable cost data per project, available every week”.

Three years is a good horizon: long enough to replace a core system, short enough to stay credible. The roadmap usually breaks down like this:

Year 1: secure and clean up. Backups, access rights, renegotiated contracts, unused applications switched off. These quick wins help fund what follows and build confidence.
Year 2: the structural project. Replacing or consolidating the management system, with written requirements and a competitive tender.
Year 3: make use of it. Dashboards, automation and first uses of AI, on data that can now be trusted.

When choosing an ERP, one simple rule: describe your processes before you look at software, and check that the vendor or its integrator can support you from New Caledonia, during Noumea working hours.

Budget, funding and trade-offs

The climate calls for restraint. In the second quarter of 2026, banks granted 12.4 billion XPF in new business loans, 10.4% less than a year earlier and well below the long-term average of 21.9 billion, according to IEOM (Institut d’émission d’outre-mer, the central bank for France’s Pacific territories). The average rate on equipment loans stood at 4.36%.

Investment fell 12.5% in volume in 2025, after a 24.3% drop in 2024, according to ISEE, New Caledonia’s statistics institute. In this context, each line of the plan should show its full three-year cost: licences, integration, training and staff time, minus the savings from what you switch off.

On the funding side, the South Province’s business aid code (CASE, Code des aides pour le soutien à l’économie) includes a grant for intangible investment that covers, among other things, software bought to develop the business. The base rate is 25%, with up to 15 extra points for priority sectors, capped at 2 million XPF (articles 1223-1 to 1223-3). It is reserved for eligible sectors: retail, construction, transport, healthcare and finance are excluded, with some exceptions. Check your eligibility before building the funding plan.

Finally, make choices. A master plan that keeps everything decides nothing. Rank projects by business value and by the risk they remove, and accept that some will have to wait.

Governance: committee, indicators, a shared IT director

Without governance, an IT master plan ends up in a drawer. Three things keep it alive.

A quarterly committee: the managing director, finance, one or two business managers, and the IT manager or main provider. One hour, a progress chart, decisions in writing.
Five indicators at most: annual IT cost per employee, project progress, major incidents, date of the last successful restore test, user satisfaction.
A named lead: many companies of this size have no IT director. A part-time shared IT director, a few days a month, can take on that role: preparing the committee, managing providers and keeping the whole consistent.

IT governance also comes down to one rule: every new piece of software goes through the committee, even if it is free, even if it is “just for one department”. For an overview of the digital issues facing a New Caledonian company, see our Digital page.

Costly mistakes

Starting with the tool. Choosing software before describing your processes means bending the company to fit the software, or paying heavily to customise it.
Underestimating staff time. An ERP change ties up your best people for months. Build it into their workload.
Forgetting the exit. A contract without a reversibility clause locks you in more surely than any technology.
Doing everything in one year. The three-year roadmap exists to spread the effort, financial and human.
Never testing a restore. An untested backup is an assumption, not a safeguard.

An IT master plan lends itself to an engagement with a scope and price set in advance, like those of our Build service.

Key point

A good IT master plan fits in a few pages: an honest inventory, a target drawn from business priorities, a costed three-year roadmap and a committee that actually meets.

Frequently asked questions

What is the difference between an IT master plan and an IT audit?

An audit describes the current situation and its weaknesses. An IT master plan starts from that picture but goes further: it sets a target, an order of priority, a three-year budget and a governance structure to track progress.

How long does it take to draw up an IT master plan?

It mainly depends on the size of your systems, the documentation you already have and how available department heads are for interviews. Set a date for presenting the plan to the management committee from the start: it is the best way to stop the inventory from dragging on.

Do you need an IT director to run an IT master plan?

Not necessarily a full-time one. In a company of 50 to 250 people, a clearly named internal lead, backed by a shared IT director a few days a month, is often enough. What matters is that one person answers to management for the overall consistency.

Sources

Lay the groundwork for your IT master plan

CAP LARGE, our offer for companies and organisations of 50 to 250 people, starts with a fixed-price diagnostic at 510,000 XPF excl. tax, presented to your management committee. It is the basis for your roadmap.

Discover CAP LARGE Book a meeting