Skip to content
ENS.EG

A Quotation Assistant: A Draft From an Approved List, a Person Sends It

31 Oct 2026

The assistant prepares a quote draft from items and prices the company already approved. It does not invent a price, and it does not press send. That is different from extracting data out of incoming documents, and different from a human multi-step form such as the Topaz request.

A quote is late because someone hunts for the last number used on a similar item, copies an old table, and forgets the installation line. The assistant in this article does not "price from experience". It reads the customer request, picks lines from an approved price list, and lays them into a draft with quantity, the approved price, and a total. Then it stops. A person opens the draft, edits if they are allowed to edit, and sends it themselves.

The approved list is the source of the number. If the item is not on it, the draft is marked incomplete and the item is not silently replaced with a near neighbor. Nearness is a human decision: the substitute may be commercially fine or it may be a mistake that changes the margin. An assistant that fills the gap to complete the page looks better in a demo and is more dangerous on send.

What the draft is allowed to do

  • Pick a line that exists on the approved list and nothing else.
  • Use the price approved today, not the price frozen in an old quote.
  • Total the lines from the quantity and the price on screen.
  • Show what it could not find so a quote is not sent incomplete in silence.
  • Store who created the draft and who sent the final version.

A discount that is not on the list is not generated. If discount policy is written bands, the draft may suggest the band and leave approval to whoever holds discount permission. If the policy is not written, the assistant does not invent a ratio in order to look useful. Write the bands, or leave the discount cell empty for a person to fill.

This is not document data extraction

Data extraction reads an incoming document, an invoice or a contract or a table, and turns what is on it into fields. That is a different job: the input is a document rather than a free request, and the output is data rather than a quote to a customer. That job has its own guide. It may sit before or after the assistant: a tender arrives as a file, a bill of quantities is extracted, then your list prices the lines. Do not name both steps as one project in the first sentence, or extraction will be estimated as sending quotes, or the reverse.

The Topaz form is a third pattern

The Topaz Events website is a human path. A visitor completes a quote request across steps and can attach files, and the team replies later. No model there prices the event. That is honest for work that does not have a closed price list for every output. If your work is closer to Topaz, build a clear request form and do not buy a pricing assistant that has no list. If your prices are tabulated, the assistant shortens the search and does not replace the person who signs the quote.

Who sends, and who is accountable?

The send control sits on a human account. A draft that left on its own to the customer is an incident, not a feature. Keep the version that was sent, because that is what the customer will argue from, not the draft edited afterwards. If a seller changes a price, the change is attributed to them and the approved list stays as it was, unless that seller is also allowed to update the list itself. Separating the two jobs stops every quote becoming a silent precedent that changes the price for everyone.

What we ask in order to see if the list is ready

  • The current list file: item, unit, price, and approval date.
  • One real customer request, with the name removed if you need that.
  • Who may change a price before send.
  • Whether discount is written bands or a decision each time.
  • Where the quote is stored after send so the team can return to it.

Pricing questions

Will the assistant price a brand new item?

No. A new item enters the list by a human approval first. Only then may it appear on a draft. Pricing the new item by automatic similarity is outside this scope until you write a similarity rule whose risk you accept.

What about language?

The draft leaves in the language you approve for quotes. If the customer writes colloquial Arabic and the lines are formal, the bridge is a human sentence in the introduction, not a renaming of the approved lines.

What if the price changes in the morning?

A quote that has not been sent yet takes the new price if you set the rule that way. A quote that was already sent stays as sent. Write the rule so a message that already left is not recalculated.

Reading incoming documents is explained in AI document data extraction. A human multi-step request is visible on the Topaz Events website.

Send one page of the price list through start your project. The WhatsApp button under the page fits that same page when the file is small.

Have an idea or a system that needs building?

Tell us about your project in three short steps. We will review it and contact you to agree on the next step.

Start a project