Technical audit

Before touching anything you need to know what is there. An audit is not a report for the drawer: it is the conversation that decides where the budget goes and where it does not, with the facts on the table instead of the instincts of whoever argues loudest.

Free review

When you need this

You inherited a system and nobody on the current team built it.
You have been given wildly different quotes for the same thing and cannot tell which to believe.
You are being told it all has to be rebuilt and you want a second opinion.
You are buying a company or a product and need to know what you are buying.

What it includes

A map of the systems already in place and of where the time leaks out.
Conversations with whoever runs the process, not only whoever manages it.
The decisions that will be expensive to reverse, put on the table.
Diagnosis and target architecture, in writing.

How we do it

This is phase 01 of the method, and it can be bought on its own. It ends with a diagnosis and a target architecture, and with that in hand you decide whether to carry on with us, with someone else, or with nobody.

Five phases, each with its own acceptance criteria

Questions about this service

Can we buy just the audit?

Yes. It ends with the diagnosis in writing and commits you to nothing. Some people use it to set next year’s budget.

Does it work if another vendor built the system?

That is the most common case. We review what is there, not who made it, and the report says what holds up and what does not in terms you can check.

Usually comes with

Integration and data