Quote Software: Turning Price Lists and Rules into Consistent Documents

A quote is the document a company puts itself on the line with: a price, terms, a date. When it’s done by hand, every copy of a previous file drags along another customer’s discount, an old price list, a clause that no longer applies. Putting it into software is meant to remove the repetitive work without losing control over who can grant what.

The opposite risk is locking everything down and pushing sales reps to work outside the system, where nobody sees anything. The project succeeds if exceptions are planned for from the start, not if they’re simply forbidden.

Before the software: what’s inside a quote

Start by breaking down a real quote, a recent and complicated one, not the simple textbook case.

• The line items: what you sell and in what unit of measure. If installation is billed by the hour in one case and as a flat job in another, the difference needs to be decided now, not halfway through the project.
• What gets calculated: quantity times price, but also minimums, rounding, fixed charges, shipping.
• What gets written: payment terms, timelines, exclusions, warranties. These are recurring texts and need to be kept in one place, or everyone will use their own version.
• What depends on the customer: price list applied, usual discount, document language.

This breakdown is half the work. A quote that nobody in the company can break down out loud is a quote the software will reproduce just as confused as it is.

Price lists, discounts, and validity

A price isn’t a number: it’s a number valid for a price list, a period, and a quantity. Keeping these four things together is the part that pays off the most.

• Discounts need to be distinguished by origin: list discount, a sales discount granted case by case, a promotional discount with an end date. Only the second one needs an approval.
• The quote’s validity period belongs in the document and in the system, because it’s needed to know which open quotes still count and which don’t.
• When the price list changes, quotes already sent don’t change. The document captures the prices at the moment it was sent, and the system keeps them that way.

Exceptions, approvals, and final sign-off

Rules cover the normal cases. The system’s value shows up on the rest: who can deviate from the price list, by how much, and with whose consent.

Two warnings. The limits need to be calibrated to reality: if half of all quotes require an approval, the limit is wrong and the approval turns into a rubber stamp. And the request needs to be possible to make and get within minutes, even from a phone, because at the moment it’s needed the sales rep is almost always with the customer.

Versions, document, and history

A quote changes several times before being accepted, and that’s normal. What must not change is the ability to know which version you’re looking at.

1. Every revision is a new document with a recognizable number, not an overwrite. Customer and sales rep both need to be able to say “the second one” and mean the same thing.
2. The PDF is generated by the system. If the document can be tweaked by hand afterward, price control breaks down in one step.
3. The history keeps what changed between one version and the next, and who changed it. It’s needed on the day a customer accepts the wrong version, and it happens.
4. Superseded versions remain viewable but not acceptable: readable, yes, orderable, no.

From acceptance to opening the job order

Acceptance is the moment a quote stops being a sales document and becomes a production commitment. It’s also the point where, without a system, the data gets retyped by hand by someone else.

• What acceptance opens: a job order, an order, a service call. This needs to be decided, because it determines who sees the work.
• What carries over: line items, quantities, agreed terms, attachments. If only the total carries over, production works in the dark and calls the sales rep back.
• What doesn’t carry over: discounts granted and internal notes stay where they are, visible only to those who need to see them.
• How acceptance is recorded: a signature, a written reply, a customer purchase order. The proof needs to be kept together with the accepted version, not in an inbox.

When quote software isn’t the answer

• If you produce few a year and they’re all different, setup time outweighs the time saved: it’s worth putting the templates and recurring texts in order first.
• If prices don’t come from rules but from a case-by-case judgment, the system can organize the document and the approvals, not calculate the price. That’s still a result, but it needs to be said upfront.
• If it’s unclear who approves, digitizing the process only makes it more rigid. Roles need to be established first, or the software will freeze them wrong.

What this guide doesn’t cover

This guide covers internal, predictable rules: price lists, discounts, approvals, versions, the handoff to the job order. The case where the customer themselves configures their request on the website and gets a price follows different constraints. And using an automatic assistant to draft text or summaries needs to be assessed separately, because it changes the kind of check needed before sending.