Client loginDanskBook a consultation
All services
An independent view of what you already have

IT Consulting

Most organisations are not short of systems. They are short of a basis for deciding which ones stay, which ones go, and which ones are not worth any further attention.

Contact us
What you get
Portfolio overview with dependencies and lifecycle
Per-system verdict: build, buy, standardise or retire
Risk and cost picture
Prioritised action plan
Material that can be used directly by management
How we work

Advice without a stake in the answer

Independent of vendors
We do not sell licences and hold no agreements that make one answer more profitable than another.
Experience from the operations side
We have run platforms for thousands of users ourselves. The recommendation accounts for what has to be maintained afterwards.
Including the case for leaving it alone
The recommendation covers what is better left untouched. That is often the hardest part of the report.
What we know

A portfolio is an economy, not a list

Applications have a lifecycle, and the cost of a system is rarely the licence. It is the integrations, the dependencies, the knowledge that leaves with a single employee, and the speed the system permits the rest of the organisation. We assess the portfolio as one economy, not as a series of isolated decisions.

Technology rarely creates productivity on its own. The gain arises when workflows, roles and decision processes change with it, and it fails to arrive when they do not. Our assessment therefore covers the organisational complements: what has to change around the system for the investment to be worth anything.

Retiring a system is a decision on a par with acquiring one, and usually the harder of the two. It requires someone able to account for the consequences with enough certainty that management dares to act. That account is what we are good at, because we have stood with the operations afterwards.

Current knowledge

Where the field is moving

Licensing models have become a strategic risk

Recent years have delivered brutal lessons in what dependency means. Acquisitions where the price of an established platform multiplied at short notice. AI features bundled into licences nobody asked for, with price increases to match. Consumption-based models where the bill is only known afterwards.

The lesson is not that vendors are malicious. It is that a portfolio decision is also a negotiating position. The buyer who knows their alternatives and their exit cost pays a different price than the one who does not. Ignorance is priced, and priced hard.

We hold the portfolio up against the market at regular intervals: what would the equivalent cost today, what would a switch cost, and what does that mean for the next negotiation. That is not distrust of vendors. It is the precondition for dealing with them as equals.

Technical debt can be quantified

Technical debt was long an emotional argument: the developers sigh, management sees a system that works, and the conversation ends in a draw. There is no longer any reason for that. The debt can be measured in what it costs: how long a change takes, how often it fails, and how much capacity goes into keeping the system up rather than moving it forward.

Once those numbers are on the table, renovation turns from a technical complaint into an investment case with a payback period. Some systems turn out to be cheaper to live with than anyone thought. Others turn out to cost a full-time position a year in hidden friction. Both answers are valuable.

What matters is that the decision moves to where it belongs: with management, on an informed basis, with the consequences made visible. Technical debt is neither shame nor fate. It is a loan, and loans are managed.

Sovereignty has moved into procurement

Where data sits, and whose law applies to it, was for years something lawyers handled at the end. Not anymore. Geopolitical uncertainty and shifting administrative practice abroad have made jurisdiction a genuine requirement in European tenders and boardrooms.

At the same time the EU has given customers new rights. The Data Act, applicable since autumn 2025, establishes the right to switch provider and caps what a switch may cost. That changes the balance of power, but only for those who know their rights and have tested that their data can actually get out.

Our recommendations account for both: how sensitive each system is, what may sit where, and what it would cost to change your mind. Sovereignty is not an ideology. It is due diligence applied to dependency.

The engagement

Four steps, from starting point to operations

Step 01MappingApplications, integrations, dependencies, licence costs and lifecycle gathered in one place.
Step 02AssessmentEach system is assessed on strategic value, risk and cost, and placed as differentiation or commodity.
Step 03RecommendationWhat to build, buy, standardise or retire, with consequences and sequence.
Step 04HandoverYou get the material, so the decisions can be made and defended without us.

What the market has turned into a commodity should be bought rather than maintained. Attention belongs where you differ.

Niels Reinau, founder of iCEO
Who you'll work with

Niels Reinau

Niels founded iCEO after a career spent at IBM, at eBay, and running platforms at DanDomain and Zitcom, two of the largest hosting companies in Denmark. Zitcom is today team.blue Denmark, and DanDomain is one of the brands it still trades under. He works alongside consultants who have been in this industry for twenty-five years. You get that experience directly, not a partner at the pitch and a graduate on the work.