Home/Company/Leadership
Company

Sixty people. The handful who will be on your account.

A firm this size can staff several engagements properly and still keep one named team on each. You meet them before you sign, and they are the same people three months in.

Headquartered in the United States · working worldwide

OW
Oliver Whitfield
Founder
LinkedIn
Runs discovery personally on the engagement — the first week is never delegated.
Signs the boundary document before any build starts, and owns it when scope is questioned.
Named on the support rota. There is no tier to escalate past.
Is in the first conversation, and still on the account a year later.
true of every engagement lead, on every account
7
Sixty people, a named team
you deal with the same team throughout
The team

The people who lead the work.

Sixty-plus engineers, consultants and analysts across delivery, data and AI. These seven lead it, and one of them is on every engagement from the first call to the runbook.

OW
Oliver Whitfield
Founder

Runs discovery on every engagement and signs the boundary document before any build starts. Spent six years inside a lending operation before building software for one, which is why the first week of a project is spent on the floor rather than in a workshop.

Ownsdiscovery and architecture
CH
Charlotte Hargrove
Managing director

Accountable for whether we can staff an engagement properly before we agree to it. Says no to more work than she says yes to, which is the reason the named-team promise on this page holds.

Ownsdelivery and capacity
HA
Henry Ashcombe
Engineering lead

Owns the lending platform that replaced a Salesforce org, and is on its support rota four months after launch. Wrote the weighted routing that most of this site describes.

Ownsplatform engineering
AP
Amelia Pemberton
Head of data and reporting

Spends most of her time on definitions rather than dashboards, because four teams counting differently is a governance problem wearing a visualisation. Built the server-side attribution running against five ad platforms.

Ownsdata, attribution and BI
EB
Edward Bramley
Head of solutions

Reads other people's systems for a living — every automation, field and integration — and writes down what nobody documented. Came from operations rather than software, which shows in the questions.

Ownsdiscovery and integration
ER
Eleanor Radcliffe
Head of AI systems

Built the SMS assistant that stands down and the guardrails that make it stop. More interested in what an agent must not attempt than in what it can.

OwnsAI systems and evaluation
GF
George Fairbourne
Head of client operations

Owns what happens after launch: the support rota, the runbooks, and whether a client could take a system in-house tomorrow if they wanted to. Treats that last one as the real test.

Ownssupport and handover
How the firm is organised

Sixty people, and still one team on your account.

Scale is what lets us staff several engagements properly at once. It is also the thing that usually ruins delivery, so here is exactly how we hold both.

01Who is actually on your engagement?A named team of four to eight, depending on scope, led by one of the people above. You meet them before anything is signed.
02Does the team change during the build?Not the core. Specialists join for a phase and leave when it ends, and they are introduced by name when they arrive.
03Who runs discovery?An engagement lead from the group above, on every project. It is the week that decides everything else, so it is never delegated.
04Who answers when something breaks?Someone from the team that built it. There is no separate support tier that has to learn your system during your outage.
05What does the rest of the firm do?Other engagements, and the shared work underneath — infrastructure, security review, QA and the internal tooling every project uses.
06What happens when someone leaves?The runbook exists for that, not for us. A system only one person understands is a risk we carry, not one we pass to you.
The network

Where we bring people in.

Sixty people covers most of what a project needs. For the rest — brand, video, specialist regulatory review — we bring in people we have worked with before, named at the point they join and never counted as our headcount.

Named before they start

You meet them and approve them. Nobody appears on your project unannounced.

Not counted as headcount

Sixty-plus is our headcount. The network does not inflate it on this page or in a proposal.

Under the same terms

Your code, your data, your ownership — the contract does not change because a specialist touched it.