How ready is your team to build with AI?
Ten questions, about three minutes, no email. You get a score out of 30 on people, workflows and readiness, your weakest axis with one action for this month, and the two answers that cost you the most points. If the honest answer is "not yet", the result says so.
Workflows is your weakest axis: 4 of 12 points.
One thing to do this month: For one week, have everyone note the three tasks that took the most time, then add up the hours by task.
What this team AI readiness assessment checks
The Builder Check is a free, three-minute self-assessment of how ready a team is to build with AI; the Builder Scan is the paid, two-week audit inside your company. It does not test one person’s AI skills. Ten checkpoints look at the people, the work and who owns the result; each answer scores 0 to 3 points.
| Axis | Points |
|---|---|
| People | 9 |
| Workflows | 12 |
| Readiness | 9 |
| Level | Score range |
| Spectator | 0–9 |
| Tinkerer | 10–16 |
| Builder-ready | 17–23 |
| Operator culture | 24–30 |
The four levels, once
| Level | What it means | First move | What we offer |
|---|---|---|---|
| Spectator0–9 | Honest read: the 90-day program would be premature. There is not yet enough builder energy or workflow clarity to transfer capability onto. | Name the friction and give one curious person protected time. Read the free guide → | Nothing paid for now |
| Tinkerer10–16 | There is real energy here — but it is uncoordinated and undocumented. The risk: enthusiasm that evaporates when the enthusiast leaves. | Find which tinkerers can become builders, and which workflows deserve them first. | The on-site Builder Scan |
| Builder-ready17–23 | Strong signals: candidate builders exist and your workflows have enough shape to build on. | Confirm the builders and price the business case before committing. | The Scan, then the 90-day program |
| Operator culture24–30 | Rare. You already behave like a team that owns its systems. The question is no longer "can we build" but "what should we build next, and who referees the standard". | Decide what to build next and who referees the standard. | The Referent Residency |
Whatever the score, if the 90-day goal is a report that reassures or people who took a training, the result never points to the program.
The paid Builder Scan
If the level points to it, the Builder Scan is the paid follow-up: two weeks inside your company, roles mapped, five to eight builders identified and a priced business case. It starts from €4,900, is scoped on the call, and is credited in full against the program if you continue within 60 days. See the Builder Scan →
The ten checkpoints, with the points for each answer
PEOPLE
Who experiments with AI on your team today?
- 0 pt Nobody, really
- 1 pt One enthusiast, on their own
- 2 pt A few people, uncoordinated
- 3 pt Several — and they share what works
When a tool your team relies on changes, what happens?
- 0 pt We wait for official training
- 1 pt We complain, then adapt late
- 2 pt A few people figure it out
- 3 pt Someone documents it and teaches the others
If you asked for five volunteers to automate parts of their own jobs, you would get…
- 0 pt Silence
- 1 pt One or two, maybe
- 2 pt About five
- 3 pt More than five — you would have to choose
WORKFLOWS
Can you name where your team loses the most hours each week?
- 0 pt No idea
- 1 pt A feeling, but no numbers
- 2 pt Yes, roughly
- 3 pt Yes — measured and written down
How much of that work follows a repeatable pattern?
- 0 pt It is all one-offs
- 1 pt Some of it
- 2 pt Most of it
- 3 pt Almost all — and it is documented
Where does critical process knowledge live?
- 0 pt In people’s heads
- 1 pt Scattered documents
- 2 pt Partial playbooks
- 3 pt Maintained playbooks someone owns
Has anyone tried automating part of their own job?
- 0 pt Never
- 1 pt Tried once, abandoned
- 2 pt One thing runs quietly somewhere
- 3 pt Several automations are in daily use
READINESS
If an automation failed silently for a week, would you know?
- 0 pt No
- 1 pt Eventually, by accident
- 2 pt Probably — a customer would tell us
- 3 pt Yes — we log and review exceptions
Who would own an internal AI system after it is built?
- 0 pt Nobody, honestly
- 1 pt IT, by default
- 2 pt Whoever built it
- 3 pt A named referent role with time allocated
What do you actually want to be true in 90 days?
- 0 pt A report that reassures us
- 1 pt People who took a training
- 2 pt Systems running in production
- 3 pt Running systems AND people who can build the next one
Who wrote it, and how the cut-offs were set
Written by Loïc Guyon, the operator behind LearnAIthing, from building and running AI agents for client firms. The cut-offs between levels are a practitioner’s judgment, not a statistical norm: no sample of teams has been scored yet to validate them. Read the level as a conversation starter; the weakest axis and the two answers that cost the most points are the useful part. Last reviewed on 11 October 2026.
What this self-check leaves out
Ten questions cannot judge data access, tools or security. Before anyone builds, ask your IT lead four things:
- Can the people who would build read the data they need, with access granted in writing?
- Which AI tools are approved, and under which company account?
- Which data must never be pasted into an outside tool?
- Who signs off before an automation touches a customer?
Questions about the Builder Check
Is the Builder Check free?
Yes: ten questions, about three minutes, and you see, copy and print your result without giving an email. The Builder Scan is a different thing: two weeks of our time inside your company, paid, from €4,900.
Does it test my own AI skills?
No. It reads a team: who experiments, how repeatable the work is, and who would own a system once it runs. To build your own practice, see the individual path. See the individual path →
What happens after the result?
Copy the link to share it, or print it as a one-page PDF. If you want to talk about whether the paid Builder Scan fits, leave your details under the result; a person replies within two business days.