Find the work worth automating. Before you fund it.
The Business Process Workshop is a fixed-price, fixed-scope engagement that maps how a function's processes run today, measures what they cost, and ranks where automation, AI agents or a simple fix would pay back. It runs for four to six weeks and ends with a prioritized roadmap and a decision, not a slide deck.
When the workshop is the right start
Ideas from every team, no priority order
Use cases are arriving from several departments and nobody can say which pays back first.
A board that wants AI, a CFO who wants numbers
You need a baseline and a business case before anyone signs off a build.
Pilots that stalled
You have tried automation or AI before and want the next attempt aimed at the right process.
A function under pressure
Finance, operations, onboarding or claims is carrying manual work and rework nobody has measured.
What you would be buying
A fixed-price workshop that maps how a function's processes run, sets the baseline and ranks what to automate, fix or leave alone, ending in a decision.
What you receive
- Process inventory and heat map across the function
- Current-state process maps for the priority processes
- Baseline and benefits workbook with low, expected and high cases, and every assumption written down
- Opportunity register, each candidate scored for value, feasibility, risk and governance
- Prioritized roadmap, reissued within two business days of the workshop
- Executive report and workshop pack within five business days
What you provide
- A sponsor who can make the call at the end
- Time with the people who run the processes, about an hour each
- Whatever metrics exist, however partial
- No system access and no licenses: the workshop works from interviews, observation and documents
How success is measured
- Leadership can choose between options on the evidence supplied
- Every finding traces back to an interview, a capture session or a document
- The first build can start without another discovery phase
A workshop establishes what a case is worth. It does not itself realize a saving, and we do not report one.
What can hold it up
- Process owners being available within the four or six week window
- A sponsor who sets the scoring weights at kick-off
- A named decision-maker who can accept or reject the roadmap
After it goes live
The workshop ends with the report and roadmap, which are yours to keep. Where ETT continues into a proof of value or build, the roadmap becomes the plan of record.
Deliverables and measures describe the standard shape of this engagement. Exact scope, duration and commercial terms are agreed and confirmed in writing before work starts.
How we do the work
Process inventory and heat map
Every process in the function long-listed and scored, so the priorities are visible on one page.
Current-state process maps
Swimlane maps for the priority processes, showing the handovers, rework and exceptions as they really happen.
Baseline and benefits workbook
Effort, volumes, error and rework rates and cost, with low, expected and high cases and every assumption written down.
Opportunity register
Each candidate scored for value, feasibility, risk and governance, using weights your sponsor sets at kick-off.
Prioritized roadmap
What to build first, what to fix first, and what to leave alone, reissued within two business days of the workshop.
Executive report and workshop pack
The findings and the recommendation in a form your leadership can decide on, within five business days.
Why this matters
Ask ten managers what to automate and you will get ten answers, most of them the work that annoys them most. That is a fine place to start and a poor place to invest.
The processes with the most rework, exceptions and hidden cost are often the ones nobody puts forward, because nobody sees them end to end.
The cost of guessing wrong has gone up. Gartner expects more than 40% of agentic AI projects to be cancelled by the end of 2027, mostly on cost, unclear value and weak risk controls (Gartner, June 2025). The workshop makes that call on evidence, before you spend on a build.
If the numbers do not stack up, we will tell you to stop, and you keep everything we produced.
Business Process WorkshopFour lenses on every process
Not everything should get an agent, so every process in the workshop is looked at four ways.
Rules-based automation, for stable, high-volume steps where a software robot is cheaper to build and run and easier to audit. AI and document intelligence, for steps that read emails, PDFs and forms that vary from one to the next. Agentic operations, for steps where the next action depends on judgment within limits you set. And fix first, or leave alone: a broken process should be fixed before anything automates it, and some work is not worth automating at all.
The workshop needs no system access and no licenses. If your processes run through systems that keep event logs, process mining gives you the same picture from the data, and on larger programs we run the two together, with the workshop as the decision point at the end of discovery.
Interviews, observation and documents. Fast, low cost, no system access. A first view of a whole function.
System event logs and desktop capture. Every variant and loop, at volume. Best where processes run through core systems.
Two editions, one fixed price each
Both editions are fixed price and fixed scope, agreed in writing before work starts, with half invoiced on signature and half on delivery.
One function, four weeks.
- 12 processes long-listed
- 3 processes mapped in detail
- 8 stakeholder interviews
- Half-day workshop
- Full deliverable set
Up to three functions, six weeks.
- 25 processes long-listed
- 6 processes mapped in detail
- 16 stakeholder interviews
- Full-day workshop
- Board presentation of the findings
How the four-week Focus workshop runs
Kick-off and long list
Week one. We agree the scope, the scoring weights and the people we need, and long-list the function's processes.
Interviews and capture
Weeks one to three. We sit with the people doing the work and record how it actually gets done, including the workarounds.
Baseline
Week three. Effort, volumes, error and rework rates, and cost per process, with every source tagged so it can be checked.
The workshop
Week four. Findings played back for challenge, priorities agreed, roadmap issued. The Enterprise edition adds a board presentation.
Decide
Build, fix, or stop. A proof of value on the first priority process typically runs three to four weeks.
Often delivered alongside
Timing, cost, access and ownership
How long does it take?
Four weeks for one function (Focus), six weeks for up to three (Enterprise). The pace is set mostly by how quickly we can get time with the people who run the processes.
How much does it cost?
It is a fixed price for each edition, agreed in writing before we start: half on signature and half on delivery. Travel and expenses are excluded.
What access do you need?
Time with process owners and whatever metrics exist. No system access and no licenses: the workshop works from interviews, observation and documents.
What do we keep?
Everything: maps, workbook, register, roadmap and report. They are yours whether or not you work with us afterwards.
What happens next?
Build, fix or stop. If you go ahead, a proof of value on the first priority process typically runs three to four weeks.
About this service
What is a business process workshop?
A structured engagement that maps how work runs today, measures what it costs and ranks the improvement and automation opportunities, ending in an agreed roadmap. Ours is fixed price and fixed scope, so you know the cost and the end date before it starts.
How is this different from process mining?
The workshop works from interviews, observation and documents. Process mining works from system event logs. The workshop is the faster, cheaper starting point; mining adds hard data where the processes run through systems. Many programs use both.
Do we need UiPath or any other license?
No. The workshop is tool agnostic and needs no licenses or system access. If the roadmap points to a platform, we say which one and why.
What if the answer is "don't automate"?
Then that is the answer, with the evidence behind it. A process that should be fixed or left alone is a valid finding, and it saves you a failed project.
Who from ETT runs it?
An engagement lead, a process analyst (two on Enterprise) and an automation and AI architect. You deal with the people doing the work.
Which function would you start with?
Tell us where the manual work and rework sit. We will scope a fixed-price workshop, or tell you straight if you do not need one.
Around four minutes. Indicative guidance based on your answers.