Edific

How we work

A pilot first. Then we build. Then we keep verifying.

Every engagement starts with a pilot on your own documents. What follows is scoped and quoted from what the pilot found — not a seat count, not a fixed tier.

01

Paid pilot

A first, bounded run on your own documents — the same test we publish, applied to your data.

Scoped on a callCredited to the build if you go ahead.
02

Build

Deployed on your own infrastructure — your server or VPS, inside your perimeter.

Fixed quote after the pilotNo pilot, no quote.
03

Ongoing verification retainer

Continued operation, monitoring, and review once the build is live and running.

Retainers begin at €[TODO: Hammadou sets floor]/month

Included at every phase

Evaluation gate on every fieldHuman review queueArt. 28 DPAFull audit trail
Start a pilot

No pilot, no quote. If you’d rather just talk it through first, that works too — reach out and we’ll scope it on a call.

Questions worth asking

Asked before, answered plainly

The questions worth asking before you send us a document. Can’t find your answer here?

Nowhere. Edific runs on your own server or VPS; it is never sent to us or a third party. That is a design decision, not a setting you can turn off.

Edific. A named point of contact owns your engagement end to end — the same person you talk to signs the DPA and stands behind the result. Less brand, more accountability.

On our published test — 3 hard receipts, ~15% for standard OCR — Edific got 18 of 18 fields correct. Small, deliberately hard sample, presented as exactly that. The number that matters is the one from a pilot on your own documents.

Its job is to be wrong loudly. The evaluation gate flags uncertain fields for human review before export, and any slip is traceable in the audit log and fixed at the source.

Scoped per engagement, not per seat — it follows volume, document types, and infrastructure. You get a fixed quote after a pilot. No pilot, no quote.

Yes, structurally. Processing happens on your own infrastructure, and the Art. 28 DPA describes the architecture as it actually works.

Next step

See it on your own documents

Not a deck. Not a demo dataset. Send a batch of your real documents — the difficult ones — and get back verified, structured data with every field scored and logged. Then decide.

Runs on your infrastructure. Covered by a DPA. Edific accountable for the result.