Idun Group servicesAI support engagementDiscovery call · 30 minutes

Idun Group, AI support to get the most value from the AI already running at your site

30 to 50 % of AI initiatives fail to return what they should: abandoned projects, under-used licences, agents stuffed with data that burn tokens and hallucinate. A consultancy specialised in AI, Idun Group structures your AI support engagement around value: we analyse the real usage of your AI platforms with our log-analysis tooling, then we deliver strategic advice with a roadmap that says what to industrialise, what to consolidate and what to cut. Our references include LVMH, Airbus, L'Oréal and Randstad.

40+

AI diagnostics run in a year

41,200

users measured

218

qualified use cases

01
The finding
Gartner · McKinsey

Why 30 to 50 % of AI initiatives fail to return what they should

30-50 %

of AI initiatives fail to return what they should (Gartner: at least 30 % of proofs of concept abandoned).

The real brake is no longer adoption, it is the absence of measurement

AI is already everywhere in your company: Claude, ChatGPT, Gemini, Copilot, in-house agents. What is missing is visibility on real usage: nobody knows which use cases create value, which cost without serving, nor what the whole represents in consolidated cost. Without that measurement, industrialisation decisions rest on intuition and stall at the first hard trade-off.

20-40 %

of the AI licences paid for go unused, across the estates we analyse

Subscriptions taken out then dropped, redundant tools on the same use case, inherited zombie projects: waste is structural as soon as several AI tools coexist. This is a field finding: across the estates we analyse, 20 to 40 % of the AI licences paid for go unused. Analysing real usage makes it visible, quantified and open to arbitration at renewal time.

What a structured AI support engagement must deliver to escape that trap

A structured AI support engagement rests on 3 non-negotiable requirements. Without these 3 conditions, the technology changes nothing about how profitable your AI is.

Decisions taken on measured real usage, never on intuition

A roadmap prioritised by return on investment before any development

Results aggregated by team and by tool: we analyse usage, never people

The Idun Group AI support journey
01

Discovery call

30 minutes

Your AI context, the method, the likely scope: no access to your data before signature

02

Scoping

Mandatory interviews

IT department and business units: the tooling does not replace them, it makes them factual

03

Analysis

Logs and exports

From what you already produce, on the platforms you administer, installing nothing

04

Debrief

Roadmap

Recommendations to industrialise, consolidate or cut, ready for the steering committee

That is what the journey looks like at Idun Group. Everything starts with a 30-minute discovery call: here are the questions it covers.

Discovery call · 30 minutes

The questions the discovery call covers

  • Which AI platforms do you administer, over what scope and for which teams?
  • Where does the AI budget go: licences, consumption, features bundled into business software?
  • Which use cases should be industrialised, which consolidated, which cut?
  • What level of real adoption sits behind the licences you pay for?

No score, no automated verdict: these questions are handled in conversation, with your context. The call opens no access to your data, pre-sales is handled by people.

The next section sets out the three blocks of the engagement that answer those questions.

02
Formats
Analysis · Advice · Steering

The three blocks of an Idun Group engagement, from analysis to the decision

Each block answers a distinct objective: measure what your teams really do with AI, decide on figures what to industrialise, consolidate or cut, then follow the effect of those decisions over time. Consulting built on tooling rather than generic training, with three principles: an isolated network is possible; results are aggregated by team and by tool, never by person; and the logs you already have are read without installing anything on workstations.

01

Analysis of real AI usage: deciding on figures, not on intuition

We start from the logs and exports you already produce, on the platforms you administer (Azure OpenAI and in-house models, Dust, Copilot, custom agents), installing nothing and re-instrumenting nothing. Handing over exports or a read-only connection: the exact arrangement is settled in the scoping meeting. Interviews with the IT department and the business units are a mandatory step: our usage-analysis tooling does not replace them, it makes them factual. You come out with:

  • the map of your real AI usage, tool by tool
  • the use cases detected with their estimated return on investment and your teams' unmet demand
  • the waste identified (the list of what to abandon, the under-used licences) and the full cost of your AI, licences and consumption included

All of it is delivered in a report ready for your steering committee, with explicit recommendations: industrialise, consolidate or cut. We sell neither the agents, nor the agent platform, nor the training we recommend: the analysis serves your decision, not a catalogue.

02

Strategic advice and roadmap: arbitrating what deserves to be industrialised

Building on the analysis, we prioritise your use cases by return on investment, effort and adoption, we arbitrate licences at renewal time and we flag the same use case found across several tools, which deserves one single implementation. The engagement runs through to the decision in the steering committee, with a roadmap. To keep the deliverables current over time, the continuous insights option (recurring re-analysis, the same deliverables kept up to date) extends the engagement.

03

Execution by your teams: industrialising only what pays

Downstream of the advice, we tell you which use case to industrialise, which training to run and for whom; we do not do it for you. Execution stays with your teams, your integrators or a partner, and we can help you choose one. Idun Cockpit, the tool used for the analysis, can stay with you to measure the effect. The full approach is set out on our AI agency page.

How do these three blocks fit together in practice? The table below answers at a glance.

From the discovery call to the follow-up over time, each block has its format and its deliverable, with no grey area about what you receive. Nothing is committed until the analysis has proven the value.

Book a discovery call
03
Trade-off
Institutional schemes · AI Act

Institutional support or specialised support: what you have to weigh

Institutional schemes

A first institutional conversation: what it covers and what it does not

The first conversation offered by an institutional scheme helps narrow a still-vague need. It stops there, however: no measurement of your real AI usage, no recommendation grounded in your data. Funding-support schemes complement that first conversation, without the analysis tooling that lets you decide on figures.

The Idun Group gap

Recommendations grounded in your real usage: the gap with generic schemes

An institutional scheme delivers general guidance, valid for any company. At Idun Group we analyse the logs and exports of your AI platforms instead, and we deliver quantified recommendations (what to industrialise, consolidate or cut) with a roadmap. And if the analysis does not prove a return on investment, we tell you so in writing. Handing over exports or a read-only connection, results aggregated by team and by tool, never by person. And we sell neither the agents, nor the agent platform, nor the training we recommend.

Anticipating compliance: what the AI Act changes for your engagement

The regulatory question weighs more and more in the choice of an AI support engagement, including for companies that thought they were out of scope.

AI Act · EU Regulation 2024/1689High risk · deferred to 2 December 2027

The deadline for the obligations covering high-risk AI systems (annex III of EU Regulation 2024/1689: recruitment, credit, education) has been deferred from 2 August 2026 to 2 December 2027, following a European Commission proposal of 19 November 2025. The penalties remain unchanged: up to 35 million euros or 7 % of worldwide turnover. We anticipate that classification from the analysis of your AI usage onwards, as an extension of the engagement, never as its starting point.

04
Evidence
References

Idun Group in the field: our references

LVMH
Generative AI

perfume and cosmetics

An Idun engagement on the generative AI platform of all the perfume and cosmetics brands.

Inskip
85%

real activation

At this consulting and training firm, the analysis of real Claude usage established 33 users for 39 seats.

SNCF Immobilier
50

critical use cases uncovered

AI Flash Audit won through a public tender, run in its social-housing subsidiary. Engagement in progress.

Book a discovery call
05
Get started
Discovery · scoping · analysis · debrief

Starting your AI support engagement with Idun Group: 4 steps

01

Step 1: a 30-minute discovery call

The first contact with Idun Group is a 30-minute discovery call: your AI context, the method and the likely scope of the engagement. We ask for no access to your data before signature: pre-sales happens in conversation, with people.

02

Step 2: scoping, with mandatory interviews

We run scoping interviews with the IT department and the business units: a mandatory step, our tooling does not replace them, it makes them factual. The interviews give the intent and the context, the logs give the facts: it is the combination that makes the audit. The scoping meeting also settles how data is collected: handing over exports or a read-only connection.

Expert advice

Before the discovery call, list the AI platforms you administer (Azure OpenAI and in-house models, Dust, Copilot, custom agents). The more complete the inventory, the faster the scoping and the more the debrief reflects your real usage.

03

Step 3: the analysis, from the logs and exports you already have

We start from the logs and exports you already produce, on the platforms you administer (Azure OpenAI and in-house models, Dust, Copilot, custom agents), installing nothing and re-instrumenting nothing. We analyse usage: results are aggregated by team and by tool, never by person, and the exact status of the processing is validated with your data protection officer.

04

Step 4: the debrief and the roadmap

We present the analysis on your real data: a map of usage, use cases quantified, the waste identified and explicit recommendations (industrialise, consolidate or cut), with a roadmap. You decide, on figures.

06
FAQ
Frequently asked questions

Frequently asked questions about the Idun GroupAI support engagement

Q.01What does an AI support engagement with Idun Group cost?+
No pricing is published: every quote follows the analysis and is given in a meeting. What we sell is a fixed-scope engagement, analysis included, delivered within 15 days; its scope is framed by the discovery phase.
Q.02How long does an AI support engagement last, from first conversation to debrief?+
The discovery call lasts 30 minutes, and the engagement is delivered within 15 days. The pace, the format and the audiences for the debriefs are framed with you at the start.
Q.03What kind of company needs an AI support engagement?+
A company that has already deployed AI and does not know what it returns. We work first with companies of 500 to 5,000 employees, counting the headcount of the entity that buys, not of the group: a subsidiary or a business unit of a large group fits. That size marker excludes no one: what qualifies is usage, with at least 50 AI licences deployed, and a decision taken in France.
Q.04Do we have to re-instrument our AI tools before the analysis?+
No. We start from the logs and exports you already produce, on the platforms you administer, installing nothing and re-instrumenting nothing. Handing over exports or a read-only connection: the exact arrangement is settled in the scoping meeting. We analyse usage: results are aggregated by team and by tool, never by person; the exact status of the processing is validated with your data protection officer.
Q.05What is the AI Act and what obligations does it create for my company?+
EU Regulation 2024/1689 governs every AI system deployed in Europe. The transparency obligations (article 50) have applied since 2 August 2026; the deadline for high-risk systems (annex III) has been deferred to 2 December 2027, with penalties unchanged at up to 35 million euros or 7 % of worldwide turnover. We anticipate that classification from the analysis of your usage onwards, as an extension of the engagement, never as its starting point.
Q.06What is the difference with a first institutional conversation?+
A first institutional conversation delivers general guidance, with no measurement of your real AI usage. We deliver a quantified analysis of your usage and a roadmap; if the analysis does not prove a return on investment, we tell you so in writing.

A structured AI support engagement, from analysis to decision.

A 30-minute discovery call, scoping with your teams, analysis of the logs and exports you already produce, then a quantified debrief with a roadmap. You industrialise only what pays.

$ Discovery call · 30 min
$ Scoping · log analysis
→ Debrief + roadmap