Pick the sentence that sounds like you.
Four sentences per question, scored 1, 2, 4 and 5. Pick I don’t know where you cannot answer; it counts, it never scores. The band appears after eight scored answers. Press Load our answers to see how we score ourselves, honestly, in October 2026.
Readiness scorecard · self-reported · nothing leaves your browser
Pick the sentence that sounds like your company today.
Twelve questions, two per pillar, four sentences each. Pick I don’t know when you cannot answer; a band appears after 8 scored answers.
0 of 12 answered. Answer at least 8 to see a score.
Data
Can an assistant reach your records, and can it say where an answer came from? At Pirxey: Our second brain reads twenty-five tools with each person's own logins, and the index tells it what to open first.
– of 50 of 2 answeredReason
Is there a business reason with a number on it, or a demo that impressed someone? At Pirxey: Every brief we publish starts from one question we actually had, with the count that answered it.
– of 50 of 2 answeredRules
If an answer is challenged, does somebody own the decision, and is there a trail? At Pirxey: We keep an inventory of every AI system in use and a standing group that approves a new use of a model on company data.
– of 50 of 2 answeredPeople
Do the people who will use it know what it is bad at? At Pirxey: Our monthly Pulse: 77 answers in September, 69% at Crew level or above after three editions.
– of 50 of 2 answeredPlumbing
Can you connect, watch and change a model without a heroic week? At Pirxey: One maintained setup of connections, checks on every change, and a loop with a person at five stops.
– of 50 of 2 answeredBacklog
Is there a ranked list, or a pile of wishes? At Pirxey: We rank by value against the number of systems touched, and the first working version has a six-week limit.
– of 50 of 2 answeredYour scorecard · 0 of 12 answered
Answer at least 8 of the 12 questions to see a band. 0 so far.
Self-reported, not an audit: the score says where to look, not what is true. Nothing is sent anywhere. With Remember on, the answers stay in this browser profile until you press Clear.
What each pillar asks, and what we do about it.
Six things we check before an AI project, in plain words. Under each: how it works at Pirxey as of autumn 2026, and the brief that shows it.
Data
Can an assistant reach your records, and can it say where an answer came from? Not a data lake: a list of the systems that hold what you would ask about, an owner per system, and the sensitive sets marked before anyone connects a tool. Our second brain reads twenty-five tools with each person’s own logins, and the index tells it what to open first. Tracing an answer back to its source still takes a person; that is our open item here.
Reason
Is there a business reason with a number on it, or a demo that impressed someone? The test is a business owner who will be asked about adoption, not the engineer who built it. We have two or three named problems with a measure each, and every brief we publish starts from one question we actually had. The rule for when a pilot earns more budget is the part we have not written down.
Rules
If an answer is challenged, does somebody own the decision, and is there a trail? We keep an inventory of every AI system in use, including the unofficial ones, and a standing group that approves a new use of a model on company data. What may go to a hosted model is written down, shared knowledge is checked before it is saved, and a person approves what leaves the company. Brief 017 is the long version.
People
Do the people who will use it know what it is bad at? Measured by use on real tasks, not by workshop attendance. Our leaders used the assistant weekly before anyone else was asked to, which is the honest reason the company followed. The monthly Pulse had 77 answers in September, 69% at Crew level or above after three editions, and it asks every month who is blocked by what.
Plumbing
Can you connect, watch and change a model without a heroic week? One maintained setup of connections with the person’s own logins, logs someone reads, checks on every change, and a loop with a person at five stops. The six-week build in brief 018 ran nine checks on every change; the saved set of questions that runs before a prompt change is what we add next.
Backlog
Is there a ranked list, or a pile of wishes? Value against the number of systems touched, one table, the top item in progress with a date, and a baseline measured before the start. We rank quarterly and give a first working version six weeks. The baseline before the start is the step we skip most often, which is why our own card points there first.
Where to look, not what is true.
A self-assessment is a conversation starter with yourself. It is answered by the people who built the current setup, about the setup they built, so it leans generous. Ours does too: we loaded our answers so you have something real to compare with, not because they are audited. A budget decision or a board sign-off wants someone to read the data and the code, not the founder’s opinion of them.
What the band can do is point. If Rules is your lowest pillar, the three first moves are cheap and take a month, and you will find out quickly whether the organisation wants this. If Data is lowest, expect the first project to spend most of its time on plumbing, and plan for that instead of being surprised by it. Our own card points at Backlog: we skip the baseline before a project starts, and the card is right.
For what to do with the result, brief 009 turns five plain scores into a ninety-day plan that starts with one repeatable workflow. This brief is the diagnosis; that one is the plan.
Our numbers, and one idea we borrowed.
Each card says what kind of source it is and whether whoever published it sells something in this category.