What is IT strategy consulting?

IT strategy consulting is the work of setting out, in writing, how a business will use technology to reach its commercial goals over the next two to three years, then sequencing and costing the changes needed to get there. A good engagement produces a roadmap: a ranked list of investments and decisions, each with a rough cost, an owner, a dependency map and a clear line back to a business objective such as growth, margin, resilience or readiness for sale. It is not a procurement exercise and it is not a list of products. It is the decision layer that sits above your projects and tells you which ones earn their place.

The difference between a strategy and a wishlist is prioritisation under constraint. Every business can name twenty things it would like to fix. Strategy consulting forces the harder question: given a fixed budget and a finite year, which five move the needle, in what order, and what happens to the rest.

When does a mid-market business need it?

Most mid-market firms do not need a strategy because technology is broken. They need one because the business has changed faster than the technology decisions behind it. The common triggers are concrete. You are growing by acquisition and inheriting systems that do not talk to each other. A new investor or board wants a credible plan, not anecdotes. A near miss or an audit finding has exposed how thin your security really is. Your IT spend keeps rising while the same complaints recur. Or a key person holds the whole picture in their head and you have no documented direction if they leave.

The other reliable signal is decision paralysis. When every technology choice escalates to the managing director because nobody can say whether it fits the plan, there is no plan. That is the point at which a few weeks of structured strategy work pays for itself, because it replaces a hundred small arguments with one agreed direction. If your concern is specifically the security half of that picture, our cyber security consulting and board cyber governance pages cover how that strand fits in.

What the engagement actually delivers

A serious IT strategy engagement follows a clear arc. It starts with discovery: interviews with leaders, a look at the application and infrastructure estate, current spend, the risk picture and the contracts and renewals that constrain your options. It then sets the destination, the target IT operating model and capabilities the business needs to support its plan. From there it identifies the gap between today and that destination, and turns the gap into a sequenced, costed roadmap.

The deliverable you keep is short and usable, not a hundred-page binder nobody reads. Expect the following.

• A current-state assessment covering systems, spend, security posture and key risks.
• A target operating model: the capabilities, structure and sourcing the business needs.
• A prioritised roadmap with indicative costs, sequencing and dependencies across the next two to three years.
• A view of where to build internal capability and where to use a fractional or managed model.
• A one-page summary the board can act on, with the trade-offs made explicit.

The test of the roadmap is simple: a finance director should be able to read it and understand what each line costs and why, and an operations lead should be able to see what changes for their team and when.

Independent practitioner versus a big firm

The large consultancies do strategy well at scale, and for a multi-billion-pound transformation they are the right call. For a mid-market business the economics rarely work. You pay for a brand, a pyramid of junior staff and a methodology overhead, and the partner who sold the work is seldom the person in the room afterwards. You often end up with a polished deck and a delivery bill to match.

An independent practitioner who has actually run technology in businesses your size offers a different trade. You get a single senior person doing the thinking and the writing, who has owned a budget and a board relationship rather than only advised on them. The roadmap is grounded in what is achievable with the team and money you have, not what looks impressive on a slide. The cost is a fraction of a firm’s, and the same person can stay on to help execute through a fractional CIO and CISO or interim CIO and CISO arrangement, so the strategy does not die in a drawer. The honest weakness of the independent model is bandwidth: one person cannot mobilise fifty consultants overnight. For the mid-market, that is rarely what is needed.

What it costs and how it is priced

IT strategy work is usually scoped as a fixed-price engagement over a defined number of weeks rather than billed by the hour, so you know the cost before you start. Price scales with the size of the estate, the number of sites and entities, and whether security and compliance need a deep look. A focused roadmap for a single mid-market business is a modest, defined cost; a multi-entity group after several acquisitions is more involved. The relevant comparison is not the fee, it is the cost of the wrong investments the strategy prevents and the duplicated spend it removes. Our pricing page sets out how Starkhorn structures engagements.

Where the strategy surfaces a specific need, it points to the right follow-on rather than padding the bill: a virtual CISO or CISO as a service for ongoing security leadership, a plan to meet NIS2 compliance obligations, an incident response plan if you have none, or an AI governance position as teams start using AI tools without oversight.

Why Starkhorn

Starkhorn is led by Daniel J. Jacobs, who has spent over 20 years in technology and security, 15 of them in leadership roles, including Interim Group Technology Director at VetPartners, the BC Partners-backed veterinary group, and CIO and CISO at Jardine Motors Group. He is the author of The Strategy Bridge and holds PRINCE2, ITIL Foundation and full membership of the Institute of Interim Management.

Setting technology direction for a private-equity-backed group and a national motor retailer means Daniel writes strategy the way a board reads it: costed, sequenced and tied to the commercial plan rather than to a product roadmap.

Frequently asked questions