Build and test an AI MVP in weeks
Test the first build and plan the production decision.
Turn requirements into structured markdown, settle gaps with your experts and pair through the first build. At PPL, that produced a two-week greenfield working proof of concept, which did not enter production. Production work is a separate 90-day programme for one agreed workflow.
30 minutes with James · how this would work in your organisation
The basis for this approach
This is our approach to a bounded first build. The PPL example was one greenfield working proof of concept with one client engineer; it is not a repeatable two-week production promise.
The demand signal
PPL’s requirements were converted to structured markdown, gaps were resolved with subject-matter experts and the build began from a blank Azure repository. In two weeks the document-to-BI proof of concept worked. 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
The requirements change shape between handoffs
PDFs, diagrams and conversations can leave contradictions unresolved. Build one structured requirement corpus so the people specifying, building and accepting the work can test the same intent.
A short build is mistaken for a production release
A working first version still needs the evidence, controls, ownership and adoption work for production. Keep that decision and its budget separate from the prototype.
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
Settle the uncertain requirement first
Convert the requirements, map their relationships and run the gap-and-contradiction pass. Resolve those questions with your subject-matter experts before committing code to the approach.
- 02
Pair on one bounded workflow
Build against the whole requirement set with your own engineer involved throughout. At PPL the greenfield build included security review roughly every fifth prompt; that example was a proof of concept, not production.
- 03
Use the result to choose the next scope
The published proof of concept is two to four weeks at £20,000–£55,000 fixed. It leaves a go/no-go decision and a fixed quote for the separate 90-day programme, with completed design coming off the quote.
The published proof of concept is two to four weeks at £20,000–£55,000 fixed.
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.
PPL, 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.Tenhaw, Agentic Proof of ConceptTenhaw, 90-day outcome programmeThe 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.
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.
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.
Our approachWhat is a forward-deployed engineer?
Understand how forward-deployed engineers work in your repositories, pair with your engineers and hand over the capability. See the buying options.
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
How small should the MVP be?
Choose one workflow and the uncertainty you need to test. Agree the examples and acceptance decision with the team so a small build can settle something useful rather than merely demonstrate a feature.
What makes weeks realistic?
The PPL example combined a bounded greenfield scope, structured requirements, subject-matter experts resolving gaps and one client engineer pairing throughout. It was one working proof of concept in two weeks, not a general timeline promise.
What is not ready after an MVP?
Production reliability, assurance, operating ownership and adoption at scale still need evidence and a separate decision. PPL’s build did not enter production or change a regulatory or audit position. This is not legal advice.
Who owns the code?
Code is built in your repositories. Client-specific deliverables, documentation and code become yours on payment of the applicable fees, and your engineers pair so they learn the method during the build.
What does the first build cost?
Tenhaw’s Agentic Proof of Concept is £20,000–£55,000 fixed, excluding VAT, over two to four weeks. The 90-day programme is a separately agreed £120,000 or £180,000 fixed production scope.