What should an AI discovery workshop actually include?
19 July 2026
What should an AI discovery workshop actually include?
A paid AI discovery workshop should leave you with a decision, not just ideas. You should know which AI opportunities are worth pursuing, what each one will cost, what data and systems are involved, what the legal and operational risks are, who owns the next step, and whether the business case is strong enough to continue. If the output is only a slide deck of generic use cases, you have not bought discovery. You have bought a brainstorming session.
What should be included before the workshop starts?
A good AI discovery workshop starts before anyone walks into the room. The provider should ask for enough information to avoid wasting the first hour on introductions and generic AI examples.
At minimum, pre-work should include a short business questionnaire, a list of core systems, a sample of current workflows, known pain points, current software costs, rough team size by function, and any compliance constraints. If customer data, employee data or sensitive commercial data may be involved, the provider should also ask about data protection ownership and existing policies.
This matters because the UK is not a blank sheet for AI adoption. The Department for Business and Trade reported 5.5 million UK private sector businesses at the start of 2024, with SMEs making up 99.8% of that population and small businesses alone making up 99.2%. Most buyers are not enterprise AI labs. They are practical companies that need AI to fit around real staff, real systems and real budget constraints. Source: DBT Business population estimates 2024.
Pre-work should normally take 30 to 90 minutes of your time and 1 to 3 hours of the consultant's time. If a provider charges for discovery but does no preparation, expect a shallow session.
What should happen during the workshop?
The workshop itself should be structured. A useful format is not everyone saying where they think AI might help. It is a disciplined working session that turns operational friction into a ranked implementation backlog.
| Workshop stage | What it should cover | Useful output |
|---|---|---|
| Business goals | Revenue, margin, service quality, capacity, risk reduction or speed | Clear success criteria |
| Workflow mapping | Where work enters, who touches it, what systems are used, where delays occur | Shortlist of candidate processes |
| Data review | Data sources, ownership, quality, permissions, retention and sensitivity | Data readiness score |
| Use case design | What AI would actually do, what humans still approve, and where automation stops | Defined use cases, not vague ideas |
| Risk assessment | Data protection, cyber security, bias, customer impact, operational failure and accountability | Risk register and control list |
| Cost model | Build cost, licences, integrations, maintenance, staff training and governance | Implementation budget range |
| Prioritisation | Value, complexity, risk, data readiness and time to benefit | Ranked roadmap |
The most important part is the cost model. For most UK SMEs, a realistic first AI implementation after discovery is not £500 and it is not £250,000. A useful internal automation or agent workflow often lands between £5,000 and £25,000 for build, testing and handover. A more integrated system touching CRM, email, documents and approvals can be £25,000 to £75,000. Enterprise transformation work from firms such as Accenture, PwC, Deloitte or McKinsey can go much higher, and that can be appropriate for large organisations with complex governance and multiple business units.
A discovery workshop should tell you which lane you are in. If it cannot, it has failed.
What should the deliverables be?
The deliverables should be concrete enough for a leadership team to decide whether to continue, pause or reject the idea. A paid workshop should not end with a pretty PDF that says AI can improve productivity.
Good deliverables include:
- A one-page executive summary with the direct recommendation.
- A mapped list of the workflows reviewed.
- A ranked AI opportunity backlog with 3 to 10 use cases.
- A cost range for each serious use case, in pounds.
- A benefits estimate, including time saved, risk reduced or revenue protected.
- A data readiness assessment.
- A risk and governance register.
- A recommended first implementation scope.
- A 30, 60 and 90 day action plan.
- A clear list of what not to do yet.
The last item is not optional. Discovery should kill weak ideas. If every idea survives the workshop, the provider is probably trying to sell implementation rather than advise properly.
For example, a customer service agent that drafts replies from approved knowledge articles may be a good first use case if the business has a strong helpdesk history and clear tone of voice. A fully autonomous refund approval agent may be a bad first use case if policies vary by customer, staff routinely override the rules, or the data is scattered across email, spreadsheets and finance software.
How much should an AI discovery workshop cost in the UK?
Here is the honest pricing. A short, practical AI discovery workshop for a UK SME should usually cost between £1,500 and £3,500. A more serious discovery project with interviews, workflow review, data assessment and a written business case should usually cost between £4,000 and £8,000. Anything below £1,000 is likely to be either light-touch sales activity or a group training session. Anything above £10,000 should include deeper analysis, multiple stakeholders, technical review and a board-ready recommendation.
| Format | Typical UK price | What you should expect |
|---|---|---|
| Free discovery call | £0 | Qualification, fit check, rough direction. Not a workshop. |
| Half-day workshop | £1,500 to £2,500 | Focused mapping, 3 to 5 use cases, light prioritisation. |
| Full-day workshop | £2,500 to £3,500 | Workflow mapping, risk review, prioritised opportunities, basic cost ranges. |
| Discovery sprint | £4,000 to £8,000 | Pre-work, interviews, data review, workshop, business case and roadmap. |
| Enterprise assessment | £10,000 to £50,000+ | Multi-department review, security, architecture, governance and operating model. |
At Precise Impact AI, we would rather say this plainly: if you only need ideas, do not pay for a full discovery sprint. Book a training session, run an internal workshop or use publicly available AI use case lists. If you need an investment decision, pay for proper discovery because the cost of building the wrong thing is usually far higher than the cost of deciding properly.
What risks and governance should be covered?
Any workshop that ignores governance is incomplete. That does not mean turning a practical SME session into a legal seminar. It means asking the right questions early enough to avoid expensive rework later.
The UK government's AI regulation white paper sets out five cross-sector principles for responsible AI: safety, security and robustness, transparency and explainability, fairness, accountability and governance, and contestability and redress. It also makes clear that existing regulators apply rules in their own sectors rather than sending every business to one new AI regulator. Source: A pro-innovation approach to AI regulation.
The ICO's AI and data protection guidance also highlights accountability, transparency, lawfulness, accuracy and fairness. If your AI use case touches personal data, the workshop should identify whether a Data Protection Impact Assessment may be needed, who the controller is, what lawful basis applies, and how people will be told about AI use. Source: ICO guidance on AI and data protection.
Security also belongs in the room. The National Cyber Security Centre says AI systems should be considered across secure design, secure development, secure deployment, and secure operation and maintenance. For an SME, that means checking data exposure, supplier access, logging, human approvals, credentials, integrations and incident response before anyone connects AI to live systems. Source: NCSC guidelines for secure AI system development.
What should not be included in paid discovery?
Paid discovery should not include theatre. You should be wary of workshops that spend half the time explaining what generative AI is, showing viral examples, or presenting a vendor's favourite tool before understanding your business.
It should also not include premature build work. Discovery may produce a prototype sketch or technical recommendation, but it should not quietly turn into a build commitment before the business case is agreed. That is how companies end up paying for automations that save 20 minutes a week while ignoring processes that waste 20 hours.
Be especially careful with these red flags:
- No named deliverables before you pay.
- No discussion of data protection or security.
- No cost ranges for implementation.
- No prioritisation method.
- No willingness to say an idea is not worth doing.
- Every answer points to one vendor, one platform or one licence bundle.
- The output is described as a strategy deck, but not as an implementation decision.
A good consultant should be able to tell you where competitors or alternatives are better. Microsoft partners may be the right fit if your whole business already lives inside Microsoft 365, Power Platform and Dynamics. A specialist automation agency may be better if the problem is mainly workflow integration. A large consultancy may be right if the work affects regulated enterprise operations. Precise Impact AI is best suited to practical UK businesses that want commercially grounded AI implementation without buying a huge transformation programme.
When this does NOT apply
This advice does not apply if you are buying basic AI awareness training. Training is about confidence and capability. Discovery is about deciding what to implement.
It also does not apply if you already have a mature internal product, data or automation team. In that case, you may need technical architecture review, vendor due diligence, model evaluation or governance support rather than a general discovery workshop.
Finally, it does not apply if leadership has already chosen the solution and only wants external validation. A discovery workshop cannot be honest if the answer has been decided before the work starts. In that situation, call it a review, not discovery.
What is the bottom line?
An AI discovery workshop should include enough operational, commercial, technical and governance work to answer one question: should we invest in this, and if so, what exactly should we do first?
The output should be a priced, prioritised, risk-aware roadmap. It should tell you what to build, what to avoid, what it will cost, what needs to be true for it to work, and who owns the next step.
If you want to explore whether a paid discovery workshop makes sense for your business, book a free call. No pitch, no pressure, just an honest conversation about whether discovery would produce a useful decision for you.
Is This Right For You?
An AI discovery workshop is right for you if you have enough operational complexity for AI to matter, but not enough clarity to start building. That usually means a UK business with multiple recurring workflows, a CRM, finance system, helpdesk, project tool, ecommerce platform or document-heavy process, and a leadership team that wants numbers before committing budget.
It is probably not right if you only want a general ChatGPT training session, if you already have a validated implementation backlog, or if the business cannot spare senior people for the workshop. Paid discovery only works when the people who understand the work are in the room.
Frequently Asked Questions
How long should an AI discovery workshop take?
A focused workshop usually takes half a day or one full day. A proper discovery sprint can take 1 to 3 weeks because it includes pre-work, stakeholder interviews, system review and a written business case.
Who should attend an AI discovery workshop?
You need senior decision-makers, process owners and at least one person who understands the systems and data. For an SME, that usually means the owner or managing director, operations lead, sales or service lead, and someone responsible for IT or data protection.
Should a discovery workshop include technical architecture?
It should include enough architecture to identify systems, integrations, data flows, security constraints and likely build complexity. It does not need a full solution design unless you are paying for a deeper discovery sprint.
Is a free AI discovery call the same as a workshop?
No. A free call is a fit check. It should help both sides decide whether a workshop is worth doing. It should not be expected to produce a roadmap, cost model, risk register or implementation plan.
What should I receive after the workshop?
You should receive a written summary, ranked use cases, cost ranges, risk notes, a recommended first implementation and a 30, 60 and 90 day action plan. If you only receive generic slides, the workshop was not specific enough.
Can an AI discovery workshop prove return on investment?
It can estimate return on investment, but it cannot prove it before implementation. A good workshop should show the assumptions clearly, such as hours saved, error reduction, licence costs, build cost and staff adoption risk.
Should we do discovery before choosing AI tools?
Yes, unless your use case is extremely simple. Choosing tools first often leads to the wrong architecture. Discovery should define the job, data, risks and success criteria before deciding whether the answer is ChatGPT, Microsoft Copilot, Power Automate, a custom agent, or no AI at all.