- Give every request one owner, one traceable record and an explicit definition of quote-ready information.
- Separate repeatable preparation from commercial judgment, approval authority and customer commitments.
- Treat delivery, revision and follow-up as part of the quotation process, with clear stop conditions and outcome records.
What the sales quotation process includes
For this guide, the sales quotation process begins when a customer asks for a price or provides information that should lead to one. It ends when the quote is accepted, declined, replaced, expired or deliberately closed. That boundary is broader than document generation because the operational delays usually sit between systems and people.
This is a seller-side workflow. It is not a buyer's procurement process for soliciting supplier bids, and it is not the full quote-to-cash cycle that continues through contracting, fulfilment, invoicing and collection. Keeping those intents separate gives the workflow a useful owner and keeps this page distinct from OpSmith's commercial implementation pages.
If your team wants the system designed and implemented, the relevant commercial service is quote automation. This guide explains the operating model and decisions that should exist before that build.
Start
A customer request, qualified opportunity, configuration or renewal event creates a need for a quote.
Middle
The team completes requirements, prepares pricing, resolves exceptions and obtains required approval.
End
The customer outcome and final quote version are recorded, and all scheduled follow-up stops correctly.
A seven-stage sales quotation workflow
The stages below are a reference model, not a mandatory software configuration. A simple business may combine stages, while a complex or regulated sale may add technical, finance or legal review. What matters is that each transition has an owner, required evidence and an observable status.
1. Capture
Create one request record containing the customer, source, requested outcome, received files and original message.
2. Complete
Determine which facts are required to price this request and obtain only the missing information that changes the quote.
3. Prepare
Apply approved products, rates, scope rules and reusable content to produce a reviewable draft with assumptions visible.
4. Approve
Evaluate value, margin, discount, terms, delivery promises and exceptions against the authority model.
5. Deliver
Release the approved version through the intended channel and record the recipient, time, version and expiry.
6. Revise
Treat material changes as a new commercial state, recalculate affected values and obtain approval again where required.
7. Follow up and close
Send bounded, relevant next steps; detect replies and outcomes; stop automation; and update the customer record.
Carry one information model through the workflow
Start with a controlled quote request intake process. Email, forms, attachments and salesperson notes can remain as source evidence, but the workflow also needs structured fields that pricing rules and reviewers can use consistently.
Separate known facts from assumptions. A customer's requested quantity is a fact from the source. An estimator's expected installation time is an assumption until it is reviewed. A default payment term is a policy value. Storing them as if they were interchangeable makes later revisions difficult to explain.
Every quote should have a stable identifier and a version. The quote record should connect customer requirements, calculation inputs, exceptions, approvals, the released document and the final outcome. Avoid creating an approval in one inbox, a PDF in another folder and follow-up tasks in a third system with no shared identifier.
Source
What the customer or connected system actually supplied, with time and origin preserved.
Interpretation
How the team classified or translated that source into scope, quantities and requirements.
Commercial state
Prices, costs, discounts, taxes, terms, validity, exclusions and calculated outcomes for one version.
Decision record
Rules evaluated, exceptions, authorized reviewer, decision, rationale and timestamp.
Decide what automation prepares and what a person promises
Automation can collect inputs, identify missing information, retrieve approved product data, perform deterministic calculations, assemble standard content, route decisions and watch statuses. It should not quietly fill unknown requirements, invent a discount, select an unauthorized substitute or release a consequential commitment because a timer expired.
Use a sales quote approval workflow to place people at the decisions that require authority or judgment. Standard work can flow quickly when the rules are satisfied; unusual margin, terms, scope or risk should arrive with the context the reviewer needs.
The broader principle is explained in human-in-the-loop automation: review should be proportionate to uncertainty and consequence. A person's click is not a useful control if the evidence is missing or every quote is approved automatically out of habit.
Treat revisions as controlled changes, not overwritten files
Customers change quantities, scope, delivery dates and terms. A useful revision process shows what changed, which calculations were affected and whether the earlier approval still applies. It never edits the only copy of the quote or leaves two documents labelled final.
Define material changes in business language. A corrected spelling may not require reapproval. A changed product, price, discount, delivery commitment or term usually should re-evaluate the relevant rules. The workflow can route only the affected decision when the authority model allows it, rather than restarting every review by default.
Preserve versions
Keep the released quote and its evidence immutable; create a new version for a revised commercial state.
Compare changes
Show reviewers the fields and calculations that changed instead of asking them to rediscover the difference.
Withdraw stale versions
Mark superseded quotes clearly and prevent follow-up or acceptance against an invalid version where possible.
Continue after the quote is sent—and know when to stop
A sent quote is not the end of the operating process. A controlled automated quote follow-up workflow can confirm receipt, surface questions and prompt an appropriate human action without continuing after the customer's situation changes.
Stop conditions are more important than message count. A reply, acceptance, decline, revision request, explicit opt-out, salesperson takeover, invalid address or expired quote should change the path. The outcome must return to the quote and customer record so another system does not keep sending from stale status.
When the commercial need is broader than one sent quote, OpSmith's lead follow-up automation service connects inquiry capture, qualification, ownership and useful human follow-through.
Measure the process without confusing speed with quality
Begin with a baseline from recent representative quotes. Record elapsed time as well as human touch time: a quote can require only thirty minutes of labour while waiting two days for missing information or approval. Segment standard and exceptional quotes because combining them can hide the part of the process that actually needs redesign.
Use the automation ROI calculator to keep released staff capacity separate from actual cash savings. A faster quotation process may increase responsiveness or throughput without immediately reducing payroll.
Input quality
Percentage of requests complete on first review and average clarification rounds.
Preparation
Median human touch time from quote-ready request to reviewable draft.
Approval
Time waiting for approval, exception rate and frequency of requested changes.
Outcome
Delivery time, revision rate, response status, expiry and reasons for accepted, declined or closed quotes.
Turn the map into a bounded implementation
Select one quote type with meaningful volume, stable calculation inputs and a responsible business owner. Document current examples, including incomplete requests, unusual terms, revisions and lost opportunities. Decide which source system owns each fact and how the workflow proves that a customer-facing action occurred.
Pilot with a limited group and assisted authority. Compare output calculations and wording with the approved human process, test every stop condition and practice recovery when a system update is uncertain. Expand only after the team can explain and recover the workflow.
OpSmith's business process automation audit turns one real quoting process into a current-state map, opportunity score and decision-ready implementation brief before a larger build.
Frequently asked questions
What is the difference between a sales quotation process and quote-to-cash?
The sales quotation process runs from the request for a seller's price through the quote outcome. Quote-to-cash continues through order, contract, fulfilment, billing and collection, so it is a larger operating scope.
Can a sales quotation process be fully automated?
Some standard quotes can move with little routine handling when requirements, pricing authority and output checks are explicit. Unusual scope, terms, risk and consequential commitments normally require accountable human review.
When should a revised quote be approved again?
Re-evaluate approval whenever a changed field could affect price, margin, scope, delivery, terms, risk or another controlled condition. Define material changes in advance rather than relying on memory.
Which system should own the quote status?
Choose one authoritative record for the commercial state and outcome, then make connected systems consume or update it deliberately. The best owner depends on the existing CRM, quoting and order systems.
What should be measured before quote automation?
Measure request completeness, clarification rounds, preparation touch time, approval waiting time, error and revision rates, delivery time, outcomes and residual human effort using representative recent quotes.