A conversation. A defined review. A practical plan.

An introductory conversation

Tell us what you are working on, the stage you have reached and any deadline. We discuss the question, the people involved and whether our experience fits the work.

You do not need a finished brief. A short description is enough to begin.

A written scope before work starts

We set out the system or use case under review, the evidence and access needed, the activities, deliverables, fee and timing. You know what is included and what sits outside the scope.

For a focused review, we agree a fixed fee once the scope is clear. If a larger project needs a feasibility stage first, we make that a separate decision.

The review

We examine the agreed documents, systems or model behaviour with the relevant people in your team. Depending on the question, that can include governance records, supplier evidence, representative tests or deployment constraints.

We discuss material findings as they emerge. Missing evidence and untested assumptions stay visible in the assessment.

Findings you can act on

The handover connects each finding to the decision it affects:

• A written assessment of the agreed question and supporting evidence.
• Prioritised actions, with suggested owners, dependencies and the evidence needed to close them.
• A discussion of the findings and the next decision.

For a technical evaluation, this can include test results, configuration details and acceptance criteria. For governance work, it can include a gap list, responsibilities and a plan for putting controls into use.

We agree how your team will use and maintain the deliverables. Any follow-on implementation or review cycle is scoped separately.

Choose a starting point

Explore our engagements for governance reviews, model evaluation and embedded AI feasibility. We can also scope a defined implementation project or continuing support.