Strategy
Level 5/5
Opportunity map
Aspida · 8 ideas from 6 workshops
ValueHours saved × how often it happens
FeasibilityData ready, low risk, low effort
New idea
Opportunity map8 ideas
Pilot now
Quick wins
Park
Plan
Feasibility →
Value →
We help teams find the AI use cases worth funding, prove them quickly and roll them out safely across the business.
Most companies have tried AI; fewer can point to what it changed. In McKinsey's 2025 State of AI survey, 88% of respondents said their organisation used AI regularly in at least one business function, but only 39% reported any effect on EBIT at the enterprise level. We close that gap: find the work where AI pays, prove it on real tasks, measure it honestly, and roll it out with the rules and training that make it stick.
Our guide From AI pilots to real gains covers the approach in detail.
Use cases assessed
20+
Time to first prototype
2wks
We start where the time goes. Workshops with each team collect the tasks that repeat, the documents people re-key and the questions they answer again and again. Each idea is scored for value, the hours saved multiplied by how often it happens, and for feasibility: whether the data is ready, how costly a mistake would be and how much effort it takes. The top-right corner becomes the first pilots.
Claims intake · minutes per claim
Illustrative
Before25 min
Read the email and attachmentsRe-key into the claims systemCheck the policyRoute to a handlerAcknowledge the customerAfter6 min
1234−19 min per claim
Before · 25 min
Read the email and attachments6 min
Re-key into the claims system8 min
Check the policy5 min
Route to a handler3 min
Acknowledge the customer3 min
After · 6 min
AI reads and extracts, a handler checks2 min
Policy check suggested1 min
Handler confirms and routes2 min
Acknowledgement drafted1 min
−19 min per claim
AI pays when the workflow changes around it, not when a chatbot is added to the old one. In the claims example, AI reads the email and attachments and fills in the claim, a handler checks it, and the acknowledgement is drafted: 25 minutes becomes 6, with a person still deciding.
Kostas Georgiou
Claim: water damage, 14 Imitou Street, Athens
A pipe burst upstairs last night and water came through the kitchen ceiling. Photos attached. Policy AS-204-7731.
3 photosPolicy.pdf
Extracted · check before confirming
PolicyAS-204-7731
IncidentWater damage
Date30 Sep 2026
DamageKitchen ceiling, floor
UrgencyStandard
ConfirmConfirm6-week pilot · Illustrative data
Active handlers
61 of 64
Minutes saved per claim
19
Accepted without changes
95%
A pilot is a working prototype in real hands, on real work, measured against a baseline taken before it starts. Each week we track how many people use it, how much time it saves and how often its output is accepted without changes.
People's sense of speed can mislead. In METR's 2025 study, experienced developers expected AI tools to make them 24% faster and turned out 19% slower, while still believing they had sped up. So we measure the work itself.
Test set200 real claim emails
Water damage, photos attachedPass
Motor claim, policy number missing: asks for itPass
Injury mentioned: flagged urgentPass
Complaint mixed with a claimFail · fixed in the next prompt version
Illustrative data
Model A · 94.5% · €0.012 per claim · 2.1 s
Before anything scales, it runs a test set of real cases with known answers. Each model and prompt is scored for accuracy, critical errors, cost and speed, and only the options that clear the gate go forward. The cheapest model is often good enough; sometimes it isn't, and the test set shows which.
Data classes
PublicWebsite, brochuresAny approved tool
InternalProcedures, templatesEnterprise tools only
ConfidentialCustomer and claims dataApproved tools with a data agreement, no training on your data
RestrictedHealth and payment detailsNo AI use without DPO sign-off
Approved tools
Workspace assistantUp to Internal
Claims copilotUp to Confidential
Meeting transcriptionUp to Internal
Public chatbotsUp to Public
New request · Contract summariser · Commercial lines
Clear rules help people use AI openly instead of quietly. We write a short usage policy, classify your data from public to restricted, match each class to approved tools, and set up a simple way to request new tools and record every use in an AI register.
In the EU, the AI Act has required organisations using AI to support their staff's AI literacy since 2 February 2025. For a recognised structure, ISO/IEC 42001 sets out an AI management system and the NIST AI Risk Management Framework maps the risks.
Training plan
W1W2W3W4W5W6W7W8
Weekly active users · 12 weeks · Illustrative data
18 champions · 1 per 22 staff · office hours weekly
Adoption is a people project. We train leaders first, then a network of champions who help their colleagues, then each team with examples from its own work, and track weekly active use team by team. The teams whose work changed most use it most.
Map, prove, measure, roll out: a first pilot in real use in about six weeks, then team by team.
Score candidate use cases by value, feasibility and risk.
Build two or three working prototypes against real data.
Evaluate quality and cost before anyone scales anything.
Policy, training and integration into daily tools.
An AI opportunity map, working prototypes, an evaluation harness, a usage policy and data classification, a rollout plan and training for every team. You keep the prompts, the code and the test sets.
Enterprise AI assistants for everyday work, models from several providers for custom tools, retrieval over your documents, evaluation and monitoring tooling, and your existing identity and data-protection controls.
Strategy
Level 5/5
Engineering
Level 5/5
Quality
Level 4/5
Risk
Level 4/5
People
Level 3/5
Answers to the questions we hear most often about AI programmes.
No. Most engagements start with teams that have tried a chatbot and little else. We begin with the work, not the technology: where the time goes, what repeats and what good looks like.
We classify your data first and match each class to the tools allowed to handle it: business terms that keep your data out of model training, EU hosting where you need it, and nothing confidential in consumer tools.
Every pilot has a baseline and a target agreed before we build, such as minutes per task, error rate or response time. We measure the work itself, because people's sense of speed can be wrong: in METR's 2025 study, experienced developers expected AI tools to make them 24% faster and were 19% slower.
Rarely because of the model. A 2025 MIT report found that most generative AI pilots it looked at had no measurable effect on profit and loss, while the few that worked were tied to a specific workflow and built into how people work. That's the approach we take.
Whichever scores best on your test set at an acceptable cost and speed. We try several on the same cases, and the choice can change as models improve.
In the EU, the AI Act has required organisations using AI to support their staff's AI literacy since 2 February 2025; 2026 amendments softened the wording from ensuring it to supporting it. Beyond the law, training is what turns a tool into a habit.
A short usage policy, a data classification, a list of approved tools, a simple way to request new ones and a register of AI uses. ISO/IEC 42001 and the NIST AI Risk Management Framework give it a recognised structure when you need one.
About six weeks to a first pilot in real use: two weeks of discovery and scoring, two to three weeks to build and a week to measure. The rollout then goes team by team.
In the pilots we run, it takes over the repetitive parts of a job, such as re-keying and first drafts, and leaves the judgement with people. A large study of customer-support agents found the biggest gains among newer staff.
All names, companies, people and figures in the examples and illustrations on this page are fictional and shown for demonstration only. They do not correspond to real clients, customers or results.