Short answer
What is an opportunity analysis, in concrete terms?
A list of possible projects, each costed in terms of money, time and expected gain, filtered by your real constraints: available budget, people who can be assigned, regulatory obligations, state of your information system. We keep three or four, set the rest aside in writing, and stand by this choice before your committee.
The four constraints we always look at
- The money available now, not next year's theoretical budget. A project that does not fit within this quarter's cash flow is not a project, it is an intention.
- Your people's time. An AI project takes up time from operational staff for scoping and checking. If nobody is available, the project will fail, whatever its technical quality.
- The state of your data. Data that is scattered, duplicated or has never been cleaned inevitably limits what can be built. It is often the first real project.
- Your obligations. Regulated sector, health data, public procurement, customer requirements: they narrow the scope and must be known before promising anything.
The deliverable is short: a table of the projects selected, a table of the projects set aside with the reason, and the cost of doing nothing. That last figure is the one that triggers decisions.