SVC-02 / Technology Consultancy

Technology Consultancy

Architecture, audits and roadmaps — before you commit budget to a build.

2–5 weeks
What you run nowAuditOption AOption BOption CCosted roadmap
Three costed options, one recommendation, and the reasoning attached. Dashed = yours.

The situation this addresses

You have three quotes describing three different systems and no way to tell which one is right. The cost of choosing wrong is a year.

How we approach it

In order.

  1. 01Read the existing system: code, infrastructure, data, and the invoices.
  2. 02Interview the people who work around the system’s gaps.
  3. 03Write down the options with costs, risks, and what each one forecloses.
  4. 04Recommend one, and say plainly what would change our mind.

What this looks like in practice

You have quotes. They describe different systems at different prices, each written by a supplier with an interest in the answer. What you are missing is not another opinion — it is an assessment from someone who does not get paid more if you pick the bigger option.

We read what you already run: the code, the infrastructure bill, the data, the integrations that were meant to be temporary. Then we talk to the people who work around the gaps, because the shape of the workarounds tells you where the system is actually failing, and that rarely matches where the org chart thinks it is failing.

What you get, in writing

Options, not a recommendation dressed up as inevitability. Each one costed, each one with its risks named, and — the part usually left out — what each option forecloses. Choosing a managed platform buys you speed and costs you a category of future change. That trade should be made on purpose.

We do recommend one. We also write down what would change our mind, so you can check later whether the reasoning still holds.

The roadmap is portable

The sequenced plan you get at the end is written to be handed to any supplier, including one that is not us. If we have done this properly you should be able to put the work out to tender on the strength of it — and whether you can is a fair test of whether the advice was independent.

What you end up with

Three things you can point at when it is finished.

  • SVC-02-01

    System, data-flow and cost audit

  • SVC-02-02

    Costed options paper with a recommendation

  • SVC-02-03

    Sequenced roadmap you can hand to any vendor

We provide

  • Independent assessment of what you already run
  • Written options with costs and risks attached
  • A roadmap that does not depend on hiring us

You provide

  • Read access to systems and infrastructure
  • Time with the team that operates them
  • Current spend figures
Engagement shape
Fixed-fee audit, or a retained architecture review.
Indicative duration
2–5 weeks. Confirmed in writing after the discovery call, not before.

What usually sits next to it

Rarely bought alone.

  • SVC-01

    Software Development

    Custom web and backend systems built to your operations, not to a template.

    Read the service detail

  • SVC-03

    Hardware Implementation

    Specification, procurement, install and commissioning of the physical layer.

    Read the service detail

  • SVC-04

    AI Solutions

    Models, RAG pipelines and decision systems wired into real business data.

    Read the service detail

Next step

Bring us the process, not the specification.

A discovery call is 45 minutes. You get a written summary of what we heard and what we would do about it, whether or not you go further with us.