17/09/2026
A question I keep asking before discussing any AI project:
If we remove the word “AI” from the requirement, what business problem are we actually trying to solve ❓
Because once you ask that question, the conversation often changes.
Sometimes the real problem is not AI.
It is a quotation process that takes too long.
Customer information scattered across different systems.
Employees copying the same data between WhatsApp, Excel, email and ERP.
Teams that cannot access the information they need without asking someone else.
Or legacy systems that were never designed to support newer workflows.
In situations like these, adding AI does not automatically solve the problem.
Sometimes it simply adds another layer on top of an already inefficient process.
Before deciding to build an AI assistant, agent or automation, I usually want to understand a few things first:
→ What business outcome are we trying to improve?
→ Where does the process actually break down today?
→ What data does the solution need?
→ Where is that data currently stored?
→ Which existing systems need to be connected?
→ And most importantly: does AI genuinely need to be part of the solution?
Sometimes the answer is AI.
Sometimes it is system integration.
Sometimes it is better data.
Sometimes it is workflow redesign or automation.
And sometimes, the right decision is not to build anything yet.
That distinction matters.
My role is not to find somewhere to insert AI into every business.
It is to understand the business problem first, then determine where technology can create meaningful value — and what needs to be fixed around it for the solution to actually work.
For companies exploring AI right now, this is one of the most important conversations to have before choosing a tool, vendor or project.
If your company is exploring AI, tell me the business problem you are trying to solve.
I’ll tell you the first thing I would examine before deciding whether AI is even the right place to start.