Technical Due Diligence

Technical Due Diligence

After a low-code implementation derailed at £3M, JFDI conducted independent technical due diligence, reviewing the codebase and architecture and identifying critical failings.

6 December 2022

The Challenge

A prominent UK financial services company, with no software development capability of its own and a long backlog of IT requirements, adopted a new low-code platform on the advice of a Big Four consultancy. The plan was sensible on paper: build a small, simple pilot system first, then use the same platform to clear the backlog one system at a time.

Business analysts gathered requirements, developers started building, and users began working with the system while it was still being written. After nearly £3M of expenditure, the pilot was unfinished, running out of control, and generating a growing catalogue of bug reports that hinted at deeper structural problems. Relations between the client and the consultancy had reached an impasse. JFDI was called in to carry out independent technical due diligence and find out what had gone wrong.

“JFDI provided a thorough examination of everything that had been produced and a professional evaluation of each part. We were left with a clear path forward as well as the ammunition we needed to pursue a satisfactory outcome from what was otherwise an adversarial us-and-them situation at a complete impasse.” — CTO

JFDI’s Approach

We started from evidence, not opinions. Our consultants obtained a copy of the entire codebase, frozen at the point the developers left, and worked through it systematically.

  • Built a table of complexity metrics for every code module, so the riskiest modules got the closest scrutiny first
  • Read the users’ bug reports for patterns pointing to performance bottlenecks or structural faults
  • Asked for the outputs of the long business-analysis phase: requirements, system design and wireframes
  • Reviewed code, database design and security against the platform vendor’s own published best practice

Key Findings

Business Analysis & Documentation

Despite a lengthy, labour-intensive analysis phase, the consultancy could not produce any documentation: no requirements, no system design and no wireframes.

Code Quality

Several hundred thousand lines of ‘low-code’ diverged from the vendor’s best practice, lacked functional decomposition, hard-coded special cases against specific database record IDs, and carried almost no comments explaining why.

Performance

The database had no indices. Queries, stored procedures and views were plentiful but often unused, and many processes ran several whole-table scans, then looped over the results in code. Better database design and algorithms could improve performance significantly.

Security

Authentication and authorisation broadly followed the vendor’s guidance, but one algorithm adopted in the code opened the system to attacks such as code injection.

Outcomes

The review took four consultants four weeks. JFDI presented its findings to the client in September 2020. Remedial work began straight away, prioritised by the users’ bug reports and guided by our recommendations; code quality has been improving steadily since, and many of the structural issues have already been fixed.

Just as importantly, the client came away with an independent, evidence-based account of the project, which gave them a clear way forward with the consultancy.

About the Client

Company: A prominent UK financial services company

Industry: Financial services

Services used: Technical due diligence consultancy

Software: A leading low-code platform

Need independent technical due diligence?

JFDI’s TDD specialists provide detailed analysis and risk assessment for investors, M&A activities, and private equity evaluations.