testclub_

The people who do the work

Testclub was founded in 2012 to test software in places where getting it wrong is expensive: trading platforms, insurance, energy and government.

Twenty-five years of that work taught us where defects really come from. Rarely bad code. Almost always the things nobody specified. And the same gap that lets a bug through will let an attacker through.

So today we apply that discipline where the stakes are highest: the security of your APIs and the reliability of your AI systems. The work is the same. The consequences are not.

The team

Omar El Dali FOUNDING DIRECTOR

Omar El Dali

Omar's early career started in engineering where he spent the next decade noticing that the most expensive failures were never really in the code. They lived in the gap between what was asked for and what was built. He founded Testclub in 2012 to work in that gap full time, testing systems for trading platforms, fintech, insurance, health, energy and government. Twenty-five years on, the gap has moved to APIs and AI systems. So has he.

LinkedIn →

Sara Leatherland COO

Sara Leatherland

Consultancies are judged on their findings and kept on their delivery. Sara is why Testclub gets kept. An experienced business leader and operations specialist, she runs how the company works: scoping engagements so they start clearly, keeping delivery tight while they run, and ensuring what was agreed is what arrives.

LinkedIn →

Deepthi Kolla LEAD CONSULTANT

Deepthi Kolla

Deepthi has written test automation almost every working day for fifteen years. Java, Selenium, Appium, Playwright. As Lead Consultant she works across Testclub's projects, turning specifications into executable tests and leading delivery on engagements like Sportingtech and Nephila. If a finding needs proving, or a specification needs pinning down in code, it lands with her.

LinkedIn →

Values

01 · EVIDENCE

Evidence over assertion. Every claim reproducible, every finding shown with impact.

02 · INQUIRY

Specification thinking. Asking questions the team may not have asked.

03 · METHOD

Discover, specify, interrogate, report. Conclusions follow from evidence, never precede it.

This way of working has a longer argument behind it. Why specification gaps are where bugs, breaches and AI failures live, and why the skill of finding them transfers.

Read our philosophy: Specification is security →

Track record

Before security, Testclub spent years building and repairing QA practices for clients including Schroders, EDF Energy, esure, Nephila Capital, Nando's and Sportingtech, including a full QA transformation at Sportingtech. That heritage is why the security work reads unfamiliar systems quickly. We have spent twenty-five years learning how teams actually specify, build and break things.

View case studies →