01
Why an assessment comes first
Most transformation work fails not because teams lack skill, but because decisions are made without a shared understanding of the system and the organisation around it.
Before changing anything, it is important to understand: what actually exists today, where the real constraints are, what must not break, and what kind of change is realistically possible.
Skipping this step often leads to expensive rewrites, stalled projects, or systems that are newer but no easier to control.
The assessment is not a formality. It is the work that makes the rest possible.
02
Who this assessment is for
This assessment is designed for organisations with existing systems where change feels risky or overdue.
It is most useful when:
- There is uncertainty about how the system really works
- Previous attempts to modernise or rewrite have failed or stalled
- Key knowledge has left the organisation
- Leadership needs a clear basis for deciding what to do next
This approach is not intended for situations where speed or lowest cost is the primary goal. It is designed for teams who value understanding, control, and deliberate change.
03
What the assessment involves
The assessment focuses on outcomes, not a fixed checklist of activities. Depending on the situation, it typically results in:
- A clear description of the current system and its context
- Identification of what is missing (documentation, tests, ownership, or process)
- Explicit risks, both technical and organisational
- Boundaries of feasibility — what is easy, what is hard, what is blocked
- Clarity on what kind of change is possible, and what kind is not
The assessment does not involve:
- Reviewing every line of code
- Building documentation from scratch
- Writing tests or implementing fixes
- Starting delivery work
It is analytical and directional by design.
04
What you get out of it
The primary outcome is a written assessment document that captures the findings clearly and objectively.
This document is intended to:
- Give you a shared understanding of the current situation
- Make risks and constraints explicit
- Support internal discussion and decision-making
- Serve as a reference point for whatever happens next
If helpful, the findings can also be presented verbally or adapted for a specific audience, such as senior leadership or a board.
Even if no further work follows, the assessment should leave you in a better position than before — with more clarity and fewer unknowns.
05
How pricing works
The assessment is a standalone piece of work with independent value.
Pricing reflects:
- The expected scope of the assessment
- The level of senior attention required
- The number of people involved
- Whether on-site work, travel, or additional specialisms are needed
- The depth and form of the outputs
Pricing is agreed upfront and measured in days, not hours. We do not track or bill by the hour, and we do not produce activity logs. The price reflects the cost of clarity: focused time, experience, and judgement applied to your situation.
06
Assessment pricing
Most assessments take between two and five focused working days, depending on complexity and expectations.
Exact pricing is confirmed after a short initial discussion to ensure:
- The assessment is appropriate for your situation
- Access to systems, information, and people is available
- Expectations about scope and outputs are aligned
The assessment is priced independently of any future delivery work. Proceeding beyond the assessment is always a separate decision.
07
What happens after
At the end of the assessment, there are three valid outcomes:
- You decide to proceed with further work
- You pause to consider options internally
- You decide not to proceed
In some cases, the assessment may conclude that meaningful change is not currently feasible. That conclusion is part of the value of the work.
There is no obligation to continue beyond the assessment.
08
First conversation
The first conversation is a short, time-limited discussion to check fit and readiness.
Its purpose is to:
- Understand the nature of the situation
- Confirm that an assessment makes sense
- Check access to systems, information, and people
- Align on expectations and constraints
It is not a technical diagnosis and not a solution-design session. This conversation typically lasts 30–60 minutes and is scheduled in advance.