Tenhaw, or someone else.
- comparisons that name the situations where you should buy the other route
- 6 of 6
- build, buy, or build it with someone, weighed before you pick any supplier
- 3 routes
- our fixed-price audit, published, against an estimated £150k–£500k for a large-firm equivalent
- £44,000
- to be told on a call if another route fits you better
- 30 mins
The six comparisons, each argued in full
Read the one you are weighing.
Tenhaw vs Big Four
Same ambition. Very different delivery model.
Choose them for scale, indemnity cover and board comfort. Choose us for senior operators in your rooms and a contractual exit date.
Read itTenhaw vs AI boutiques
Most are strategy firms or build shops. We are neither.
Choose them for a narrowly scoped model build or a vertical specialism. Choose us when the pilots worked and then failed to scale.
Read itTenhaw vs Offshore partners
Cheaper per head, and that is the point of it.
Choose them when the requirement can be written down and cost per head is the constraint. Choose us for the months where nobody can write it down yet.
Read itTenhaw vs Contractors
Cheaper per day, and right whenever you already have someone to direct them.
Choose them whenever somebody already has the authority and the time to direct them. Choose us when that person is your sponsor and they already have a job.
Read itTenhaw vs Hiring in-house
You should hire. The question is what happens in the meantime.
You should hire, and recruiting your permanent team is written into our scope. The only question is what happens during the search.
Read itTenhaw vs Internal taskforce
The cheapest option, and the one that most often stalls at pilot.
Run it first, it is the right first move. Call us at the point where scaling needs authority the taskforce does not have.
Read itThe six routes, side by side
Find your row. Every line is taken from the comparison page it links to, including the situations where a route beats us.
| Route | Typical cost | Who does the work | When it wins | Board optics |
|---|---|---|---|---|
| Big Fourthe Big Four and global consultancies | £150k–£500k for an equivalent audit, our estimate rather than a published figure | A partner sells it, consultants two to eight years into their career deliver it | You need hundreds of people across countries, nine-figure indemnity cover, or the board expects the name | ImmediateNobody asks you to defend the name |
| AI boutiquesother boutique AI consultancies | Often cheaper than us for a narrowly scoped piece of work | A strategy bench or an engineering bench, rarely both in one squad | You need a specific model built, or deep vertical domain knowledge, and the operating model is not in question | Requires a caseAn unfamiliar small supplier, same as us |
| Offshore partnersoffshore and nearshore delivery partners | A quarter to just over half the same firm's published onshore rate, on its own G-Cloud 14 card | A large offshore bench working from a written specification, across a time-zone gap | The scope is specified and stable, you need overnight cover, or you need twenty engineers and to hold them for years | StraightforwardA cost saving is the easiest paper anyone writes |
| Contractorshiring contractors or freelancers directly | Roughly £610 to £870 a day after agency margin, our estimate rather than a published figure | Individuals you brief, sequence, review and re-brief yourself | The architecture is settled, you need specific skills, and you can absorb the direction load | NeutralResource spend rarely reaches a board |
| Hiring in-househiring an in-house AI leader | £180k–£350k plus equity, with 25 to 30% recruitment fees on top | One permanent hire, three to six months after they start, six to nine months after you open the role | You have a credible internal candidate, or your timeline tolerates a six-to-nine month search | NeutralApproving a headcount is routine |
| Internal taskforcerunning an internal AI taskforce | Effectively free: people already on your payroll | Part-time enthusiasts from one or two functions, with no mandate to change anyone's job | You are still exploring what agents can do, and have not yet hit the scaling wall | NeutralNo new money leaves the building |
| TenhawThis is us | £44,000 fixed audit, £20k–£55k for a proof of concept | A forward-deployed squad of three senior people, with no pyramid of juniors behind them | Pilots worked and then stalled, and scaling now needs roles, decision rights and governance to move | Requires a caseWe are not a name your board already trusts |
Big Four
- Typical cost
- £150k–£500k for an equivalent audit, our estimate rather than a published figure
- Who does the work
- A partner sells it, consultants two to eight years into their career deliver it
- When it wins
- You need hundreds of people across countries, nine-figure indemnity cover, or the board expects the name
- Board optics
- Immediate. Nobody asks you to defend the name.
AI boutiques
- Typical cost
- Often cheaper than us for a narrowly scoped piece of work
- Who does the work
- A strategy bench or an engineering bench, rarely both in one squad
- When it wins
- You need a specific model built, or deep vertical domain knowledge, and the operating model is not in question
- Board optics
- Requires a case. An unfamiliar small supplier, same as us.
Offshore partners
- Typical cost
- A quarter to just over half the same firm's published onshore rate, on its own G-Cloud 14 card
- Who does the work
- A large offshore bench working from a written specification, across a time-zone gap
- When it wins
- The scope is specified and stable, you need overnight cover, or you need twenty engineers and to hold them for years
- Board optics
- Straightforward. A cost saving is the easiest paper anyone writes.
Contractors
- Typical cost
- Roughly £610 to £870 a day after agency margin, our estimate rather than a published figure
- Who does the work
- Individuals you brief, sequence, review and re-brief yourself
- When it wins
- The architecture is settled, you need specific skills, and you can absorb the direction load
- Board optics
- Neutral. Resource spend rarely reaches a board.
Hiring in-house
- Typical cost
- £180k–£350k plus equity, with 25 to 30% recruitment fees on top
- Who does the work
- One permanent hire, three to six months after they start, six to nine months after you open the role
- When it wins
- You have a credible internal candidate, or your timeline tolerates a six-to-nine month search
- Board optics
- Neutral. Approving a headcount is routine.
Internal taskforce
- Typical cost
- Effectively free: people already on your payroll
- Who does the work
- Part-time enthusiasts from one or two functions, with no mandate to change anyone's job
- When it wins
- You are still exploring what agents can do, and have not yet hit the scaling wall
- Board optics
- Neutral. No new money leaves the building.
Tenhaw
- Typical cost
- £44,000 fixed audit, £20k–£55k for a proof of concept
- Who does the work
- A forward-deployed squad of three senior people, with no pyramid of juniors behind them
- When it wins
- Pilots worked and then stalled, and scaling now needs roles, decision rights and governance to move
- Board optics
- Requires a case. We are not a name your board already trusts.
The two lowest-commitment ways to start are Programme & Delivery Management at £18,000–£35,000 a month, buyable on its own with no requirement that Tenhaw builds anything and cancellable on 30 days' notice either way, or an Agentic Proof of Concept at £20,000–£55,000 fixed over two to four weeks.
Neither commits you to a build. How to put a small supplier to your board sets out the four facts a paper needs, in the form it needs them.
Every row above assumes you should be buying a supplier at all. Build it, buy it, or have someone build it with you is the question that comes first, and if the workflow is not differentiated the answer is none of these rows.
These are not mutually exclusive. Running alongside an incumbent large firm is a common arrangement, with the boundary written down, and the Big Four page answers that question directly.
Costs are as stated on each comparison page. Ours are published in full on the pricing page, alongside the large firms' own published framework rates.
A table cannot weigh six routes against your situation. A call can.
Talk it throughChoosing an AI consultancy
The two questions every buyer starts with when choosing an AI transformation partner, answered with the routing rather than a pitch.
What is the best AI consultancy in the UK?
It depends on what you are buying, and any answer that names one firm without asking is selling something. If you need hundreds of people, multi-domain regulatory depth or a brand your board already accepts, the best buy is a global firm, whose published G-Cloud 14 rates run £2,050 to £3,625 a day at the top grades. If you need senior operators building working software inside your own teams, the best buy is a senior-led boutique, and five tests separate a good one from a brochure: named accountability on every engagement, published prices you can do arithmetic on, evidence labelled as production or proof of concept, a contractual exit with the capability transferred to your permanent team, and a security page that answers your CISO's questions in static prose. Tenhaw publishes all five, including the day rates (£950 to £1,560) every engagement price derives from, and the comparison pages on this site say when a global firm, contractors, an internal taskforce or an offshore partner is the better buy.
How do you choose an AI consultancy in the UK?
Ask four questions before any pitch deck opens. First, who exactly turns up, whether senior people who do the delivery themselves, under a no-substitution term, or a partner who sells and a pyramid that delivers. Second, what has actually reached production. Ask every candidate to label each case study as production, pilot or proof of concept, and watch what happens. Third, how the engagement ends: a contractual exit date, your own engineers upskilled by pair-programming, and everything deployed in your estate so nothing needs migrating when the supplier leaves. Supplier lock-in is designed out at the start or built in by default. Fourth, what the price derives from. Published day rates you can multiply (ours are £950 to £1,560, and Big Four rate cards top out at £2,600 to £2,855, from G-Cloud 14 and not yet re-verified against G-Cloud 15) beat a number that appears at the end of a sales process. Then send your security team the candidate's assurance page before the first call: screening, insurance in figures, breach notification in hours, data residency, and the toolchain that checks AI-generated code. A supplier who publishes those answers has decided to be checked. A supplier who sends a deck has decided not to be.
What contract terms matter most when hiring an AI consultancy?
Read three clauses before you read the price. Ownership comes first, and with Tenhaw you own all code, documentation and work product from day one, not on final payment. Next, what a month has to produce. Engagements are retainer-shaped, every month carries a value target, and a month that delivers none is reported to you as a failed month. Then how it ends, with an exit date agreed at kickoff and 30 days' notice either way, in writing. Ask any supplier for each as drafted wording rather than an assurance, and where personal data is in scope, check the breach notification clock. Ours is 24 hours, as a term of the Data Processing Agreement.
How do you tell if an AI consultancy builds or only advises?
Ask what the first paid engagement ends in. A firm that builds prices work that finishes in running software, a firm that advises prices work that finishes in a document, and both are honest buys. Three checks separate them: does the fixed price include working code, does that code land in your own repositories, and can you read their engineering standard before signing. Tenhaw is the worked example. The £44,000 audit runs four weeks and ends in working prototypes, a proof of concept is £20,000 to £55,000 fixed over two to four weeks, and the 72-rule standard behind both is open source. If your own engineers will do the building, a firm that only advises is the cheaper buy.
Which AI consultancies work with UK enterprises over 10,000 staff?
Three shapes of supplier serve that size and they solve different problems. Tenhaw works with organisations from 500 to 100,000-plus people, as a forward-deployed squad of three senior people rather than a pyramid, and James Rooney co-led the design of HSBC Global Payment Solutions' target operating model for 500 teams and a $450 million budget. A global consultancy is the better buy when hundreds of people have to mobilise across countries in a quarter, or when the programme also spans tax, legal or regulatory remediation under one contract. An offshore partner is the better buy once the specification is settled and volume is the constraint. At your size the deciding number is how many functions the first workflow crosses, not headcount.
Who does agentic AI delivery for UK banks?
Four categories bid for that work: global consultancies, systems integrators, specialist AI product firms, and small forward-deployed firms like Tenhaw. Ours is the narrow buy, with the operating model, the engineering and the adoption in one squad of three. The banking record behind it is the founder's, earned inside HSBC in an executive delivery governance role across 150-plus global teams and a $102 million budget, and in the co-design of Global Payment Solutions' target operating model for 500 teams. In a regulated insurer, a two-week proof of concept is being productionised now. What settles the rest is whether your first workflow touches a customer outcome, because that pulls your second line into the design from week one.
Best AI transformation partner for a UK government department?
Two things decide a departmental shortlist, the delivery record inside government and which agreement you are buying through. Tenhaw was the portfolio manager for Tecknuovo, hands on as part of the contract, standing up a Portfolio Management Office from nothing and running it across 19 projects, including public-sector delivery for HMRC, the MOD and Thames Water. On the second, Digital Outcomes and Specialists 7 went live on 30 January 2026 and every call-off runs through a further competition, so the route to market shapes the team before the technology does. Ask every bidder what their first paid engagement ends in, and whose repositories the code lands in.
Which AI consultancy suits a UK retailer?
Two shapes fit, and they are different buys. A specialist AI or data firm is better for a narrowly scoped model, demand forecasting or personalisation, where the operating model is not in question. Tenhaw is the other shape, with the operating model, the engineering and the adoption in one squad, sequenced so something lands inside a trading cycle rather than after it. A proof of concept is £20,000 to £55,000 fixed over two to four weeks, and the retail clients behind us are Greggs, YOOX NET-A-PORTER and Colart, delivery transformation rather than agentic build. Either way peak trading freezes roughly a quarter of the delivery year, and head office and frontline adoption are two different programmes.
Who can run an agentic programme across three countries?
Tenhaw runs engagements across the UK, Europe and the United States, and past delivery covers the UK, Australia, the USA and Singapore. At Yondr we made global delivery predictable across the UK, US and Singapore, which was delivery discipline rather than agents. The honest limit is shape. We field two or three senior people from a London base with no local office, so multi-country work means a UK team travelling and one time zone anchoring the decisions. If each country needs its own people permanently, a global firm or an offshore delivery partner does that and we cannot. The question underneath is whether this is one workflow with local policy variations or three separate builds.
Who should a Lloyd's market insurer hire for agentic AI?
Tenhaw's current agentic engagement is with a London specialty insurance business, confidential at the client's request, where a two-week proof of concept turned PDFs into business intelligence on Azure over ground the business had circled for roughly a year. It is a proof of concept being productionised rather than a production system. A global firm is the better buy where the programme also spans regulatory remediation or a carve-out under one contract. Your own shortlist turns on where a binding authority already draws the boundary of a decision, and on which function signs the output, since anything feeding technical provisions answers to the actuarial function as well as to a product owner.
Is a 500-person UK business too small for an AI consultancy?
Not too small, though often better served by something cheaper. Tenhaw's stated range starts at 500 people, and the published prices are a £44,000 fixed four-week audit and £70,000 to £85,000 a month for a build team of three, which is a serious line at that size. An internal taskforce or one contract engineer is frequently the better first move. Where we fit is when a single workflow is genuinely how you compete and nobody internal can direct the build. Smaller organisations also carry a real advantage in having fewer org charts a decision has to cross, which is usually what decides whether the change sticks.
Who does agentic AI for a UK energy or mining business?
Tenhaw's evidence in that sector is delivery rather than agents. We set up and ran the Data, Simulation and DevOps teams behind Anglo American's £40bn hydrogen business case, work that spun out as First Mode. What we do not do is write safety cases, and our default across the IT and OT boundary is read-only, with no write path your own OT security function has not designed. Where a transformation firm earns its place is engineering knowledge work, simulation and planning, and capital project reporting across distributed programmes. Your shortlist turns on whether the value sits in the analysis or in operational decisioning, because those need different suppliers.
Can a UK AI consultancy deliver for a European group?
Yes, and what matters is where the data sits and who contracts. Tenhaw LTD is registered in England and Wales, contracts from London and invoices in sterling, processes engagement data in the United Kingdom by default with EU residency available where your policy requires it, and carries 24-hour personal-data breach notification as a term of the Data Processing Agreement. What we build is deployed inside your own infrastructure under your policies. A firm with offices in each market is the better buy where a programme needs people permanently in country. Settle first which entity in the group signs the agreement, because that decides the residency answer rather than where the team sits.
Who does agentic AI delivery for UK media companies?
Two categories, and Tenhaw is the second. Specialist AI product firms sell content and asset tooling, and transformation firms change how the teams around it work. Our media evidence is the founder's delivery roles at Sky and Discovery, including the visual rebrand team on the Discovery+ and Eurosport launch, one of six teams working to a date the CEO had already announced. The wedge that pays first here is content and asset production at volume, with customer service triage and summarisation behind it. Since 6 April 2025 the CMA has enforced consumer protection law directly, which reaches anything an agent writes for a customer, so the split that decides your shortlist is customer-facing output against internal work.
What should an RFP for agentic AI work actually ask for?
Ask for the shape of the engagement, not a solution, and be careful what you make scorable. Tenhaw sells a £44,000 four-week AI Readiness Audit precisely because nobody can know an agent's accuracy on your exceptions before building against your data, so an RFP demanding a guaranteed accuracy figure rewards the boldest guess rather than the best supplier. Score two things agentic work makes unusually revealing instead. One is the stopping condition each bidder will commit to, meaning the finding that would make them tell you not to proceed. The other is how they would sequence a second workflow once the first resets the estimate. Publish the weightings. What an RFP cannot settle is whether your exceptions are patterned, which only a build reveals.
How do we compare bids priced fixed, monthly and by the day?
Convert all three into a total for the same period, then list what each one leaves out. Tenhaw makes that arithmetic deliberately easy, because the audit is one fixed £44,000 for four weeks and the rungs above it are published as monthly bands, so a total is multiplication rather than interpretation. A day rate is not a cost until you also hold people-days by grade and a calendar, so require both from every bidder. A monthly fee needs a number of months behind it, and a fixed price means nothing until done is defined in writing. What no total captures is your own people's time, which varies more between these suppliers than the fees do.
How do we judge which supplier picked the right first workflow?
Judge the reasoning, not the choice. Tenhaw's position is that the pick should not be made in a pitch at all, which is why the £44,000 four-week audit builds two or three candidate workflows as working prototypes against your real data inside your own tenancy, each with a measured accuracy read and an estimated run cost per workflow, and ranks them on that evidence. Until something like that exists, ask any bidder why that workflow, what its exception rate is today, whether the data is usable, who signs the output, and what finding would make them stop. A supplier who chose before seeing your volumes is describing someone else's business. Which workflow survives production volume is something only production settles.
What should we ask a supplier's reference client?
Tenhaw makes the call easy by naming nine of the ten organisations behind its twelve case studies, so your own network can reach them without us in the middle. Ask any supplier's reference what cannot be scripted. Is it still running, who runs it now, what changed after the team left, what it cost to run in year two, how much of their own people's time it took, and was that engagement the team now proposed to you. Ask what each written study actually claims, too. Ours label a proof of concept as exactly that, including the agentic flagship being productionised inside a regulated insurer. What no reference settles is how their estate differs from yours.
Our incumbent supplier says they can do agentic AI too. How do we test that?
Test the team, not the account. Tenhaw publishes its shape before any pitch, a forward-deployed squad of three made up of an Agentic Lead, an engineer and an adoption lead, with James Rooney personally accountable, at £70,000 to £85,000 a month. Ask your incumbent to bid the same fixed scope over the same weeks, and to say what agentic work the people it would put on this have actually shipped. Their knowledge of your estate is real value and should be weighed as such rather than discounted for being familiar. What the bids will not settle is whether estate knowledge or agentic experience matters more here, and that turns on how much of the first workflow is integration.
Should we agree the follow-on price before the pilot starts?
Ask for it, and treat reluctance as information. Tenhaw settles it by publishing every rung before you buy the first one: an Agentic Design Team at £35,000 to £55,000 a month, an Agentic Build Team at £70,000 to £85,000, and Programme and Delivery Management at £18,000 to £35,000, each on 30 days' notice either way with the exit date set at kickoff. The risk you are pricing against is real. A supplier finishes a small first piece holding all your context while your comparators have gone quiet, and that is the moment a follow-on gets quoted. Which rung you actually need is the part nobody can fix in advance, because the first piece decides it.
How do we brief suppliers before we can give them our data?
Give every bidder one identical pack and date it. Tenhaw's first paid step exists for this gap, and the £44,000 four-week audit is where prototypes get built against your real data, inside your own tenancy, under your policies, with UK data residency by default, because nothing before that point can be built on. The pack needs the decision you want moved, monthly volume, today's exception rate, which systems hold the information, who signs the output, and two or three redacted examples under NDA. Then ask each supplier what they would need in week one, and what they would do if that access slipped. Data quality is what no pack shows, and it surfaces the first time someone queries the source.
Build it, buy it, or have someone build it with you
Before you choose between suppliers, work out whether you should be buying a supplier at all. Three routes, what each is best at, and the four questions that settle it.
Buy the product when being average at this workflow would cost you nothing. Build it yourself when the workflow is part of how you compete and you already have engineers who can carry evaluation, monitoring and model upgrades as a standing job rather than a project. Have someone build it with you when the workflow is differentiated and that capability is not there yet, which is the common case and the one Tenhaw is priced for. The question that settles it is not technical and it is not about models, but about whether your version of this process is worth being better at than everyone else's. If it is not, buy something off the shelf and spend the money where it changes your position.
Buy an agentic product
A vendor's product, configured against your data and your process.
- The workflow looks like everyone else's, and being average at it costs you nothing
- You need something running this quarter, on a pilot budget rather than a programme budget
- You would rather not own evaluation, monitoring and the model upgrade treadmill, and a vendor's engineers will carry all three
- The vendor sees a hundred customers' edge cases and you see one, so their roadmap is ahead of what you would build
- Your exceptions are the work. Products are built for the common case, and if the exceptions are why your process is expensive you will be configuring around them indefinitely
- The workflow is part of how you compete, and buying it makes you identical to whoever else bought it
- The data the product needs lives in six systems that do not speak to each other, in which case you have an integration programme with a licence fee attached to it
- Your risk function needs a decision trail the vendor does not expose. Ask for that before signing rather than after
- What it costs
- Licence, plus the integration that rarely reaches the business case.
- Who owns it in year two
- The vendor. Their roadmap is now your roadmap.
Build it yourself
Your own engineers, your own repository, your own operating model.
- The workflow is a differentiator and you intend to keep changing it
- You have engineers who can carry evaluation, monitoring and model deprecation as a standing job
- The value is in how you use data that is already yours
- You want the capability permanently, and your timeline can absorb the learning
- Nobody internal has done it before, so the first months are tuition paid at your own salary cost, which is fine if you planned for it and expensive if you did not
- The engineers you would use are the ones currently holding the estate up
- You end up building the parts that are the same for everybody. Orchestration, retrieval and evaluation harnesses are where the year goes
- The organisation around it does not change, which is how a working system ends up unused
- What it costs
- Salaries you are already paying, plus the year.
- Who owns it in year two
- You do. That is the point of it, and it is also the cost of it.
Have someone build it with you
A partner builds inside your estate, paired with your engineers, and leaves on a dated exit.
- The workflow is differentiated and the capability is not there yet
- You want the capability at the end rather than a dependency, and the test is whether your own engineers can run it without the supplier
- Roles, decision rights and governance have to move alongside the software
- You want a fixed price on the first step and a contractual exit date on the rest
- It is the most expensive of the three per unit of software, and if the workflow was never differentiated you have paid a premium to build something you could have bought
- Nobody internal is paired onto the build, in which case you have bought a demonstration rather than a capability
- You have no intention of hiring behind it, so what you are really buying is a dependency with an end date on it
- What it costs
- £20,000 to £55,000 fixed for a proof of concept, £70,000 to £85,000 a month for a build team of three.
- Who owns it in year two
- You do, if the handover was real. That is the clause to read before the price.
The four questions that settle it
None of them is about models, and the first one decides most of these arguments on its own.
- 01
Would being average at this workflow cost you anything?
If the honest answer is no, buy something. This settles most build-versus-buy arguments before anyone opens a vendor comparison, and it is the question asked least often. - 02
Is the difficulty in the volume or in the exceptions?
Volume is a product problem and products are good at it. Exceptions are a build problem, because your exceptions are specific to you and nobody else's roadmap will ever reach them. - 03
Who owns it in year two?
Every route has an answer to this and only one of them is free. Models get deprecated, prompts drift, upstream formats change, and the evaluation set has to be maintained by somebody. Decide who before you decide what. - 04
What does your risk function need to see?
If they have to evidence how a decision was reached, an auditable trail from decision to outcome is a design constraint rather than a feature request. It rules routes in and out before price is discussed.
We sell one of these three, so read the section with that in front of you. Two things make it less self-serving than it looks. We do not resell products, models, platforms or licences and we take no margin on any of them, so no part of your run cost is revenue for us and we have no reason to talk you into a larger one. And Programme and Delivery Management is buyable on its own at £18,000 to £35,000 a month with no requirement that we build anything, including on a programme where the answer turned out to be buy. Our own agentic evidence is proofs of concept rather than a production system, and each case study says so.
Run cost, and who takes a margin on it, is set out in full on the pricing page, and what our agentic work has and has not reached is on the case studies.
If that is the decision in front of you, thirty minutes usually settles it.
Talk it throughBuild, buy, or build it with someone
The six questions buyers ask before they get as far as choosing a supplier.
Should we build or buy agentic AI?
Buy when being average at the workflow would cost you nothing. Build when the workflow is part of how you compete and you already have engineers who can carry evaluation, monitoring and model upgrades as a standing job rather than a project. Have someone build it with you when the workflow is differentiated and that capability is not there yet. What decides it is whether your version of this process is worth being better at than everyone else's. A useful second test is where the difficulty sits. If it is in the volume, that is a product problem and products are good at it. If it is in the exceptions, that is a build problem, because your exceptions are specific to you and no vendor roadmap will reach them.
When is buying an AI product the right choice?
When the process is not differentiated, when you need something running this quarter on a pilot budget, and when you would rather a vendor's engineers carried evaluation, monitoring and the model upgrade treadmill than yours. A vendor who sees a hundred customers' edge cases will often be ahead of anything you would build for a common workflow. Two things stop it. If your exception cases are the reason the process is expensive, you will be configuring around them indefinitely. And if your risk function has to evidence how a decision was reached, ask to see the decision trail the product exposes before you sign rather than after.
When should we build agentic AI in-house?
When the workflow is a differentiator you intend to keep changing, when the value is in data that is already yours, and when you have engineers who can own evaluation, monitoring and model deprecation as a standing job rather than a project. The costs to price in are that the first months are tuition paid at your own salary cost, that the engineers you would use are usually the ones holding the estate up, and that a great deal of the year goes on building the parts that are the same for everybody, meaning orchestration, retrieval and evaluation harnesses. The failure that is not about engineering at all is the organisation staying the same shape, which is how a working system ends up unused.
Can we buy the commodity parts and build the differentiated ones?
Yes, and it is usually the right shape. Models, hosting, search and retrieval, orchestration frameworks and observability are bought by almost everybody building this way, and building your own version of them is where a year disappears. What is worth building is the comparatively thin layer that encodes your exceptions, your policy and your data. If a supplier proposes building the commodity layer for you, ask them why, and ask what you would be able to change in it a year later without them.
What does it mean to have someone build agentic AI with you?
A partner builds inside your estate and your repositories, paired with your engineers rather than in a separate stream, and leaves on a date agreed at kickoff. The measure of whether it worked is not the demonstration, it is whether your own people can run and change the thing without the supplier. On a live engagement, the client engineer who paired on a whole two-week proof-of-concept build finished it saying they were 70% confident they could run the process unaided. That is the number worth asking any supplier for, and it is worth being suspicious of anyone who answers 100%.
Is it cheaper to build or buy an agentic system?
Cheaper to start, almost always buy. Cheaper over three years, it depends entirely on whether you would have kept changing the thing, and no price list answers that. We publish our own build prices. A proof of concept is £20,000 to £55,000 fixed, and a build team of three is £70,000 to £85,000 a month. We will not publish a licence figure for products we do not sell. The number both sides usually leave out is run cost: inference, the platform, storage and search, evaluation and monitoring, and the human review your process still needs. On a build it lands on your own vendor contracts inside your own tenancy, and Tenhaw takes no margin on any of it. On a licence it is inside the subscription until your volumes move. Put it in the business case at the start rather than finding it in year two.
The questions people arrive with
Each answer is the same one given on the comparison page it belongs to.
Should we hire a Big Four consultancy or a boutique for AI transformation?
Choose a global consultancy when you need hundreds of people across multiple countries, deep multi-domain regulatory expertise, or when board expectation requires the brand. Choose a small forward-deployed firm like Tenhaw when you need senior operators building working systems inside your teams, a contractual exit, and pricing you can see before you engage. The determining question is usually whether you need scale or seniority.
Should we hire a Chief AI Officer or use an interim?
Both, in sequence. Hire permanently, which is the right end state and cheaper over any multi-year horizon. Use an interim Embedded Agentic Lead if the board's timeline is shorter than a six-to-nine month search, or if you cannot yet write the job specification accurately. The interim's job includes writing that specification and recruiting against it.
Why do internal AI taskforces stall?
Because scaling an agent pilot requires changing roles, decision rights and governance across functions the taskforce has no authority over. A taskforce is typically staffed part-time by enthusiasts from one or two teams. It can prove agents work; it cannot redefine other people's jobs, and that is what scaling actually requires.
Should we hire AI contractors directly or use a consultancy?
Hire contractors when the architecture and the sequencing are settled, you need specific skills, not a team, and somebody internal has both the authority and the time to direct the work daily. It is cheaper per day, and for that situation it is the better buy. Use a consultancy when the open questions are what to build and how the organisation has to change around it, when nobody internal can absorb the direction load, or when you want one contract with one named person accountable for whether the workflow actually worked rather than whether the tickets closed. The deciding question is not price, it is whether you have the management capacity.
Should we use an offshore or nearshore delivery partner for agentic AI?
Use one where the work can be specified: engineering volume against a written requirement, an overnight or weekend rota, or a bench you need to scale to twenty people and then hold. The cost advantage is real and large, with TCS listing offshore rates between roughly a quarter and just over half of its own onshore rates for the same SFIA level on the G-Cloud 14 framework. Use a small onshore firm like Tenhaw for the part that cannot be specified yet, which in agentic work is usually the first few months: which exceptions matter, what the data actually contains, where a human stays in the loop, and how roles and decision rights change once an agent takes a decision. Plenty of programmes should buy both, with the boundary written down.
What makes an AI transformation consultancy different from an AI build shop?
A build shop delivers working AI software. A transformation consultancy changes how the organisation operates so that software is actually adopted: redefining roles, moving decision rights, rewriting governance and managing the resistance that follows. Most failed agentic programmes have working technology and an unchanged organisation.
Comparing us against a firm you can name
Answered from rate cards the firms published themselves on the UK government's G-Cloud 14 framework, with the caveats stated beside the figures.
What are the alternatives to Accenture for AI delivery?
Four, and they are different trades, not better and worse. Another global consultancy, if what you need is scale, multi-domain regulatory depth and a name your board already accepts. A boutique or specialist firm, if you need senior people building inside your teams rather than the top of a pyramid. An offshore or nearshore delivery partner, if the requirement can be written down and cost per head is the binding constraint. Or your own people, through a permanent hire, contractors or an internal taskforce, if you have the management capacity to direct them. On price, do not assume the boutique route is automatically cheaper. Accenture's own published G-Cloud 14 rate card lists strategy and architecture at £2,240 a day at SFIA Level 7, £1,040 at Level 4 and £760 at Level 3. The first is 1.4 times our £1,560 partner rate, not the four times usually assumed, the second sits inside our own band, and the third is below our £950 associate rate. Where a small firm actually costs less is people-days to reach the same answer, not day rate.
Is a boutique cheaper than Deloitte for an AI programme?
At the top grade yes, and by less than the folklore suggests. On the G-Cloud 14 framework Deloitte publishes £2,740 a day at SFIA Level 7 on its specialist card and £2,450 on its standard card, against Tenhaw's published £1,560 partner rate, which is 1.6 to 1.8 times rather than the four times commonly assumed. Deloitte's lowest figure on either card is £1,425 at Level 3, above our £1,250 senior practitioner rate, so it publishes no grade inside our associate-to-senior band. Not every large firm prices that way. Accenture publishes £1,040 at Level 4 and £760 at Level 3, and TCS £1,070 and £680, all four at or below our senior rate and two of them below our £950 associate rate. If day rate alone is your criterion, some of the large firms win that comparison. Day rate is the wrong unit anyway. Team size times duration is the comparable number, which is why our fixed-price AI Readiness Audit is £44,000 against the £150,000 to £500,000 a large firm typically prices an equivalent assessment at, our estimate rather than a published figure.
Tenhaw vs EY: which fits an agentic AI build?
Team shape, and what you can check before you sign. On the G-Cloud 14 framework EY publishes £2,600 a day at SFIA Level 7 and £1,300 at Level 4, against our published £1,560 partner and £1,250 senior practitioner rates, and its card counts a working day as 7 hours where the other cards use 8. What Tenhaw sells is a forward-deployed squad of three senior people on published prices: a £44,000 audit, fixed, four weeks, ending in working prototypes, an exit date agreed at kickoff, 30 days' notice either way, and the code and documentation yours as they are written. If the programme also spans audit, tax or regulatory remediation under one contract, EY is the better buy.
Who are Tenhaw's competitors?
Three groups, and they win different work. Global firms: Accenture, Deloitte, EY, KPMG, PwC and PA Consulting publish G-Cloud 14 Level 7 rates from £2,240 to £3,625 a day, and one of them is the right buy when you need scale across countries, or depth across tax, legal and regulatory work under one contract. UK boutiques: Faculty, Mind Foundry, Aiimi, Advancing Analytics, Kortical and Datasparq, described on this site only from their own published material, three of them selling a platform of their own. Offshore partners, once the specification is settled and cost per head decides it. Tenhaw is priced for the case where the operating model, the engineering and the adoption move together.
How do we shortlist Tenhaw and a global firm for the same brief?
Compare people-days rather than day rates, and make the first step small enough to be reversible. A partner-led pyramid and a squad of three price differently by design, so team size times weeks is the comparable number and rate cards settle little on their own. Ask both to scope the same problem and price against that. Ours is fixed at £44,000 for four weeks, standalone, ending in working prototypes, with no obligation to continue, and the monthly work that can follow runs on 30 days' notice either way, so a shortlist of two need not become a single bet. If the roll-out needs hundreds of people across countries, award it to the global firm.
KPMG vs a specialist for AI governance work?
It turns on whether you are buying an opinion or a working control set. Tenhaw designs governance inside the delivery: the decision trail, the evaluation set, the human review points and a named internal owner, built into the workflow while the workflow is built. KPMG sits in the global audit and advisory category, and where the requirement reaches into regulatory remediation, tax or a formal assurance opinion, that category is the better buy. Its published G-Cloud 14 card lists £2,855 a day at SFIA Level 7, dated April 2024 and re-verified on 21 August 2026, against our £1,560 partner rate. What stays open is whether your risk function will accept controls designed by whoever built the system.
PwC quoted us a day rate. How does it compare with yours?
Set the quote beside our published three. Tenhaw charges £1,560 partner, £1,250 senior practitioner and £950 associate, excluding VAT, and they do not move by category. PwC's own G-Cloud 14 card does move, and sharply, from £2,750 at Level 7 under Strategy and architecture down to £1,000 at the same level under Delivery and operation, on a document uploaded in May 2024 that carries no publication date of its own. Two further traps. SFIA levels are not job titles, so mapping them onto anyone's grades is guesswork. And a rate multiplied by a team size you have assumed is not a cost. Ask for people-days by grade, because only the supplier knows the mix it intends to staff.
Does PA Consulting cost less than a Big Four firm for AI work?
Not on the published evidence, and Tenhaw's pricing page carries every card so you can check it yourself. PA Consulting is not a Big Four firm, but its own G-Cloud 14 rate card lists £3,625 a day at SFIA Level 7 on the UK co-located version, dated September 2024, which is the highest published Level 7 figure we found anywhere on that framework. The four Big Four cards top out between £2,600 and £2,855. Our partner rate is £1,560. So the label a firm carries is a poor proxy for what it costs, and the number that decides the total is people-days, which nobody can price before the scope is agreed.
TCS or a UK boutique for an agentic AI build?
Split it by whether the requirement can be written down yet. Tenhaw is the firm that sits in the room while that is worked out, and our Agentic Proof of Concept is £20,000 to £55,000 fixed over two to four weeks, built in your estate with your engineers paired on it. TCS belongs to the global IT services category, and its onshore G-Cloud 14 card, uploaded March 2025, lists £2,050 a day at SFIA Level 7 and £680 at Level 3, below our £950 associate rate. Once the specification is settled and what you need is volume held for years, that category wins. What decides it is how much of the workflow still lives in exceptions nobody has written down.
Do we need McKinsey for an AI strategy, or can we start with a build?
You can start with a build, and Tenhaw's AI Readiness Audit is designed to be exactly that start: £44,000 fixed over four weeks, ending in working prototypes against your own data inside your tenancy, an estimated run cost per candidate workflow and a board readout. A recommendation to stop is a valid outcome. A global strategy house answers a different question: which markets to compete in, what the portfolio should look like, a case for change that has to convince a board. Which of the two you need depends on whether your uncertainty is about direction or about whether agents can do the work at all.
BCG X or a specialist firm to build our agents?
Tenhaw is the specialist end: a squad of three, an Agentic Lead, an engineer and an adoption lead, with James Rooney personally accountable, code written in your estate from the first weeks and yours as it is written, an exit date agreed at kickoff and 30 days' notice either way. The first step is published too, £20,000 to £55,000 fixed for a proof of concept over two to four weeks. A build unit inside a global strategy house is the buy when the strategy relationship and the engineering sit under one contract, or when the roll-out needs hundreds of people across countries. What neither settles is whether this workflow is differentiated enough to be worth building at all.
Should Accenture or a specialist productionise the pilot we already built?
It depends how far the pilot has to travel. Tenhaw sells an Agentic Build Team at £70,000 to £85,000 a month, three practitioners under partner oversight, working in your repositories with your engineers paired on the build, and recruiting your permanent team is a stated deliverable. That shape suits one workflow taken properly into production and then run by you, which is the shape of the work running now inside a regulated insurer, where month three is productionising a two-week proof of concept against the client's security standards. A global systems integrator is the buy where productionising means rolling one pattern across many countries and staffing the support rota afterwards.
Accenture or Deloitte for agentic AI: how do they compare?
Tenhaw will not rank two firms it has never delivered alongside, and a supplier who does it for you is guessing. What is checkable is what each publishes. On the G-Cloud 14 framework Accenture lists £2,240 a day at SFIA Level 7 and £1,040 at Level 4, and Deloitte lists £2,740 at Level 7 on its specialist card and £2,450 on its standard one, both re-verified against their source documents on 21 August 2026. Every card is linked from our pricing page beside our own £1,560, £1,250 and £950. Then ask both the same three questions: who is actually in the room, what the first paid engagement ends in, and whose repositories the code lands in.
Is EY cheaper than KPMG on published day rates?
On the headline yes, and by less than it looks, which is why Tenhaw prints both cards with the caveats attached. On G-Cloud 14 EY publishes £2,600 a day at SFIA Level 7 against KPMG's £2,855, both dated 2024 and re-verified against their source documents on 21 August 2026. EY's card also defines a working day as 7 hours where the other cards use 8, roughly a 14% difference the headline never shows and wider than the gap between the two headlines. Our partner rate is £1,560, and our own engagement prices derive from that rate card at twenty billable days a month. Day length, category column and grade mix all move the real number.
Should the Big Four firm that audits us build our AI as well?
That is your audit committee's call rather than a capability question, and it does not arise with Tenhaw, because we provide no statutory audit or assurance services. We sell delivery, from the £44,000 AI Readiness Audit over four weeks, ending in working prototypes, through to an Agentic Build Team at £70,000 to £85,000 a month, with the code, documentation and work product yours from day one. Where a firm you already retain knows your controls estate well, that familiarity is genuine value and worth using wherever your own rules allow it. The point your committee has to settle first is whether designing the controls an agent will run under counts as a non-audit service it can approve.
Tenhaw or Faculty for an agentic AI programme?
Different trades, so the brief decides it rather than the logo. Tenhaw is a London firm that puts a forward deployed squad of three, an agentic lead, an engineer and an adoption lead, inside your teams. The prices are published, £44,000 fixed for a four week audit ending in working prototypes, then £70,000 to £85,000 a month for a build team. Faculty, from its own published material read in July 2026, positions itself around applied AI across sectors including defence, national security, health and financial services. Where the hard part is the model itself, a specialist AI firm leads and we partner for that work. What settles it is whether roles and decision rights have to move alongside the software.
Tenhaw vs ThoughtWorks for building agentic software?
Judge it on what you can read before signing. Tenhaw builds inside your own repositories against an open source engineering standard of 72 rules with RFC 2119 severities, paired with your engineers, and the code and documentation are yours from day one rather than on final payment. The team is three senior people at £70,000 to £85,000 a month, with an exit date agreed at kickoff and 30 days' notice either way. A global software engineering consultancy is the better award when the programme needs several teams running for years across countries. How many teams your first workflow needs is the number to settle before either of us quotes.
We shortlisted BJSS and Tenhaw. What settles it?
Whether anyone can write the specification yet. Tenhaw's AI Readiness Audit is £44,000 fixed over four weeks and ends in working prototypes built against your own data inside your tenancy, with an estimated run cost per candidate workflow, because the exception cases and the data quality are the part nobody can write down in advance. For a platform migration or a data platform build, where the work is engineering volume against a written requirement, a UK systems integrator is the better fit. Both can be true in sequence. Neither website tells you which half your programme is in today.
Kainos or Tenhaw for a multi-year digital programme?
Whether you intend to own this capability in house afterwards. Tenhaw sells monthly work built to end: £70,000 to £85,000 a month for three senior people, an exit date agreed at kickoff, 30 days' notice either side, and recruiting your permanent team written into the scope as a deliverable. Every month carries a value target, and a month that delivers none is reported to you as a failed month. If what you want instead is a supplier holding a standing team for three years, an enterprise delivery firm is shaped for that and we are not. Nobody outside your organisation can tell you which of the two you are buying.
Do we need a public sector specialist like Made Tech for one workflow?
Not necessarily for a single workflow, and Tenhaw's terms are the part to check. The AI Readiness Audit is £44,000 fixed over four weeks, ending in working prototypes built inside your own infrastructure under your own policies, with UK data residency by default and EU available. The public-sector record behind it is the Tecknuovo portfolio office, built from nothing and run across 19 projects including delivery for HMRC, the MOD and Thames Water. What the audit cannot settle up front is whether the Algorithmic Transparency Recording Standard reaches this workflow at all, which the standard's own scope and exemptions policy decides.
Our shortlist has Slalom and Tenhaw. What actually differs?
Who owns the operating model, the build and the adoption. Tenhaw keeps all three in one team, whether that is an Agentic Design Team of two senior people at £35,000 to £55,000 a month or an Agentic Build Team of three under partner oversight at £70,000 to £85,000. We sell no product and resell no models, platforms or licences, so no part of your run cost is revenue for us. Where you need several disciplines mobilised at once, or people across several countries in a quarter, a large consulting firm is the better award. Whether those three things have to move together in your organisation is a judgement only you hold.
How do we compare Tenhaw and Capgemini on price?
Not on day rates, because only half the arithmetic is public. Tenhaw publishes its own side in full: £1,560 partner, £1,250 senior practitioner, £950 associate, and a £44,000 fixed four week audit. The competitor cards this site quotes are G-Cloud 14 documents seven suppliers published themselves, PA Consulting, KPMG, PwC, Deloitte, EY, Accenture and TCS, each re-verified against its source on 21 August 2026, and Capgemini is not among them, so we will not quote a figure we have not read. What decides it is the team size and duration each supplier proposes against your scope, and neither number exists until they have seen it.
Is Tenhaw just a pricier version of an Infosys team?
No, because it is a different unit of purchase. Tenhaw's £70,000 to £85,000 a month buys three senior people under partner oversight, with James Rooney personally accountable, pairing with your engineers so the capability lands with them. Recruiting your permanent team is a stated deliverable, the exit date is agreed at kickoff, and a month that moves no number you agreed is reported to you as a failed month. Once the requirement is settled and what you need is volume, a global delivery partner is the right buy and we are the expensive way to write the code. Whether your engineers end up able to change the system without us is the test either way.
These are public-sector framework rates, and almost none of our work is public sector. We use them because private-sector consultancy rates are commercially confidential and nobody publishes them, so framework cards are the only competitor pricing that can be verified. They are also competitively tendered against volume commitments, which makes private commercial rates more likely to sit above these figures than below them. If anything, the table understates the gap.
These are SFIA levels, not job titles. The rate cards do not say partner, director or manager, so we quote the levels as the suppliers publish them: Level 7 is defined in the cards as "set strategy, inspire, mobilise", Level 3 as "apply". Nor are the rates directly comparable on their face: EY defines a working day as 7 hours where the others use 8, roughly a 14% difference the headline figure hides. Every figure in this table is quoted from the linked PDF.
These figures are from G-Cloud 14, and every card was re-verified against its source document on 21 August 2026. G-Cloud 15 was awarded on 6 August 2026 but publishes no pricing documents yet, so G-Cloud 14 remains both the live buyer catalogue and the newest published pricing these suppliers have.
No page on this site is built against an individual firm. Where one is named, here, on the boutique comparison or in the index this site publishes for AI assistants, it is named from its own published material and nothing characterises it beyond that. The full table, with each figure linked to the supplier's own PDF, is on the pricing page, and its headline finding goes against us: the Big Four are not four times our price.
Or bring the shortlist to the call and we will tell you where we do and do not belong on it.
Talk it throughStill weighing it up?
Thirty minutes with James Rooney. If another route fits you better, we would rather tell you now than three months into an engagement.
most start with a fixed-price AI Readiness Audit · £44,000 · 4 weeks · working prototypes
Calendar not loading? Open it on cal.com or email hello@tenhaw.com.