The method
The Workshop takes your team through the first four stages in half a day. The Build Day is the fifth. The 90-Day Plan is the sixth. Every stage works on your own tasks, with the people who do the work and the people who decide in the same room.
Workshop
Builds a shared, plain-English understanding of what AI is good at, where it is weak, and how it becomes a thinking partner beyond routine work. Short practical exercises, no survey tasks yet.
A common language, and the myths cleared out of the room.
Workshop
In pairs, each person writes a brief for an assistant for their own daily work, builds it on your agreed platform, tests it on a real task from this week, checks the result and improves the brief.
A foundational assistant for every delegate, and a daily practice for using, checking and improving it.
Workshop
In small mixed groups, takes the use cases from the pre-Workshop survey and the room and designs them: the goal, the work, the human checks. Decides what can be done today, what needs a Build Day and what stays with people.
Designed use cases with a verdict on each.
Workshop
Sorts every case with AIKE™, names an owner and a partner for each, agrees standards and logs the decisions. Agrees the daily practice and whether to book a Build Day.
A ranked shortlist with named owners, a shared log and agreed next steps.
Build Day
Builds and tests the selected cases on your own systems, working back from the outcome you want. Reviews what worked, agrees the human checks, decides what is ready for daily use.
Tested prototypes, evidence of what worked, and a decision on each.
90-Day Plan
Carries the way of working into everyday work through Activate, Embed and Sustain, with named owners, agreed standards and reviews at 30, 60 and 90 days.
Consistent working practices your team owns, and measured change.
Most teams stop after the Workshop and keep using what they built. The Build Day and the Plan are there when the shortlist deserves them.
A useful way to think about the work
Necessary, repetitive, rule-bound work can happen without a person doing it by hand.
AI helps people make a better version of work that matters.
Human judgement, relationship or craft is the point. Keep the work with people.
Work with no useful reader or outcome can stop.
Look for opportunities to improve thinking and decisions alongside automation. Simplifying or removing a task can be valuable too.
Try the thinking →Demystify to Deploy™ is a six-stage method for UK leaders and their teams: Demystify, Explore, Design, Organise, Build, Deploy. It was created by Nathan Jones, founder of Elansio, and is a UK registered trademark, UK00004319368.
Your company's own work, tasks and workflows shape the preparation and practical exercises from the outset. A pre-Workshop survey brings your team's cases into the room. The six stages sit across the Workshop, Build Day and 90-Day Plan; they are not six separate sessions.
Demystify builds shared understanding of what AI is, what it does, and where it fits the work your team already does.
Most teams arrive split. Some people use AI every day at home and have quietly stopped mentioning it at work. Others have tried it once, found it underwhelming, and moved on. A few are waiting for permission. That spread is the real starting problem, because a team that disagrees about what AI is cannot agree on where to use it.
This stage replaces mystique with fact, in plain language, with no jargon and no vendor pitch. By the end everyone in the room is working from the same picture.
The opening explanation is general: no delegate names or survey tasks appear in Demystify. We distinguish augmentation from automation and agents, and ask: if this output is wrong, when will we find out and who will notice first?
Write a brief for your own personal assistant before opening the platform. Build it in pairs on your agreed platform, test it on a real task from your working week, check the output and improve the brief.
The brief describes your role, working week, regular outputs, preferred format and tone, what the assistant must and must not do, and what information it may receive. Your partner reads it back and challenges what is missing.
Learn configuration, functions and safe-use rules through the build, not a platform demonstration beforehand. Connectors are explained and subject to your organisation's approval route, not switched on in the Workshop.
Every delegate leaves with a foundational assistant, not a finished business system, and a daily practice for using, checking and improving it. Explore comes before Design so you can use your assistant to sharpen the cases that follow.
Use your assistant with colleagues to describe and design company use cases from the pre-Workshop survey or raised in the room. These are designed cases, not finished systems.
Start with a clear goal. Use Starter or Builder cards according to each case's current status. Write first, then ask colleagues from other functions to identify missing steps, information and handovers.
Your personal assistant stays open to help draft, challenge and sharpen the case. Identify where AI could augment people, where automation is suitable, what stays human and how you would find out if the output were wrong.
Apply an AIKE™ lens to each case, name an owner and partner, and log the case, status, data and human checks. Sort cases into ready to build, needs a decision first or bigger than a day.
The four lenses are Automate, Innovate, Keep and Eliminate. Keeping work human is a deliberate choice. Record when and how an error would be noticed, and agree who takes the next step.
The shared log and three-column wall become the Build Day's input list, starting with cases ready to build. Ask the sponsor who owns the calendar and discuss a Build Day date. Delegates continue daily practice with their personal assistants.
At the Build Day, people with different roles work back from the outcome, then build and test selected cases on the company's own systems. Present results, limitations, human checks and next steps with names and dates. No same-day deployment promise.
The six-hour, on-site day starts with solving and deciding together: inputs, outputs, fixed steps, judgement, review and permitted information. In the afternoon, the owner drives the build, runs it, improves it and runs it again.
Teams of three or four present what they built, what it got wrong, what stays human and what happens next. Not everything will be finished. Agree readiness, approvals and pilot dates rather than treating a Workshop build as a production deployment.
For teams that want continued support, the 90-Day Plan is the Deploy stage.
Through the 90-Day Plan, establish documented, agreed ways of working, named owners and written standards. Activate, Embed and Sustain are the three months, with check-ins at 30, 60 and 90 days.
Carry forward the owners and partners named in Organise and the cases developed at the Build Day. Everyone who touches a workflow should follow its agreed standard. EMIL™ Integrating is the operational measure; Leading opens a discussion about continued support.
The aim is stronger capability and useful working habits that your team can maintain. The Plan is offered only at the Build Day, with monthly pricing agreed around your team's workflows and priorities.
The Workshop covers Demystify, Explore, Design and Organise. The Build Day covers Build. The 90-Day Plan covers Deploy. Your company's own tasks and workflows connect all three products.
The Demystify Workshop is £980+VAT for up to 20 people and covers the first four stages at thinking depth. Teams leave with a shared understanding, a prioritised shortlist of opportunities, hands-on experience of their own work, and a clear read on what deserves to continue.
The Build Day is £1,395+VAT for a six-hour on-site build day available only after the Workshop. It develops and tests the designed cases on your own systems.
The Demystify to Deploy™ 90-Day Plan is offered only at the Build Day, with monthly pricing shaped around your team's real workflows and priorities, and is offered only at the Build Day. It delivers the Deploy stage through adoption support over 90 days.
The Workshop is the required starting point for Build Day, and the Workshop and the Build Day together lead into the Plan.
AIKE™ is a framework for deciding what should change in a workflow and what should stay as it is. It has four lenses, applied in this order:
Most teams reach for Automate first and stop there. That produces a faster version of the same business. Innovate is where the interesting gains sit, because it asks what becomes possible rather than what becomes quicker.
Keep and Eliminate take more organisational confidence to use well. Deciding that something should not change, or should not exist, requires a maturity that early-stage teams rarely have yet. That is what the EMIL model describes.
EMIL describes how far an organisation has moved with AI, across four levels. It sets expectations for what is realistic to attempt next.
EMIL matters because it governs how deeply the AIKE™ lenses can be applied. Automate and Innovate are available to an organisation at Exploring or Mobilising. Keep and Eliminate come into full use at Integrating and Leading, when a business has enough evidence to defend a decision to leave something alone or shut it down.
Demystify to Deploy is a six-stage method for UK leaders and their teams, created by Nathan Jones of Elansio. The six stages are Demystify, Explore, Design, Organise, Build and Deploy. It is a UK registered trademark, UK00004319368, registered on 3 April 2026.
Explore gives every delegate a foundational personal assistant built from a written brief about their own work. They then use that assistant in Design to draft, challenge and sharpen company use cases with colleagues. The brief comes before the platform; the assistant comes before the case design.
These are six stages, not six separate sessions. The Workshop covers Demystify, Explore, Design and Organise. The six-hour Build Day covers Build on your company's own systems. The 90-Day Plan covers Deploy, with written working standards and check-ins at 30, 60 and 90 days. A business can stop after the Workshop and keep using what it has built.
No. Demystify to Deploy is built for business teams rather than developers. It works with the tools you already have, including ChatGPT, Microsoft Copilot, Claude and Google Gemini, and it starts from your workflows rather than from the technology.
AIKE™ is a four-lens framework for evaluating work against AI: Automate, Innovate, Keep and Eliminate. It is used during Design and Organise to decide which tasks should change, which should stay as they are, and which should stop.
EMIL describes an organisation's AI maturity across four levels: Exploring, Mobilising, Integrating and Leading. It sets how deeply the AIKE™ lenses can be applied, because deciding to keep or eliminate work requires more organisational evidence than deciding to automate it.
Yes. The Workshop is a complete piece of work in its own right, priced at £980+VAT for up to 20 people, and many teams take real value from it alone. The Workshop is the required starting point for Build Day, and the Workshop and the Build Day together lead into the Plan.
Demystify Workshop is £980+VAT for up to 20 people. The Build Day is £1,395+VAT for a six-hour on-site build day, available only after the Workshop. Demystify Workshop + The Build Day is £2,195+VAT, saving £180. Demystify to Deploy™ 90-Day Plan, offered only at the Build Day with monthly pricing shaped around your team's real workflows and priorities.
Tell me where your team is with AI and what you would like to be different. Twenty minutes, no sales script, and a straight answer about whether this method fits your business.
Book a 20-min callLast reviewed: 3 August 2026.
