Technology strategy, from a firm with nothing to sell
IT Strategy Consultancy No product. No commission. No agenda.
An IT strategy is a decision about where money goes, in what order, and what the business gets back. Intology writes those strategies for UK organisations: current state, target state, a costed and sequenced roadmap, and an investment case a board can actually approve.
Most technology strategies are written by someone who sells technology. That does not make them dishonest, but it does make them predictable, and it is why so many of them recommend a platform rather than a sequence. Intology holds no reseller agreements, no vendor partnerships and no implementation revenue. There is no version of your strategy that pays us more than another.
What an IT strategy is, and what it is not
An IT strategy sets out how technology will support what the business is trying to do over the next three to five years, and what has to change to get there. It covers applications, data, infrastructure, security, the operating model that runs it all, and the money and sequence required.
It is not a technology roadmap on its own. A roadmap without a business case is a wish list, and a roadmap without a sequence is a wish list with dates on it.
It is not a vendor selection. Choosing a platform is a separate exercise that comes after the strategy has established what the platform is for. Doing them in the wrong order is how organisations end up fitting the strategy to the product they already bought.
And it is not a document. The test of an IT strategy is whether the executive team can use it to say no to something in six months' time. If it cannot do that, it has not made any decisions.
What goes into an IT strategy
The components vary in emphasis with sector and maturity, but a complete strategy addresses all of these:
- Business context: the strategy, the operating pressures and the outcomes technology is being asked to support
- Current state: applications, data, infrastructure, security posture, contracts, cost and technical debt, assessed rather than assumed
- Target architecture: the application and data landscape the business needs, at a level a board can understand
- Operating model: how technology is organised, resourced, governed and funded, including the in-house and outsourced split
- Sourcing and vendor position: what is bought, from whom, on what terms, and where the commercial exposure sits
- Security, resilience and regulatory obligations, treated as design inputs rather than a later review
- A costed, sequenced roadmap with dependencies, so the order is defensible and not just a list
- The investment case: cost, benefit, risk and the measures that will show whether it worked
We publish an overview of these components in our guide to the essential components of an IT strategy.
When an IT strategy is the right spend
The trigger is usually one of these:
- A new CEO, CFO or investor is asking what the technology estate costs and what it is delivering
- A major contract or platform is approaching end of life and the renewal decision has been deferred twice
- An acquisition has left the group running duplicate systems with no agreed target state
- Technology spend has grown faster than revenue and nobody can explain which parts create value
- A private equity sponsor needs a costed technology plan to underpin the value creation thesis
- The organisation is being asked to adopt AI and has no view on where it fits or what has to be true first
If none of those apply and the estate is stable, you may not need a strategy at all. We will say so, and it will have cost you one conversation.
How Intology builds an IT strategy
A strategy for a mid-market organisation takes six to ten weeks. Larger or multi-entity groups sit at the longer end. We work from evidence rather than workshops alone, and the executive team is in it throughout rather than presented with the conclusions.
Stage 1
Business context and objectives
We start with what the business is trying to achieve, the pressures it is under and the outcomes the board is accountable for. A technology strategy written without this is a procurement plan.
Stage 2
Current state assessment
Applications, data, infrastructure, security, contracts, cost and technical debt, assessed from the evidence: the contract register, the cost base, the incident record and the people running it. This stage routinely surprises the executive.
Stage 3
Target state and options
The application and data landscape the business needs, and the credible routes to it. We present options with their trade-offs rather than a single recommendation dressed as inevitability.
Stage 4
Roadmap, sequencing and cost
The work is sequenced by dependency, capacity and value, and costed over the full term including run cost, internal effort and the change the business will have to absorb.
Stage 5
Investment case and board approval
A board-ready case with cost, benefit, risk and the measures that will prove it worked. We present it to the board where that helps, and we answer the difficult questions ourselves.
Independence, and why it changes the answer
Intology holds no reseller agreements, no vendor partnerships and no implementation revenue, and does not bid to deliver the programmes it recommends. That is a structural position rather than a policy applied case by case.
In practice it changes three things. The target state is built from your requirements rather than a partner's product set. The roadmap can conclude that the right first move is to fix process, renegotiate a contract or retire something, none of which generate work for anyone. And the cost model includes the internal effort and change capacity the business will actually need, which is the number most vendor-authored cases leave out.
It also means we will tell you when the honest answer is that you do not need a strategy engagement. That has happened, and it is the clearest evidence the position is real.
Strategy, transformation, or a specific decision
Three different engagements, and the wrong one wastes a quarter.
You need a strategy
There is no agreed target state, spend is not explained, or a board or investor is asking questions nobody can answer with evidence. That is this page.
You need transformation delivery
The strategy exists and is agreed, and the work now has to be sequenced, mobilised and delivered. That is IT transformation and technology strategy execution, and it is where most of our engagements end up.
You need one decision made well
The estate is broadly fine and the question is narrower: which ERP, which finance system, which supplier. That is a selection exercise, not a strategy.
Where the strategy is agreed and delivery is the problem, see IT transformation and technology strategy. Where the question is a platform choice, see independent ERP selection or finance system selection. Where it is a service or partner, that is an RFP or RFI process. Where the estate is moving to cloud, see cloud transformation.
What you receive
A strategy the board can fund, not a deck.
- A documented current state covering applications, data, infrastructure, security, contracts and cost
- A technical debt position with the risk and cost of leaving it
- A target architecture at a level the board can understand and the technical team can build from
- An IT operating model with the in-house and outsourced split, resourcing and governance
- A sourcing and contract position, including where commercial exposure sits
- A costed roadmap sequenced by dependency, capacity and value
- A full-term cost model including run cost, internal effort and change capacity
- A board-ready investment case with benefits, risks and success measures
- A one-page summary the executive team can actually use to make decisions
Who we work with
Intology works with FTSE-listed companies, PE-backed businesses, mid-market organisations and UK public sector bodies, typically £25m to £2bn revenue or equivalent public sector budget. Over fifteen years we have delivered more than one hundred programmes for over fifty clients.
Engagements are staffed with senior practitioners only. The person writing your technology strategy has held the accountability for delivering one, which is a different discipline from advising on it.
Frequently asked questions
The questions UK boards and CFOs most often ask before commissioning an IT strategy.
What is an IT strategy?+
What are the components of an IT strategy?+
How long does an IT strategy take?+
How is this different from a strategy written by a technology supplier?+
Do you recommend specific products?+
Who needs to be involved from our side?+
Do you deliver the strategy afterwards?+
Does an IT strategy have to include AI?+
How is an IT strategy engagement priced?+
Can your board explain what technology is delivering?
Tell us what is driving the question: an investor, a renewal, an acquisition, or a cost line nobody can account for. We will tell you honestly whether you need a strategy, a narrower decision made well, or nothing from us at all. The initial conversation is free and carries no obligation.