The product
Not a chatbot. A system that works.
DOLMIR Software reads the requests that arrive by email, understands them, checks them against what your company knows and prepares the reply to the customer. Then it waits for a person’s yes. Today it is a prototype on the request-for-quotation process, tested only on simulated data.
Product status
prototypeReads
The text of emails; attachments not yet
Verifies
Customer records and item catalogue
Prepares
The reply to the customer, for approval
Does not
Quotes, prices, management system
Data
Demo with simulated data
The product, live, on a request to the demonstration company · simulated data
Sales inbox
3 messagesFonderia Bianchi S.p.A.
08:41
Order confirmation no. 4471/2026
Officine Rossi S.r.l.
09:12
Request for quotation — 2,000 pcs SL-441
Good morning, please send us a quotation for 2,000 SL-441 brackets as per the attached drawing, delivery by 30/09. Kind regards, Meccanica Rossi.
Disegno_staffa_rev3.pdf
newsletter@forniture-online
09:15
Offer of the month: tools -20%
DOLMIR Software
1 conflictReading
Customer
Officine Rossi S.r.l.
sender · customer records
Quantity
2,000 pcs
email text
Code
«SL-441» · bracket
email subject and text
Delivery
30/09/2026
email text
Attachment
Disegno_staffa_rev3.pdf
attachment received · not read
Checks
Customer on record
customer records · Officine Rossi S.r.l.
Code in the catalogue
catalogue · «SL-441» matches SL-4410 and SL-4415
Two possible items. DOLMIR does not choose: it flags it and asks.
Quantity and delivery
2,000 pcs · 30/09/2026 · from the email text
Outcome
decision requiredDecision required
Which item does the customer mean?
SL-4410 or SL-4415: the person who knows the customer knows, not the software. The reply asks for confirmation, together with what is already clear.
Approve · Revise
Planned actions · after the yes
- ○Reply sent to the customer
- ○Request passed to whoever prepares the quote, already read and checked
- ARRIVES
- READS
- VERIFIES
- STOPS
- ACTS
A request arrives, in the middle of everything else.
The system works out what it is and extracts the data, each value with its source.
It checks them against your customer records and your catalogue.
The code written in the email matches two items. The system does not guess: it asks a person.
Approved: the reply goes out to the customer, and whoever prepares the quote finds the request already read and checked.
Demo with simulated data: the company, documents and amounts are invented.
The problem it solves
A request arrives. Then two days go by.
It arrives by email, with a drawing attached. Someone reads it, works out who the customer is, checks codes and quantities, looks for what is missing, writes back to ask. Only then can the quote begin. Meanwhile the customer waits — and the person doing it is the one needed elsewhere.
The customer gets a reply within the hour, not in two days
A confirmation of what was understood and what is missing, ready to approve.
Whoever prepares the quote finds the request already read and checked
Customer recognised, data extracted with its source, exceptions already declared.
Nothing is invented
Where a value is missing or does not add up, the system stops and asks. It is its most important function.
How it works
Five movements, always the same.
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.
Interactive demonstration
Watch it work on four requests.
Four emails, four different outcomes. Choose a case and follow the five steps — or let it run. The approval button is real: without a yes, nothing goes out.
Demonstration scenario · simulated data
Step
01 ARRIVES
A request for quotation arrives in the sales inbox, with a drawing attached.
Sales inbox
Officine Rossi S.r.l.
09:12
Request for quotation — 2,000 pcs SL-4410
Good morning, please send us a quotation for 2,000 SL-4410 brackets as per the attached drawing rev. 3, delivery by 30/09. Kind regards, Meccanica Rossi.
Disegno_SL-4410_rev3.pdf
acquisti@officinerossi.example
Reading and checks
Reading
Customer
Item
Quantity
Delivery
Attachment
Checks
Customer on record
customer records · Officine Rossi S.r.l.
Item in the catalogue
catalogue · SL-4410 · laser-cut bracket
Quantity given
2,000 pcs · from the text
Delivery date given
30/09/2026 · from the text
Outcome
Nothing leaves from here until the request has been read, checked and — where needed — decided by a person.
Demo with simulated data. The company, customers, items and messages are invented.
The context
Every piece of data arrives with its history.
A request never comes alone: it has a customer, an item in the catalogue, an attached drawing, a person who has to decide. DOLMIR links what it reads in the email to what the company already knows, and whatever does not add up surfaces on its own.
Tap a record to see what the system knows about it.
Officine Rossi S.r.l.: one customer, all of its records. Orders, quotes, documents and conversations linked across the management system, the CRM and email — without copying anything.
The request that has just arrived. Under verification: the code as written matches two items in the catalogue.
ambiguous code · SL-4410 or SL-4415
The code in the email is incomplete: the catalogue holds both SL-4410 and SL-4415. The system does not choose between them.
It confirms what has been understood — quantity, delivery — and asks which item they mean. It goes out only after a yes.
The attachment arrives with the email and stays linked to the request. Its content is not read yet: the extracted fields come from the email text, each with the line it comes from.
The person the system hands the request to, already read and checked, with the open question.
Tap a record to see what the system knows about it. · Relations in the demonstration company: simulated data.
Today, by hand
Seven steps, two people, four places.
Illustrative example on the demonstration case. Steps and counts describe the demo scenario, not a measurement at a client.
Today, by hand
- 01Someone opens the email
- 02Reads the attached drawing
- 03Looks up the customer in the management system
- 04Checks the code in the catalogue
- 05Copies the data into a spreadsheet
- 06Asks whoever decides to confirm
- 07Writes to the customer
With DOLMIR Software
- 01The request is read and checked as soon as it arrives
- 02Exceptions are already declared
- 03A person approves the reply
- 04Whoever prepares the quote starts from checked data
It does all the work. It stops only where judgement is needed.
A language model always has a fluent answer available. DOLMIR Software is built against that tendency: every value has a source, every value is checked, and where there is no match the system declares «undetermined» instead of producing a plausible number. The person is not a courtesy step: the person is the gate.
Architecture
Above your systems, not in their place.
01Input
The sales inbox, read-only. Emails as they arrive; attachments are logged, not yet read.
02Context
Customer records and item catalogue, entrusted to the system — even in a spreadsheet.
03Understanding
Reading, extraction with sources, five completeness rules.
04Verification
Every value checked against customer records and catalogue, with a stated outcome.
05Gate
Decision required or undetermined: the case goes to a person.
06Output
The reply to the customer, prepared; sent only after the yes.
Product status
What it does today, what it does not, and what comes next.
- It reads the text of emails in the sales inbox
- It recognises the customer from the sender, against the customer records
- It extracts quantities, codes, descriptions and dates, each with its source
- It checks against customer records and the item catalogue
- It declares what is missing or does not add up: five completeness rules
- It prepares the reply to the customer; a person approves and sends it
- It does not calculate prices or prepare quotes
- It does not compare with past requests
- It does not read from or write to the management system or the CRM
- It does not promise delivery dates, other than the one the company has configured
- It sends nothing on its own
The quotation path — with the customer’s price list imported and every figure tied to a verified line of that list — is on the roadmap. It will appear on this page when it is in production, not before.
What it takes to start
- Read access to the sales inbox
- Customer records and item catalogue, even in a spreadsheet
- A person who approves
The useful way to judge it is to watch it run on five real requests you received in the last two weeks — including the ones where it stops.