Studio:Blueprint
Get started
How it works

Diagnose. Run. Prove.

Every engagement follows the same path. The system connects each stage so nothing falls between the gaps.
The operating loop

Five stages. One connected path.

01
Diagnose

Score the client against your methodology.

What happens in the system

The Forge builds your diagnostic from defined dimensions and criteria. The client completes it. Scores are produced deterministically: the same inputs always produce the same output.

02
Scope

Turn the diagnosis into a proposal.

What happens in the system

The Proposal Builder maps diagnostic scores to deliverables, pricing, and timeline. An engagement is created with quoted value, hours, and clear scope.

03
Deliver

Run the work. Track everything that matters.

What happens in the system

Programme actions are generated from diagnostic gaps. Time is logged against the engagement. Deliverables are tracked. Scope changes are recorded with fee impact. Health index is computed continuously.

04
Evidence

Prove that the work changed something.

What happens in the system

The Evidence Canvas links uploaded client artefacts to methodology questions. Each finding can support, contradict, or leave a criterion insufficient. This is not a file store. It is a structured proof layer.

05
Prove

Reassess. Show the score movement.

What happens in the system

The client retakes the diagnostic. The score delta is calculated automatically. Evidence is reviewed alongside the new scores. Progress is visible to both consultant and client through the Client Portal.

These stages are not five separate tools. They share one data model. The diagnostic feeds the programme. The programme drives delivery. Evidence proves the change. Reassessment closes the loop.

Start with a diagnostic. The system takes it from there.

Pick the assessment that matches the operating question in front of you.