Employee-funded AI is a procurement signal, not just a shadow-IT offence
Deloitte estimates UK workers spend nearly £1 billion a year on AI tools, while many users receive no training. Personal spending reveals unmet access and workflow demand—but it does not prove business value.
What happened
Deloitte published a survey of 25,000 UK working adults on generative-AI use, training, time savings and personal spending.
Why it matters
When employees buy tools themselves, bans alone can hide demand without resolving security, access or evidence gaps.
Deloitte’s UK GenAI Workforce Survey covers 25,000 working adults across 22 industries and 24 roles, with fieldwork in May and June 2026. Deloitte reports that 63% had used generative AI, half of users had received no training and 31% of users employed it at work without their employer’s knowledge. Reuters reports that one in six workers paid personally and that Deloitte estimated annual personal spending near £1 billion.
Those figures describe self-reported behaviour, not audited expense data or causal productivity. Only 7% said they saved at least five hours a week; 31% of workplace users reported no time saving. The survey therefore supports a demand signal, not a blanket return-on-investment claim.
Read personal spending as a queue
An employee who pays for a tool may be bypassing policy, but may also be revealing an unresolved job-to-be-done: translation, analysis, coding, drafting or search that the approved stack does not serve. Treat each discovered tool as a request entering a governed intake queue.
Record the workflow, data classes, users, cost, claimed benefit and approved alternative. Triage high-risk cases immediately—regulated data, client material, source code and automated decisions—while giving low-risk experiments a fast route to a sanctioned sandbox. A control that only blocks access can drive use off-network and erase the very evidence needed to manage it.
Separate adoption from value
The strongest counterargument is that workers may buy fashionable tools with no measurable benefit. Deloitte’s own time-saving result keeps that possibility open. Require a short evidence period before reimbursement or enterprise procurement: baseline cycle time and error rate, observe changes, include review time and exceptions, and ask whether the workflow improved rather than whether the tool felt useful.
Procurement, security, HR and learning teams should share one register. Training must cover the approved workflow and review duty, not generic prompting alone. Access equity also matters: a workplace where useful AI depends on personal spending will select by disposable income.
Use the Skills Atlas to map the capability behind each request. The decision is not “allow shadow AI” or “ban it.” It is whether repeated personal demand justifies a safer, equitable and measurable service.