Process

How your website becomes a source that AI systems can trust.

Nearly every mature website contradicts itself. Not from negligence, but because over the years many people have written on many pages and no one has laid all the pages side by side. Generative AI systems do exactly that: They read everything. If they find three versions of the same fact, they guess—or invent a fourth. Aivis-OS, however, works in two phases: First, the historically accumulated damage is eliminated; from then on, real value is built.

Aivis-OS transforms contradictory statements into a verified, machine-readable source. We measure and document whether and how AI systems react to it with forensic precision.

Phase A · Onboarding · One-Time

Your website is freed from contradictions, strategically condensed if desired, and technically connected after passing the QA gate. In the end, the clarified domain, within the verified scope, is free of contradictions, and every URL is delivered in a structured manner. No scenario and no monitoring yet.

Phase B · Governance · Monthly, Optional

Month by month, a scenario is completed until your agreed build plan is worked through. The build has an agreed end; after that, it is maintained and guarded.

Your own domain is the only place on the web where your company is not a guest. That’s why sustainable AI Visibility is created precisely there. But the sequence is the product: enriching content for machines before contradictions are resolved only makes errors more permanent. The journey to becoming a primary source is not an endless process. Its scope is agreed upon as a build plan; the end is visible from the start.

Aivis-OS models the domain as a shared data network instead of treating each URL in isolation. The same entities are uniquely referenced across page boundaries, and their relationships are jointly verified. We are not aware of any other provider that resolves a domain’s contradictions before structuring it.

The Beginning

How did we find each other – a recommendation from your agency, a conversation, your own inquiry? However it happened: Your curiosity deserves attention, and the free compact audit would be our first contribution. We allocate it deliberately – to companies where it will be read.

Free

We read your website the way an AI reads it – you don’t need to install anything. The compact audit counts your conflict groups, estimates the number of your core entities and scenario fields, and substantiates the findings with one or two examples. The conflict count later determines the clarification package; core entities and scenario fields form the initial planning basis. An answer baseline is only created with Scenario 1 in B1.

Free · One Condition

We discuss numbers and examples as soon as it is clear who in your organization is responsible for published statements. The limit of the free step: You receive the count, the estimates, and selected evidence. The complete list of occurrences is part of the commissioned clarification package or the separately available full audit.

Binding Cap

Onboarding as a sum: The counted conflict groups determine the fixed price of the joint clarification package. Added to this is your chosen level of responsibility for implementation; domain condensation is an optional project with a confirmed fixed price. The process concludes with the complete pipeline run at €3 per actual URL. There is no additional connection, delivery, QA, or structural flat fee.

The total is a binding cap: After condensation, we recount conflict groups and URLs – a target number is not predicted beforehand. If the level of the clarification package or the actual URL inventory decreases, the difference will be credited. The total can only increase with your new signature.

Onboarding · Optional

We define the most important guiding scenarios and examine all content, including available SEO data. Three candidate groups are assessed separately: duplicate content; outdated content whose updating is no longer economical; and content that deviates from the page’s purpose or your positioning and acts as a disruptive signal.

The result is a reasoned decision per URL – keep, realign, merge, or remove – with an editorial action and redirection plan. Your team or agency implements, we review and recount. How many URLs will remain cannot be reliably predicted before analysis and implementation.

Onboarding · Core

The joint clarification package: Each conflict group receives exactly one decision – prepared by agents, overseen by you. Agents generate the full audit, decision papers, and the complete editorial and action plan; Aivis-OS checks exceptions and completion. Corporate truth is not generated. It is accounted for.

1 · Clarify and hand over: Your editorial and IT teams implement themselves; the subsequent QA gate acceptance costs from €1,900.
2 · Lead implementation: Your team implements, Aivis-OS leads the process with two reserved person-days per week, system queries, moderation, and ongoing review. Leadership packages are available for 4, 8, 12, or 16 weeks; QA gate and a follow-up review are included.
3 · Full implementation: Aivis-OS additionally takes over editorial and IT. The execution package is calculated from the confirmed action plan and agreed upon as a fixed price with a cap – never as a flat multiplier.

We implement the data layer in all three variants via our plugin or an API. For content corrections, assuming centralized control, we recommend implementation via your CMS interface: this is how we work internally and with several clients, saving both time and costs.

“Never before—otherwise you cement errors.”

The gate confirms: All conflict groups identified within the verified scope are decided, implemented, and closed after review. Only then is content built for machines. What is checked is consistency, not completeness; there may still be gaps, but no competing truths. The model may vary. Your facts may not. Those who have cleaned up with their own team join here: We check the result, approve it, and only then start the basic delivery.

Onboarding · Completion

“For every URL. Still without a scenario.”

Make your domain the place where the correct version begins: After passing the QA gate, the complete pipeline run processes the clarified domain. High-quality structured data is generated for each URL. Standard export and WordPress delivery are included; only individual CDN and enterprise CMS connections remain separate projects.

This concludes onboarding: The domain, within the verified scope, is free of contradictions and machine-readable. It does not yet contain a scenario, no pre-delivered core entity package, no monitoring prompts, and no answer baseline. The specific scenario in B1 determines which entities and values are required.

Governance · Build Phase

If you book Governance, Scenario 1 begins here. We define a specific customer query; the system determines the necessary entities and monitoring prompts. The prompts are sent to the AI systems and generate the answer baseline. After that, for each entity, we see which values are already known and which are missing. Missing values are supplemented in the visible content and in the machine-readable layer. This creates new structured data and new internal and external relationships. One month after the baseline, it is checked again.

Each subsequent month begins another scenario. A scenario bundles up to ten involved entities and up to ten verification questions. A maximum of two scenarios remain open simultaneously. If both are not yet implemented by the client, a third will not start; the contract automatically switches to the appropriate maintenance plan until a slot becomes free. The pause extends the open build plan by the same number of months. Nothing expires, and you don’t pay a build price for waiting. Once the agreed build plan is completed, the build price ends.

Governance · Maintenance

After the build, the “Maintain” plan preserves the state. Direct entry after onboarding is also possible: In this case, B2 initially monitors the domain and basic delivery, but starts with zero monitored scenarios and zero monitoring costs. Only a scenario defined in B1 generates prompts and a series of measurements. Three instruments remain clearly separated:

Conflict Watch

checks your entire website daily and reports new contradictions early, with a decision template – so you can correct before AI systems adopt the wrong version. Before each deployment to a new page, it checks the page itself.

Attestation

queries nine AI systems at fixed intervals and verifies the answers against your approved facts – correct, missing, incorrect, or outdated, assessed per core entity. Previously processed scenarios are also regularly re-measured this way.

Measurement Series

accompanies each processed scenario: baseline, implementation, and renewed verification in the subsequent attestation.
Growth Without Surprise

New scenarios arise from your business, not from our imagination: a new product, a new language, a relaunch, an acquisition – or an entity that gains weight on the watch list. Then the “Build” plan returns for the counted new scenarios.

Your scope never grows silently – neither does your price.

A clarified domain has a dual effect: directly on machines that read it, and indirectly through everyone who adopts its statements – employees, agencies, editorial teams, partners, and portals. First source. Then echo.

The number of core entities, not the URL count, determines the Governance plan. Up to 10,000 URLs, the path remains calculable. Above 50 core entities, “Program” works on two to three scenarios in parallel, with monthly attestation and API access. Two parallel scenarios start at a service contribution of €7,000 per month, three at €9,600. Additionally, there is €3 per URL and complete run, and €60 per monitored scenario, language, and month.

Pilot

The complete path, small: one business unit · proof before scaling

Domain Condensation

Optional Domain Condensation · Full scan, SEO data, and editorial action plan

Waves

Division by division through onboarding · plannable in next-year budget

Program

2–3 scenarios in parallel · monthly attestation · API access included