Approval is a control, not ceremony#
The point is to catch the small number of quotes that are genuinely outside policy without slowing down the many that are not. Thresholds do most of that work: standard pricing goes out unblocked, a discount past a stated line needs a second signature.
An approval step applied to every quote regardless of size teaches everyone to route around it, which is worse than not having one.
The state a quote moves through#
Draft, then approved internally, then sent, then accepted or declined, then expired. Each transition wants a timestamp and an actor, because the questions asked later are always who approved this and when did it go out.
Expiry deserves particular attention. A quote with no end date is an open-ended offer, and old quotes resurface at exactly the wrong moment.
Quote and invoice should be one record#
The common failure is a quote in one system and an invoice in another, reconciled by hand. Every re-keying is an opportunity to get a line item, a discount or a tax treatment wrong, and the mismatch is normally found by the customer.
Generating the invoice from the approved quote removes the class of error entirely: the same lines, the same totals, with the approval attached to the document that produced them.
Quote approval in SalesShift#
SalesShift quotes carry an approval workflow, and an approved quote generates the invoice directly — one action, the same line items, on the same record as the deal and the contract. Invoices can be issued, voided and rendered as a PDF.
Further reading#
See it running
Signals, prospect search, sequences, deliverability and pipeline on one record.