Business consulting · Technology strategy
The technology roadmap that says what to build, what to buy, and what to kill
A fixed-scope engagement that turns your systems, vendors, and backlog into a three-year plan your team can execute, with sequencing, rough costs, and an owner on every initiative.
Year 1
- Retire the manual order-entry spreadsheet$
- Stand up one customer data model$$
Year 2
- Automate invoice matching and exceptions$$
- Replace the ticketing vendor on renewal$
Year 3
- Agent-assisted case handling, phase one$$$
Named initiatives, sequenced by year, with a rough cost band on each.
What you get
Five concrete deliverables, not a strategy conversation
- 01
Digital transformation sequencing
The order to move manual operations onto systems, quarter by quarter, so the business keeps running while the work happens.
- 02
A build, buy, or vendor opinion
An experienced technical opinion on an architecture, a build vs buy call, or a vendor shortlist, written up and defensible to your board.
- 03
Process optimisation that finds the few processes worth automating
An operational review across functions that names the three processes worth automating now and the twenty worth leaving alone.
- 04
A three-year roadmap with named initiatives
Each initiative sequenced, with dependencies, a rough cost band, and an owner. Not a slide per quarter; a plan your team can run from.
- 05
A kill list
The initiatives already in flight or on the backlog that are not worth the spend, named explicitly, with the reason in one line.
What the diagnosis looks like
Every initiative gets a verdict, in writing
The diagnosis names what is worth continuing, what is worth starting, and what is worth stopping. Each verdict carries one line of reasoning, so the leadership team can defend it in the next operating review.
Ask what this looks like for your systems- Keep
Customer data migration
Blocks three other initiatives already funded.
- Kill
Second BI dashboard rebuild
Duplicates a report finance already trusts.
- Keep
Legacy approvals workflow rewrite
Costs four hours a week across two teams today.
- Kill
In-house chat widget
A vendor does this better for less than the build cost.
Every initiative on the backlog gets a verdict and a reason, not a maybe.
How we work
Four phases, each ending in a written document
- 01
Discovery
Interviews across functions, a system inventory, and a map of how work actually flows today.
- 02
Diagnosis
What is working, what is costing, and the three decisions leadership has to make next quarter.
- 03
Plan
A named roadmap with sequencing, dependencies, rough costs, and what gets killed.
- 04
Executive briefing
A one-page summary, a full document, and a working session so the plan survives the quarterly operating review.
Questions buyers ask
Before you scope a project
- Do you also build what you recommend?
- Sometimes. We are equally happy to hand the roadmap to your in-house team or to another vendor. The recommendation and the build are two separate engagements, priced and scoped separately.
- How long does a technology strategy engagement take?
- A diagnostic runs four to six weeks. A full strategy and three-year roadmap runs eight to twelve weeks. Both end with a written document and a working session, not a slide deck.
- Will you actually talk to our team, or just leadership?
- We interview across functions, not just the leadership team. That is how we learn what a system or process actually does day to day. Executive-only engagements produce roadmaps that do not survive contact with the operating business.
- What goes into the roadmap document itself?
- Named initiatives in sequence, their dependencies, a rough cost band for each, an owner, a one-page summary for the board, and a kill list of initiatives not worth pursuing. It is written to be executed, not filed.