White Papers
Research and reference you can act on.
Frameworks, reference architectures, and benchmark data drawn from engagements — with the method documented so you can disagree with it.
Library
Papers and reference architectures
Request any of these and we will send the full document. No drip campaign attached.
Legacy modernisation: a decision framework
A structured method for deciding whether to retain, refactor, replace, or retire a core system, with the cost model we use on engagements.
Available on request
The state of enterprise AI adoption
Findings from 140 enterprise deployments: where value was realised, where programmes stalled, and what separated the two groups.
Available on request
Cloud landing zone reference architecture
Our opinionated multi-account foundation for AWS and Azure, including identity boundaries, network segmentation, and guardrail policy sets.
Available on request
Zero Trust implementation sequencing
A phased rollout order that keeps an organisation operational, with the friction cost of each control measured rather than assumed.
Available on request
ERP programme benchmark report
Duration, cost, and failure-mode analysis across 40 implementations, including the three predictors most correlated with overrun.
Available on request
Data platform patterns for regulated sectors
Modelling, lineage, and access-control patterns that satisfy financial and healthcare audit requirements without crippling analyst velocity.
Available on request
Questions
No gates, and where the numbers come from
The short version: download anything without giving us your details.
Access and method
Do I have to give you my email to read these?
No. Everything here downloads directly with no form, no gate and no follow-up sequence. If a paper is useful you can decide whether to talk to us; harvesting contact details from people doing research is a poor way to start a relationship.
Where does the data in these come from?
Our own engagements, anonymised and aggregated, with the sample size and method stated in each paper. Where we cite external research we link the primary source rather than a summary of it. Where a claim rests on a small sample we say so rather than rounding it into a headline.
Can we cite these in an internal business case?
Please do, with attribution. If you need something clarified for an internal audience — a method note, a breakdown by sector, a caveat spelled out — ask and we will usually write it. That is more useful to us than a download count.
Need the underlying data?
For the benchmark reports we can usually share the anonymised dataset and method under a short agreement.