AI Strategy
Decide where AI deserves your investment, and in what order.
There's no shortage of possible uses for AI. The question for a leadership team is which ones serve its objectives, what each needs in data and people, and which to start with. We help you make those calls, then turn them into a roadmap your teams can carry out.
The decisions this work lets you make.
Priorities
You know which use cases to start with, once they're compared on expected value, implementation effort and operating constraints.
Investment scenario
You choose between two or three scenarios, which differ in the number of use cases, their order and how deeply they connect to your systems.
Build or buy
For each use case, the work establishes whether an off-the-shelf tool is enough or a development specific to your business is justified.
Owners
Each use case you keep has an owner on your team, and each stage of the roadmap ends with a decision that belongs to them.
How we compare use cases.
This work is the first part of our AI Transformation engagement, which then covers the pilot, integration into your tools and adoption by your teams.
Step 01
Objectives
We start from the leadership's objectives, such as cutting a lead time, absorbing growth or serving a customer base better.
Step 02
Inventory
With your teams, we list the tasks where AI could help, along with the documents and systems they rely on.
Step 03
Data readiness
For each use case, we check that the data exists, that it's accessible and that someone answers for it.
Step 04
Comparison
Each use case is assessed on expected value, implementation effort and operating constraints.
Step 05
Decisions
The leadership chooses its scenario, decides what to build or buy and names the owners.
Step 06
Roadmap
The chosen use cases follow one another according to their dependencies, in the order the leadership approved.
What a prioritisation looks like.
| Use case | Expected value | Effort | Data | Decision |
|---|---|---|---|---|
| Searching the quality documentation | High | Low | Ready | First pilot |
| Reading delivery notes | High | Medium | To prepare | Second stage |
| Draft replies to quote requests | Medium | Medium | Ready | Third stage |
| Demand forecasting | Very high | High | Incomplete | After work on the data |
| Chat assistant on the website | Low | Medium | Ready | Set aside for now |
In this example, demand forecasting would bring the most value, but its data is incomplete, so the roadmap places it after work to make that data reliable. Searching the quality documentation comes first, because it takes little effort and its documents already exist. The website chat assistant is set aside for now, because this company's customers go through their sales rep rather than the website.
Investment scenarios and the choice of tools.
We present the leadership with two or three scenarios, which differ in the number of use cases, their order and how deeply they connect to your systems. Each scenario shows what drives its investment, such as the systems to connect, the volume handled, hosting and follow-up after go-live, as well as what it leaves out. The leadership therefore compares complete options, and the amount for each is set once the scope is agreed.
The build-or-buy choice is made use case by use case, because an off-the-shelf tool is often enough for a common need, while a process specific to your business can justify a development. We take no commission from any software vendor, so our recommendation doesn't depend on the tool you choose.
Applications in your industry.
Balancing use cases and confidentiality
The most useful use cases often touch sensitive data, so the roadmap first settles what can be processed, by whom and on which hosting.
See the industry
Choosing between documentation, logistics and reporting
Quality documentation, logistics files and cross-site indicators often compete for first place, and the state of the data then decides the order.
See the industry
Starting from reliable stock
Customer replies, replenishment and network reports all depend on accurate stock, so the roadmap starts with that foundation when it's missing.
See the industry
Making the firm's knowledge work
Searching past files and preparing proposals draw on the same documents, and the roadmap orders them so the first use case serves the second.
See the industry
FAQ
Frequently asked questions
What is an AI strategy, and why define one before deploying?
An AI strategy sets the use cases your company commits to, their order and the resources they need, before any spending on delivery. It therefore avoids launching pilots that lead nowhere, for lack of data, an owner or a link to a leadership objective. It ends with a roadmap, with an owner for each use case you keep.
How is this different from your AI Transformation engagement?
The strategy is its first part. It covers the assessment of use cases, the leadership's decisions and the roadmap, while AI Transformation also covers what follows, from the pilot to integration into your tools and adoption by your teams. You therefore decide on the next step once the roadmap is in hand.
How do you choose between OpenAI, Google, AWS or an open-source option?
No platform wins on every front, because each makes different trade-offs between answer quality, usage charges, data hosting and support. So we compare the options on your own criteria and your own documents, then check each provider's terms, retention and training included, before recommending one. The choice can also differ from one use case to another.
Where does Law 09-08 fit in the roadmap?
For each use case you keep, the roadmap describes the personal data involved, how it moves and who can access it. The declaration or authorisation request to the CNDP falls to the data controller, which is your company, and this description helps you prepare it. Our AI Security & Governance page sets out our approach.
How much does AI strategy consulting cost in Morocco?
The investment depends on the number of departments and processes reviewed, the interviews and workshops to run, and the deliverables expected, such as the roadmap or the brief for a first pilot. So we set the amount after a first conversation about the scope you want to cover.
Let's discuss your priorities
Let's prepare your leadership's roadmap.
Tell us your leadership's objectives for the year and the teams involved. We'll explain how we would compare the use cases, and what the work would let you decide.
- The call lasts thirty minutes, by video.
- You speak directly with a Claro expert.
- Afterwards, we email you the next step we recommend.