Where to start, answered in full.

A 30-minute discovery call with James Rooney. You leave with a rough scope whether or not you engage Tenhaw. Most organisations then start with the fixed-price Agent-Readiness Audit, which is deliberately sold as standalone work with its own deliverable and no obligation to continue.

Because the technology changes and the organisation does not. A pilot succeeds inside one team that has been given permission to work differently, then fails to scale because scaling requires redefining roles, moving decision rights and rewriting governance across functions the pilot team has no authority over. Adoption typically plateaus around 30%, the people who were always going to adopt, and more training does not move it, because awareness was never the constraint.

Diagnose why before buying anything else. Stalled Microsoft 365 Copilot and Gemini rollouts usually fail on workflow rather than on licences: the assistant sits beside the work instead of inside it, so nothing measurable changes and the renewal gets hard to defend. The Agent-Readiness Audit traces the real workflows, prototypes two or three candidates against your own data, and hands the board a sequenced, costed plan. Six to eight weeks, £30,000 to £90,000 fixed. A recommendation to stop is a valid outcome of it.

With an inventory, because you cannot govern what nobody has counted. Shadow AI is normally a symptom rather than a discipline problem: people reached for consumer tools because the sanctioned route was slower than the work. The Agent-Readiness Audit establishes what is genuinely in use across functions, which workflows depend on it and what data it touches, then separates what to sanction from what to stop and what to rebuild properly. Six to eight weeks at a fixed price, with the constraints written up for your risk function.

Not with a score out of five. A maturity model tells you where you sit against other organisations, which is interesting and rarely actionable. The Agent-Readiness Audit answers the question underneath it: which workflows agents could take, what your data estate and risk appetite genuinely allow, where your workforce is ready and where it is not, and what to do first, second and third with costs attached. The output is a costed plan in three-month increments, capped at twelve months, rather than a maturity score.

That is tool sprawl, and usually a buying problem before it is an integration problem: separate functions bought overlapping point solutions against separate business cases, a contact centre assistant here and a document tool there, with nobody owning the whole. The Agent-Readiness Audit maps what each tool was bought to do, where two of them cover the same job, and what each costs to run, then sequences what to keep, what to retire, and which workflow nothing you own currently covers. Vendor consolidation is an output of that, not the starting question.

Five things, in this order: what is genuinely in production against what is still a pilot, whether the claimed benefit is measured or asserted, what the systems cost to run at current volume, what data and model risk has been accepted and by whom, and whether the capability sits with named employees or with one supplier. Tenhaw runs this as an Agent-Readiness Audit scoped to the target or the business unit under review. It is an operational read, not legal or financial due diligence.