AI readiness assessment: twenty questions, a written answer
Twenty questions about your systems, your data and the work your team does by hand. An engineer reads your answers and sends you a written reply: the first task worth automating, whether your data needs to stay private, and what a first step would involve. If the honest answer is “not yet”, we say so. No call, no sales deck.
- A readiness view in four areas
- The first workflow worth automating
- Private AI or cloud model
- What a first step would involve
How the assessment works
Five short screens, four questions each. It takes about fifteen minutes. You can go back and change answers before you send them.
What you get back
A short written report by email, from an engineer, not a template. It covers:
- A readiness view in four areas: data, systems, process and team.
- The first workflow we would suggest automating, and why.
- Whether your data needs private AI or can use a cloud model.
- What a first step would involve, and what your side would need to provide.
- An honest recommendation, which may be to wait.
Twenty questions, five short screens
Answer what you can. Blank answers are fine; the engineer will ask if something matters.
- About fifteen minutes
- Your answers are read by an engineer, not a sales team
- We only call if you ask us to
The twenty questions we ask, and why
Your systems
AI is most useful when it can act inside the systems where work already happens.
- Which business systems does your team rely on most? A CRM, ERP, helpdesk, project tool or in-house app all count.
- Which accounting or finance software do you use? Invoices and quotes are the most common automation candidates.
- Do you sell online, or run a customer portal or app? Order and customer data is a rich source for agents.
- Where do your emails and documents live? That is what an assistant would read.
Your data
AI can only use what it can reach, and the biggest cause of stalled projects is data that needs work first.
- Where is your most important business information stored today?
- Is any of it restricted from leaving your company? This decides private or cloud AI.
- Roughly how many documents or records are involved? This shapes the hardware and the approach.
- How clean and consistent is that data?
The work
The best first project is a repeated, well-understood task.
- What are the three tasks your team repeats most by hand?
- Who does them, and roughly how many hours a week do they take? This gives the measure of success.
- Which of those tasks involve reading or writing text? Those are the tasks language models handle best.
- Has anyone on the team already tried an AI tool for this? What worked and what did not is useful evidence.
Constraints
Rules, hosting, budget and timing shape where the AI can run and how big the first step should be.
- Are there compliance or regulatory rules you must follow?
- Does your IT team manage servers, or is everything in the cloud? This decides who can host a private model.
- What is your rough budget range for a first project?
- When would you like to see the first result?
About you
Enough to send the report, and nothing more.
- Your name and role.
- Your company and its size.
- Your work email, so we can send the report.
- Whether you would like a call to go through the report. We only call if you ask.
Questions people ask about the assessment
Something else on your mind? Ask an engineer directly.
Is it really free?
Yes. It is how we decide, together, whether a project makes sense. About half of assessments end with “not yet”.
Who reads it?
An engineer. We do not have a sales team.
Will you call me?
Only if you tick the box on the last screen.
What happens to my answers?
They are stored so we can write your report, and they are covered by our Privacy Policy. They are not shared.
Twenty questions, fifteen minutes, a written answer
Start at the top of the form, or send an engineer a note first if you prefer.