When an AI User Can Become a Provider
Why organisational roles must be assessed against the system and the change By Manfredi Marrocco A company buys an AI system and describes itself as “the customer.” The description makes sense commercially. It does not
Why organisational roles must be assessed against the system and the change
By Manfredi Marrocco
A company buys an AI system and describes itself as “the customer.” The description makes sense commercially. It does not settle every legal responsibility under the EU AI Act.
The role depends on the system, the activity performed and the applicable legal provisions. A change to a system's branding, design or intended purpose can alter the analysis. The decision that matters is not simply who paid the invoice; it is what each actor has done.
The legal framework and timing
The consolidated text of Regulation (EU) 2024/1689, as available on 31 October 2026, defines roles including provider and deployer and establishes rules for different kinds of AI systems. Article 25 identifies circumstances in which a distributor, importer, deployer or other third party is considered a provider of a high-risk AI system for the regulation's purposes. Those circumstances include specified branding, substantial modification and changes to intended purpose, subject to the article's conditions.
Timing matters. The Commission's Article 113 service desk identifies different application dates, including later dates for specified high-risk system categories after amendments in the Digital Omnibus. A role analysis should not describe a future obligation as already applicable. Check the latest consolidated text, relevant transitional provisions and the particular system before applying a conclusion.
This article is a governance analysis, not a legal opinion on a specific system. It does not assert that every configuration change makes an organisation a provider.
A fictional change of purpose
Imagine a company, Eastmere, that obtains an AI system designed to organise general customer enquiries. A business unit proposes adapting it to rank job applicants. The vendor calls the product “general purpose,” and the project manager considers the company merely a user.
The proposed use raises a classification question: does the system, as deployed and intended to be used, fall within a high-risk category, subject to the regulation's definitions, conditions and exceptions? The answer cannot be inferred from the vendor's marketing label. The organisation needs to examine the actual intended purpose and the relevant legal criteria.
Article 25(1)(c) concerns, under its stated conditions, modification of the intended purpose of a system not classified as high-risk so that it becomes high-risk under Article 6. A change in use is not automatically sufficient in every case; the conditions, timing and factual allocation of responsibilities matter.
Ask what changed
An internal review should document the original system, intended purpose and provider's instructions. It should then describe the proposed changes: new purpose, integration, branding, input data, outputs and deployment context. A change that appears small to a project team may be significant to classification or the allocation of duties; conversely, a routine configuration choice should not automatically be labelled a substantial modification.
| Question | Why it matters |
|---|---|
| What was the original intended purpose? | It establishes the baseline against which the change is assessed. |
| Who made or requested the change? | Commercial, technical and legal responsibilities may sit with different actors. |
| What does the modified system do in practice? | Actual use and outputs can differ from a project's description. |
| Does the relevant classification apply? | Obligations and application dates vary by system and context. |
| What documentation and access are available? | A new responsible actor may need evidence and cooperation from the original provider. |
The questions are a proposed governance aid. They do not replace the definitions and conditions in the regulation or determine the result for Eastmere.
Eastmere should record two separate conclusions: its role assessment under the relevant provision and the date on which the resulting duties apply to the particular system. A correct role analysis can still produce an incorrect operational instruction if it uses an obsolete application date. Equally, a later date does not make today’s design decisions harmless. Preserve the classification facts and timing source as separate, versioned inputs to the change decision.
The contract cannot answer every question alone
A supplier agreement may allocate technical tasks, information sharing and cooperation. It should be reviewed, but a contractual label cannot change the facts of how a system is modified and used. The AI Act's allocation of roles must be analysed under the applicable provisions.
The amended Article 25 also addresses cooperation and information in certain circumstances. Its detailed conditions, exceptions and application dates should be read directly. An organisation considering a material change should know whether it can obtain the documentation, technical access and assistance needed for its planned responsibilities before making the change.
This is a practical problem as well as a legal one. If the new use depends on evaluating a model in a different context, but the organisation cannot obtain the necessary information or test the relevant behaviour, it may be unable to support a responsible deployment decision even before any specific legal conclusion is reached.
A role assessment should survive a product update
Eastmere can retain a short versioned record identifying the system, supplier, intended purpose, classification rationale and applicable legal dates. It should name the facts on which the conclusion depends. If the system is later offered under Eastmere's own branding or its purpose changes, the owner can see which assumptions require review instead of starting from a purchasing label.
A technical release can also change the analysis without being described as a new product. A supplier might add an automated action, alter an integration or change the information available to human reviewers. Those changes do not automatically satisfy the legal definition of substantial modification. They are reasons to examine the relevant definition and determine whether the existing assessment remains valid.
The review should avoid two symmetrical errors. Treating every minor setting as a provider transformation can make governance unusable. Treating all changes as ordinary customer configuration can conceal a material shift in purpose or responsibility. The applicable legal test, supported by the facts and current text, should decide the question.
Where a question cannot be resolved from available documentation, record it and limit the deployment decision accordingly. A controlled internal evaluation may be a useful next step, subject to applicable law, but it should not be represented as permission for an unrestricted consequential use. Clear boundaries allow technical experimentation and legal analysis to proceed without quietly turning a pilot into a service whose responsibilities nobody has assessed.
Build a change gate
A proportionate change gate can ask the project team to identify the system and supplier, describe the proposed use, record affected people and decisions, flag potential high-risk contexts and route the proposal to legal, privacy and technical specialists. The gate should also record the applicable timing and unresolved questions.
If the role or classification remains uncertain, possible responses include narrowing the pilot, seeking further information, postponing a consequential use or obtaining specialist advice. These are options, not universal legal permissions. Once the change is approved, the organisation should monitor further modifications and supplier updates that could alter the assessment.
The useful question is not “Are we the customer or the vendor?” It is “What activity are we performing with this system, which legal role follows from that activity, and when do the relevant provisions apply?” That question keeps the analysis attached to the system rather than the purchasing label.
Originally published by Dev.to Security. Aggregated on AIWithGhost for educational purposes — full credit and traffic to the original publisher.