Our own score
We scored 15 out of 25
We built an instrument that scores how ready a business is for AI agents, and ran it on ourselves before running it on anybody else. Every point below cites something you can check from your own browser. We score well on the two domains a visitor can see and poorly on the three that have to be built, and those three are what we are building.
Reading the number
The total hides the shape, and the shape is the useful part
Fifteen out of twenty-five sounds like a middling result. Two strong domains and three weak ones is a plan. Every business we have scored so far has this shape, because Discovery and Data are what a website already does by accident and the other three have to be decided on purpose.
Where 15 puts us: an agent can work out what we sell and what it costs without a person in the loop, and still cannot transact. The instrument caps the total when one domain is far behind the others, which is the part of our own result we are watching. Governance at 2 becomes the ceiling on everything else the moment we make anything transactable, so the controls get built before the next endpoint rather than after it.
The scorecard
What an agent actually meets, domain by domain
Each card is the finding for one domain, taken on the date at the top of this page. The four items in the roadmap below are what moves the low three.
- Discover 4 of 5
Discovery
An AI system can find this site, read every page of it as plain text, and see a stated position on what it may do with what it reads.
- Understand 4 of 5
Data
An agent can read what we sell and what it costs, and the machine-readable copy agrees with the page it sits on.
- Access 3 of 5
Interfaces
An agent can ask this site what we sell and what it costs, and get data back rather than a page to parse.
- Act 2 of 5
Transactions
Every path to getting work started runs through a person or an external calendar.
- Govern 2 of 5
Governance
We have a written position on crawling and no controls over agents acting.
Check it yourself
Four of the five domains are scoreable without asking us anything
That is a design decision in the instrument rather than a convenience. Evidence anyone can verify from outside survives an argument in a boardroom, and it means we can score a prospect before the first call. It also means a competitor can score us, which is the reason this page exists.
Governance is the exception. Nothing about approval thresholds, audit trails or revocation can be verified from outside an organization, so that score is the one we are asking you to take on our word. When we score a client, Governance evidence is recorded as attested rather than verified for the same reason.
What happens next
Four things, ordered by how much score each one moves
This is the same sequencing we would give a client at 15 out of 25. The cheapest point goes first, and the governance work goes before the endpoint that needs it rather than after.
-
A modified date on every page, and something watching it
Staleness has to raise an alert to a named owner rather than wait for a reader to notice, which makes this an operating commitment rather than a build. It is the cheapest point on the board and the one we have put off longest. Takes Discovery from 4 to 5.
-
Agent identity and an audit trail
Registration, scope, thresholds and a revocation path, tested rather than assumed. It has to be built before the second endpoint rather than after it, because opening access before controlling it is the mistake we tell clients to avoid. Takes Governance from 2 to 4.
-
A callable eligibility check
Enough for an agent to establish whether an engagement fits its user before a person is involved. This is the one that needs the controls above it first, and it is the expensive one. Takes Transactions from 2 to 3.
-
A data contract on the catalogue
What each field means, how often it changes, who owns it, and something that notices when a price goes stale rather than waiting for a reader to. Takes Data from 4 to 5.
Come back and check. The score carries the date it was taken, and the date moves with the number. A published score that quietly stops being true is the failure this whole page is about.
Why publish this
We are working toward 25 out of 25, in the open
We ran the Index on ourselves before running it on anybody else, and published what came back the same day we had it. 15 is where we are, and the four items above are how we get the rest. Anyone can write about agent readiness. Publishing a score against your own instrument, with the evidence linked and a date on it, costs something to be wrong about.
Find out what your own score is
Four of the five domains we can score from the outside before you have engaged us. Bring your website and whatever agent access your team has already granted, and we will show you the point where a machine stops.