Skip to content

How we work

How an engagement runs, start to finish

The same route whether it ends in a document or in a standing arrangement. Most of it is also stated on the pages it belongs to; this page puts it in order and links there.

Order of work

Before anything is touched

Measurement comes before a plan, and a plan comes before a price. Each step ends in something you hold.

  1. A 30-minute call

    What you run, what hurts, and whether a diagnostic would tell you anything you do not already know. If it would not, we say so on the call and that is the end of it.

    You get: the list of read-only accesses a diagnostic needs

  2. Read-only inventory

    A read-only role and, where it helps, a metrics agent. Two weeks of measurement before any change, so the plan starts from what runs, not from what the diagram says.

    You get: a read-only inventory and fourteen days of measured data

  3. A plan with a price

    What we would change, in what order, what it costs and what we will not touch. Fixed scope, priced before it starts.

    You get: a plan with a price and the order of work

  4. Operate, or hand it over

    A standing arrangement with a monthly written summary — or infrastructure as code, runbooks and decisions left in your repository so your team carries on without us.

    You get: the monthly summary while we operate; at hand-over, infrastructure as code, runbooks and decisions in your repository

Price

How a price is formed

Scope is written before the price.

For an audit or ongoing operation the price covers the named work, not the hours spent; consulting is the one format billed by the day, and it is still scoped to a question.

Anything outside the scope is a new short agreement.

Ways to work with us

A month

During ongoing operation

Alerts arrive where your team already looks. There is a stated window for acknowledging them, and an engineer behind it.

A fix that needs a change nobody agreed stops at the plan and comes back as a question. Urgent action during an incident follows a runbook agreed beforehand, and is written up afterwards.

Each month ends in a written summary: what changed, what broke, how capacity moved and what it cost. An incident gets its timeline and its cause in the next one.

The response window, who answers, and what a month contains
Illustrative layout · figures from the EFS case

Ending

If it ends

Either side can end it with 30 days' written notice.

What you already hold stays: the repository, runbooks and decisions. What we hand over on the last day: the access list to revoke and the last monthly summary.

Nothing we set up needs us to keep running. The MetrixForge agent is the one optional piece: keep it, or remove it together with the alerts that come from it.

All questions

Start with the part that costs nothing

A fortnight of measurement, a readout and a document you keep — whether or not anything follows it.