Usage already in place
We record which assistants are used inside the company, often on personal accounts and without management knowing. That is generally the first surprise and the first risk to handle.
This work suits companies where the subject is on the table, where every board member has a different idea, and where nobody knows what to do first. We answer three questions: where the real gain sits, whether your data makes it possible, and in what order to move so the budget is not spent on scattered experiments. Along the way we list the GDPR and European AI regulation points that your lawyer or DPO needs to settle.
The deliverable exists to support a decision, not to be admired. It is a working document for a management team, with figures that can be argued over.
We record which assistants are used inside the company, often on personal accounts and without management knowing. That is generally the first surprise and the first risk to handle.
Which departments lose hours to monotonous work, and what that represents over a year, calculated from interviews and from data pulled out of your systems.
What is collected, where it sits and whether it can be used. Documents scattered across laptops, private mailboxes and an ageing file server are the most common obstacle.
Against each idea we flag what may fall under the AI Act or call for an impact assessment, and we prepare the list of questions for your legal adviser.
Confidential material leaking through instructions typed into an assistant, the legal basis for processing personal data, dependence on a single vendor outside the European Union.
The order of the projects, the people to involve, a budget per stage, and the precise moments where management decides whether to continue.
How long the review takes depends on the size of the company and the number of departments involved. Interviews and workshops run online, so nobody loses a whole day in a meeting room.
We ask department heads where their teams lose time and what they actually miss in daily work.
We look at what is really in the databases, rather than at what the written procedures say should be there.
Each candidate gets a score for gain, effort and risk, with a short justification that you are free to dispute.
We present the plan, collect objections and rework it until it can carry a genuine budget decision.
Without one named owner, the plan does not move an inch. Somebody has to carry it between departments, chase progress and report on it. Otherwise the document lands in a shared folder and reappears a year later, unchanged, during the next budget round. So we ask about that person at the first meeting, before any discussion about tools.
No, nothing is built at this stage. The result is an ordered list answering the question of where to start, with a budget beside each line. A company that already knows its use case, say sorting the orders that arrive by email, is better off going straight to a pilot instead of paying for analysis.
The heads of the departments concerned, whoever runs your IT, and a member of management who can decide. Having the DPO in one of the workshops helps. If the business side withdraws, what remains is a technical exercise with no connection to real work, and the plan will never be applied.
Schemes linked to France 2030 or supported through Bpifrance periodically cover business digitisation, and a written strategy sometimes helps put a file together. We are not a grant broker and we promise no outcome. The plan is built to stand on its own even if no outside funding arrives.
That conclusion has value: it saves you from funding a project with no return. We would rather write that it is too early, list the preparatory work that would change the picture, such as sorting out a product catalogue, and let you decide. An honest strategy also says what not to do this year.
The tool market moves quickly; your processes and your data move much more slowly. We suggest a short review twice a year: updated costs, new capabilities, regulatory changes. The priority list itself usually lasts longer than people expect, because it rests on how your company works rather than on the fashion of the moment.
Write what you expect from AI and what has already been tried in your company. We will look at the situation and give you a frank assessment.
Message received
An answer follows inside one working day. Report an outage that is stopping people working and it moves ahead of everything else.
Nothing here under that name. Check the spelling, or simply choose the nearest large city instead. Since every engagement runs remotely, whichever you pick changes nothing about what we do for you.