How it works

A layer above your systems. Not in their place.

Your company’s information lives in different places: email, documents, spreadsheets, the management system, people. DOLMIR adds a layer that reads what comes in, checks it against what the company entrusts to it — customer records and catalogues, even in a spreadsheet — stops where judgement is needed and prepares the action. Nothing is replaced. Nothing is migrated.

Your company

The DOLMIR layer

intelligent layer

01Understanding
It reads emails, attachments and documents; it extracts the data with its source.
02Context
What the company already knows: customer records, catalogues, rules.
03Verification
Every value checked against the context, with a stated outcome.
04Flow
States, owners, hand-offs: what happens next, and who does it.
05Human approval
Where judgement is needed, the flow stops and waits for a yes.

Action

A prepared reply
Data ready for whoever decides
A record of what was done, and by whom

What goes in, what comes out

Emails and attachments, as they arrive
Documents: PDFs, drawings, confirmations, certificates
The context the company entrusts to the system: customer records, catalogues, rules
The decisions people make

Out

Extracted information, each item with its source
Checks with an outcome: matches, does not match, cannot be determined
Declared exceptions, assigned to whoever decides
Prepared actions — replies, drafts, data ready — that go ahead after the yes

The five movements

It arrives, reads, verifies, stops, acts.

Whatever the process, this is its shape. The content changes — a request for quotation, an order confirmation, a document — not the sequence.

01ARRIVES
The information arrives
An email, an attachment, a document, a message: it comes in as it is.
02READS
The system reads and understands it
It extracts the data that matters, each value with the source it comes from.
03VERIFIES
It checks it against what the company knows
Customer records, catalogue, rules: each value either finds a match or it does not.
04STOPS
Where judgement is needed, it stops
It does not invent a plausible value. It says what does not add up and hands it to a person.
05ACTS
After the yes, the action goes ahead
With a record of what was read, verified and decided — and by whom.

The states

Five states, always visible.

At every moment the system says how sure it is and who has the last word. Colour carries a meaning, not a decorative function.

VERIFIED
The value matches the document and what the company knows. It can proceed.
Customer · Officine Rossi S.r.l. · customer records
CONFLICT DETECTED
Two sources say different things. The system shows it; it does not choose.
Code · «SL-441» → SL-4410 or SL-4415 (catalogue)
DECISION REQUIRED
A real fork in the road. The options are ready, each with its evidence.
Which item does the customer mean? · Approve / Revise
UNDETERMINED
The data is not enough. No plausible value is invented.
Item · «the usual bushings» · no match in the catalogue
HUMAN APPROVAL
Nothing goes out without a yes from a named person. Then the flow resumes.
Approved by M. Rossi · 09:31 · recorded

Knowing when to stop is the main function.

A language model always has a fluent answer available. The layer is built against that tendency: thresholds, evidence and explicit gates. Where there is no match, it declares «undetermined» instead of producing a plausible value.

How it stays under control

What it takes to start

Very little. And nothing to migrate.

01An input
Read access to the inbox, or to the documents folder.
02The context
Customer records and catalogues, even in a spreadsheet. The management system stays where it is.
03A person
Whoever approves. The system prepares; the yes is human.

Tell us the problem Explore DOLMIR Software