Method

Diagnose, fix, prove, hold.

The same four stages on every engagement. Each one ends with something you own, and you can stop after any of them without owing the next.

  1. 01

    Diagnose

    5 days

    Findings in writing, ranked by severity, each with the cost of leaving it alone. Fixed price. You own the document whether or not we continue.

  2. 02

    Fix

    2–6 weeks

    Agreed scope, fixed price, explicit definition of done. No hourly billing, no scope drift, no surprise invoice.

  3. 03

    Prove

    2–4 weeks

    Before and after, measured. If the numbers did not move, that gets said out loud rather than buried in a status deck.

  4. 04

    Hold

    monthly

    Monitoring, alerting and a monthly review, so the thing that was fixed stays fixed. Optional, cancel any month.

Four things you can hold me to.

Not values on a wall. Each one is something you can point at mid-engagement and say I did not do.

Manmohan Singh mid-explanation in a meeting room

Evidence before opinion

I read the code, run the command and check the output before telling you what is wrong. A diagnosis from a conversation alone is a guess in a suit.

Fixed price, fixed scope

Hourly billing rewards the wrong thing. You get a number and a definition of done before work starts, and if scope changes you get a new number rather than a larger invoice.

Bad news travels fastest

If something is going to slip, or a measurement came back worse than hoped, you hear it that day. Status reports that only contain good news are how projects arrive at their deadline broken.

You keep everything

Source, documentation, infrastructure, reasoning. No dependency on me by design. If the engagement ends your team can carry it forward without a call.

Start at stage one.

A teardown is five days and a fixed fee. You get the document either way, and no obligation to continue.

Get in touch