§ approach
How we engage
No black boxes. Here is what working with us actually looks like, from the first call to the handover.
§01 scope
We scope before we sell
We start with a short paid discovery — usually two to four days.
We read your accounts, your runbooks (or the gap where they should be), and talk to whoever carries the pager. You get back a written plan: current state, the risks ranked, the work sequenced, with named owners and a cost estimate. No month-long audit, no slideware.
§02 first-weeks
What the first two weeks look like
Week one
We get read access, map what’s actually running, and stand up the basics — a Terraform skeleton, somewhere for docs, one shared view of alerts. By Friday you have the current-state map and a plan you’ve signed off.
Week two
We ship the first real change — a right-sizing pass, a pipeline for one service, a noisy alert fixed. Small enough to be safe, real enough to show how we work. You review it like any other pull request.
§03 your-team
How we work with your team
We work in your repositories and your channels, not a walled-off vendor portal. Changes arrive as pull requests your engineers review and merge. We’ll join the standup and the on-call rotation when it helps. The measure of success is that your team ends up more capable, not more dependent on us.
§04 handover
What we hand over
Everything we touch is left documented — Terraform for the infrastructure, runbooks for the operations, short decision records for the choices and the why. At the end there’s a walkthrough and a handover of everything: repositories, state, and access. Keep us on or run it yourself; either way, you own it.
§05 shapes
Ways to work together
Project
A defined outcome with a start and an end.
Fixed scope — a migration, a cost pass, a pipeline build. We scope it, do it, document it, and hand it over. You are not left with a dependency.
Retainer
Ongoing reliability without a full-time hire.
A set number of engineer-days a month for on-call, maintenance, and steady improvements — with the coverage tiers agreed up front and written down.
Embedded
A team that needs senior hands inside it.
We work in your repos, standups, and on-call as part of the team for a fixed period, then hand back with your engineers levelled up rather than sidelined.
Sounds like the way you’d want to work?
Tell us what you’re running and we’ll suggest where to start.