who builds it

One person wrote the cascade, the calibration and this site.

James Rooney, founder. Entity Bind is a product name; the company you contract with is named in the terms.

Every article, comparison and method page here is published under one name, and it is the name on the mail you get back. There is no switchboard and no handover to an account team — and the company you would be contracting with is on the public register under a different name from the product, which is the first thing worth checking.
the decade behind the decisions

James Rooney, Founder

Photograph of James Rooney in a navy cap, glasses and a check scarf, mouth open in mock surprise, against a brick wall

James Rooney has spent a decade landing delivery transformation inside HSBC, Microsoft, Sky, F1, Discovery and Anglo American, advising 150+ teams at HSBC against a $102M budget, which was the scope of the role rather than his authority, and co-leading the design of the target operating model prepared for global rollout to 500 teams. He codified that experience into The Tenhaw Way and now embeds as interim Agentic Lead inside organisations rebuilding around AI agents.

Alumnus of Newcastle University. His LinkedIn profile is the place to check that paragraph against. A claim about a person is worth what it can be checked against.

what he is answerable for

Four things, and the page that lets you test each one

An about page can assert anything. These are the four the rest of the site has to survive being read on.

The cascade, and where it stops

The seven stages, the order they run in, and the rule that stops at the cheapest one that can decide. The page sets out what each stage costs and what it is allowed to conclude.

How it works→

The confidence floor, and the calibration behind it

The 0.90 floor is enforced in code rather than recommended, and the accuracy page publishes the method, every figure with the population it was measured over, and a long section on what those figures do not demonstrate.

The measurement report→

The words, including the ones that concede

The guides, the glossary and the comparison pages, which name what each alternative does better and say plainly where somebody else is the better buy. A comparison written by the vendor is worth reading only if it can lose.

Every comparison→

The escalation route

Four routes on the contact page, three addresses, one person behind all of them. If a decision this product made is wrong, the receipt is at a URL and the person who wrote the policy is the person who reads the complaint.

Four ways in→
the entity on the paperwork

Entity Bind is a product. The terms name the company.

Entity Bind is a product name and has no legal personality of its own, so a procurement team searching the register for the product name will not find its supplier under it. Contracts, invoices and the data processing terms are with the company named in the first clause of the terms, which also gives its company number and VAT number. The privacy notice names the same company for data protection. That is a normal arrangement and a five-second thing to settle.

The data processing terms, the retention and erasure position and the sub-processor list are on the trust page, and the two documents that bind the parties are the terms and the privacy notice.

what experience is not

A track record is not a measurement

One founder and a design-partner product is a small thing to bet a supplier master on. The three sentences below are the ones /accuracy publishes, unchanged. A decade of delivery inside large organisations is a reason to expect the work to be done properly; it is not a substitute for the measurement.

the three, in the words /accuracy carries
  • No SOC 2. It has not been started.
  • No independent external validation of the accuracy figures. Every fixture is one we built.
  • No production customer holdout. The evidence is internal.

It is an early-stage product, sold and priced as one. Global data breadth and independent market validation are not yet at incumbent scale, and the accuracy figures come from internal fixtures rather than an external holdout.

What people ask before they write in

Five questions about the publisher rather than the product. Each answer names the page it can be checked against.

Who is behind Entity Bind?

James Rooney, founder. He wrote the resolution cascade, the calibration method published on /accuracy, and the words on this site, and he is who reads the mail sent to hello@entitybind.com. There is no switchboard and no handover to an account team. James Rooney has spent a decade landing delivery transformation inside HSBC, Microsoft, Sky, F1, Discovery and Anglo American, advising 150+ teams at HSBC against a $102M budget, which was the scope of the role rather than his authority, and co-leading the design of the target operating model prepared for global rollout to 500 teams. He codified that experience into The Tenhaw Way and now embeds as interim Agentic Lead inside organisations rebuilding around AI agents.

Is Entity Bind a company I can look up on the register?

No, and that is worth knowing before procurement searches for it. Entity Bind is a product name with no legal personality of its own. The company you contract with, and its registration, are named in the terms at /terms and in the privacy notice at /privacy. Contracts, invoices and the data processing terms are with that company.

Who wrote the accuracy figures, and has anyone independent checked them?

He wrote them, and nobody independent has checked them. That is stated on /accuracy in the same words it is stated here: No SOC 2. It has not been started. No independent external validation of the accuracy figures. Every fixture is one we built. No production customer holdout. The evidence is internal. Every figure the site publishes carries the population it was measured over, which is the only defence a self-measured number has.

If a match is wrong, who do we complain to?

The person who wrote the policy that made it. Every decision carries a receipt that reopens at a URL, so the argument starts from the evidence the pipeline actually used rather than from two recollections of it. The contact page takes four kinds of question at three addresses, and one person is behind all of them.

Is there a team page with names and CVs?

No. This site names one person, and it does not publish associate names, CVs or team size. A page of unnamed profiles would be the one thing an about page cannot afford. You create your Entity Bind workspace online, verify your email and create your own API keys. James Rooney reads assisted Sprint and evaluation requests. We take design partners a handful at a time, each on a scoped pilot.

the ask

Start with your own company records.

Create your Free workspace online and start with your own company CSV. If you want help with a first file or have a question, write to hello@entitybind.com; it reaches James Rooney. Nothing needs tidying first, and a half-formed question is a fine place to start.

300 credits. No card.

For a guided review of your file, explore the Merge Safety Sprint →