Human-in-the-loop
The system prepares the drafts and flags the critical points. The manager decides, validates and approves. Nothing is submitted autonomously.
VerdePilot is designed for regulated processes: explainability, evidence and human approval are part of the product.
The system prepares the drafts and flags the critical points. The manager decides, validates and approves. Nothing is submitted autonomously.
Every section shows where the data comes from, which calculations were made and what still needs to be verified.
Architecture designed for enterprise data: permissions, logs, document isolation and integration with existing processes.
VerdePilot operates as a data processor (art. 28 GDPR), with a DPA and declared sub-processors. Customer data is never used to train models.
Hosting and inference in the EU by design, with dedicated residency options to agree during the pilot.
Designed for transparency: mandatory human approval as a control measure and traceable evidence for every output.
VerdePilot is designed for enterprise data, with permissions, logs and document isolation, and it adapts to the customer's constraints. The system prepares drafts and evidence: it does not submit anything autonomously.
No. Your data is used only to prepare your drafts and evidence, never to train shared models.
Hosting and inference in the EU by design. Customer data is not used to train models and the model providers are declared in the DPA, together with the other sub-processors.
Some connections are available, others are configured during the pilot: we map your sources and set up the access needed on your real case.
No. It prepares drafts, evidence and anomalies; submission and responsibility remain with the manager. It is a human-in-the-loop copilot, not an automatic submission system.
Every figure in the draft is linked to its source: any errors surface in review, where every data point is verifiable. Approval and submission responsibility remain with the manager.
Typically 4-6 weeks on a real process. We need access to the data sources and a point of contact for validating the drafts.
The pilot is quoted on scope: data sources, number of sites and the filing you choose. After the pilot you move to an annual subscription, per module and per site.
You move to a subscription on the scope validated in the pilot, expanding gradually to new modules and new sites when it makes sense for you.