Quotation and proposal automation: pricing, approvals, versions and follow-up
In a lot of businesses the quotation is the product. It is where the margin is decided, where the delay happens, and where deals are lost quietly to whoever answered first.
This page covers what to automate in quoting, in the order that pays back soonest, and how to do it without handing pricing control to a system nobody can override.
Where quoting actually goes wrong
Ask three people in a sales team to quote the same job and you will usually get three numbers. Not because anybody is careless, but because the price list exists in several versions, the discount that was approved last quarter is remembered differently, and the last similar quote is the one that gets copied.
The delay is just as costly. A quote that takes two days because it needs a cost from somebody who is travelling loses to a competitor who answered in an hour with a worse price. Speed of response is a commercial lever, and quoting is where most businesses lose it.
Where this has actually run. Wobble has run 25 client engagements across six countries, and every one is published with its outcome rather than described in general terms. See the work, with the numbers.
One source for price, and a rule for everything that moves it
The foundation is a single place where price lives, with every modifier expressed as a rule rather than a habit. Volume breaks, customer category, payment terms, freight, installation, and whatever your trade adds to a base price. Written as rules, they can be applied consistently and changed once.
Then set approval limits by value and by margin, not by value alone. A large quote at a normal margin is routine; a small quote below floor margin is the one that needs a second pair of eyes. Systems that only check the total let the damaging discounts through.
Assembly, so the document builds itself
Once price is a rule, the document is mechanical. Line items, specifications, terms, validity, exclusions and the covering text assemble from the selection rather than being retyped from the last similar job. Which removes the most common quoting error: a stale clause or an old price surviving a copy and paste into a new customer's document.
Keep the salesperson able to override, and keep the override visible. A system that cannot be overridden gets bypassed entirely, usually by somebody building the quote in a separate file. An override with a reason recorded is information. A bypass is an invisible loss.
Versions, expiry and the follow-up nobody does
Every quote should carry a version and a validity date, so a conversation three weeks later is about a specific document rather than a general memory of a number. When a revision goes out, the previous version should remain readable. Disputes about what was quoted are won by whoever has the record.
Follow-up is where the return is largest and the effort is lowest. Most quotes are never chased. A system that reminds a named person, with the customer's history and the quote in front of them, recovers deals that were not lost on price but on silence. And an expiry date is a legitimate reason to make contact, which salespeople value more than a reminder.
What the numbers should tell you afterwards
Once quoting runs through one system, you get the analysis that was previously impossible: win rate by product, by salesperson, by discount band and by response time. Which turns pricing from an argument into a decision. The response time figure is usually the one that changes behaviour, because it is the only variable the team controls entirely.
What we will not build into it
Nothing that sends a priced document to a customer without a named person approving it, and nothing that changes a price silently. A quoting system that can issue on its own is a liability sitting in front of your customers, and the first time it is wrong it is wrong in writing.
How we approach it
We start with your last twenty quotes, won and lost. That shows where the real variation is, which approvals exist in practice rather than on paper, and how long quoting actually takes end to end. The first build is usually narrow: one product family, one approval rule, one follow-up sequence, live in weeks and measurable against those twenty.
It runs in your own accounts, next to whatever you already use for CRM and accounts. Related: custom CRM development and CRM automation.
Answers before you automate quoting
What should be automated first in a quotation process?
Pricing from a single source with every modifier written as a rule, then document assembly, then follow-up. Follow-up gives the fastest return for the least effort, because most quotes are never chased and the deals recovered were lost to silence rather than to price.
How do you keep control of margin when quoting is automated?
Set approval limits by margin as well as by value. A large quote at normal margin is routine; a small quote below floor margin is the one needing a second look. Systems that check only the total let the damaging discounts through.
Should salespeople be able to override an automated price?
Yes, with the override and its reason recorded. A system that cannot be overridden gets bypassed, usually by somebody quoting from a separate file, and a bypass is an invisible loss where an override is useful information.
Why does quote version control matter?
Because a conversation three weeks later should be about a specific document rather than a general memory of a number. Every quote should carry a version and a validity date, with previous versions kept readable. Disputes are settled by whoever has the record.
What does a quoting system let you measure?
Win rate by product, salesperson, discount band and response time. Response time is usually the figure that changes behaviour, because it is the one variable the sales team controls entirely.
Send us your last twenty quotes
Won and lost. We will show you where the variation really is, which approvals exist in practice, and how long quoting takes end to end. That analysis is useful to you whether or not we build anything.
Book AI Readiness Call ↗