Sooner or later somebody asks an operator for an AI strategy: a board, a bank or a customer working through a vendor questionnaire. The request is fair. A long slide deck is the wrong answer to it.
An AI strategy is not a deck. It is a short document that says which parts of your business you will change with software this year, in what order, and how you will know it worked. It fits on one page. Below is what belongs on that page, what to leave off, the European rules that shape it whether you read them or not, and the start plan that turns the page into something running in production.
What an AI strategy actually is
Strip the vocabulary away and a strategy is a set of decisions made in advance, so you do not have to make them under pressure. For AI there are four.
- Where you lose money today. Not where AI is interesting. Where the leak is, in euros per month.
- Which leak you fix first. One, ranked by cost, not by how good the demo looked.
- Who owns the result. A named person, internal or external, accountable when the number does not move.
- What you will not do. The tempting projects you are deliberately skipping this year.
A document that answers those four is a strategy. A document that surveys the technology market and ends with three horizons is a literature review with an invoice attached.
Why AI strategy documents stall
The failure is structural, not intellectual. Four separate jobs sit inside any AI programme: finding the leak, deciding what to fix, building the fix, and running it afterwards. A strategy document covers the second job and quietly assumes the other three.
So the deck lands, everyone agrees it is sensible, and nothing happens. Nobody measured the leak, so nobody can size the prize. Nobody is on the hook for the build. Nobody has been told who keeps the thing alive at 2am in December when it breaks. The strategy was not wrong. It was incomplete in exactly the places that require a person to do work.
The cheapest fix is to write the strategy after a measurement instead of before one. That inverts the usual order, and it is the whole reason our engagements open with an audit rather than a workshop.
What Europe means by an AI strategy, and why it is not yours
Search the phrase and the first results are often government documents. They are worth reading once, and worth not confusing with your own plan.
The Apply AI Strategy and the AI Continent Action Plan
The European Commission published the AI Continent Action Plan on 9 April 2025 and the Apply AI Strategy on 8 October 2025. The Commission calls the Apply AI Strategy its overarching sectoral AI strategy: it complements the action plan with measures to boost AI adoption across ten key industry sectors and the public sector, particularly among SMEs. Estonia's own plan is the kratikava, the national AI adoption action plan for 2024 to 2026, published at kratid.ee (all four pages checked 26 and 27 October 2026).
Those documents tell you where public money and public attention will point over the next few years. They tell you nothing about which of your invoices is late. Read them for context, close the tab, go back to your own numbers.
The rules you inherit either way
Two frameworks are worth reading before you write the page.
The EU AI Act entered into force on 1 August 2024 and sorts AI systems into four risk levels: unacceptable, high, transparency and minimal. Its transparency rules came into effect in August 2026: when a system talks to a person, that person has to be told they are dealing with a machine. The high-risk list covers areas such as hiring and worker management, access to essential services such as credit scoring, education and critical infrastructure. After the AI Omnibus, which entered into force on 27 July 2026, those high-risk rules apply from 2 December 2027, and from 2 August 2028 for AI built into regulated products (European Commission page, checked 26 October 2026). Back-office document handling is quieter, right up until it touches hiring, credit, or anything else that decides something about a person.
The NIST AI Risk Management Framework is voluntary and American, and it is a useful checklist. Version 1.0 was released in January 2023 and NIST says it is being revised (checked 26 October 2026). Its four functions, govern, map, measure and manage, double as an honesty test for your page. If you cannot say who governs a system and how you measure it, you have a wish rather than a strategy.
The one-page AI strategy: what goes on it
Seven lines. If a line will not fit in three sentences, it is not decided yet.
- The leak. One sentence naming where money or time goes missing, with a monthly cost attached. "Supplier invoices wait in a shared inbox for days before anyone codes them, and we pay late fees on some of them" beats "we want to improve efficiency".
- The number that must move. One metric with a baseline you already counted. Quote response time, days to invoice, hours per month-end close, cost per handled ticket.
- The first system. What gets built, named concretely. Document intake into the ledger. Quote requests read from email into the CRM, one piece of sales process automation, from lead to close. Not an AI layer.
- The stack. The actual tools. Make.com or n8n for workflow, the accounting system and CRM you already run, and the model provider for any step that needs judgement. Naming the stack forces the conversation about who owns the accounts.
- The owner. One name. If the honest answer is nobody, that is your finding for the quarter.
- The guardrails. Where a human stays in the loop, what data leaves the building, which processor agreement covers it, and which risk level the system sits in. For a worked example, our post on how we run our own company on Claude Code lists what our agent may do alone and what waits for a human yes.
- The not-doing list. Three things you are skipping and why. This is the line that keeps the page a strategy instead of a wish list.
That is the document. Anything longer is a proposal or a stalling tactic.
A practical start plan
Measure before you buy
Count the thing you want to fix for one normal month first. How many quote requests came in, how long each waited for an answer, what a won job is worth. Without a baseline you can only argue about the result later. The AI audit for business walkthrough starts here too.
Pick one job, not a portfolio
Choose the single job with the highest monthly cost and ignore the rest for now. Five half-configured systems produce less than one that runs.
Ship it beside the old process
Run the new system alongside the manual one for a month. Nobody gets fired, nothing gets deleted, and you get a fair comparison instead of a vendor chart.
Decide from the month, not the demo
At the end of the month, compare against the baseline you wrote on line two. If the number moved, write the next line of the page. If it did not, you learned something for the price of one month rather than one annual contract.
What to leave off the page
Three things belong in the bin.
Technology surveys. A list of models with release dates ages within months, and it never told you what to build anyway.
Headcount fantasies. The claim that AI will let us avoid three hires cannot be tested this quarter, and it poisons the room the moment your team reads it. Talk about hours and euros instead.
Percentages you did not measure. A figure lifted from a vendor slide does not belong on a page you will be held to. The point of the exercise is that every number on it traces back to something you counted yourself.
Two things that change the page
The first is ownership after go-live. Building a workflow on Make.com or n8n is rarely the hard part. Who runs it afterwards is, so that name belongs on line five before anything gets built.
The second is search. If your buyers ask an assistant about suppliers in your category, your own content becomes part of how they find you. Being readable and quotable for those assistants is covered in how to get your business cited by AI. If that applies to you, a line about it belongs on the page.
How to tell the strategy is working
One test, monthly. Take the metric on line two and ask whether it moved. Whether people like the new system does not count. The number does.
A second test, quarterly. Can somebody other than the person who built the system explain how it works and switch it off? If not, you do not have a system, you have a dependency. That is the same failure as the consultant who walks out with the knowledge, wearing a different costume.
Both tests are easier to apply to somebody else's work first. Our case studies list the systems that were built, with the live URL where the work is a public site. That is the format to demand from anyone pitching you: something you can open, not a slide you have to believe.
Where to start
Write the leak line first, in euros, before anything else on the page. If you cannot fill it in, that is the finding, and the other six lines can wait a week.
Our free 30-minute audit, run by our CEO and co-founder Karl-Kristjan Saar, is built around that line: how the work runs today, where time, money or information is lost, and what that costs. The findings are yours whether or not you work with us. If a fix is worth building, it is scoped and priced only after the audit, because a price quoted before anyone has seen your volume is a guess wearing a suit. The build side sits under automation, the work we have shipped is on the case studies, and the shape of the engagement is on the consultancy page.
If you need an outside team for the first build, our page on AI consultancies in Estonia sets out how trainers, resellers, large firms and teams that build the system differ.
Questions operators ask about AI strategy
What is an AI strategy?
It is a short document that records four decisions: where your business loses money today, which of those leaks you fix first, who is accountable for the result, and which tempting projects you are skipping this year. Everything else is context. A document that surveys models and ends with three horizons is a literature review, not a strategy, because nobody can be held to it next quarter.
How long should an AI strategy be?
One page. The constraint is the point: a section that cannot be written in three sentences is a decision nobody has made yet, and a long document hides that. Keep the supporting measurement in an appendix if the board wants it, but the page itself stays short enough that the owner of each line can be named out loud in a meeting.
Do we need an AI strategy before we build anything?
You need a measurement before you build, and the strategy is what you write once you have it. Reverse that order and a programme can stall: the deck is approved, then nobody can size the prize because the baseline was never counted. Measure one normal month first, then write the page, then build one system.
What does the EU AI Act require from our AI strategy?
The Act sorts AI systems into four risk levels: unacceptable, high, transparency and minimal. Its transparency rules, in effect since August 2026, mean that when a system talks to a person, that person has to be told it is a machine. Hiring, credit scoring and other decisions about people are on the high-risk list, with those rules applying from 2 December 2027, so name the level on the page rather than assuming it.
Who should write the AI strategy?
Whoever will be accountable for the number moving, with help from whoever will build the system. A strategy written by people who never touch delivery often describes work that nobody has agreed to do. If an outside party writes it, ask a blunt question first: will they also build the fix and say who runs it afterwards, or are they handing you a document and an invoice?
A one-page AI strategy is harder to write than a slide deck, because every line commits somebody to something. That is the feature. Start with the leak line and put a monthly number beside it.
