Because it is engineering work, not a pre-sales meeting. Days on site, a real code audit and a set of deliverable documents are what you are paying for — not a quote.

Do we keep the documents if we do not continue?

You may use them freely for your own internal evaluation. Having a third-party supplier implement them is subject to a usage fee defined in the contract.

Is the fee credited against the project?

Where the work proceeds to implementation we credit all or part of the fee against the project price, with the proportion and the window written into the contract. For a client who does not continue, the study still stands on its own and the documents are yours.

Will you speak to our current development team?

Yes, and it matters. We are not looking for someone to blame — we are looking for the structural gap that is blocking output.

Service

Technical Assessment

Turning scope, boundaries and budget from guesswork into measurement.

The purpose of this work is not to write software. It is to make the project’s real scope, technical limits and budget knowable. Any fixed price given before that is either too high or gets overrun, and both outcomes work against the client. Scope and duration follow the size of the job: a small code audit takes days, the analysis of a multi-unit programme takes weeks. You are left with documents that hold value whether or not you continue with us.

What it covers04

Code and architecture audit

The state of the existing codebase, which parts of the data model are usable, and whether it is worth saving.

Process map

Current flows unit by unit, the work running in spreadsheets, and where things break down.

Cost comparison

Multi-year total cost of ownership for the current setup against the proposed one.

Phased roadmap

Phase definitions, dependencies, effort estimates, a risk register and a fixed-price proposal.

Process04

Groundwork

Kick-off, access, review of the existing codebase and integrations.

Field

Interviews with each unit, observing processes in place, collecting the files and forms in use.

Analysis

Technical audit, integration feasibility, data ownership boundaries and the target data model.

Synthesis

Findings presented to management, with a fixed-price implementation proposal.

Systems we have assessed04

In sectors01

Public Sector and Institutions

FAQ04

Why is it paid?: Because it is engineering work, not a pre-sales meeting. Days on site, a real code audit and a set of deliverable documents are what you are paying for — not a quote.
Do we keep the documents if we do not continue?: You may use them freely for your own internal evaluation. Having a third-party supplier implement them is subject to a usage fee defined in the contract.
Is the fee credited against the project?: Where the work proceeds to implementation we credit all or part of the fee against the project price, with the proportion and the window written into the contract. For a client who does not continue, the study still stands on its own and the documents are yours.
Will you speak to our current development team?: Yes, and it matters. We are not looking for someone to blame — we are looking for the structural gap that is blocking output.

Has your software been almost-ready for months?

The cause is usually not the team but undefined scope and absent technical ownership. Let us measure it first.

Contact How we work