Art deco illustration: stepped brass tower among stylised clouds, with signal arcs and sunburst rays on a navy background

Services · Cloud and operations

The only constant is change.

Transformation, migration and operational optimisation. Cloud, on-premises or hybrid – the right choice, and an implementation that keeps operations running.

Timeframe

From 4 weeks to 1 year

Rough estimate – I adjust it after our first meeting.

Environments

Azure, AWS, GCP and hybrid

Independent

No ties to suppliers

The problem

In-house or outsourced operations?

Many companies end up in one of two camps. Either they move to large international providers and lose the fast, personal support they actually need – “I’ll just call the local IT guy”. Or they keep their local IT guy, but lack specialist expertise.

There is rarely a simple answer. Outsourcing can be cheaper, more scalable and more secure – but it can also become more expensive, more complex and create a supplier dependency that is hard to get out of. The right choice depends on your systems, your processes, your size and where you are heading.

I help you compare the options, explain the differences clearly and develop a strategy that fits your size and business. I stay with you all the way – from requirements and evaluation to decision and procurement.

Art deco emblem: brass server cabinet and cloud connected by an arc, on a navy background

Examples

Real-world experience.

100 clients in 6 months

I personally led a migration of 100 clients from one data hall to another in 6 months.

A project that was stopped

I have been part of stopping a project for the benefit of the client’s budget. The business case did not hold up.

Not always to the cloud

Sometimes the right answer is to bring back in-house parts that have cost more outside than they should, merge several suppliers into one, or build a hybrid where sensitive data stays on-premises.

Rarely the technology

In my experience, it is rarely the technology that makes or breaks it, but the planning, communication and risk management.

What is included?

This is what I review.

Current state

Mapping of your existing infrastructure, applications and dependencies. What do you actually have?

Strategy

Cloud, hybrid or on-premises? Azure, AWS, GCP or a combination?

SLA comparison

What do the suppliers promise and what do you need? Requirements are matched against the offers, and the pitfalls in the small print are highlighted.

Migration plan

Prioritisation of migration waves, rollback strategies and timeline. Starting with a PoC to build confidence before you take the full step.

Implementation

Support throughout the journey – from landing zone and security configuration to go-live and handover.

Art deco emblem: brass document with a checklist, on a navy background

What you get

Everything is examined with an open mind – including backing out of a cloud contract that no longer fits your business.

Examples of measures

  • New operating environment live within the agreed time and budget
  • SLA levels verified and approved by the business
  • No unplanned downtime during the migration
  • Clear documentation of the new architecture and responsibilities
  • Cost per service known and comparable before and after
  • Supplier dependencies mapped and accepted

How it works

Timeframe: from 4 weeks to 1 year

Rough estimate – I adjust it after our first meeting.

Weeks 1–2

Mapping and current-state picture. Systems, contracts and dependencies are inventoried.

Weeks 3–4

Choice of strategy and supplier evaluation. The options are compared and you get a recommendation with clear pros and cons.

Week 5 onwards

Migration planning and implementation in prioritised waves, with full operations throughout the process and go/no-go points along the way.

An operations strategy can be set in a few weeks; a full transformation can take a year. A transformation takes energy out of an organisation – the right pace, clear communication and protecting the core business are as important as the technology.

What do I need from you?

  • A non-disclosure agreement (NDA), signed before anything starts.
  • Access to relevant people – short conversations, on your initiative and with your approval.
  • Openness about the current situation – documents, contracts, system overviews and, ideally, your own thoughts on what isn’t working.

Next step

Facing a crossroads?

Guarantee: if I don’t add value, you get your money back. I don’t sell hours.

How an assignment works →