Six readiness questions, and an answer that can be no

Answer honestly, it scores instantly

This is a free AI readiness assessment. Six questions about how often the work happens, whether the process is written down, who owns the project and what your systems can connect to. It scores in your browser and gives a verdict straight away. Nothing is stored, no email is asked for, and one answer can produce a not yet.

Nothing is stored and nothing is sent anywhere. The scoring runs in your browser and closing the page loses it.

Answer for the business as it is today, not as you intend it to be next quarter. An assessment answered aspirationally returns an aspirational answer.

Why two answers can override the score

A high total does not compensate for a process that exists only in people's heads, or for a project nobody inside the business owns. Those two are not weaknesses to be outweighed. They are the conditions under which the rest of the work cannot hold.

An undocumented process gives an automation nothing to be accurate against, so it will be confidently wrong in ways nobody notices for months. And a project with no internal owner does not survive its first disagreement about scope, because there is nobody whose job it is to settle it.

The scoring, in full

A score whose calculation is hidden is a sales device wearing a lab coat. Here is every weight.

• Question 1, How often does the work you would automate actually happen? A few times a month scores 0, A few times a week scores 2, Several times a day scores 4, Dozens of times a day scores 6.
• Question 2, Is the process written down anywhere? Nowhere. It lives in people's heads scores 0, Partly, and it is out of date scores 2, Yes, and it is current scores 5.
• Question 3, Who inside the business owns this project? Nobody yet scores 0, A team member, part time scores 2, A manager with authority to change the process scores 4, The owner or a director scores 5.
• Question 4, Where does the data live today? Paper, or one person's phone scores 0, Spreadsheets and messaging apps scores 2, Software that has an export scores 3, Software with a proper API scores 5.
• Question 5, Could you tell whether it worked? No idea what the current number is scores 0, A rough sense, nothing recorded scores 2, Yes, we track it already scores 5.
• Question 6, How does the team feel about changing how they work? They will resist it scores 0, Mixed, some will and some will not scores 2, They have been asking for it scores 5.

What the bands mean

The thresholds are judgement, not arithmetic, and they are stated so you can disagree with them.

• 22 and above out of 31: ready. The question is which task, not whether.
• 14 to 21: close. Start on one narrow piece and close the weakest answer first.
• Below 14: too early. Automation on top of missing groundwork makes the gaps look like facts.
• Either override answer: not yet, whatever the total says.

Where this assessment is the wrong tool

It assumes you already have a task in mind. If the question is which part of the business to look at rather than whether to automate a known process, this will not answer it, and the useful exercise is measuring where time actually goes for a fortnight.

It also assumes the process should exist. Some of the most valuable work is discovering that a weekly report nobody reads has been produced for four years. Deleting a task beats automating it, and no self-assessment will tell you which ones those are.

What happens if you take the score to a supplier

Scoring 22 or above does not mean buy something. It means the conditions hold, and the first thing worth deciding is whether to build it with your own team. Where somebody in-house already writes automations and will still be there next year, a business scoring well on questions two, four and five can do the first one alone, and this assessment is then more use to you than to anybody selling. Whoever builds it, you own the system and it sits in your own accounts under your own logins, which is a thing to settle before a supplier starts rather than at the end.

No price is published anywhere on this site, and the reason is visible in the six questions above. Question one is volume. Question four is what your tools will actually permit. Question two is how much of the process exists in writing. Those three are most of what moves the number, which is why a figure quoted before anybody has looked at them is a guess with a decimal point on it. The timing is published instead of the price: the audit takes the first week, one named system is live inside a fortnight, and the second and third land across month two.

Anything built has a stop written into it before it goes live. Spending, pricing, anything published in your name and any serious complaint wait for human approval, and a workflow that meets a case outside its scope hands it to a person with the record attached rather than guessing. The work behind that is published with its figures rather than described: more than 500 calls a day for Big Texas Land Buyers, a delivery line rebuilt as one audited automation for Quillon, three ERP systems for RM Gulistan Engineers in Karachi. Haad, the co-founder who owns growth and client solutions, takes the conversation that follows a score. Wobble works from Karachi, month to month, across 25 engagements in six countries.

Common questions

Do I have to give my email to see the result?

No. The score appears as you answer, nothing is stored, and nothing is transmitted. Gating a result behind an email turns an assessment into a lead magnet, and nobody links to a lead magnet.

What does AI readiness actually mean?

AI readiness means the conditions an automation project needs are in place: work repetitive enough to be worth automating, a process documented well enough to build against, someone inside the business who owns the outcome, data reachable from a system, a number to measure against, and a team that will use it. Technology is rarely the constraint.

Why can two answers override the total?

Because they are conditions rather than strengths. An undocumented process gives the build nothing to be accurate against, and a project with no internal owner does not survive its first disagreement about scope. No total compensates for either.

What should I do if I score too early?

Three things, in order: get the data out of paper and phones into something with an export, write down what the process actually is today rather than what it is supposed to be, and start recording one number so a before exists to compare against. All three are cheaper now than after a failed build.

How accurate is a six-question assessment?

It is a filter, not a diagnosis. It is accurate enough to tell you whether to have the conversation, which is what it is for. Anything claiming to size or scope a project from six questions is guessing with a progress bar.

Is this the same as the AI Readiness Call?

No. This is instant, free, ungated and self-scored. The call is a conversation with a person about a specific business. This exists so you can decide whether that conversation is worth having, including deciding that it is not.