Most AI ideas arrive as a one-line question in a meeting and leave as somebody's job. If that job is yours, the hard part isn't picking a tool; it's knowing whether the problem needs one at all. Here's a test you can run in an afternoon: five signs that say yes, three that say stop, and two problems scored side by side.
Why we wrote this
The question that lands on your desk
It's the Tuesday ops review, and the agenda has run long. Someone raises the claims backlog again. Forty new claims arrive a day, two assessors triage them, and the queue is now nine days deep.
The general manager leans back and asks, "Can't we just use AI for that?" Heads nod around the table. The minutes record an action: "Explore AI for claims triage", with your name next to it.
The short answer: AI suits work that happens often, draws on information you already hold, and needs the same judgement made over and over. A person should be able to check the result. It doesn't suit work that's rare, that a simple rule could handle, or where nobody agrees what good looks like.
Why "let's try AI" is the wrong place to start
Interest isn't the gap. The National AI Centre's latest quarterly adoption insight found 43% of Australian SMEs reported some level of AI adoption between December 2025 and February 2026. More than half of the businesses not adopting (54%) said AI isn't relevant to them.
Both camps tend to skip the same step. One decides AI fits everything, the other decides it fits nothing. Neither tests the specific problem on the table.
Here's the part AI vendors tend to skip: plenty of "AI problems" are really process or software problems. Fixing them that way is cheaper, faster and easier to maintain. That's a good outcome, not a consolation prize.
Five signs a problem suits AI
Run each one against the action item on your list. You're looking for at least four of the five.
1. It happens often
-
What it is: volume. AI pays back through repetition, not one-off brilliance.
-
What it looks like: a task your team does daily or weekly, dozens of times. Claims triage, supplier invoice queries, delivery exceptions.
-
What good looks like: you can count how many times it happened last month, from a system rather than a guess.
2. The inputs already exist
-
What it is: AI works from what you give it. If the information is already captured, even messily, you have a starting point.
-
What it looks like: emails, PDFs, forms, past decisions and notes in your CRM or core system.
-
What good looks like: you can point to where each input lives and who controls access to it.
3. People make the same kind of judgement call, over and over
-
What it is: the line between AI and ordinary automation. AI can handle work that needs reading and weighing, where a fixed rule breaks on the exceptions.
-
What it looks like: an experienced person reads a document or request and decides what happens next. Triaging claims, checking loan documents, routing customer enquiries.
-
What good looks like: your best person could explain roughly how they decide, and two of your senior people would mostly agree.
4. Scale is the bottleneck, not expertise
-
What it is: the team knows how to do the work but can't keep up. AI adds capacity; it doesn't supply know-how nobody has.
-
What it looks like: a backlog that grows every week, even though the work isn't hard.
-
What good looks like: if you doubled the team, the problem would mostly go away.
5. A person can check the output before it matters
-
What it is: a natural review point, so a wrong suggestion is caught before it costs anything.
-
What it looks like: a step where someone already signs off. A draft is read before it's sent, or a recommendation is approved before it's actioned.
-
What good looks like: nothing reaches a customer, regulator or bank account without a person seeing it first. The same insight found only about half of current AI users check outputs before they affect customers. Design the check in from day one, with clear intervention points where a person can pause or override it.
Three signs it isn't an AI problem
A rule or software you already own would do it
Nobody agrees what a good result looks like
It's rare, or high-stakes with nobody checking
Two problems, side by side
Two illustrative problems from a mid-sized logistics business. First, the five signs, where yes is what you want.
|
Five signs
|
200 delivery exception emails a day
|
Reformatting the monthly board report
|
|---|---|---|
|
Happens often
|
Yes, daily
|
No, monthly
|
|
Inputs already exist
|
Yes, emails plus order records
|
Yes
|
|
Repeated judgement
|
Yes, each email needs reading and routing
|
No, same layout every time
|
|
Scale is the bottleneck
|
Yes, two coordinators can't keep up
|
No
|
|
A person checks the output
|
Yes, a coordinator approves each action
|
Yes
|
|
Score
|
5 of 5
|
2 of 5
|
Then the three warnings, where no is what you want.
|
Three warnings
|
Exception emails
|
Board report
|
|---|---|---|
|
A rule or existing software would do it
|
No
|
Yes, a template would
|
|
Nobody agrees on a good result
|
No, the right action, same day
|
No
|
|
Rare, or high-stakes and unchecked
|
No
|
No
|
For the exception emails, AI reads each email, matches it to the order and suggests an action: rebook, refund or escalate. The coordinator approves or corrects it, and corrections are logged to tune the suggestions. The two coordinators now review instead of reading from scratch.
The emails pass five of five and trip no warnings, so they're worth a proof of concept. The board report scores two and trips the rule warning. It's worth an afternoon with a template.
What drives the effort
This isn't free, and the cost depends less on the AI than on your situation. Three drivers move it most.
- Where the information lives. One system is quicker than six. Each extra source adds an integration, an access request and another format to clean.
- How often the work changes. A stable process is easier to get right. If the rules or products shift every quarter, the solution needs re-testing every quarter too.
- How much review is needed. Regulated work needs more human checkpoints and a record of who approved what. Those take time to design properly.
If governance is new ground, the National AI Centre's Guidance for AI Adoption includes a free AI policy template and an AI register template.
How we approach it
NEXUS Foundation
Check your own problem
- Does it pass at least four of the five signs?
- Does it avoid all three warning signs?
- If either answer is no, have you checked whether a rule, template or tool you already own would fix it?
Yes to the first two means it deserves a proper look. A no to either is still progress, because you've found the cheaper answer or the reason to wait.
Frequently Asked Questions
How do I know if AI is right for my business?
What's the difference between AI and automation?
What are good AI use cases for business?
When should you not use AI?
Does our data need to be perfect before we start with AI?
How long does it take to find out if an AI idea will work?
What affects the cost of an AI project?
How many use cases should we start with?
What if none of our ideas pass?
Discover app development insights and AI trends with Akash Shakya, COO of EB Pearls. Learn how we build successful digital products.
Read more Articles by this Author