7 min read
July 2026
AI adoption for small teams: where to start, in order
Six steps. Most small teams do them in the opposite order.
Start with the work, not the tools. Spend a week finding where the hours actually go, then pick one workflow. Decide who checks the output before anything goes live. That order is the whole answer, and here is the reasoning behind it.
The sequence
The real barrier is not what people assume
Eurostat asked EU enterprises that had considered AI and decided against it why they stopped. Lack of relevant expertise came first, named by 70.3%. Cost was named by 38.4%.
The pattern holds at every company size: 70.9% of small enterprises named expertise, against 65.1% of large ones. This is not a problem that money solves. The tools themselves are cheap, and a capable assistant costs less per month than a single freelance hour.
70.3%
named lack of relevant expertise as a reason for not adopting AI, vs the 38% that named cost.
Eurostat, ICT enterprise survey, 2025.
So the gap is not budget and it is not access. It is that nobody has an hour to work out where this fits. A bad first attempt is also expensive in confidence.
That changes the first move. If the barrier were cost, you would start by choosing a cheaper tool. Since the barrier is knowing where AI fits, you start by looking at your own work.
Where European small businesses actually are
EU27 enterprise AI adoption reached 20.0% in the 2025 reference year, up from 13.5% the year before. That comes from Eurostat's ICT Enterprise Survey. Adoption is climbing fast. Four in five European enterprises still do not use AI in any way the survey counts.
In Portugal it is lower. INE's IUTICE 2025 survey put it at 11.5% of firms with ten or more workers. That is up from 8.6% in 2024 and 7.2% in 2021.
Enterprises using AI
EU27 adoption grew by half in a single year, and Portugal is climbing at the same pace from a lower base. On a 0–100 scale the other half of the story stays visible: most European enterprises still do not use AI at all.
The size gap is the striking part: 9.4% among firms with 10 to 49 people, against 49.1% among firms with 250 or more. The European Commission's Digital Decade assessment puts Portuguese SMEs at 11.5% against roughly 20% across the EU.
Adoption is mostly a company-size story
Same country, same year. A large Portuguese firm is more than five times as likely to use AI as a small one. That gap is what this article is about closing.
Read that as reassurance rather than alarm. If you are a ten-person team in Lisbon who has tried ChatGPT a few times, you are not late. You sit roughly where the median sits, and ahead of most of your market.
1. Find the hours before you find the tools
Before evaluating anything, spend one week noting where time actually goes. Not a formal audit. A shared note, and everyone adds tasks that felt slower than they should have been.
You are looking for three properties: it repeats, it produces text or images or structured output, and nobody enjoys it.
That list is your shortlist. Almost every failed AI rollout we have seen started with a tool somebody liked and worked backwards to find it a job.
2. Pick one workflow, not one department
The instinct is to say "let's use AI in marketing". Too broad to act on and impossible to evaluate. Pick one workflow. Not marketing, but "the monthly client report write-up". Not admin, but "turning call notes into follow-up emails".
One workflow gives you a before and an after. It gives you a person who owns it. The first one often does not work. When that happens you learn something specific, instead of concluding that AI does not suit your business.
Give it four weeks. If it has not stuck by then, drop it and move to the next item on the list. Something that has not become habit in a month will not become habit in three.
3. Choose fewer tools than you think
BCG surveyed 1,488 full-time workers in the United States in 2026. Self-reported productivity rose when people used three or fewer AI tools, and fell once they reached four or more. Three is the ceiling, not the target. For most small teams the right number at the start is one general assistant, used properly, and nothing else.
Tool sprawl looks like progress and functions as cost. Every additional tool is another subscription, another login, another set of habits. It is also another place where client data might sit, and another thing to explain when someone leaves.
If you take one thing from this article, take this one. It is free and it works immediately.
4. Decide who checks the output
This is the step that gets skipped, and it is the one that determines whether any of this actually saves time.
Workday's January 2026 study of 3,200 business leaders found 85% of employees saving one to seven hours a week with AI, with nearly 40% of that immediately lost to rework. Sage found 48% of finance professionals spending 15 or more hours a week on checking, and named the effect the verification tax.
The verification tax
Of every hour AI gives back, roughly this much survives contact with checking and fixing. It is the difference between a workflow that pays for itself and one that only feels faster.
Time saved is not the number that matters. Time saved minus time spent checking and fixing is. For a lot of teams that number is close to zero.
So before a workflow goes live, answer one question in writing. Who reads this before it matters, and would they catch an error? If the answer is nobody, you have not automated a task. You have moved the risk somewhere you cannot see it.
5. Write down what you are not going to use it for
A short list. Half a page. It covers three things: what data never goes into a tool, what work is never AI-drafted, and what always gets human sign-off.
Two reasons this matters more than it sounds. The practical one is that people are already using these tools, whether or not you have a policy. A written boundary is the difference between informed use and quiet use.
The regulatory one is that the EU AI Act asks for this. The AI literacy duty under Article 4 has been in force since February 2025. Transparency obligations under Article 50 apply from 2 August 2026. A short internal document is most of what taking that seriously looks like for a small team.
Dates worth knowing
February 2025
The AI literacy duty under Article 4 came into force. Already applies to you.
2 August 2026
Transparency obligations under Article 50 start to apply.
6. Measure the net, not the saving
Pick one number before you start. Hours on the task, turnaround time, or output volume at constant quality. Record it for two weeks beforehand. Then measure the same thing afterwards, including the checking time.
This sounds fussy for a small team. It takes about ten minutes a week. Without it you can carry a tool for a year because it feels faster.
What good looks like after three months
One workflow that has genuinely changed
A named person who owns it
One or two tools the whole team can name
A written rule about what stays human
A number showing whether it worked
What to do next
Start the shared note this week. One week of observation costs nothing and it determines whether everything after it is aimed at the right thing.
If you would rather not build the sequence from scratch, ViraOps has it laid out. The AI Foundations track walks a team through it. The Monthly Workflow Playbook adds a complete worked example each month.
ViraOps is €89 a month, up to five seats included, with a 14-day free trial.
Sources
- Eurostat, ICT Enterprise Survey, 2025 reference year, published December 2025
- INE, Inquérito à Utilização de Tecnologias da Informação e da Comunicação nas Empresas, 2025
- European Commission, State of the Digital Decade country report, Portugal, 2026
- OECD, AI adoption by small and medium-sized enterprises, 2025
- BCG, survey of 1,488 full-time workers, 2026
- Workday, AI productivity and rework study, January 2026
- Sage, verification overhead research, 2026
- Regulation (EU) 2024/1689, Articles 4 and 50