EME·Strategy
AThe transformation program

Your teams use AI on their real problems.
And it sticks.

A structured program built on your actual processes. No slides. No retainers. Tools and skills your teams keep.

ForSMEs and mid-sized companies
Format12-week blocks · ~half-time
OutputPoint-people activation, POC portfolio, adoption measurement, IT-ready use case briefs
The method

Identify the friction. Shape the use case.
Make adoption measurable.

Every engagement follows the same three movements: map where work actually gets stuck, qualify which AI response will land with the team, then build and activate with adoption tracked from day one.

1

Map the work

Read the business process directly with the team. Surface friction points, frequency and data available. Determine whether the use case is ready to build or needs further qualification.

2 to 3 days preparation
2

Qualify and build

Work with the point person on their actual tasks. Score the use case against business impact, data readiness and adoption risk. Build the first functional proof with the team, in one session.

1 to 2 workshops
3

Measure adoption

Use case documented and prioritized. POC handed over or briefed to IT. Adoption baseline set. Active use cases enter a measured production track with point-people usage as the signal.

5 working days
4 concrete cases

Where this has worked,
function by function.

Sales A technical expert prepares every client presentation from scratch. → An outline built in one session. Reusable across the team.
Client projects Every new client project starts with a blank page. The handoff between the team that sells and the team that delivers is the highest-friction point. → A structured kickoff brief in minutes: what is confirmed, what is still open, what was promised and what is out of scope.
Customer follow-up A portfolio of customer accounts with no segmentation, no health indicator, no dedicated person. → A first A/B/C segmentation from a raw CRM export. Operational before the first hire.
Between teams The sales team signs. The project team takes over. Neither alone owns the gap between them. → A joint session. Both point people design the handoff together. The friction that lived between two departments gets an owner and a tool.
Impact metrics
AI adoption How fast does the team take ownership?
Point people autonomous within 30 days≥1 use case per point person
Active use cases at week 8≥5 per function
IT briefs handed overSprint-ready spec
Measured impact What do we measure, before and after?
Time spent on the targeted taskMeasured before and after
Turnaround time (quote, customer reply)Baseline first, then tracked
Actual use of each use caseTracked by team
Program discipline Is the program self-sustaining?
Weekly adoption checkSelf-reported by the point person
Use case scoring completedSession 1
IT handoff brief in backlogBy week 6
Indicative targets · vary by engagement
Client case · B2B software company

From scattered AI experiments to a structured program, across eight departments.

Client case B2B software company
B2B software company Internal AI transformation Adoption led by point people Prototypes
Challenge

AI opportunities existed in every department, but initiatives were scattered, unevenly framed and difficult to prioritize.

Engagement

An internal program: point people in every department, use cases qualified and published in a shared knowledge base, working prototypes, and adoption tracking presented to management.

Impact

More than 60 use cases published across eight departments, each documented so teams can pick it up. Adoption is tracked through the point people and team feedback.

Example prototype shown at a B2B software company: preparing the follow-up of a customer account.
60+Use cases published
8Departments
12Point people appointed
NextCommercial intelligence
Active engagement · impact measurement in progress

What comes next. After adoption, a commercial intelligence engagement is in preparation with this client: reconciling internal data and enriching it with external data, to prospect better and see a customer's departure coming. No results yet.

Also: The operational fix →

Start

Bring one real problem.

We work through it in thirty minutes.

Bring one real problem. We work through it in thirty minutes. → Or just say hello