Three artefacts sit on the table when an engagement has genuinely closed. One is a decision log that names, for every commitment, the person who owns it and the date it gets reviewed. One is a shortlist where the scoring weights were agreed and written down before any vendor demonstrated anything. One is a standards register that pairs each system you run with the obligation it discharges and the evidence you already hold for it. A firm that hands over a slide deck and an hour of a partner's time has produced none of the three.
Reaching that table is mechanical work. You inventory systems against contracts, map each one to the obligation behind it, agree who decides and who can veto, weight the buying criteria before procurement opens, and record every change to those weights with the reason attached. Technology advisory services earn their fee in the discipline of that order, which is why the shape of the firm you buy from matters more than the seniority of the person who presents the findings.
The three models this page compares
An independent adviser, usually a fractional CTO, is retained to sit on your side of the table with no product to resell and no implementation team waiting behind the recommendation.
A delivery-owning IT advisory, of the kind FCDO Services provides, advises on IT strategy, service integration and management, and IT service management while also running service desks, projects and cost management for clients. Its service management and information security accreditations describe an organisation built to operate.
An implementation-attached adviser advises and then builds. BDO's technology advisory services sit on finance and accounting systems, and BDO is an authorised partner of Xero and iplicit, which means the advice, the selection work, the data migration and the user acceptance testing come from the firm that also earns implementation revenue. Protiviti runs technology consulting on the same pattern at larger scale, from strategy and design through implementation, risk management and managed services. Pulse Accountants shows the smaller version, where tech advisory services ride on an existing accountancy relationship and cover technology assessment, platform selection and team structure.
Ownership of the recommendation is the first difference
The independent adviser has nothing to sell after the report, so the recommendation is the product and the pressure runs towards the smallest system that solves the problem. The delivery-owning advisory carries its recommendation into a service desk it may then run, which produces careful thinking about operability and supportable design while pulling scope towards the work it already delivers. The implementation-attached adviser recommends platforms it is accredited to implement, and partner status is a reasonable predictor of where the recommendation lands unless the shortlist was weighted before the first conversation.
You can test this before signing anything. Ask each firm to name the recommendation it would lose money on. An independent adviser will name several. A delivery-owning advisory will name the services it does not run. An implementation-attached adviser will name the platforms it does not partner, and that answer tells you the boundary of the advice you are buying.
What technology advisory services leave behind as evidence
The independent adviser's exit artefacts are documents you keep, namely the decision log, the weighted shortlist, the standards register and a named owner for each open commitment. The delivery-owning advisory leaves operating machinery, service levels, escalation paths, a service integration regime that binds several suppliers into one front door, and a working view of how mature your IT service management actually is. The implementation-attached adviser leaves a configured system, migrated data, test evidence and a support contract, which is a solid legacy when the problem really was a system.
The standards register is the artefact most often missing and the easiest to specify. The AI and Digital Regulations Service's guidance on technical standards sets out that following standards is best practice, that designated standards allow a presumption of conformity, and that every standard carries a version and a region, gets reviewed every few years, and must be checked for currency before you rely on it. A register without a version column and a region column is a wish list. The same machinery appears in regulated markets, where Ofcom's statement on Technology Notices describes technology accredited against minimum standards of accuracy set by government after the regulator's advice.
Where the three models draw the edge of scope
Protiviti's own explanation of the field separates IT consulting, which manages infrastructure such as servers, networks and databases, from technology consulting, which reaches emerging technology and enterprise change. That distinction decides which firm you need. FCDO Services draws its line at strategy, service integration and service management, and will not pretend that an emerging technology question is a service desk question. BDO draws its line at the finance function, which is the right boundary when reporting, controls and data interpretation are the constraint. An independent adviser is the only one of the three whose scope is set by the question.
Boundaries matter because the edge of a firm's scope is where your project stalls. The handover between an advisory report and an implementation team is the usual failure point, and the model that owns both ends of that handover will always have a smoother story to tell about it.
How the buying decision is weighted before procurement
The technology code of practice published by GOV.UK exists to help public bodies design, build and buy technology, and its collated guidance covers buying, spend controls, marketplace routes and open standards. Read it as a checklist for the private sector too, since it encodes the order of operations that most failed procurements skip. Criteria and weights are agreed and recorded first. Longlists are built against those weights. Demonstrations happen afterwards and cannot move the weights without a written reason.
Firms differ on who writes those weights. An independent adviser can write them with you and has no reason to shade them. A delivery-owning advisory may end up bidding for the work the weights describe. An implementation-attached adviser knows its partner economics well enough to write weights that favour them, and will do so honestly unless someone else holds the pen.
What happens in the ninety days after the report
Technology Advisory Group's audit and assessment work describes a deliverable set that includes a multi-quarter roadmap reviewed with executive leadership, executive summary reporting, and periodic review under a dedicated virtual CIO. That is the operator's answer to the post-report void, and it works when you want one throat to hold. An independent adviser's answer is different and should be tested at procurement, since the real exit criterion is whether your team can run the next selection without them. An implementation-attached adviser's answer is a support contract, which is continuity of a system.
Where the fee sits, and what flexes
Independent advisory fees sit in a retainer or a fixed-price assessment, and the scope flexes by renegotiating the retainer. Delivery-owning advisory fees split between advice and the services that follow, so the advisory line can look cheap against a larger service line. Implementation-attached fees tend to split between advisory days and implementation margin, and the second number is where the firm's interest lives. None of these shapes is dishonest, but they are not interchangeable, and comparing them on headline day rates is how organisations end up buying a system they did not choose.
The attributes that decide between them
| Attribute | Independent adviser | Delivery-owning IT advisory | Implementation-attached adviser |
|---|---|---|---|
| Artefacts at exit | Decision log, weighted shortlist, standards register, named owners | Service levels, escalation paths, supplier integration regime | Configured system, migrated data, test evidence |
| Who can bid on the build | Anyone, including your own team | The adviser itself | The adviser, on its partner platforms |
| Where the fee sits | Retainer or fixed assessment | Advice plus delivery and service desk | Advice plus implementation and managed support |
| Behaviour under pressure | Recommends the smallest system that works | Scope drifts towards what it operates | Shortlist drifts towards partner economics |
| Best fit | You need judgement and you can execute | You need judgement and someone to run it | The problem is genuinely a system |
When each model is the wrong purchase
The independent adviser is wrong when you have no delivery capacity at all, because a good decision log does not answer a service desk call on Monday morning. The delivery-owning advisory is wrong when the question sits outside the services it runs, since the answer will be shaped to fit the estate. The implementation-attached adviser is wrong when the constraint is governance, and it is wrong whenever the shortlist would be settled by partner economics with your name on the signature.
Buying technology advisory services well comes down to specifying the artefacts before you discuss the fee. Name the decision log, the weighted shortlist and the standards register as deliverables. Name the review date for each commitment. Name the exit test, which is your team running the next procurement without the adviser in the room. The firms that agree to all three are the ones whose advice you can actually use.


