A quote is a promise. If software writes one, the numbers have to come from the company’s book or from a person who typed them. “The model thought $420 sounded right” is not a commercial process.
ServiceBrief AI treats quote generation as matching and drafting, not as creative writing. This post is the rule and the workbench around it.
Detect first, price second
The report pipeline can notice that the visit implies billable work: a coil clean, a part replacement, a return trip. That is quote opportunity detection. It is not yet a price.
Pricing is a lookup against price-book rows the company maintains (including CSV import). Aliases exist because nobody says the SKU out loud the same way twice. If nothing matches, the item is flagged. It does not become a confident line with a made-up unit price.
A draft is a document with a lifecycle
Managers need more than a suggestion in a chat bubble. They need a workbench: title, line items, quantities, optional min/max, customer message, versions, restore, AI revise, approve, send, accept, reject with a reason, dismiss, cancel, PDF, convert to a follow-up.
Sending email is a manager action. Customers can approve or decline on a public link. Staff can record an override when the real yes happened on the phone. Quote discussion in the email inbox can move status when the reply is clearly an answer. None of that requires the model to have invented the dollars.
Ranges and confidence are allowed. Fiction is not.
Some work is a range until someone is in the attic. A min/max on a draft is honest. A single fake precision number is not. Showing price confidence is useful if it means “how sure was the match,” not “how punchy was the prose.”
Keep quotes on the job
Quotes attach to the job and can attach to a follow-up task. One open quote per follow-up keeps the office from forking three competing PDFs for the same return visit. The report story and the quote stay in the same workspace so a manager is not reconciling two tools.
What buyers should ask
Ask any AI quoting tool where a number came from. If the answer is “the language model,” keep walking. If the answer is “row 18 in your book, or a blank your manager filled,” you can have a conversation.
We built ServiceBrief that way because field-service owners will forgive a slow draft. They will not forgive a wrong price that went out with their letterhead.