Problem
Everything is priority one.
We cannot say what we will not do.
The roadmap is a wish list, not a plan.
Outcomes
- An agreed order of work
- Spend tied to outcomes
- A plan the board can approve
Scope
In scope
- Current-state review
- Prioritisation workshops
- Roadmap and cost model
Not included
- Detailed solution design, which sits under enterprise and solution architecture
- Build and delivery
Technology Due Diligence
When an organisation is about to acquire a company, invest in one, or appoint a major supplier, it needs an honest view of the technology behind the decision. We assess the architecture, code quality, security posture, team capability, licensing and technical debt, then report the risks in plain terms with an estimate of what it would cost to address them.
- Typical triggers: an acquisition, an investment round, a large outsourcing contract or a platform purchase.
- Typical output: a due-diligence report with a red, amber and green risk summary and remediation costs.
Approach
Discovery
We agree the decision you are making, the constraints and how success will be judged.
Delivery planning
We shape options, sequence the work and set out costs and risks.
Build and test
We produce the artefacts and pressure-test them with the people who will own them.
Operational readiness, hypercare and closure
We hand over, support the first weeks of use, and confirm the outcome before we close.
Deliverables
Technologies
Controls
Frequently Asked Questions
Is this just a document?
No. It is a decision you can act on, with an agreed order of work and the costs to go with it.
Can you help us deliver it afterwards?
Yes, through project delivery, embedded specialists or managed services.
Ready to scope this?
Tell us what you are weighing up and we will help you put it in order.