Required inputs
- Decision context and primary alternatives
- Available architecture, operating and economic information
- Interviews with accountable leaders and technical stakeholders
Fixed-scope engagement
Technology Decision Review
A 10-business-day independent review of an architecture, platform, vendor, cloud, AI or build-versus-buy decision before approval or contract signature.
- Duration
- 10 business days
- Starting price
- From €9,500 excl. VAT
- Basis
- Fixed written scope
Outcome
What you are left holding
A written recommendation with evaluated options, cost and operating assumptions, technical limits, decision conditions and a 90-day action plan.
A decision review compares the real options against the same constraints and keeps rejected alternatives in the record.
Decision questions
Questions answered in the engagement
- 01
What decision must leadership approve, and what is outside its scope?
- 02
What does each option require from architecture, operations, security and people?
- 03
Which claims are supported by evidence, and which remain assumptions?
- 04
What conditions and controls are required before proceeding?
Deliverables
Documents and decisions provided
- 01
Decision scope, assumptions and evaluation criteria
- 02
Options, trade-offs, risks and cost assumptions
- 03
Recommended option and rejected alternatives
- 04
Decision conditions and 90-day action plan
Scope boundaries
Required inputs and exclusions
Not included
- Running a procurement tender on the client's behalf
- Detailed implementation design or production coding
- A guarantee that every stakeholder will support the recommendation
Completion criteria
How you know it is finished
Leadership has an approved decision record; engineering teams have the constraints, owners and next actions required to proceed.
Fit
Use this engagement when
The choice is expensive or difficult to reverse.
Internal stakeholders recommend different options.
A vendor proposal is progressing without agreed evaluation criteria.
Leadership requires a documented technical recommendation.
Process
Four steps from scope to handover
Confirm scope
Agree the decision, stakeholders, inputs, exclusions and deadline.
Collect evidence
Review documents, interview accountable people and test relevant technical claims.
Analyse
Compare options, findings, dependencies, cost assumptions and implementation constraints.
Handover
Present the recommendation, actions, owners, open decisions and acceptance criteria.
Contact
Discuss this engagement
Send the decision, affected system, known constraints and deadline. Keep confidential reports out of a first message — a secure route is agreed first.
Send the context↗