you may be confident you know the answer.
are you sure?
Over the years, we have asked business owners and companies questions they thought they already knew the answers to — until they discovered they didn't. Sometimes a closer look was enough to reveal the gap. In other cases, the answer only became clear when something went wrong — sometimes in a worst-case scenario. Before explaining our approach and the way we work, we want to start with some of those questions that led us to develop our method:
01 what if IT stopped
tomorrow?
Production and people stopped. What would it cost?
How long until you are working again?
How much of your work could you afford to loose?
02 you know where your data is
do you know who controls it?
Who accesses and controls the platforms holding it?
And under which jurisdictions do they operate?
How much control do you need — and at what cost?
And what if there is no suitable European alternative?
03 what if the hardware you planned
isn't available?
What happens when delivery takes months instead of days?
Does your hardware lifecycle fit the reality of
your business?
04 did you digitalize your company -
or did you just buy some technology?
Did technology make work simpler, or add another step?
Does your technology work with your processes —
or just alongside them?
the reality
The questions above relate to four areas of IT that directly affect how a business operates:
- Business continuity looks at what happens when IT stops working.
- Digital sovereignty looks at how much control you actually have over your data and the platforms holding it.
- Lifecycle & shortage looks at how hardware is managed, especially when availability, delivery times and prices can no longer be taken for granted.
- Digitalization looks at how technology supports and improves the way your business works — not simply at how many digital tools you have.
When we look at these questions together with our customers, the reality is often different from what they expected.
Click the corresponding number to explore what we commonly find.
01 - business continuity
what if IT stopped tomorrow?
Production and people stopped. What would it cost?
How long until you are working again?
How much of your work could you afford to loose?
The answers we hear most often sound reassuring:
- “We have a backup.”
- “We use the cloud.”
- “We have a support contract.”
- “We have someone who takes care of IT.”
Could something this small stop your entire business?
Your car doesn’t need a broken engine to leave you stranded. A loose screw can be enough — or one small component you had never thought about, which suddenly fails and isn’t in stock when you need it. The rest of the car may be perfectly fine. You’re still not going anywhere.
Your IT isn’t very different. You protected the expensive and obvious parts. Your server has a support contract. But what about everything it depends on?
A small device under a desk. A router on a shelf. A particular power supply nobody thought about until it failed. Individually, they may appear insignificant. But if everything else depends on them, their price tells you very little about the cost of their failure.
Have you identified every small component that could stop your business?
“Nothing like this has ever happened to us.”
Then one morning the systems don’t start — or you discover you’ve been attacked by cybercriminals.
The backup exists, but nobody knows when it was last tested. The latest — or perhaps the only — backup doesn’t work, or has been compromised as well. The person who normally takes care of IT is on holiday. Passwords, contacts and recovery instructions are stored on the system nobody can access. A failed component has to be ordered — and won’t arrive until next month. Nobody is quite sure who should make the first call, or what should happen next.
The clock is running. Your people are waiting. Your customers are waiting. When will you be working again?
Most companies have never had a serious fire. They still insure the building, install fire extinguishers and have an evacuation plan displayed on the wall. Not because they expect a fire tomorrow, but because they understand what it would mean if one occurred.
Technology risk is no different. The question is not only how likely something is to happen — but what it would mean for your business if it did.
02 - digital sovereignty
you know where your data is
do you know who controls it?
Who can access and control the platforms and infrastructures holding it?
And under which jurisdictions, do they operate?
How much control do you need — and at what cost?
A European datacenter doesn’t tell the whole story. Neither does a provider’s origin outside the EU alone.
Keeping everything on-premises can give you a very high degree of control. But that control comes with costs and responsibility: security, maintenance, redundancy, recovery and the expertise to manage it properly. Without the necessary investment, having everything under your own roof doesn’t necessarily make it safer.
Moving everything to the public cloud answers different problems. It can provide security, resilience and capabilities that would be expensive to build yourself. But cloud doesn’t automatically mean backup, lower costs or independence and control. Without the right planning, it can create dependencies and lock-ins that only become visible when you need to change something — or leave.
Neither extreme is the answer for every business.
That’s why we look at European Digital Sovereignty from a different perspective.
For us, it goes beyond data location. Access, control and jurisdiction matter — but so do functionality, quality and cost.
Where European solutions meet the requirements, we give them priority. But what if there is no suitable European alternative?
A business still needs the technology that allows it to operate effectively. Using a non-European platform does not have to mean giving up control over everything around it.
We can limit unnecessary dependencies, keep critical data independently accessible through local or European copies, separate services where appropriate and maintain realistic recovery or exit options. Where jurisdiction is relevant, it can also become part of the assessment.
Digital sovereignty also doesn’t have to happen overnight. Replacing established platforms simply to meet a predetermined cut-off date can create new costs, operational risks and unnecessary disruption.
We prefer a gradual approach: reduce dependencies where it brings real value, introduce European alternatives where they meet the required quality and cost, and plan migrations around the business — including existing processes, integrations and the people who use them.
The objective is not European technology at any cost. It is to move towards greater European digital sovereignty at a sustainable pace — while consciously managing the dependencies that remain.
Identify what you don't control. Understand what happens if it changes. Reduce the dependencies that can reasonably be reduced. Protect yourself against the ones you choose to keep.
Our approach starts without a predetermined answer. We combine on-premises, cloud and hybrid solutions according to business requirements, while keeping control over what is outsourced and avoiding unnecessary dependencies and lock-ins.
In practice, this can mean keeping critical data independently accessible through local or vendor-independent copies, separating services so that one provider does not become the only way to access or recover them, or maintaining an exit path before it is actually needed. Where control or jurisdiction matters, we consider not only where the data is stored, but also who operates the service, who can access it and under which jurisdictions.
Where they meet the requirements, we give priority to open and European solutions — based on quality and suitability, not ideology.
The objective is not independence at any cost. It is knowing where the dependencies are, keeping control where it matters and making sure there is a realistic way out when circumstances change.
03 - lifecycle & shortage
Traditionally, lifecycle management made hardware predictable.
You knew approximately how long equipment would remain in service. Replacement could be budgeted in advance. Systems could be replaced proactively before age increased the risk of failure. Environments remained more standardized and easier to manage.
Where the business required it, vendor support contracts could provide defined replacement and service conditions. In other cases, broad availability made fast replacement a reasonable alternative.
You didn’t wait for something to break and stop the business. You replaced it before it became a problem.
The conditions that made these models predictable can no longer be taken for granted.
Two things in particular have become much harder to predict: delivery times and prices.
Meanwhile, a planned replacement may arrive months later than expected or cost considerably more than budgeted.
And the alternative — waiting until something breaks and simply ordering a replacement — depends on availability that may no longer be there when you need it – or may come at an unaffordable cost.
Even a support or replacement contract cannot eliminate every uncertainty. Supply-chain disruption, shortages and geopolitical events can affect availability beyond the control of both customer and supplier, while contracts normally contain provisions for exceptional circumstances.
A contract can reduce risk. It cannot make unavailable hardware available.
Has your hardware lifecycle adapted to this new reality?
— or is it still based on the availability and prices we used to take for granted?
The answer doesn’t necessarily mean abandoning the lifecycle model you already have.
Where existing vendor contracts still provide the required service levels, acceptable costs and reliable availability, there may be no reason to change them.
But where the traditional model can no longer provide what the business needs, alternatives may have to become part of the lifecycle.
A system may remain in service beyond the manufacturer’s support lifecycle through specialized post-vendor maintenance, with defined service levels and access to spare parts. Professionally refurbished enterprise hardware with a support and warranty contrcat, can provide another option where performance requirements allow it.
In other cases, redundancy or hardware prepared in advance may provide better continuity. With today’s prices and uncertain delivery times, keeping a compatible replacement switch on the shelf can sometimes be more economical — and more predictable — than relying on an expensive support contract or hoping that a replacement will be available when it is needed.
But flexibility comes with a new problem: complexity.
What used to be one vendor, one contract and one replacement cycle may now involve several manufacturers, maintenance providers, sourcing channels and different lifecycle strategies across the same infrastructure.
That may reduce your dependency on a single model — but someone still has to manage it.
This is where we can help.
We can work alongside your internal IT team, existing suppliers and vendor contracts to plan and coordinate the different parts of your hardware lifecycle. Where appropriate, lifecycle management itself can become a managed function — giving you access to different vendors, maintenance models and sourcing options without requiring your internal team to manage every relationship and alternative individually.
Keep what works. Add alternatives where the traditional model no longer does. We help manage the complexity in between.
We start by understanding your requirements, risks and existing infrastructure — and build the lifecycle around them.
Talk to us about your hardware lifecycle
04 - digitalization
did you digitalize your company -
or did you just buy some technology?
Did technology make everyday work simpler — or add another step?
Does your technology work with your processes — or just alongside them?
When we get to know a new company, we frequently encounter:
Max from the company next door tells you over lunch how much things improved after moving to a new cloud subscription and replacing some of his devices. His business isn’t so different from yours. It sounds reasonable. You bought it too.
But is buying the technology enough to make it work with the way your company works?
We frequently encounter a different reality. The new systems are there and they work. The electronic invoice is created because it has to be. Around it, quotations still arrive by email, orders are confirmed on the phone, information is entered again somewhere else and documents are saved where only Maria knows how to find them.
When Maria is on holiday, some things wait until she comes back.
Maria isn’t the problem. Quite the opposite: she knows the customers, the exceptions and how things actually get done. But if the old process continues and the digital one is simply added beside it, technology hasn’t removed work. It has added another step.
And the answer isn’t necessarily to automate everything.
The more technology is adapted to the way your company works, the more customization and integration usually cost. The more you use technology as it was designed, the more your people may need to adapt and learn new ways of working.
There is no right balance for every company — or even for every process. Some things are worth automating completely. Others only partly. And sometimes the technology you already have can do more than you realize.
There is one more thing worth remembering. For years, paperless was treated almost as a synonym for progress. Today, when systems can become unavailable through a failure or cyberattack, a deliberately kept non-digital copy can sometimes be the most reliable part of a process.
Digitalize where it creates value.
Automate where it makes economic sense.
Keep the human where the human makes sense.
And occasionally, keep the piece of paper.
Digitalization isn't about making everything digital
predictable IT
Technology has become essential to how businesses operate. As that dependency has grown, traditional ways of managing IT have evolved — and need to evolve further.
Building on those existing concepts, we developed our own approach. We call it Predictable IT.
REACTIVE
Fix what breaks.
For many years, this was a reasonable approach. Technology supported the business, but fewer everyday processes depended completely on it. When something stopped working, somebody fixed it.
PROACTIVE
Prevent what you can.
As the dependency on technology increased, waiting for something to break became more expensive.
Monitoring, maintenance, updates and preventive replacement help identify problems before they cause an outage. This remains an essential part of good IT management.
But prevention has limits.
PREDICTABLE
Plan for what prevention can’t cover.
Cybercrime evolves. Providers can fail. Hardware can become unavailable. People make mistakes. Supply chains are disrupted and geopolitical events can change conditions outside anyone’s control. No technology, vendor or consultant can eliminate all of these uncertainties.
We call our approach Predictable IT. While predictability in IT is often associated mainly with costs, we extend the same principle to risks, outages and recovery.
It means considering the relevant exceptions that proactive management cannot prevent — and planning what to do when they happen.
A proper analysis and some preparation can make the difference between a planned response and improvisation: reducing downtime, limiting the impact on the business and avoiding unnecessary costs while operations are being restored.
Predictable IT doesn’t mean making everything more expensive or complicated.
The objective is not protection at any cost. It is the right level of preparation for the risk, impact and cost.
your business first
We aim to be technology and vendor-neutral. We don’t start with a preferred brand, technology or architecture. Where you already have a preference or an established environment, we can work with it — with internal expertise and certified partners covering most major technology brands.
We start with your business: what needs to work, what it depends on, what could interrupt it and what level of risk is reasonable.
The answer doesn’t always have to be more technology, but we wish to offer some examples of our approach:
recovery plan
Keeping a printed copy of the recovery plan, because when systems fail, the cloud or local system holding the digital copy may be exactly what you cannot access.
independent control
alternative lifecycles
Because the end of a warranty or vendor support contract, doesn’t necessarily mean end of useful life.
Reliable hardware can sometimes remain in service with appropriate third-party post-warranty support, instead of being replaced simply because the manufacturer’s support has ended.
documentation
Documenting how important things are done and where essential information can be found, so the business can continue even when the person who normally knows the answer isn’t there.
Good documentation supports your people — it doesn’t replace their knowledge and experience.
Sometimes the right answer is cloud. Sometimes it stays on-premises. Often different requirements lead to a combination of both.
this is how we do IT
Before choosing a solution, we need to understand not only the technology, but how the business actually depends on it, starting at the first step with a broader business inventory:
The technology follows the requirement — not the other way around.
every business is different
let's talk
We have given you an introduction to how we think and how we work. Behind it is a broader framework of products, services, technologies and expertise that we combine according to your requirements — rather than trying to fit every business into the same solution.
Maybe you:
- have a specific project in mind and need the expertise or resources to implement it;
- are looking for a new IT provider or technology partner;
- are considering outsourcing part or all of your IT for the first time;
- you are looking for specific hardware, a difficult-to-source component or replacement part;
- want a second opinion on an existing environment, project or proposal;
- simply want an independent check of your current IT situation;
- or recognized one of the topics discussed above and would like to explore it further.
- just want to have a coffee and talk about IT — getting to know each other doesn’t need to start with a project.
You don’t need to know the solution before talking to us.
Tell us what you have in mind, what concerns you, or what you would simply like to have checked. We can start from there.