What an agentic proof of concept can prove in four weeks
Understand what a two-to-four-week agentic proof of concept can establish, what stays unproven and how to make a useful go/no-go decision.
In two to four weeks, a proof of concept can show that one workflow works on your real data, inside your tenancy, and whether your own engineers can run the method. It can’t show production reliability, regulatory sign-off or adoption at scale. At PPL, a two-week greenfield build produced a working proof of concept, which was not production.
30 minutes with James · how this would work in your organisation
The basis for this approach
This is our approach to scoping and reading proof-of-concept evidence. PPL is one greenfield example, with one paired client engineer, not a production reliability or repeatable-speed benchmark. This is not legal advice.
The demand signal
Tenhaw publishes the PPL build’s requirement method, seven-stage document pipeline and human-review routing. The same case states that nothing moved into production and no regulatory or audit position changed.
Bring the reason this is on your agenda to a 30-minute call with James, and we can explore what it would take in your organisation.
Book a 30-minute callWhy it stalls
2 failure modes we keep meeting
Success means a convincing demonstration
A useful proof answers the question agreed before the build. Without acceptance examples, failure cases and an owner for the decision, a demo can end without settling whether to proceed.
A prototype result is extended beyond its scope
A working test on real data is evidence about that workflow under those conditions. Production reliability, assurance and wider adoption still require their own work and decisions.
If one of these sounds familiar, bring it to a 30-minute call with James and we can explore a way past it.
Book a 30-minute callHow we approach it
3 moves, in order
- 01
Prepare the real requirements and examples
Turn existing documents into structured markdown, expose gaps and contradictions, and resolve them with the people who know the process before the build starts.
- 02
Pair and record the results
One or two Tenhaw engineers pair with your team in your tenancy. Test the agreed examples and record passes, failures and cases needing human review.
- 03
Make the next decision explicit
The £20,000–£55,000 fixed scope ends in a go/no-go decision and a fixed quote for the 90-day programme. Design already completed comes off that quote. Continuing is a separate choice.
Test the agreed examples and record passes, failures and cases needing human review.
Prefer to talk it through? Ask us on a discovery call →
Sources
Every source below was opened and read before it was attached. Where nothing survived that check, the claim on this page was softened rather than given a plausible-looking link.
Tenhaw, Agentic Proof of ConceptPPL, the two-week working proof of conceptOne greenfield build paired with one client engineer. Nothing moved into production and no regulatory or audit position changed.The closest guides to this one
Nearest first, then the rest. Each one carries the same label: written from delivery, or the method we would bring. All 34 are on the hub.
AI readiness assessment or proof of concept: which first?
Choose between a £44,000 AI readiness audit and a £20,000–£55,000 proof of concept by the decision you need to make next.
Our approachBuild and test an AI MVP in weeks
Test the first build and plan the production decision.
DeliveredDocument intelligence to business intelligence
Turn source documents into data your business can check and use.
DeliveredVoice agents and conversation intelligence
Choose recorded-call insight or a live agent, then design the right workflow.
Our approachRetrieval, RAG and permission-aware knowledge access
Answer from useful sources while keeping access tied to the person asking.
Our approachRAG, fine-tuning or prompting: how to choose
Choose the experiment that answers your knowledge, behaviour or cost question.
Or bring the problem to a call instead of reading three more of these.
Book a 30-minute callWork out the next step for your team.
A 30-minute call with James Rooney to discuss your workflow, people and budget. Leave with a rough scope and a useful next step.
Agentic Proof of Concept · £20k–£55k fixed · 2–4 weeks · excluding VAT
No time that suits? Email hello@tenhaw.com. Calendar not loading? Open it on cal.com.
Describe the work
Describe the work in a paragraph. James replies with a rough scope and budget range within two working days.
Questions this guide answers
What does a PoC not prove?
It does not establish production reliability, regulatory sign-off or adoption at scale. PPL’s two-week greenfield build was a working proof of concept; nothing moved into production and no regulatory or audit position changed. This is not legal advice.
What data do you need?
A chosen workflow, usable real examples and access agreed for the test in your tenancy. Include the awkward cases your team encounters, because they help expose where the approach needs review or further work.
What does go/no-go mean?
A decision based on the agreed tests: proceed, change the approach or stop. If the evidence supports production work, Tenhaw supplies a fixed quote for the 90-day programme, with completed design deducted from that quote.
How do you measure handover?
Have your engineers run the method during the build and check what they can repeat. At PPL the paired engineer reported 70% confidence after two weeks. That was one engineer’s self-reported confidence, not an independent capability or productivity measure.
What does it cost?
The published Agentic Proof of Concept is £20,000–£55,000 fixed, excluding VAT, over two to four weeks. One or two Tenhaw engineers pair-program with your people; production work is scoped separately.