AI Business Case for UK SMEs

In short

A board-ready AI business case in plain language: what we’d build, what it costs, what it returns, what could go wrong, who signs off what. Wingenious produces this as part of Leadership Discovery and Roadmap: a working session with your leadership team, then a written proposal and roadmap within a week.

What’s in the document

1. Executive summary: one page, board-readable
2. Problem statement: what business outcome are we improving?
3. Proposed AI capability: what we’d build, in plain language
4. Investment + ROI: costs, returns, payback (see AI ROI calculation)
5. Built-vs-buy: defensible recommendation (see built-vs-buy analysis)
6. Vendor shortlist: top 3 with pros/cons (see vendor shortlisting)
7. Implementation plan: sequence, timeline, owners
8. Risk register: what could go wrong, with mitigations
9. Governance: who approves what, audit trail design
10. Recommendation: proceed / pause / kill, with reasoning

Why this exists

Most SME AI investment decisions get made on vendor sales materials. Leadership Discovery replaces that with a defensible internal document. Your board can actually scrutinise the proposal rather than the pitch deck.

What gets missed when an SME skips this stage

The pattern repeats often enough to be worth naming. An SME identifies an AI opportunity, gets enthusiastic about it, watches two vendor demos, picks the more polished one, signs a 24-month contract and a procurement order, and starts the build. Six months in, the team realises the use case needed twice as much integration work as anticipated, the data was nowhere near as clean as the demo implied, the vendor is charging substantially more than the headline number once volume kicked in, and the projected ROI was based on assumptions that nobody actually challenged.

The business case stage prevents this. It is not bureaucracy. It is the cheapest way to surface the failure modes before they cost real money. A structured look at the numbers before committing reliably saves the SME from spending £30,000 to £80,000 on the wrong build. Leadership Discovery pays for itself many times over even when its conclusion is “proceed as planned”, because the proceeding is now defensible rather than impulsive.

The other thing that gets missed is the sequencing question. AI investments rarely sit alone. The use case picked for the first build affects what is realistic for the second and third. Building a customer-facing AI before the governance posture is in place is a different risk shape from building it after. The business case surfaces sequencing trade-offs that the leadership team would otherwise not consider until they are already mid-build.

What goes into each section, in detail

The document is structured for a leadership team to read in one sitting and to scrutinise in detail if they want to.

Executive summary

One page. The proposed investment, the expected outcome, the headline cost, the headline return, the recommended decision, the risks the board should know about. Designed to be read by a non-executive director on a train. Decision-ready without reading further.

Problem statement

The business outcome the investment is improving, named in commercial terms. Not “we want to do AI” but “we want to reduce our cost-per-acquired-customer by 15 percent” or “we want to recover 12 hours per week per support agent”. The business case is anchored to a measurable outcome, not to an aspiration.

Proposed AI capability

What gets built or bought, in plain language. The shape of the workflow. The tools that touch it. The data that flows through it. The human touchpoints. The boundaries of what is in scope and what is explicitly not in scope.

Investment and ROI

Three-year total cost of ownership: build cost, ongoing licence cost, ongoing operational cost, internal time. Against it: expected return, calculated using your specific volume and salary figures, with sensitivity ranges showing the answer at conservative, base and optimistic assumptions. Payback period in months. NPV at a sensible discount rate. The numbers are calibrated to UK SME reality, not enterprise benchmarks.

Built-versus-buy recommendation

The defensible answer to whether this use case is a vendor product, a custom build, or a hybrid. Reasoning attached. See built-vs-buy analysis for the framework.

Vendor shortlist

If the answer is buy or hybrid, three named vendors with pros, cons, pricing at your volume, contract risk, data residency and reference customers. See vendor shortlisting for the framework.

Implementation plan

What happens in what order. Who owns each step. Where Wingenious sits (delivery, oversight, or out of the way entirely). What dependencies need resolving before the build starts. What dependencies can run in parallel.

Risk register

The realistic things that could go wrong, sorted by likelihood and impact. Each one with a mitigation. The risks that get included are not the ones consultants normally cite (“technology may not work as expected”) but the specific ones for this build (“supplier data integration may need bespoke parsing because the supplier still ships invoices as scanned PDFs”).

Governance

Who approves what. Audit trail design. Human-in-the-loop specification per workflow output. Compliance posture against UK GDPR, ICO guidance, the Data (Use and Access) Act 2025, and the EU AI Act where it applies. See AI governance models for the framework.

Recommendation

The defensible answer to the proceed-pause-kill question, with reasoning. Leadership Discovery has produced more than a few “pause and address X first” recommendations and a small number of “kill” recommendations. The outcome does not change what is charged for the work; the independence is the whole point.

How the work is done

Leadership Discovery is a working session of two to four hours with the leadership team, with preparation before and a written output after:

• Before the session. A short questionnaire and a look at how the business runs. Use case definition refreshed, volume and cost baseline gathered where available.
• The session. Owner or MD plus heads of operations, sales and finance, four to six people typically, at their site anywhere in the UK or remotely. Data and integration scoping, the shape of the ROI model, built-versus-buy options and the main risks are worked through together.
• The roadmap. Within a week the client receives the written proposal and roadmap, a clear list of what not to do yet, and a recorded readout to share with colleagues who were not in the room.

The output is delivered in editable form (Google Doc, Word, or whatever shape suits the SME’s board pack). Nothing is locked in Wingenious tools.

What happens when the board approves

The same document feeds straight into a delivery engagement. Three typical next moves.

1. The build stage. Production workflow delivered, with 30-day stabilisation.
2. A smaller build. Scoped down for scopes that do not need the full build shape.
3. Vendor procurement track. Where the answer is buy, the SME proceeds directly with the recommended vendor using the business case as the procurement reference document.

About two-thirds of clients proceed to delivery within 90 days. The remaining third either pause and address prerequisites, kill the investment, or run the delivery themselves using the document.

What happens when the board does not approve

Leadership Discovery has paid for itself. The SME has avoided a wrong investment that would have cost many times more to discover by building. The document is reusable; many SMEs return to it 12 to 18 months later when conditions have changed and the original use case looks more viable.

How to commission this when there is no use case yet

A common SME shape: the leadership team knows they want to do something with AI but does not yet have a specific use case to commission a business case against. A deep-dive business case is the wrong starting point in that situation. Two better entry points.

The first is Leadership Discovery and Roadmap. It produces the ranked shortlist of candidate use cases, then deep-dives the top one.

The second is an AI strategy workshop, half day or full day. The workshop produces a draft 90-day plan with named use cases; Leadership Discovery then deep-dives the priority one.

Either entry point produces the specific use case definition that makes a business case worth commissioning.

What the roadmap and readout cover

The written roadmap and recorded readout are structured for a leadership team that may not have been involved in the detailed work.

They open with the executive summary and recommendation. The leadership team gets the conclusion before the detail. If the recommendation is “proceed”, the rest is about how. If the recommendation is “pause” or “kill”, the rest is about why and what to do instead.

The substantive sections follow: the ROI projection with its assumptions, the built-versus-buy reasoning, the vendor shortlist, the risk register and the governance posture. Each section invites challenge from the leadership team; the document is built to be argued with, not absorbed passively.

The close covers decisions and next steps. Who is going to do what by when. What additional information would change the picture. What dependencies need resolving before the build can start.

Why Leadership Discovery has a defined scope

The defined scope is deliberate. SMEs benefit from knowing what they are getting in advance rather than discovering it as the work unfolds. Leadership Discovery covers the pre-session questionnaire, the working session, the written proposal and roadmap, the recorded readout and the editable model handover. It is the first paid stage, it follows the free one-hour call, and prices are not published.

There is no commitment to later stages. Each is bought on its own, and the roadmap is yours to take to another implementer if you prefer.

The recommendation is independent of the outcome. Leadership Discovery that recommends proceeding costs the same as one that recommends pausing, or one that recommends killing the proposed build. The independence is structural: Wingenious has no incentive to push toward proceeding because what is charged does not change with the answer.

Related capabilities

AI ROI calculation · Vendor shortlisting · Built-vs-buy analysis · AI use case identification

Related

Sectors where the business case matters most: manufacturing, law firms, accountants.