Tenhaw vs Big Four
Same ambition. Very different delivery model.
- Audit cost. Big Four: £150k–£500k typical
- £30k–£90k fixed
- Team seniority on the ground. Big Four: Mixed, weighted to junior
- Senior operators only
- Global mobilisation. Big Four: Effectively unlimited
- UK, Europe, US
The short answer: Tenhaw or Big Four
The Big Four and global consultancies (Accenture, Deloitte, McKinsey, EY, PwC, KPMG) bring scale, brand safety and depth in regulated environments, if you need 200 people across twelve countries next quarter, they can do that and Tenhaw cannot. Tenhaw is a small forward-deployed consultancy: a handful of senior operators who embed inside your organisation, build the systems alongside your people, and leave on a contractual date with your permanent team in post. The trade is scale and procurement comfort against seniority-per-pound and accountability for the outcome.
The case for the Big Four and global consultancies
Weigh these first. They are real advantages, and on some programmes they are the deciding factor.
- Global scale: hundreds of people mobilised across geographies quickly
- Deep regulatory and audit expertise, particularly in financial services and pharma
- Established procurement, insurance and indemnity positions that clear enterprise legal easily
- Brand safety: nobody on your board will question the choice
- Broad adjacent capability across tax, legal, risk and technology implementation under one contract
Which should you choose?
There is a real answer here, and it is not always us.
Tenhaw
is the right call when:
- You want the people who did the work at HSBC and Microsoft in your rooms, not managing from a partner deck
- Your last transformation produced a strategy that never landed
- You want the operating model and the engineering accountable to one firm rather than to two suppliers pointing at each other
- You want a committed monthly increment you can inspect, rather than a phase gate a quarter
- You want a contractual exit date and permanent-team recruitment written into the scope
Big Four
is the right call when:
- You need hundreds of people mobilised across multiple countries within a quarter
- Your procurement floor requires suppliers with nine-figure indemnity cover
- The programme spans domains well beyond operating model and delivery, into tax, legal or M&A integration
- Board or regulator expectation specifically requires a Big Four name on the work
- You need to call a reference who has run this supplier's agentic system in production inside a regulated firm, because we cannot yet give you one
If that is you, say so on the call and we will tell you the same thing. It is cheaper for both of us than finding out in month three.
Prefer to talk it through? Ask us on a discovery call →
Where the models differ
The differences that change what you get, rather than adjectives.
- 01
Who is actually in the room
TenhawA forward-deployed squad of three: an Agentic Lead, an engineer and an adoption lead, each of them someone James Rooney has already delivered alongside. James Rooney is personally accountable for every engagement, the same person who advised HSBC's CIO on target operating models across 150+ teams and a $102M budget. The squad is the whole team, and the people on your engagement are not substituted without your written agreement.
Big FourA partner sells the work and a senior manager oversees it, with delivery staffed by consultants typically two to eight years into their career. The expertise that won the pitch is rarely the expertise doing the work. The pyramid beneath the partner is what funds global scale, and it is exactly what lets a large firm put 200 people across twelve countries next quarter.
- 02
What gets handed over at the end
TenhawAgentic workflows running in production with named internal owners, a permanent team recruited and in post, and documentation. The exit date is agreed at kickoff and the final sixty days are a taper.
Big FourTypically a comprehensive target operating model, implementation roadmap and change materials, often accompanied by a proposal for the next phase. Some engagements do land production systems; many produce excellent analysis that the client then struggles to execute alone.
- 03
How the commercial model shapes behaviour
TenhawFixed-price audit, then monthly retainers with a production increment committed to and reported against every month. Recruiting your permanent replacement team is a stated deliverable, so the engagement is structured to end.
Big FourTime-and-materials or milestone-based, with account growth as an explicit commercial objective. Good firms manage this tension professionally, but the model does reward extended tenure in a way a small firm's cannot.
- 04
Depth versus breadth
TenhawOne thing: rebuilding how organisations work around AI agents, informed by a decade of landing delivery transformation. Outside that, we will tell you we are the wrong supplier.
Big FourBreadth across strategy, technology, risk, tax and operations. If your agentic programme is entangled with a regulatory remediation and a carve-out, that breadth has real value a specialist cannot match.
Tenhaw and Big Four, dimension by dimension
| Dimension | Tenhaw | Big Four |
|---|---|---|
| Production agentic deployments to reference | None in production yet: a regulated-estate proof of concept is productionising now | Multiple, named, in regulated firms |
| Team seniority on the ground | Senior operators only | Mixed, weighted to junior |
| Typical team shape | Forward-deployed squads of 3 | 10–200+ pyramid |
| Delivery cadence | Monthly increment, committed and reported | Milestone / phase gates |
| Global mobilisation | UK, Europe, US | Effectively unlimited |
| Audit cost | £30k–£90k fixed | £150k–£500k typical |
| Builds, or only advises | Builds, with an engineer embedded in the squad | Varies by engagement |
| Recruits your permanent team | Stated deliverable | Rarely in scope |
| Contractual exit date | Agreed at kickoff | Usually open-ended |
| Published pricing | Yes | No |
| Regulatory / audit depth | Delivery and governance only | Deep, multi-domain |
| Board-level brand safety | Requires a case | Immediate |
Some rows in that table go against us. They stay in it, because a comparison you cannot lose is a comparison nobody should believe.
- Tenhaw published rate card, benchmarked against G-Cloud 14
Our £1,560, £1,250 and £950 day rates set beside the large firms' own published framework rates, with every competitor figure linked to the supplier's own PDF and the caveats stated beside it. The £150,000 to £500,000 large-firm assessment figure used in the FAQ above is our own read of the market and is not sourced to a published document, so treat it as an estimate to check rather than as a citation.
- Accenture SFIA rate card, G-Cloud 14, strategy and architecture
Source of the Level 7 £2,240, Level 4 £1,040 and Level 3 £760 figures quoted on /pricing. Competitively tendered public-sector framework rates, dated April 2024, so they need not match private commercial rates.
- Deloitte LLP specialist rate card, G-Cloud 14
Source of the Level 7 £2,740 figure. Deloitte publishes a second, standard card with different rates, also linked from /pricing.
- KPMG LLP SFIA rate card, G-Cloud 14
The highest published Big Four Level 7 rate we located, at £2,855. No PwC card was found on the framework, and we will not estimate one.
- EY onshore rate card, G-Cloud 14
Level 7 £2,600 and Level 4 £1,300. EY defines a working day as 7 hours where the other cards use 8, roughly a 14% difference the headline rate does not show.
What a small supplier can evidence
Scale buys an assurance position that clears legal without a conversation. We publish ours in full: what is in place, and what is not yet.
- UK GDPR and Data Protection Act 2018 compliant, as a UK-registered company
- DPA with sub-processor annex available for every engagement
- 24-hour personal data breach notification, committed in the Data Processing Agreement
- UK data processing by default, with EU residency available where an engagement requires it
- Engagement sub-processor list published on the security page and annexed to the DPA
- BS7858-standard personnel screening before client access
- No-substitution commitment written into the SOW: the people on an engagement are not changed without the client's written agreement
- Named-tool-only policy for AI systems touching client data
- Professional indemnity £1m, employers' liability £10m, public liability £1m, cyber £25k, legal expenses £100k
- Cyber Essentials Plus: certification in progress
- ISO 27001: gap assessment complete, certification targeted for 2027
- ISO/IEC 42001 (AI management systems), under assessment, and increasingly the one clients ask for
- SOC 2 Type II: will follow ISO 27001 where clients require it
If your supplier floor requires certification we do not hold today, that is a real reason to buy elsewhere. The full position, including the DPA and the sub-processor annex, is on the security page.
Long programmes are the risk, and the data is unusually clear about it
Buyers often assume a large firm moves faster because it can put more people on the problem. The published research points the other way: the risk of a programme underperforming rises with its duration, its effort and its team size, and the biggest programmes fail most often. That is the arithmetic of the delivery model, whichever firm runs it, and it is why Tenhaw sells six-to-eight week audits, two-to-four week proofs of concept and teams of two or three rather than a hundred-person programme.
- 01
The longer a programme runs, the worse it overruns
Research from the Saïd Business School at Oxford into 1,355 public-sector IT projects, averaging $130m and 35 months, found that every additional year of duration added 4.2 percentage points to expected cost overrun and 1.2 points to schedule overrun. The catastrophic outliers clustered in the longest-running projects.
Source: Budzier and Flyvbjerg, University of Oxford, in the Commonwealth Governance Handbook 2012/13 - 02
Risk roughly doubles once a programme passes eighteen months
A study of 412 IT projects found the probability of underperformance rose from about 25% for projects of three to six months to about 50% beyond eighteen months. Team size behaved the same way: risk sat at 25 to 35% until a team passed twenty people, then rose above 50%. Above 2,400 person-months of effort, the authors found no successful projects at all.
CaveatThis was an editorially reviewed magazine article rather than a blind-refereed paper. Its headline finding also cuts against the doom statistics often quoted at buyers: 67% of the projects it examined landed close to plan.
Source: Sauer, Gemino and Reich, Communications of the ACM, volume 50 number 11 - 03
Small programmes succeed; the largest mostly do not
Across a database of more than 25,000 software projects, 61% of small projects succeeded against 6% of the largest, and 43% of the largest failed outright. The same report found agile projects succeeded almost four times as often as waterfall ones.
CaveatStandish is an industry benchmark, not peer-reviewed research, and its method is disputed. Eveleens and Verhoef reproduced it against 5,457 forecasts in IEEE Software and concluded the definitions are unsound. We cite it as a directional signal that agrees with the peer-reviewed work above, not as proof on its own.
Source: The Standish Group, CHAOS Report 2015 - 04
Adding people buys less time than it costs
Comparing 390 software applications of the same size, teams averaging fewer than four people were set against teams of nine or more. The larger teams cut the schedule by roughly 30%, but cost rose by 350% and defects found in testing rose by 500%.
CaveatThese were software builds of 10,000 to 20,000 lines of new code, not multi-year transformation programmes, and the comparison is not controlled. Read it as evidence about build teams, which is the part of a programme it actually measures.
Source: Putnam, Quantitative Software Management - 05
Short consultancy engagements have a habit of getting longer
Examining departments' use of consultants for EU Exit preparations, the National Audit Office found that 68% of individual pieces of work were scoped to run for less than three months, but that 43% of engagements had been extended at least once, half of those more than once. Average duration reached 119 days against Cabinet Office guidance of 90.
CaveatThe NAO attributes the extensions to the departments, citing client demand and shifting scope: evidence about how these engagements behave rather than about any firm's motives.
Source: National Audit Office, HC 2105, Session 2017-19 - 06
Day-rate pricing does not reward finishing early
The National Audit Office's good-practice guidance on using consultants states that "it is good practice to focus on outputs rather than inputs when contracting" and that "'time and materials' contracts may offer poor value for money". It warns that pricing on inputs like day rates while contracting for outputs "creates the risk that delivery incentives and cost controls become misaligned".
CaveatThe NAO is describing a risk created by a mismatch between how work is contracted and how it is priced. It does not condemn day rates as such, and the same body of work found 86% of officials surveyed said consultants provided a valuable contribution. We publish our own day rates, so this cuts at us too: the answer is fixed-price stages and a contractual exit date, not a cheaper rate.
Source: National Audit Office, Using consultants in government, November 2025
Read together, that is an argument for keeping the unit of work small and the clock short, whoever you hire. It is why our audits are fixed-price over six to eight weeks, our proofs of concept run two to four, delivery teams are two or three people rather than twenty, and every engagement carries a contractual exit date with your permanent team named in the scope. If you buy a two-year programme from anyone, including us, the evidence says plan for it to take longer than the plan.
Questions buyers ask us
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.
Why is Tenhaw cheaper than a Big Four audit?
Tenhaw's Agent-Readiness Audit is £30,000–£90,000 fixed, against a typical £150,000–£500,000 for an equivalent large-firm assessment. The gap is the shape of the team rather than the day rate: fewer, more senior people over 6–8 weeks, and no pyramid to fund. Our rate card is published so you can check the arithmetic, and the pricing page sets it beside the large firms' own G-Cloud framework rates. Those rates run 1.3 to 2.3 times ours at the top grade, not the four times often claimed, and at mid grades several are cheaper than us. A global firm's overhead is real and its scale requires it. You are not buying scale here, you are buying far fewer people-days to reach the same answer.
Can Tenhaw work alongside an incumbent Big Four supplier?
Yes, and it is a common arrangement. Tenhaw frequently runs the agentic operating model and embedded delivery while a larger firm handles adjacent regulatory or systems-integration workstreams. We are explicit about the boundary and will say when the other supplier is better placed to own something.
What can a Big Four firm do that Tenhaw cannot?
Mobilise at scale, carry very large indemnity positions, and bring deep expertise across tax, legal, audit and regulatory remediation simultaneously. If your programme spans those domains, or needs 200 people quickly, Tenhaw is the wrong supplier and we will say so on the call.
How do we justify a boutique to our board?
On evidence and accountability. Named clients with checkable outcomes, published prices, a monthly production increment reported against, and a contractual exit date with permanent-team recruitment in scope. The Agent-Readiness Audit exists partly as a low-risk way to test the working relationship before committing to a larger programme.
Can Tenhaw give us a reference client running an agentic system in production?
No. Tenhaw has not taken an agentic system into production for any client. A large consultancy can put you on a call with a named client running one in a regulated firm, and if that is your gate, this comparison is settled. What we can put in front of you is narrower. A live engagement in the London specialty insurance market, 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, and where month three stands up a team to productionise it. A proof of concept at HSBC applying natural language processing, sentiment analysis and entity recognition to enterprise voice data, projected rather than measured, and never rolled out. Twelve engagements written up in full with the evidence basis stated on each. And the client engineer who paired on that entire two-week build, who finished it saying they were 70% confident they could run the process without us. If a supplier answers 100%, ask them the same question about a system they built two years ago.
Do the Big Four deliberately drag work out?
There is no published evidence that they do. What the data does show is that longer programmes overrun more, larger teams carry more risk, and engagements priced on inputs do not reward finishing early. Those are properties of the delivery model rather than anyone's intent, and they apply to any supplier who sells a large, long, day-rate programme. The National Audit Office, looking at consultancy engagements that ran past their scoped length, put the extensions down to the departments buying them rather than the firms selling them.
Does a smaller team really finish sooner?
Not always, and the finding has a limit. On software builds the evidence is fairly direct: comparing 390 applications, teams of nine or more cut the schedule by about 30% against teams of under four, while cost rose 350% and defects rose 500%. Across whole programmes the finding is about risk rather than raw speed: underperformance rises sharply past eighteen months and past a team of twenty. A small team is not automatically faster. It is exposed to less of what makes programmes fail.
You publish day rates. Does the same criticism apply to you?
It applies to any input-based price, ours included, which is why the ways in are fixed-price rather than rate-based: the audit is a fixed fee over six to eight weeks and the proof of concept is a fixed fee over two to four. Where we do sell a monthly team, the engagement carries a contractual exit date and recruitment of your permanent replacements is written into the scope. The rate card is published so you can check the arithmetic, not because the rate is the product.
The other options you are weighing
Build it, buy it, or have someone build it with you
Every comparison in this section assumes you should be buying a supplier at all. If the workflow is not differentiated, the answer is a product and none of these pages apply. 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.
Tenhaw vs AI boutiques
Most are strategy firms or build shops. We are neither.
Tenhaw vs Offshore partners
Cheaper per head, and that is the point of it.
Tenhaw vs Contractors
Cheaper per day, and right whenever you already have someone to direct them.
Tenhaw vs Hiring in-house
You should hire. The question is what happens in the meantime.
Tenhaw vs Internal taskforce
The cheapest option, and the one that most often stalls at pilot.
How to put this to your board
Four things you can lift straight into a paper. None of them is an adjective, and every one of them is published on this site before you ask for it.
- 01
The price is published before the first conversation
£30,000 to £90,000 fixed for the Agent-Readiness Audit, against the £150,000 to £500,000 a large firm typically prices an equivalent assessment at. The rate card behind our figure, and the large firms' own published framework rates, are on the pricing page, so the arithmetic can be checked. - 02
The engagement is contracted to end, and to leave a permanent team behind
The exit date is agreed at kickoff rather than negotiated at the end, recruiting your permanent team is a stated deliverable, and you own all work product and code on payment. - 03
The people are senior, screened and not substitutable
Everyone on the engagement is someone James Rooney has already delivered alongside, screened to BS7858 standard before any client access, and not substituted without your written agreement. A squad of three, so the people you meet are the whole team rather than the top of a pyramid. - 04
The assurance position is published, including what is not yet held
Professional indemnity £1m, employers' liability £10m, public liability £1m, cyber £25k, legal expenses £100k, with certificates shared during onboarding. Cover levels can be increased for a specific engagement where your supplier standard requires it. Raise it on the first call and we will price the increase into the engagement. Cyber Essentials Plus is in progress and ISO 27001 is targeted for 2027. The full position is on the security page.
Board optics is the one row in the triage table where we do not come out ahead. Ours requires a case, which is why the case is written down here rather than assembled on a call.
Let's talk about where your organisation is headed.
A 30-minute discovery call with James Rooney. We'll cover where your organisation sits on the agentic curve and which rung to start on. You'll leave with a rough scope whether you engage us or not.
Most organisations start with a fixed-price Agent-Readiness Audit · £30k–£90k · 6–8 weeks