A licence that covers the platform and your scope, with an allocation of deliverables included, and nothing counted per question or per token. You know at signature what the year covers, and the price of each deliverable beyond it is written down before you sign, not discovered in March.
Because the scope changes everything: deployment mode, sector, countries under legal watch, knowledge spaces, legal entities, connected sources, annual volume of deliverables. A displayed amount would be wrong for most situations. The pricing principle, however, is public: it is what this page is about. Pricing is then on quotation.
A per-question meter encourages you to give up on a file to save money, which is exactly the opposite of the intended use. So we count what comes out: the deliverable, not the question. The credit is used when the file is opened, once only: as long as the source document and the scope analysed do not change, reviews, corrections, regenerations and successive versions consume nothing.
The more deliverables you produce, the lower the credit price, in tiers written into the quote. And when you repeat the same type of deliverable on a framework that is already loaded — a bid evaluation campaign, a renewed audit — each deliverable consumes fewer credits once the threshold is reached, a threshold assessed type by type. The vendor’s interest and the client’s point the same way: that the platform is genuinely used.
Seven minutes to connect the sources, no content migration, no answer library to write in advance: the “integration” line that weighs down software projects does not exist here.
Two tiers, and nothing else. The licence: the deployment mode, your sector pack, legal watch on the countries subscribed, your knowledge spaces, your legal entities, the connected sources, the Watch module, the service level. The deliverables: the volume you expect over the year. The number of users does not come into it.
The licence covers the platform and your scope, whatever volume you produce: the core platform according to the deployment mode, your sector pack, one knowledge space, your legal entities, one connected source, the Watch module if you subscribe to it, the service level. Legal watch is chosen country by country.
The number of users is unlimited, and the third parties you invite to fill in a questionnaire once a year add nothing to it.
The type of deliverable, then your figures. Two assumptions, set out here.
These figures stay in your browser. No form, no data transmitted.
640 hours a year spent producing these deliverables, or 91 days of work, at an internal cost of €54,400.
544 h
freed up per year, or 78 expert days given back to their core work, and €46,240 of internal cost avoided.
At consultancy rates, this substituted volume represents €78,000 of services.
The remaining time is review and approval: it does not disappear, and that is intentional.
Estimate calculated from the type of deliverable, the three values you entered and an 85% reduction in time spent. It has no contractual value and does not prejudge the result on your own documents; that is precisely what the demonstration on your documents lets you check.
The calculation is deliberately simple and leaves out the indirect effects our clients mention most: the files you can now respond to, the deals not lost to delays, and the non-conformities avoided because a gap was spotted six months before the audit.
We may as well write it here rather than let you discover it in the quote. Three things cost money, and they are the three reasons our answers hold up.
72 function agents, 12 sector agents and a librarian, built from real compliance practice. This is not a general-purpose model with a well-written prompt. Where it comes from.
One private instance per client, one model per client, and an air-gap mode available. That costs more than a pooled architecture; it is the price of the commitment “nothing leaves your environment”. The details.
Keeping grids up to date when texts change is continuous work, not a feature delivered once. Optivalue Watch.
Frequently asked
Neither, in the sense you mean. We charge per deliverable, and the price of a deliverable is the same for every client. A questionnaire response costs the same whether it covers 40 questions or 400. The credit is used when the file is opened, once only: reviews and successive versions consume nothing.
In SaaS, no: seven minutes to connect the sources is enough. In private cloud or on-premise, installation is a separate, identified line in the quote, priced before signature, not after.
No. The licence is multi-user and the number of users plays no part in its calculation. An expert who approves three answers a year costs nothing extra, and the third parties you invite to fill in a questionnaire once a year are included. What is counted is what the platform produces.
No, and that is deliberate. A self-service trial on an empty account proves nothing about what matters: the quality of the evidence drawn from your documents. Instead, we offer a demonstration on your real documents, with no commitment.
Two things are priced in your quote, and you need to know them before signing. First, your annual allocation of deliverables: beyond it, each additional credit is charged at your tier price, written into the quote and decreasing with volume. We alert you at 80% and then at 100%, nothing is charged without you seeing it coming, and an overrun never blocks the production of a deliverable. Second, the capacity of your knowledge spaces: 10,000 pages per space in SaaS, one page being 3,500 characters of extracted text. In hybrid and on-premise deployments, since the infrastructure is yours, nothing is capped. When a space is full, only the indexing of new documents stops: production on the corpus already indexed continues.
Yes, and we may as well say so here rather than let you find out later. An annual revision applies, according to a formula known in advance that does not change. “Predictable” therefore does not mean “frozen”: it means that this formula applies to the licence and the credit price, not to your consumption. Producing more deliverables triggers no revision.
The seven minutes are real and cover what they say: opening the account, connecting a first source, uploading a questionnaire and getting answers the same day. No IT project is required for that, and that is the point. Deploying across an entire document estate is something else: bulk import, connectors to your document management system or ERP, approver training, configuration of approval workflows. These services exist, they are useful beyond a certain size, and they are charged separately, each one named and priced individually in your quote. You can start without them and add them later; the reverse would be a project in disguise.
Your data is returned in a reusable format, then deleted on an agreed date with an auditable attestation. The reversibility clause is set out on the sovereignty page.
You will know what the platform does with your real document estate, and we will know which scope to price. One hour, no commitment.