How the work runs

How the work runs, from first call to handoff

The work runs in six phases: agree what the business needs fixed, prove what your environment is actually doing, design a target that survives real users, sequence the rollout so nothing breaks, roll it out in stages, and hand back the evidence. Every phase has a named output you keep. Internally the sequence is called ADAPTO.

Talk through the problem →

Phase 1

The technical work is tied to your business risk.

It starts with why this is on your desk now: a failed audit, an insurer question, a client security review, a migration that stalled, or a system nobody can safely touch. Then what finishing looks like is agreed.

This prevents security work from turning into a generic settings checklist.

What you receive

Outcome map
Stakeholder alignment notes
Scope boundaries and prerequisites

Read-only diagnosis

Nothing is touched before it is inspected. Nothing in your tenant changes until you have approved a named plan.

One fixed fee

The scope, the fee and the definition of done are agreed in writing before any access is granted. No hourly clock.

The documents are yours

You keep the written record. Hand it to your own team, your auditor, or another vendor, whatever you decide next.

Start with the right diagnostic

Describe the situation as it actually is, including what has already been tried. The reply names which diagnostic fits and what it costs before you commit to anything.

Talk through the problem

What happens next

  1. 1Describe the situationA few short fields: company size, environment, and what is going wrong.
  2. 2A reply within one business dayA first read of what you sent, and if it is a fit, a private scheduling link.
  3. 3A fixed-fee proposalNamed scope, price and definition of done. No obligation.
Talk through the problem Browse the diagnostics