Strategic IT Consulting

Technology decisions aligned to business goals

Some of the most expensive technology decisions get made quickly, in a meeting, on incomplete information. Build or buy, which platform to standardize on, whether the system creaking under load needs rewriting or just fixing. They are hard to reverse, and a wrong one is paid for slowly over several years.

What this covers

What this covers

Four things every engagement of this kind produces. What they amount to depends on where you are starting from.

  1. The decision, written down

    The decision, written down

    What is actually being chosen, what it rules out, and how hard it would be to reverse. A surprising amount of disagreement dissolves once the question is stated precisely.

  2. Options costed against each other

    Options costed against each other

    Build, buy and leave alone, each with the work it implies, the skills it needs, and what it would cost to change course later.

  3. Estimates from the people who would build it

    Estimates from the people who would build it

    Numbers from the team that would do the work rather than from a proposal. Advice from people who never have to live with the result is worth less.

  4. A recommendation, including doing nothing

    A recommendation, including doing nothing

    Not every system that feels slow needs rewriting, and not every workload belongs in the cloud. We are happy to say when the sensible answer is to leave something alone.

Build, buy, or leave it alone

Three routes to the same outcome, costed against each other. None of them is the recommended one until the numbers are in.

Build

Fits the process you actually have, because it is written around it.

Carries

A team that has to keep existing after launch.

Changing your mind

Reversible, at the cost of everything already written.

Buy

Solves the common problem quickly, and someone else operates it.

Carries

Your process bends to the product's assumptions.

Changing your mind

Reversible until your data lives inside it.

Leave it alone

Costs nothing and breaks nothing. Often the honest answer.

Carries

The original complaint, still there.

Changing your mind

Entirely reversible. The option that keeps every other one open.

Which one is right is a question about your numbers, not about the three columns. We cost all of them before recommending any of them.

How the work runs

The same four stages whichever service the work sits under, Strategic IT Consulting included.

  1. Find out where you actually are

    A short review first: what you are running now, what it costs, and where the work is genuinely blocked. It is a look at the estate, not a pitch.

  2. Come back with options, not one answer

    The realistic paths and what each would cost you, including the skills your team already has and how hard the choice would be to reverse later. Sometimes the recommendation is to leave it alone.

  3. Build it in increments

    One workflow, built and put in front of real users, before anyone commits to a larger scope. It is the fastest way to find out whether we understood the problem correctly.

  4. Leave it running without us

    Readable pipelines, alerting that speaks up instead of failing quietly, and documentation your own team can follow. A good handover is the point of the engagement, not an afterthought at the end of it.