The EU AI Act for SMBs: which duties apply to you, and when?
Most companies only use AI tools. See what the law asks of you, and what can wait.
Does it apply to you?
Four questions to find where you stand.
Yes only to the first: your duties are light. Each further yes adds duties. The exact tests are in the section for your IT manager, below.
- Does your team use AI tools?ChatGPT, Claude, Copilot, or AI inside your software. The law calls you a "deployer": a business that uses AI. Your main duty is to help staff understand the tools they use.
- Could any of your uses be banned?For example, software that reads your staff’s emotions. A handful of uses are banned outright, and a quick check rules them out.
- Does AI help you decide about people?Hiring, credit, insurance pricing, access to education or public services. These "high-risk" uses face stricter rules from 2 December 2027.
- Do you sell a product with AI built in?Even one built on a model such as ChatGPT or Claude. You are then usually its "provider": people must be told when they are dealing with an AI, and AI-made content must be marked.
Not in scope?
Light duties? Your customers may still ask.
Larger customers now ask, in security questionnaires and contracts, how you control your use of AI. A short AI policy and a list of approved tools answer most of those questions.
see how we set AI rulesWhat changes for you
For most companies: clear rules for staff, and a check.
If your team only uses AI tools, the law asks two things. Help your staff understand the tools they use, in proportion to the risk; no test or certificate is required. And make sure none of your uses is banned.
Stricter rules start on 2 December 2027 for AI that helps decide about people, such as hiring or credit: human oversight, records, and in some cases an impact assessment. Companies that sell such systems carry the heaviest load.
For most companies the real risk is not a fine. It is client data pasted into the wrong tool, or an AI answer sent to a customer unchecked. Three rules cover most of it: what data may go in, which tools are approved, and a human check before anything reaches a client.
What to do first
Map your AI use, then set the rules.
What we deliver
- A list of every AI tool and feature in use, and your role for each
- A check that none of your uses is banned or high-risk without you knowing
- An AI use policy and a list of approved tools
- Staff awareness matched to the tools each role uses
- If AI decides about people: the high-risk plan, with the 2027 deadline in your calendar
Who does what
We set the rules. Your teams and suppliers run the AI.
What we lead
- Map your AI use and your role for each tool
- Check for banned and high-risk uses
- Write the AI policy and the approved-tools list
- Train staff on the tools they use
- Prepare the evidence a customer or authority will ask for
What stays with your IT provider
- Configure the AI tools and their data settings
- Manage accounts and access
- Keep the logs and records the plan requires
We do not build, deploy or configure AI systems.
How it starts
Your first step: a map of your AI use.
In 1–2 weeks you know which AI you use, your role for each tool and which rules apply. The rest of the work is sized from that map, at a fixed fee.
- Price
- Fixed fee
- Duration
- First results in 1–2 weeks
Fixed quote after the free call.
see the AI governance serviceFor your IT manager, DPO or CFO
What the regulation requires, by article.
The obligation set that applies to you is scoped in Phase 1 Discovery by your role and your systems. These are the articles that most often land on an SMB.
- 01Art. 5
Prohibited AI practices
Binding since February 2025. Social scoring, untargeted facial-recognition scraping, emotion recognition in the workplace and education, certain biometric categorisation. The 2026 Omnibus added two more — AI-generated non-consensual intimate imagery, and CSAM — which apply from 2 December 2026. Carries the maximum fine band, and small mid-caps get no relief from it.
- 02Art. 4
AI literacy
Binding since February 2025, and softened by the Omnibus. Providers and deployers must take measures to support the development of AI literacy among staff who use or oversee AI, proportionate to the risk and context of use. The amended article says expressly that no specific level need be guaranteed for any individual — an obligation of effort, not of result.
- 03Art. 6 · Annex III
High-risk classification
Eight Annex III areas define stand-alone high-risk use: biometrics, critical infrastructure, education, employment and worker management, access to essential public and private services (incl. creditworthiness and insurance), law enforcement, migration and border control, and administration of justice.
- 04Art. 9 · 10
Risk management & data governance
Providers of high-risk systems must run a continuous risk-management system across the lifecycle and govern the quality, relevance, and representativeness of training, validation, and testing data.
- 05Art. 13 · 14
Transparency & human oversight
High-risk systems must be transparent enough for deployers to interpret and use them correctly, and must be designed for effective human oversight — including the ability to intervene, override, or halt the system.
- 06Art. 15
Accuracy, robustness & cybersecurity
High-risk systems must achieve appropriate accuracy, robustness, and cybersecurity across their lifecycle — resilient against errors, faults, and adversarial attempts to manipulate the model or its data.
- 07Art. 26
Deployer duties (high-risk)
Binding December 2027. Use per the provider instructions, assign competent human oversight, monitor operation and keep logs, suspend and report where risks emerge, and inform affected persons. The primary obligation set for organisations deploying Annex III AI.
- 08Art. 27
Fundamental Rights Impact Assessment
Public bodies and certain private deployers of high-risk AI (including creditworthiness and insurance-risk use) must complete a FRIA before deployment. Engineered to integrate with the GDPR DPIA rather than duplicate it.
- 09Art. 50
Transparency obligations
Applies from 2 August 2026, and was explicitly not deferred. Users must be told they are interacting with an AI system; AI-generated or manipulated content (deepfakes, synthetic media) must be disclosed and machine-readable marked. Article 111(4) gives systems placed on the market before 2 August 2026 until 2 December 2026 to meet that marking duty.
- 10Art. 53 · 55
General-purpose AI models
Binding since August 2025. GPAI providers must maintain technical documentation, publish training-data summaries, and respect EU copyright; models posing systemic risk carry additional evaluation, red-teaming, and incident-reporting duties.
Article 99: three fine bands, and a real SME cushion.
The AI Act's fines scale with the severity of the breach and are set as the higher of a fixed amount or a percentage of total worldwide annual turnover. Prohibited practices under Article 5 sit in the top band; the high-risk and transparency obligations that bind through 2026–2028 sit in the middle; supplying incorrect or misleading information to authorities sits at the bottom.
There is a genuine cushion for smaller organisations, and it is not the same cushion for everyone. Under Article 99(6) an SME or start-up pays the lower of the fixed amount or the percentage across all three bands — the inverse of the rule for large enterprises. A firm with €2M turnover therefore faces a top-band ceiling of €140,000, not €35M. The Omnibus added Article 99(6a) for small mid-caps, but only for the €15M/3% and €7.5M/1% bands: an SMC that breaches the Article 5 prohibitions still faces the higher of €35M or 7%. And the reputational and procurement consequences of an undocumented AI estate — surfacing in any customer, partner, or insurer due-diligence conversation — typically bite long before a regulator does.
Prohibited practices (Art. 5)
€35M / 7%
whichever is higher, of total worldwide annual turnover. Only SMEs get the lower figure in this band.
High-risk & transparency obligations
€15M / 3%
most operator obligation breaches, Article 50 included. GPAI model providers are fined by the Commission under Article 101, on the same ceiling, from August 2026.
Incorrect information
€7.5M / 1%
misleading or incomplete information to authorities. SMEs and small mid-caps pay the lower figure.
Typical timeline
The Omnibus delay is planning runway, not a holiday. A Regulated AI Deployment engagement plus pilot rollout, sign-off, and a remediation cycle is a seven-to-nine-month project, so the latest realistic kick-off for December 2027 is Q1 2027. And the nearest AI Act deadline is not 2027 at all — it is 2 December 2026.
1–2 weeks
Discovery & classification
AI estate inventory, role determination, per-system risk-tier classification, and a Service Profile that scopes the rest of the engagement.
Following discovery
Risk & gap analysis
ISO/IEC 23894-aligned AI risk assessment per system, AI Act gap analysis for your role, and a remediation roadmap with the real deadlines mapped to your calendar.
Deepest phase
Governance & controls
AI policy, roles, literacy programme, vendor due diligence, and the role-specific layer — FRIA for regulated deployers, technical documentation and QMS for providers, evaluation protocols for GPAI integrators.
Pre-deadline
Readiness & validation
Internal review against your obligations, evidence-pack assembly, gap closure, and a management-body sign-off pack ready for audit or regulator scrutiny.
FAQ