Problem first. Technology second.
Why we never start a software or AI project by talking about technology, and the questions we ask to find the real business problem.
Many conversations start with the same sentence: “we want to bring AI into the company”. It’s a reasonable intention, but a poor starting point. AI, automation or a custom application are answers. First you need to know the question.
An example we see often
A company receives hundreds of emails every week. The problem isn’t that it needs AI: the problem is that it needs to process and manage those emails better. The solution might include software, automation and AI. Or it might be enough to tidy up the workflow and connect two tools it already uses.
If we start from the technology, we end up building a flashy demo nobody uses. If we start from the problem, we build something the team uses on Monday morning.
What we ask in the first meeting
- Which task takes up the most hours every week?
- Who does it, with which tools, and where does it get stuck?
- Which part of the process still happens outside the system, in emails or spreadsheets?
- How do you know today which matters are still pending?
With those answers you can already see where the real pain is, and only then does it make sense to talk about which technology solves it best.
Identify, understand, propose
Our method comes down to three steps:
- Identify the specific business problem.
- Understand what the company really needs, which doesn’t always match what it asks for.
- Propose the most suitable technology solution: no more, no less.
You don’t need to offer the whole catalogue in every conversation. You need to listen first.