Current state
Architecture, system inventory, process map, data flows, ownership, costs and known constraints.
Raeburn Discovery™ deliverable standard
Raeburn Enterprise Transformation Blueprint™
A decision document, not a technology shopping list. Every recommendation should trace back to an observed constraint, measured baseline or explicitly stated assumption.
Risk & friction
Technical debt, duplication, security concerns, manual effort, data-quality issues, integration gaps and operational dependencies.
Opportunity map
Rationalisation, automation, AI, integration and process-improvement opportunities with assumptions and dependencies recorded.
Future state
Target architecture, process changes, controls, governance, human oversight and migration considerations.
Business case
Baseline, implementation assumptions, expected benefits, TCO, sensitivity ranges, payback logic and measurement plan.
Roadmap
Prioritised 90-day, one-year and three-year actions, with owners, dependencies, evidence gates and decision points.
Evidence rules
Actual, estimated and modelled values must be labelled separately. Vendor relationships must not determine recommendations. Material assumptions, exclusions and unresolved risks stay visible rather than being hidden in appendices.