For the decision a deck alone cannot actually make
IT Strategy Consulting
A strategy deck is cheap to produce and expensive to be wrong about, especially when it recommends spending real budget on the wrong system. This practice turns one business constraint into a costed, defensible technology decision, and names plainly where advice ends and engineering delivery begins.
How a business constraint becomes a costed decision
Build versus buy, sequencing and stop-doing calls, each ending in a written recommendation.
90 secSample frame · video pending01Before booking a strategy engagement
Is this a strategy problem or a delivery problem?
Some technology pain is actually a sequencing or budget-allocation problem wearing a technical costume. Four questions separate a genuine strategy gap from a decision that is already made and just needs building.
Does more than one system or team depend on this?
A decision touching a single system is usually a build question already. Estate-wide dependencies are what actually justify a strategy engagement.
Is the real constraint budget, not technical difficulty?
When the honest blocker is money or headcount, the strategy work is sequencing and trade-offs, not architecture.
Would getting this wrong be expensive to reverse?
High-reversal-cost decisions justify a costed, written recommendation. Cheap-to-reverse choices rarely need more than a quick internal conversation.
Is there political pressure protecting the status quo?
A system nobody wants to question is exactly the kind of decision an outside, evidence-based view is built for.
| Strategy engagement | Single decision review | |
|---|---|---|
| Scope | Multiple systems or initiatives | One build or architecture question |
| Typical output | A sequenced, costed roadmap | A single written recommendation |
| Best fit | Budget or capacity is the real constraint | A specific technical choice is unresolved |
| Hands off to | The delivery practice named in the plan | Engineering, once the recommendation lands |
02Agreed before the assessment starts
The ledger that keeps strategy advice honest
Strategy engagements drift when a recommendation quietly becomes unpaid ongoing oversight of its own implementation. This ledger sets what you bring, what gets assessed, what comes back, and what remains under your authority.
- Your side
You bring
- The business constraint driving the decision
- Budget range and the timeline forcing it
- Any vendor proposals or internal options already on the table
- Our side
We assess
- A costed comparison of building, buying and extending
- Total cost of ownership modelled past the first year
- A recommendation weighed against your actual team and estate
- Your side
You receive
- A written recommendation with the reasoning attached
- A costed model your finance team can interrogate
- A sequencing plan for whichever option gets chosen
Never leaves you
- The final decision and the budget behind it
- Every vendor relationship and negotiation
- Ownership of the roadmap the decision sits inside
Where the line sitsThe recommendation is the deliverable. It is costed and reasoned so a board can question it, not just approve it.
03From a constraint to a costed plan
Four stages, each closing on a written decision
Strategy work that drags usually skipped one of these stages quietly. This system closes each one with a document your leadership team can actually act on.
Name the business constraint, not the tech
Budget, timeline, capacity or political reality are established first, because the honest constraint is rarely the one named in the original request.
The real constraint named plainlyCost every realistic option
Build, buy, extend and do-nothing are each priced past the first year, including the cost of maintaining whatever gets chosen.
Options weighed against real costWrite the recommendation down
The decision and its reasoning are documented well enough to defend in front of a board months after the meeting ends.
A recommendation built to survive scrutinyRoute the decision to delivery
When the recommendation calls for building something, the handoff names the specific engineering practice, rather than leaving it vague.
A handoff named explicitly
04What actually drives the number
Four drivers, priced from a short scoping call
A strategy engagement is priced as a bounded piece of work, because these four factors change its depth far more than its shape.
Number of systems or initiatives in scope
Assessing one decision is faster than sequencing eight competing initiatives across an entire estate.
How much financial modelling is required
A build-versus-buy call with real budget attached needs deeper cost modelling than a straightforward sequencing question.
Whether a board-ready report is required
An internal recommendation costs less to produce than a document built to survive board-level scrutiny.
How politically contested the decision already is
A contested decision needs more evidence and more stakeholder conversations before a recommendation will actually hold.
05Evidence and proof
Recommendations that survived contact with a board.
Strategy proof is a recommendation still standing after the budget was actually spent. Every entry here remains provisional until the named client signs off in writing.
Explore case studiesA build-versus-buy call that avoided an eighteen-month detour.
Vela Ledger was weeks from committing to a platform rebuild driven by one vendor's pitch. A costed assessment recommended extending the existing core instead, at a fraction of the proposed budget.
- Rebuild avoided
- An estimated eighteen-month programme
- Recommendation delivered in
- Three weeks
Eight competing initiatives became a sequence leadership could defend.
Tern's technology roadmap listed eight initiatives with no agreed order and a budget for perhaps three. A sequencing engagement ranked them against business consequence and named what would wait.
- Initiatives sequenced
- Eight
- Leadership consensus reached
- Unanimous after review
We had a vendor telling us to rebuild and an engineering team saying not yet. The costed comparison finally settled it with evidence instead of opinion.
Sample · pending client approval
06Read this first
When strategy consulting is the wrong starting point
Paying for an estate-wide assessment when the real question is one build decision spends budget the honest answer did not need. Three exits route past this practice when the shape is already narrower. Strategy without delivery capacity behind it stays a deck, so every recommendation names the engineering practice it would hand off to.
- Software consulting
The question is really one build decision
A single stack choice, architecture review or vendor evaluation fits a narrower consulting engagement better than an estate-wide assessment.
- Technology consulting
The gap is standing leadership, not one decision
A company without anyone to make the next ten technical calls needs a filled leadership seat, not a single strategy document.
- Custom software development
The decision is already made and just needs building
If build-versus-buy is already settled, engineering capacity moves the work forward faster than another assessment.
| Shape | Best when | You direct | We carry |
|---|---|---|---|
| Single assessment | One decision needs a costed answer | The final call and its timing | Analysis and a written recommendation |
| Assessment into delivery | The recommendation should move straight to building | Priorities as delivery proceeds | Analysis, then the practice named in it |
| Standing advisory | Strategic decisions recur often enough to justify it | Company and technology direction | Ongoing judgement across recurring decisions |
07Straight answers
Asked before a strategy budget is committed.
01How is this different from technology consulting?
Technology consulting routes between standing fractional leadership and a single technical decision. This practice sits at the estate level, sequencing or costing decisions across more than one system.
02Do you only recommend building things?
No. A significant share of engagements end with a recommendation to buy, extend what exists, or stop something entirely. Building is one possible outcome, not the assumed one.
03Can the recommendation include stopping a project already underway?
Yes, when the evidence supports it. An honest strategy engagement is willing to recommend retiring a system or initiative, not only adding new ones.
04Who presents the recommendation to our board?
Either party can, depending on preference. The document is built to be presented by your own leadership, with support available if a joint presentation fits better.
05What happens if the recommendation is to build something?
The handoff names the specific delivery practice directly, whether that is a custom build, a modernisation, or another named engineering discipline.
06How long does a strategy engagement take?
Most single-decision assessments close within two to four weeks. Estate-wide sequencing across many initiatives typically takes longer, scoped upfront rather than open-ended.
07Is the recommendation independent of any vendor relationship?
Yes. Recommendations are made without a financial stake in any vendor, platform or staffing outcome, including our own delivery practices.