How We Work

No mystery, no black boxes, no “just trust the magic”. A clear sequence of steps, written down and agreed before anything important changes.

The short version

You do not get handed to an anonymous “account manager” and you do not wake up to surprise changes. From day one you deal with someone technical. We map what you already have, agree where you want to go, and then move there in calm, well-documented stages.

The steps, in order

Step 1

Discovery

A short call or email exchange where we work out who you are, what you run, and what is currently keeping you awake at night. We do not need a 40-page brief; just an honest description of reality.

If we are not the right fit, we will say so quickly and point you somewhere more appropriate.

Step 2

Baseline map

We build a simple map of what you already have: domains and DNS, hosting providers, email, code repositories, storage, backups and the “mystery boxes” nobody quite understands.

You get a written baseline: something you can show to a colleague, a client or an auditor.

Step 3

Proposal

We propose a future state that matches your risk appetite, budget and capacity. That usually includes a cleaned-up architecture, a backup and recovery story, and a plan for how Git, storage, websites and social presence fit together.

The proposal is written in plain English, with enough technical detail to be honest but not theatrical.

Step 4

Implementation

Work is carried out in agreed phases. We prefer incremental changes over dramatic “big bang” cut-overs wherever possible. You see what is happening, why it is happening, and what the fallback is.

Where appropriate we schedule changes out of hours and keep a simple change log as we go.

Step 5

Documentation and handover

At the end of the project you receive documentation that covers the important things: where services live, how they are backed up, who has access, and what to do when something misbehaves.

The aim is not a glossy manual, but a small set of notes that are actually read and used.

Step 6

Ongoing care (optional)

Some clients are happy to run everything themselves once the work is done. Others prefer us to stay involved on a light-touch basis: periodic checks, small adjustments, and being on hand when something odd happens.

Ongoing support is always agreed explicitly; there are no automatic retainers.

What you can expect from us

Plain language and clear boundaries.
No upselling into platforms you do not need.
Written notes and diagrams rather than “it lives in my head”.
A bias towards open-source tools where sensible, not ideologically.
A healthy respect for backups, documentation and exit plans.

Ready to start the conversation?

Tell us what you are running today and what you would like to be true in twelve months’ time. We will respond with a simple view of whether we can help and what that might look like.

Request a discovery chat View indicative pricing Return to main company site