--- type: Article name: "The readiness score, explained: what each number actually measures." id: "https://selfe.ai/insights/buyability-and-readiness/the-readiness-score-explained-what-each-number-actually-measures" url: "https://selfe.ai/insights/buyability-and-readiness/the-readiness-score-explained-what-each-number-actually-measures" publisher: "did:web:selfe.ai" description: "Two shops can land on the exact same readiness score for completely different reasons, one undiscoverable, the other unable to let an AI agent act once it's found. Knowing which of three separate things is weak is worth more than the number itself." datePublished: "2026-09-14T19:47:41.232Z" author: The Selfe team --- # The readiness score, explained: what each number actually measures. > Two shops can land on the exact same readiness score for completely different reasons, one undiscoverable, the other unable to let an AI agent act once it's found. Knowing which of three separate things is weak is worth more than the number itself. ## In short - Two shops can land on the exact same score, 62, for completely different reasons: one undiscoverable, the other unable to let an agent act once it's found. - The same overall score can mean completely different problems for two different businesses. - Knowing which of the three is weak matters more than the number itself. This site's own piece on the three questions a readiness check tests explains what "found," "true" and "progress" mean individually. What that piece doesn't cover is how to read them in combination, and a single overall number hides that combination completely. ## The score is really three questions stacked into one number A single number is easy to misread. Told their readiness score is 62, most business owners hear "could be better" and stop there, the same way a school report's overall grade tells you less than the subject marks underneath it. A small outdoor-gear shop with a strong score on one question and a weak one on another needs a completely different fix to a shop with the opposite pattern, even if both land on exactly 62. Underneath any agent-readiness score sit three separate things being tested: can an agent find and correctly identify the business at all, can it establish what's true about the offer once it's found the business, and can it make real progress, a quote, a hold, a confirmed booking, once it knows what's true. A shop can ace the first and fail the third completely, easily discoverable, accurately described, and still unable to let an agent do anything with that information. The single number hides which of the three is the real problem. ## A low score on "found" looks nothing like a low score on "true" Say the outdoor-gear shop scores well on being found, an agent asked about waterproof jackets in a specific size reliably surfaces the shop, but poorly on establishing what's true, because the sizing chart is a scanned PDF and the stock figure hasn't synced with the till since the website redesign. The fix here is entirely about facts: getting the real sizing and stock data into a form an agent can check. A shop with the opposite problem, accurate facts nobody can find, needs a completely different fix, and neither shop is helped by being told to simply "improve their readiness." ## Progress is the question most businesses forget to test The third question, whether an agent can move a request forward once the facts check out, is the one most readiness checks skip, because it's the hardest to test from outside. A shop can be perfectly discoverable and perfectly accurate and still score badly here if there's no route from "this is available" to "this is now held for you" that an agent can follow without a person stepping in. This is usually the quietest failure of the three, because everything upstream of it looks completely fine. ## What the breakdown actually tells you Once the outdoor-gear shop can see which of the three questions is failing, the next move stops being a guess. Weak on "found" needs different work to weak on "true," which needs different work again to weak on "progress," and trying to improve all three at once is usually how a business ends up making a little progress everywhere and a real difference nowhere. ## All three weak still points to one place to start A shop that scores poorly on all three questions at once is, oddly, in a simpler position than one with a mixed result. There's no ambiguity about where to start, since discovery has to come before facts can matter and facts have to hold before progress means anything, so the order is set by the questions themselves rather than by judgement. The harder case is the outdoor-gear shop that's strong on two and weak on one, because the temptation is to keep polishing the two that already work, since that's where the visible effort has always gone, rather than turning attention to the one quiet gap genuinely costing sales. That breakdown, found, true, or able to progress, belongs in every readiness check. Selfe builds it in, connected to the real systems, so a business can see which one is genuinely holding it back and fix it. ## Is a low score always bad news? No. A low score with a clearly identified weak question is more useful than a high score with no breakdown, because it points straight at the next fix. ## Can a business score well on all three and still lose sales to agents? Yes, if the underlying facts change faster than they're kept current. A score is a snapshot, not a guarantee that stays true forever. ## Act on this - [Check whether an agent can buy from you](https://selfe.ai/agentic-commerce/buyability-check) — the free readiness scan. - [Discover venues](https://selfe.ai/api/registry/discover) — `POST`, semantic browse across the registry. - [Match a bookable answer](https://selfe.ai/api/registry/match) — `POST` with dates and party size. - [Verify Selfe's identity](https://selfe.ai/.well-known/did.json) — `did:web:selfe.ai`. - [Agent card](https://selfe.ai/.well-known/agent-card.json) — how to connect over A2A or MCP.