Building AI Features That Won't Fail EU AI Act Scrutiny
Why EU AI Act compliance is a product strategy decision, not something to hand off to your legal team
Your legal team is asking whether your AI features comply with the EU AI Act. And the honest answer, for most CPOs I've spoken with this year, is: you don't know. Not because you haven't cared, but because compliance was never built into the roadmap. It was something to deal with later.
Later is here.
The EU AI Act started applying in stages through 2025 and 2026. If you're a CPO at a European B2B SaaS company shipping AI features, autonomous agents, recommendation engines, continuous monitoring, anything that acts on behalf of the user without explicit initiation, you now own a set of product decisions that nobody on your legal team can make for you.
"CPOs who treat EU AI Act readiness as a legal constraint will be forced into reactive roadmap rewrites. CPOs who treat it as a product strategy input will use it as a sales asset."
— Fredrik Göth
Your Risk Tier Is Determined by What Your Feature Actually Does
The EU AI Act classifies AI systems by risk, and the classification is based on function, not technology. Autonomous decision-making, continuous behavioral monitoring, and user-facing recommendations without human initiation are in the highest-risk categories. That covers most of what B2B SaaS teams have been shipping in the last 18 months.
My experience is that CPOs are surprised by this. They think of their AI feature as a productivity add-on. The regulation looks at it and sees a system that acts on users, makes consequential recommendations, and operates without a human in the loop. That's not a minor distinction.
If you've shipped an AI agent that continuously interrogates your users' behavioral data and recommends next actions, similar to what Amplitude now offers with their autonomous analytics agents, you've widened your compliance surface area beyond a single feature. You're not just managing one AI output. You're managing a continuous system that acts, logs decisions, and affects user behavior at scale. That requires a different approach to how you scope and document AI behavior from the start, not after a legal review.
Model-Level Governance Is Now a Product Decision
This is the one most CPOs are treating as an infrastructure problem. It isn't.
Which AI model runs which feature, with what constraints, under what conditions, these are product decisions with regulatory weight. Notion's choice to let enterprise customers control which AI models their agents can use isn't just a governance nice-to-have. It's a signal that model-level control is becoming a competitive differentiator in European enterprise procurement, where DPA questionnaires are already asking exactly this question.
If you can't answer "which model made that recommendation, with what instructions, constrained by what rules", you can't answer the EU AI Act's auditability requirements either. And you can't answer the question your next German or Dutch enterprise prospect is going to put in their security review.
This belongs in your product principles. Not your infrastructure backlog.
The Three Questions Every AI Feature Needs to Answer
I've started using these three as a quick product-level check when reviewing AI features in roadmap sessions:
**Transparency:** Does the user know AI is acting on their behalf? Not buried in terms of service, actually visible in the moment. If the answer is no, that's a product decision to fix, not a legal footnote to add.
**Human override:** Can the user reject or override the AI output? This isn't just a UX consideration. The EU AI Act requires meaningful human oversight for high-risk systems. If your AI recommends an action and the user has no obvious way to say no or take a different path, you have a compliance gap and a UX problem at the same time.
**Logging and auditability:** Can you show what the AI did, when, and on what basis? This is where most teams I've worked with are weakest. The model call happens, the output goes to the user, and nothing is stored in a way that lets you reconstruct the decision later. Building auditability in from the start is a fraction of the effort of retrofitting it after a legal review forces your hand.
If you're already thinking about European data handling in your PM tool stack, the [GDPR-Compliant PM Tools: The European Buyer's Guide](/blog/gdpr-compliant-product-management-tools-european-guide) has relevant overlap here, the same procurement conversations that surface GDPR gaps are now surfacing AI governance gaps too.
Compliance as a Sales Asset, Not Just a Constraint
CPOs who treat EU AI Act readiness as a legal constraint will be forced into reactive roadmap rewrites. CPOs who treat it as a product strategy input will use it as a sales asset.
European enterprise procurement has changed. Security reviews include AI governance questions. Buyers ask who controls the model, what data it trains on, and whether they can audit AI decisions. If you've built for that, you have an answer. If you haven't, you're losing deals to competitors who did.
Start with the three questions above. Run them against every AI feature currently in your roadmap. The ones that can't answer all three are your compliance gaps and your product gaps. Fix them together.
Fredrik Göth is a CPO and product leadership consultant working with product teams across Europe.
References
- European Parliament and Council — EU AI Act (2024)
- Fredrik Göth — GDPR-Compliant PM Tools: The European Buyer's Guide (2026)
Ready to try it yourself?
Sign up free and start connecting strategy to impact today.
Related reading
- GDPR-Compliant PM Tools: The European CPO's Buying GuideThe EU AI Act has changed how European CPOs evaluate PM tools — GDPR compliance alone is no longer enough. This guide covers the three gates every PM tool must clear and how to build a procurement policy that keeps your team ahead.
- The Product Vision Framework That Actually SticksMost product visions sound right but fall apart under pressure. Learn the three-layer framework that makes your product vision operational — from board meetings to daily roadmap decisions.
- The Product Vision Framework CPOs Actually NeedMost product vision statements sound compelling in the all-hands but collapse under prioritisation pressure. Here's the structural framework CPOs need to make vision operational.