Exhibit 01Case
Enterprise ERP — public university system
An $88M implementation steered back from the brink.
$88Mprogram under direct stewardship
Higher education · multi-campus
Expert Witness
Retained when an implementation failure becomes a matter.
For general counsel, litigators, and audit committees: independent analysis of ERP and enterprise-implementation failure — standard of care, causation, and the technical record — that holds up under cross-examination.
The engagement
What the firm is retained for.
Failure analysis
Forensic examination of why an ERP or enterprise implementation failed — the program record read for the decisions, omissions, and warnings that drove the outcome.
Standard of care
Opinion on whether the conduct of an implementer, advisor, or institution met the standard a reasonable practitioner would apply.
Causation
Disentangling the chain from decision to damage — what caused the failure, what merely coincided with it, and what would have changed the result.
Damages context
Framing the technical and program realities that bound a damages theory, so the financial analysis rests on what the program actually was.
Credentials that survive cross
The basis of the opinion.
- Domain depth in ERP and enterprise transformation, from selection through post-go-live remediation
- Forensic-audit muscle — the same discipline applied in the firm's accreditation and implementation audits
- A standing ERP-failure research program, peer-facing and citable
- A published book-length argument on transformation and ERP failure
The firm is available for retention, credentialed by domain expertise and forensic audit work, with a testimony record that is growing. Engagements begin with a conflicts check and a confidential review of the matter.
The credibility bridge
The audit work and the witness work are the same muscle.
Forensically examining why an implementation failed is the same discipline as testifying about why one failed. The firm's audit practice is where that judgment is built and proven — and it is what the witness work is sold on.
On the record
Exhibits a vetting reader can weigh.
Exhibit 04Publication
Book — enterprise transformation & ERP failure
The research program, in print.
Author · published work
Exhibit 05Publication
ERP-failure research program
A standing body of work on why programs fail.
Research · ongoing
How to engage
A confidential, low-friction intake.
Open a matter by email and the firm will run a conflicts check and review the posture of the case before any engagement letter.
Keep first contact to what a conflicts check needs — the parties involved — and hold privileged detail until a secure channel is established. The firm corresponds from an encrypted (Proton) account; for end-to-end encryption, write from an encrypted account as well.