Technical consulting, code review and strategic advice for digital projects – from choosing an architecture to auditing existing code. Sometimes the most useful thing we can deliver is an opinion on whether the thing is worth building at all.

What people come to us with

The decision whether to rebuild an existing system or keep maintaining it. A project that drags on where nobody can say how much is finished. The choice of a vendor or technology where an independent view is missing. And security or performance problems that only surface in production.

What you get

  • An audit of the existing solution – code, architecture, dependencies and risks.
  • Code review with a list of concrete findings rather than general advice.
  • An architecture proposal including effort estimates for each part.
  • An assessment of performance and running costs at the expected load.
  • A second opinion on a quote or specification from another vendor.

How it runs

We go through the available documents, code and access, add interviews with the people who run the system, and deliver a written document with a prioritised list of findings. Each item states its impact and an estimate of the fix, so decisions can follow value rather than how loudly a problem complains.

Consulting is a standalone service – it is not conditional on us doing the implementation afterwards.

Frequently asked questions

Do you need code access to advise us?

It helps, but it is not a requirement. Many questions can be assessed from documentation, from how the system behaves externally and from conversations with the team. For a deeper audit, repository and test-environment access makes the result considerably more precise.

Can we use consulting when choosing another vendor?

Yes, we do that regularly. We review the quote, the specification and the proposed technical solution, and flag the places that tend to get expensive later. There is no requirement for us to do the implementation afterwards.