Before buying a tool
Identify the task, the expected improvement and the simpler alternatives.
Enterprise AI readiness assessment
Find out what needs to change before you put AI into a workflow. Check the work, the information and the people around it, then leave with a practical next step.
Free to use. No email needed.
Find the real obstacle
A new tool can leave the old problem in place. Start by looking at how the work gets done today. The useful outcome may be a cleaner source document, a simpler handoff or better access. Sometimes it is a small AI test. Sometimes the existing process needs fixing first.
Identify the task, the expected improvement and the simpler alternatives.
Separate missing access, poor sources, review gaps and skill needs.
Check what changes for the next team, system or type of information.
A practical review
Use these questions with the people who do the work. Open each card for evidence to look for and a possible next action.
01
What is slow, unreliable or expensive today?
Evidence: Observe the current task. Keep a few examples and record the effort, including review and rework.
A useful next action: Compare AI with a simpler change, such as a standard reply, a better form or a clearer process.
Who can help: The person responsible for the work
02
Are the instructions and records current and consistent?
Evidence: Check a few real source documents for conflicting instructions, missing dates and unclear ownership.
A useful next action: Choose the current source and fix conflicting versions before using them to generate answers.
Who can help: The document or data owner
03
Which information can this workflow use?
Evidence: Check the rules for the chosen tool and task. Include access, sharing, retention and any sensitive records.
A useful next action: Get an answer for unresolved information questions. Use made-up or suitable public material while you investigate.
Who can help: The relevant information, IT or security owner
04
Can the people doing the work use the required features?
Evidence: Try the intended steps with their accounts, permissions and files. A successful login is only the start.
A useful next action: Fix the missing permission or feature, or narrow the workflow to what is available.
Who can help: The tool or system administrator
05
What happens before and after the AI step?
Evidence: Walk through the handoffs, systems and exception cases. Identify any step that sends, changes or approves something.
A useful next action: Start with a manual handoff where that is enough. Define and test any integration or automatic action separately.
Who can help: The workflow and system owners
06
How will someone notice a plausible but wrong answer?
Evidence: Try typical cases, difficult cases and a case with a known mistake. Name what a reviewer should check.
A useful next action: Create a short review checklist and decide when the work needs a specialist or should stop.
Who can help: The person accountable for the output
07
Can users explain the result and correct a mistake?
Evidence: Ask someone to complete the task and talk through their choices. Note where they need help.
A useful next action: Use focused practice for the gaps you observe. Fix access or source problems rather than teaching around them.
Who can help: The team lead and people doing the work
08
Who owns changes, questions and the next review?
Evidence: Name the workflow owner, support contact and review date. Check that they have accepted the work.
A useful next action: Agree who updates the material, handles exceptions and decides whether to continue.
Who can help: The workflow owner and sponsor
How to use the worksheet
Work through one task from start to finish. Write down what you know, what you still need to find out and who can act. You can use the worksheet yourselves or bring it into a conversation with Ajaia.
Name the input, the result and the person responsible. Keep a current example for comparison.
Try the access, read the sources and inspect a result. Record a gap instead of guessing.
Give the action an owner and a completion check. Agree when to review it.
Use it now
Choose one workflow. Mark each area using evidence you have actually seen. Leave an unanswered question as “Unknown”. A total score would hide which gap needs attention.
Use the evidence to choose what needs to happen next. This worksheet does not approve a deployment.
Your notes stay in this tab. They are not automatically saved or sent to Ajaia. Download them before leaving. Use general descriptions rather than private records.
What to do with the findings
A “Ready” label needs a reason. “Unknown” is a useful finding too: it tells you what to investigate before making a bigger commitment.
Keep the decision specific to this workflow. A working test with made-up information does not establish that a production integration is ready.
A worked example
Invented example. The team, findings and actions below are made up.
A support team searches help articles and rewrites similar answers. It wants AI to draft replies, with a person checking each one before sending. Three reviewers can use the approved workspace. Two help articles give different return instructions, and the team has not agreed whether real customer messages may be used.
Fix the conflicting articles and create a shared reply checklist first. Then compare standard replies with AI-assisted drafts using made-up questions. Keep real customer messages out until the information owner has agreed their use.
The first actions improve the source material and the review process. Buying more licenses or scheduling a general training session would leave those gaps unresolved.
When you want help
Bring a short description of the workflow and the gaps you have found. We can review the work with your team and help turn the findings into a prioritised plan.
The work may involve data and source cleanup, process design, tool setup, engineering or targeted practice. We agree the scope and deliverables after a conversation.
Keep private records out of the inquiry form.
Tell us what kind of workflow or project you want to hear about.
Practical questions
Yes. Fill it in on this page or download the blank CSV and PDF. The worked example is also public. The on-page worksheet does not automatically save or send your notes; download them before leaving.
Start with a workflow and the people who own it. An organisation-wide view can then compare the findings across workflows, teams and systems. One ready task does not establish that every proposed use is ready.
Record that as the next piece of work. Clearer source material, a permission change, a standard reply or a redesigned handoff may help before training or an AI build. Compare the simpler option too.
No. It records findings and next actions. The relevant owners still decide permissions, information use and deployment. It does not replace a security review or a specialist audit.
Compare similar tasks using the current process and the proposed approach. Include checking, corrections, support and any new costs. Record the quality of the result as well as time spent, and keep estimates separate from observations.
We can review the workflow with your team, investigate gaps and turn the findings into a prioritised plan. The follow-on may involve source cleanup, process design, tool setup, engineering or targeted practice. We agree the scope and deliverables after a conversation.
Yes. Explain the task with made-up or suitable public material first. Keep private records out of the inquiry form. Agree any later access and information-handling arrangements before sharing real work material.
Customer references available upon request. Tell us what kind of workflow or project you want to hear about. We arrange references individually.