Every ETT engagement is a step on one route: find where AI would pay back, decide what to build, prove it on your own process, take it live, and run it with evidence. Each step says how long it takes, what you leave with, and what it decides. Start at the step that matches what you already know.
You keep what each step produces, whatever you decide next. Nothing commits you to the following step.
Where would AI actually pay back in our operation?
A working session for your leadership team: a reality check, the scoring method, and a live map of your own operation.
Decision at the endIs there anything worth pursuing, and which route fits it?
Which AI investments will our operations own, and pay back inside nine months?
One working day, with pre-work, that turns ambition into opportunity charters owned by the executives accountable for the work.
Decision at the endWhich charters go forward, and who owns each one?
What is this process really costing us, and what should we automate, fix or leave alone?
A fixed-scope workshop that maps the processes, sets the baseline and ranks what to automate, fix or leave alone. No system access needed.
A sponsor, and about an hour each with the people who run the processes
Decision at the endBuild, fix, or stop.
How do our core processes really run, measured from the systems themselves?
The same decision as the workshop, made from system event data and desktop capture, on the UiPath platform the build will run on.
Read-only access to the systems in scope, plus process owners and nominated users
Decision at the endWhich processes to build first, on evidence.
Does it work on our process, against measures our finance team set first?
One priority process built on your systems and judged against success criteria signed before the build.
Decision at the endGo, go with conditions, or no-go.
Can we take it live and show a measured return?
The proven process built into production on UiPath, with robots, AI agents and people as one governed process, then a hypercare period.
Decision at the endScale it, or stop if a checkpoint misses. If it cannot pay back inside nine months, it should not be built.
Who runs it on a Monday morning, and can we show what it did?
Monitoring, break-fix, drift checks and change control for your robots and agents, with a monthly evidence report.
Decision at the endWhat to improve, extend or retire next.
No. Start at the route that matches what you already know. If you have a priority process and a baseline, start with a proof of value. If you have a long list of ideas and no order, start with a briefing or a Value Day. What we will not skip is the baseline, because without it nobody can say whether the work paid back.
Because a price read before the outcome is understood tends to end the conversation in the wrong place. Each route has its scope, duration, deliverables and fee agreed in writing before any work starts, and the scope is set by the outcome you want rather than a package. The briefing and the Value Day are offered at no charge.
Yes. Every route ends in a decision, and stopping is one of the options. You keep what that route produced: the map, the charters, the baseline, the Evidence File.
From the first conversation. AI Governance and Assurance and Analect run alongside the path rather than at the end of it, so the record exists before anyone asks for it.
The Value Day is designed around this timeline: the Value Day in month zero, a Business Process Workshop in months one and two, a proof of value in month three, build and go-live in months four to six, and returns measured in months seven to nine.
Tell us what you already know about the process and what the board expects. We will tell you where to start, and whether to start at all.