What are Steve Hooper AI's starting fees?
A free 20-minute call checks the fit. A prepared strategy session costs £450 for 60 minutes. The scoped Workflow Diagnostic and AI Use & Risk Review each cost £1,500. Team workshops start from £2,500, a two-week Readiness Audit from £6,500 and substantial implementation from £12,000. Smaller pilots are separately quoted. These are Steve Hooper AI's fees, not a survey of UK consulting prices.
Be clear about what the fee covers
AI consulting prices are only useful when the scope is clear. A strategy call, an audit and an implementation project involve different work. The prices below are Steve Hooper AI’s published starting prices, not a survey of the UK market.
The first question is whether you need help choosing the work or delivering it. Agree what you want to achieve before commissioning a build. If you already understand the task and the changes needed, you may not need a wider audit.
The published starting prices
Start with a free 20-minute fit conversation. An optional prepared strategy session costs £450 for 60 minutes and includes a written recommendation. The Workflow Diagnostic and AI Use & Risk Review each cost £1,500 for the defined scope. An AI Readiness Audit starts from £6,500 for two weeks, covering an opportunity map, priorities, business cases and a board-ready roadmap.
Automation & Implementation starts from £12,000 and typically takes 4–12 weeks. The engagement includes the working automation, integrations, documentation, training and 30 days of support. Fractional AI Leadership starts from £4,000 per month, for one to two days a week with a three-month minimum. Half-day and full-day team workshops start from £2,500 per workshop.
Include the costs around the project
Ask about software subscriptions, AI usage, hosting, ongoing support, staff review time and any travel before comparing proposals. A one-off build fee does not describe the entire cost of running a workflow. Ask for written commercial terms, including the treatment of VAT and expenses.
Your own team’s involvement matters too. Someone needs to explain the process, provide representative examples, review the output and take ownership. Make that time visible in the business case rather than treating it as free.
Separate capacity from cash savings
Saving ten staff hours a week creates capacity. It only becomes a cash saving if a real expense changes; it may instead help the team respond sooner, clear a backlog or handle more work. Do not count the same benefit twice as both a cost saving and extra revenue.
Start with a baseline and a conservative estimate of the time that can actually be reclaimed after human checks. Subtract the running costs. Compare that value with the project cost, and record the assumptions that would need to hold for the project to be worthwhile.
What to ask before you commit
Ask who delivers the work, which systems are included, how acceptance will be tested, what documentation you receive and who owns the result. Ask what happens when an integration fails, what support is included and what costs continue after handover.
If the scope still feels vague, describe one repeated process and the decision you need help with. That gives us a useful starting point for the conversation.
