How we work
No surprises, no lock-in.
Every engagement runs the same four stages. The depth changes with the size of the job; the order does not.
Four stages, one continuous conversation.
Most cloud work goes wrong in the same two ways: the plan is written before anyone has looked properly at what is already running, and the finished system only makes sense to the people who built it. We front-load the first problem and refuse to create the second.
The stages
Assess
Read-only access to your accounts, the bill, and whatever documentation exists. We map what is actually running — including the things nobody remembers creating — and finish with a written summary you are free to disagree with.
Plan
A prioritized list of what to change, each item costed in both money and risk. You decide what makes the cut. Prices firm up at the end of this stage, once we know what we are dealing with — not before.
Deliver
The work, sequenced so the risky parts happen while there is still room to change course. Everything lands as infrastructure as code, in your repository, reviewed by you. Weekly updates on what moved and what did not.
Hand over
Runbooks, architecture notes and a working session with your team. The measure of a good handover is that you could fire us the next day and nothing would break.
What you get
Everything we build is infrastructure as code in a repository you own, with documentation written for the person who inherits it — not a slide deck and a console full of hand-made resources.
What we will tell you
If the work does not need doing, we will say so on the first call. If your existing setup is fine, that is a useful answer and it costs you nothing. We would rather turn down a project than bill for one that does not move anything.
Planning a cloud project? Let's talk it through.
Book a free 30-minute consultation. Tell us where you are headed - migration, cost, architecture or resilience - and we will come back with a straight answer.
Book a free consultation