How do you turn the EU AI Act into a lead source for your software?

You turn the EU AI Act into a lead source by answering the questions your buyers are asking you right now about their use of AI. Build one page per question: an explainer, “does our use case count as high risk?”, a checklist, a deadline page and your own AI Act page for procurement teams. That way buyers find you at the moment they screen vendors.

Your product has AI features, and in tenders your sales team increasingly receives an AI Act questionnaire. Marketing has not a single page on it. This is how we use content marketing to turn a regulation like this into a source of pipeline. How to keep this kind of content accurate and current is covered in regulation as a lead source.

What do software vendors need to know about the EU AI Act?

The AI Act sorts AI systems into four risk levels: unacceptable risk, high risk, transparency risk (limited risk) and minimal risk. Your buyer wants to know which level your feature falls into. This is the situation as of 28 September 2026, according to the European Commission:

The high-risk dates were moved by the AI Omnibus. A political agreement on it was reached on 7 May 2026, and the amendment entered into force on 27 July 2026.

AI literacy changed too. According to the Commission, AI literacy remains an obligation for providers and deployers of AI, but the Omnibus removed the requirement for a “sufficient” level. Anyone deploying high-risk systems must still train the staff who carry out human oversight. National market surveillance authorities supervise from 2 August 2026.

What do the transparency rules mean for your product?

The transparency rules affect almost every software company that uses AI. Anyone using a chatbot must know they are talking to a machine. Certain AI content, such as deepfakes, must be visibly labelled. For machine-readable marking of AI output, systems already on the market before 2 August 2026 get a transition period until 2 December 2026.

The questions and answers on Article 50 make clear who has to do what. For a chatbot, the obligation lies with the provider, so often with you. The notice comes at the start of the first interaction, unless an average, well-informed user can already see it. Read that exception strictly. Labelling a deepfake, on the other hand, is the job of the deployer of the system, often your customer.

Your buyer wants to know what you handle and what they do themselves. Put it in a table:

What questions do buyers ask software vendors about the AI Act?

Procurement, legal and IT ask the same questions:

1. What AI is in your product, and which model does it run on?
2. Which risk class does that feature fall into, and our use of it?
3. What documentation do we get about the system, the data and the limits of the output?
4. How do users see that they are working with AI?
5. Can we switch off the AI feature or let a human decide?
6. How do you help our team with AI literacy?
7. Who follows up when the rules or the dates shift?

Put those answers on your site, and your buyer and their AI assistant will find them before they call.

Which pages do you build around the AI Act?

Don’t build a generic “what is the AI Act” page as your only piece. Plenty of others already write that, including the Commission itself. Build the pages where your product is the answer.

Sales mostly sends along the page for procurement teams. For the comparison, follow our approach to comparison pages.

How much search volume is there around the AI Act, and what does a click cost?

More than you think, and the clicks are cheap. These are average monthly Google searches over the last 12 months (Google Ads data, September 2026, cost per click in USD):

A buying term costs far more: the median across 106 Benelux software terms is about USD 22 per click. Check yours in our CPC benchmarks by industry or work it out with the click-or-article calculator.

Specific questions such as “ai act risk classes” show no volume in the tools. Yet people do search them, as long questions. New pages get a bigger share of their impressions from queries of seven words or more than older pages do. At Hedgehog that is 19% versus 10%, at Kaizo 16% versus 10%. So write those questions word for word as subheadings, as in answer-first writing for AI.

What is still changing in the AI Act?

The Omnibus shows the risk. Anyone who published a start date for high risk before the Omnibus may now have an outdated page. Update the date on the same URL and add the real update date. How to do that systematically is covered in content refresh.

Three points to track over the coming months on the sites of the Commission and your national supervisory authority:

• 2 December 2026: the end of the transition for marking AI output. According to the Commission, December 2026 also brings a new ban on AI that creates non-consensual intimate images or child sexual abuse material.
• National implementation: how Belgium and the Netherlands organise supervision and penalties.
• The high-risk dates: currently 2 December 2027 and 2 August 2028, but check them with every announcement.

Each point is a news moment: update your page within a week.

When we are not the right choice

If your product itself has to go through a conformity assessment as a high-risk system, you need a lawyer first, not content. If there is no AI in your product and your customers don’t buy AI, this regulation will bring you little. And nobody can honestly guarantee that you will appear in AI Overviews, us included.

If it does fit, content starts at 950 euros per month for 5 articles, with a minimum of three months. The broader plan is in reducing your dependence on Google Ads.

Frequently asked questions