Approach

Diagnose, Deliver, Operate in one engagement

We work in three phases, each with a clear output. You review the result before deciding on the next step.

Sketching a roadmap on a whiteboard

How an engagement runs

Most engagements follow this order. You can stop after any phase.

  1. 1

    First conversation

    A short qualifying conversation at no cost. We check whether Diagnose makes sense or whether another route fits better.

  2. 2

    Diagnose

    Kickoff with a written scope, evidence gathering, analysis, then a read-out to the decision maker.

  3. 3

    Deliver proposal

    Scope, milestones, acceptance criteria, and the Operate framework in one document.

  4. 4

    Deliver

    Build or fix per milestone, UAT, go-live, then handover with a runbook.

  5. 5

    Operate

    The retainer starts at go-live: health checks, patching, risk reviews, and monthly reports.

Principles we hold to

  • Paid discovery comes first. We do not commit to large projects on the back of a vague sales meeting.
  • Operate is designed into the proposal, because go-live is not the end of our responsibility.
  • Success means the system stays in use and stays looked after.
  • We do not lead with products that are not ready to sell.
  • We build depth in one class of problem before expanding.

Questions about how we work

Do we have to start with Diagnose?

Usually, unless the scope is already clear and documented. For pure Run or Operate needs, we can move straight to Operate after an initial system check.

Can we use the Diagnose results with another vendor?

Yes. The findings, options, and proposed scope belong to you.

How is pricing set?

Diagnose is a fixed fee per package. Deliver is priced per milestone. Operate is a monthly retainer. We quote after the first conversation because the numbers depend on scope.

Start with a first conversation

Tell us about the system that cannot stop. We will help you decide whether Diagnose is the right next step.