EME·Strategy
AThe transformation program

Your teams use AI on their real problems.
I make sure it sticks.

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

ForMid-market & scale-up teams
Format12-week blocks · ~half-time
OutputChampion 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 champion 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 champion usage as the signal.

5 working days
4 concrete cases

Where this has worked,
function by function.

Presales A senior SE at a 200-person B2B software company spends 4 hours building a custom demo per account. → Demo storyboard built in one session. Reusable across the team.
Prof. Services Every new engagement starts with a blank page. The Presales-to-PS handoff is the highest-friction point. → Structured onboarding brief in minutes: confirmed architecture, open assumptions, what was committed vs. out-of-scope.
Customer Success 280 active accounts. No segmentation, no health score, no CS resource. → First-pass A/B/C segmentation from a raw CRM export. Operational before the first hire.
Between teams Presales closes. PS takes over. Neither team alone owns the gap between them. → Joint session. Both champions co-design the handoff. The friction that lived between two departments gets an owner and a tool.
Impact metrics
AI adoption How fast does the team take ownership?
Champions autonomous within 30 days≥1 use case per champion
Active use cases at week 8≥5 per function
IT briefs handed overSprint-ready spec
Commercial impact What changes in the revenue process?
Demo prep time4h → 30min
Proposal turnaround3 days → same day
QBR preparationManual → 1 hour
Program discipline Is the program self-sustaining?
Weekly adoption checkChampion self-reported
Use case scoring completedSession 1
IT handoff brief in backlogBy week 6
Indicative targets · vary by engagement
Customer story · B2B software

"From scattered AI experiments to a structured transformation program."

Customer story B2B software
B2B software Internal AI transformation Champion-led adoption POC portfolio
Challenge

AI opportunities existed across departments, but initiatives were fragmented, unevenly framed and difficult to prioritize.

Engagement

An internal transformation program combining champion activation, use case qualification, functional POCs, adoption measurement and executive-ready reporting.

Impact

A growing portfolio of prioritized AI use cases, with adoption tracked through champions, usage signals and business feedback.

Example POC shown: account planning process.
10-15POCs
MultiFunctions
ChampionsAdoption
LiveRoadmap
Active engagement · impact measurement in progress

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