Prove it on your own process before you fund the build.
A Proof of Value builds one priority process on your real systems and data in three to four weeks, and measures it against success criteria your finance team signs before anything is built. It ends with a go, go-with-conditions or no-go decision, an Evidence File, and a production plan you can price. No criteria, no build.
When a proof of value is the right step
A priority process, not yet proven
A workshop, a discovery or your own analysis has picked the process. You need to see it work on your systems before funding production.
Pilots that never reached production
Previous proofs of concept were demos. You want one judged against numbers agreed in advance.
A CFO who wants the measure first
Finance will only back the build if the success criteria were set before the result was known.
A voice or agentic step to test
You want to see an AI agent or a voice agent handle real cases, with the controls in place, before customers meet it.
What you would be buying
One priority process built on your systems in three to four weeks, judged against success criteria finance signs before the build, ending in a go, go-with-conditions or no-go decision.
What you receive
- V1 Success criteria, signed before the build and not moved afterwards
- V2 Working build on your systems and data
- V3 Results workbook against each criterion
- V4 Evidence File: what the automation did, under whose permission, and where a person decided
- V5 Go or no-go record with the reasons
- V6 Production plan with a fixed-price pilot build, if the answer is go
What you provide
- A priority process, usually from a workshop, a discovery or an opportunity charter
- A process owner and a finance signatory for the criteria
- Integration access issued through your own secure process
- Representative real cases to run
How success is measured
- The criteria agreed in V1, and nothing chosen afterwards
- Exception rate and how many cases needed a person
- Cycle time and cost per completed case against the baseline
A proof of value measures a short run on real cases. The saving is confirmed in production, at 30 days, 90 days and month nine of the pilot.
What can hold it up
- Integration credentials arriving in the first week
- Criteria signed before the build starts: no criteria, no build
After it goes live
Whatever the decision, the Evidence File and results workbook are yours. A go moves into a fixed-price pilot build on the same platform.
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
V1 Success criteria
The measures, the baseline and the pass marks, signed by finance before the build starts and not moved afterwards.
V2 Working build
The process running on your systems and data, with the exception paths and human review designed in from the start.
V3 Results workbook
What the build achieved against each criterion, including what did not work.
V4 Evidence File
A record of what the automation did, under whose permission, and where a person made the call. Yours to keep whatever you decide.
V5 Go or no-go record
The decision, the reasons for it and any conditions, written down so the next step is not argued about later.
V6 Production plan
If the answer is go: the scope, timeline and fixed-price pilot build to take the process live.
Where a proof of value usually starts
Email and document intake
Orders, instructions or claims arriving by email and PDF, read and keyed into the system of record, with anything ambiguous sent to a person.
Why this matters
Most proofs of concept are designed to succeed. The measure is chosen afterwards, the data is cleaned by hand, and the result does not survive contact with production.
A proof of value works the other way round. The criteria are set and signed first, the build runs on your real systems, and a no-go is a valid answer that costs you weeks rather than a program.
If the criteria are not signed, the build does not start. If the result misses them, we say so.
Standard or extended
Most proofs of value run in three weeks with one system integration. Where the process needs a second integration, or an agentic step that interprets information and chooses what happens next, the extended version runs for four weeks.
Either way the shape is the same: criteria first, build second, decision at the end. A proof of value that cannot fail is a demonstration, and a demonstration does not tell your CFO anything.
One integration. Three weeks. For a process with stable inputs and a clear measure.
A second integration or an agentic step. Four weeks. For processes where the next step depends on judgment.
Built on the platform you would keep
ETT Group of Companies Inc. is a UiPath Authorized Partner and a UiPath Services Certified Partner, and resells UiPath licenses. Our delivery team holds UiPath technical certifications.
Automation proofs of value are built on UiPath, so a go means the work moves into production without re-platforming. Voice proofs of value are built on PolyAI, which ETT designs and delivers voice agents on.
The relationship behind each technology (formal partnership, authorised resale, or a platform we deploy) is stated on its technology ecosystem entry.
How a proof of value runs
Agree the criteria
Measures, baseline and pass marks set with your process owner and signed by finance.
Build
The process built on your systems with real data, exception paths and human review included.
Run and measure
Real cases through the build, measured against the criteria, with the evidence recorded as it runs.
Decide
Go, go with conditions, or no-go, recorded with the reasons.
Plan production
If it is a go, a production plan and a fixed-price pilot build, tested against a nine-month return.
Often delivered alongside
Timing, cost, access and ownership
How long does it take?
Three weeks for one integration. Four weeks where a second integration or an agentic step is needed.
How is it priced?
As a fixed fee, agreed in writing before work starts and sized to the version you need. We do not publish a price, because the right scope depends on the process and the criteria.
What access do you need?
Integration access through your own secure process, representative real cases, a process owner, and a finance signatory for the success criteria.
What do we keep?
The criteria, the results workbook, the Evidence File and the decision record, whatever the answer.
What happens next?
Go, go with conditions, or no-go. A go comes with a production plan and a fixed-price pilot build, measured at 30 days, 90 days and month nine.
About this service
What is a proof of value?
A short, fixed-scope build of one priority process on your own systems, judged against success criteria agreed and signed before the build starts, ending in a go, go-with-conditions or no-go decision.
How is a proof of value different from a proof of concept?
A proof of concept shows something can work. A proof of value shows whether it pays back on your process, against measures your finance team set in advance.
How long does it take?
Three weeks for one integration. Four weeks where a second integration or an agentic step is needed.
What happens if it fails?
You get a no-go record with the reasons, the results workbook and the Evidence File. That is a result: it stops you funding a build that would not have paid back.
Which process would you put to the test first?
Tell us the process and how you would measure it. We will tell you whether it is ready for a proof of value, and what the criteria should be.
Around four minutes. Indicative guidance based on your answers.