Skip to content
A steel test bar held in the grips of a testing machine, stretched thin at the middle just before it breaks.

Readiness review

Find out what breaks first.

So you commit budget knowing what is wrong and what fixing it costs.

Book the review
  • You agree scope and end date before granting access
  • A fixed price, quoted after a 30-minute call
  • You commit to nothing that follows
  • The report is yours to take anywhere

Example record

What you walk away with

So each line has an owner and a price you can take to your board.

You agree scope and end date before we get access.

readiness review · deliverablesSample log

  • The assessment

    what breaks first, in order

    Written

  • The priced plan

    a price against each line

    Priced

  • The first move

    who does what, and when

    Named

  • A walkthrough

    with your team, on a call

    Booked

Where we look

Bring what you have. A repository, a running system, or a pipeline that stopped scaling.

  • Security: secrets, access, what an agent can reach

  • Scale: the query and the call that die under load

  • Tests: what exists, and what a change would break

  • Licence and IP: each dependency, and the tool terms

  • Handover: whether someone else could run it

  • Cost: what a user costs you today

Deliverables

What you get

4 written artifacts. Yours to keep.

01The assessmentFindings ordered by what bites firstEvidence behind each findingWritten so your board can read it
02The priced planWhat each fix costs, in time and moneyWhat can wait, and what cannotWhat your own team can fix
03The first moveThe first piece of work, named exactlyWho would do it, by nameWhat you will see when it is done
04A walkthroughOne session for your team’s questionsRecorded for the people who missed itNo sales pitch attached

Outcomes

3 outcomes you can act on

You get a clear call with the evidence behind it. The report names one of these.

01Ready to runYou can go to production. Nothing found stops it, and the report shows why, finding by finding.
02Ready after named fixesYou know what has to change first, in the order it bites, with a price against each fix.
03Not worth taking furtherWhen fixing it costs more than it returns, the report says so. That protects your budget, and it counts as a result.

What we will not promise you

You know the limits up front. We write them into the report.

  • A certification. We do not issue one

  • A savings figure before anything has been measured

  • A verdict on your team. Findings describe the system only

  • That we do the work afterwards. Nothing that follows is assumed

What you bring

Very little, and nothing until scope and end date are agreed.

  • Access to the agreed scope, and nothing more

  • The person who last shipped a change to it

  • Your own numbers: users, load, and today’s cost

Model

What is fixed, and what you decide

What is fixed

  1. F1The end date, agreed before anything starts
  2. F2The price, which does not move once quoted
  3. F3The evidence behind each finding
  4. F4Your ownership of the report, with no conditions

What you decide

  1. C1Whether anything follows the review
  2. C2Who does the next piece of work. Us, your team, or nobody
  3. C3Who we talk to, and what we may touch

Related

What can follow the review

Next step

30 minutes to scope it.

One call sets your scope and your price. The clock starts when you say go.

Book the review →