Why discount control breaks before pricing becomes the problem
Discount control usually arrives as a pricing problem, and for a small team that is the wrong way round. What actually happens is that a rep agrees fifteen percent off because the customer asked nicely, nothing is written down, and six weeks later nobody can say whether the quarter's margin was eaten by discounting or by picking bad deals. By the time the pattern is visible it lives in a spreadsheet nobody opens.
The tell is that nobody can answer a simple question: what was the smallest discount we gave last quarter, and to whom. If the answer is in somebody's inbox, the discounting is unmanaged. If the answer does not exist anywhere, it is worse than that.
It also helps to separate two things that get bundled together. Pricing decides what you charge and who you charge it to. Discount control is the narrower question of when a rep is allowed to move, who signs it off, and where the number is recorded. Teams that conflate the two buy a quoting tool when they needed a field and a weekly review, or they hire a sales ops person to produce a report nobody acts on.
The three things a small team actually needs
Strip out the enterprise machinery and discount control for a team of three to twenty comes down to three things, and the order matters more than the tooling.
| MECHANISM | WHAT IT ACTUALLY IS | WHAT IT COSTS | WHO IT IS FOR |
|---|---|---|---|
| A place to record the price you agreed | One field on the deal record, so the number exists, can be filtered, and can be read back later | An afternoon of setup | Every team, including a two-person one |
| A rule someone can say out loud | A threshold and a named person, written down: anything under ten percent goes to the founder | One conversation, then discipline | Teams where a founder or sales lead still reviews deals |
| A weekly look at where the discount went | Filter the pipeline by discount band and read the pattern out loud | Thirty minutes a week | Any team past the point where one person remembers everything |
None of these three needs an approval workflow. They need a record, a rule, and a habit, in that order.
Most teams try to buy the second one with software and then never do the third, which is exactly how discounting quietly gets worse. Software that tells a deal is waiting for approval tells you nothing about the fact that most of your approved discounts went to one customer who always asks. The third item is the one that changes behaviour, and it is the one nobody buys.
This is also where the CRM does its genuine work and where it stops. A CRM is good at holding the record of what was agreed and at making it visible afterwards, on a deal record with the value, the stage, the owner and the full history attached. It is not a pricing system, and a post that pretends otherwise is selling you something you do not need.
What a discount approval workflow actually is
An approval workflow is a rule enforced by software: a rep changes the price, the deal waits, it goes to a named approver, and it cannot move forward until that person says yes. That is a genuinely different thing from a field and a weekly review, and the vendors sell it well.
Read the pricing pages on 9 November 2026 and you can see where each of the big three puts it.
- —Salesforce lists Approval Processes as available for purchase rather than inside the base suites, with Products and Price Books, Quotes, Contracts and Orders sitting in the same upper band. Its suites run Free at $0 per user per month, Starter at $25, Pro at $100, Core at $195, Advanced at $395 and Max at $550.
- —Zoho CRM puts CPQ in the Professional tier, described as everything in Standard plus CPQ, with CPQ framed as matching products to customer requirements and streamlining quote management with built-in price rules. The approval process itself sits a tier higher, in Enterprise, described as ensuring deals move on only after the right person approves it. Zoho CRMPlus starts at $20 per user per month.
- —HubSpot splits the same ground across Revenue Hub and Sales Hub, and describes CPQ in Revenue Hub as configure, price, quote, with the pitch being to close the deal in Sales Hub and then quote, bill and collect payment in Revenue Hub rather than bolting a separate CPQ tool on.
That is the enterprise answer, and it is priced the way enterprise answers are. Nothing on those pages is wrong, and for a company running approval chains across regions and business units it is the right buy. The question for a small team is narrower: are you buying a mechanism that enforces a rule, or are you buying somewhere to record that you already have one?
Honest caveats: when a quoting tool is the right buy
Five cases where a CRM is the wrong instrument for this problem, and one where we are the wrong product.
- —You sell configurable things. If a quote is a set of line items chosen from a catalogue, priced with rules, and signed, then you need quoting software and a price book. A CRM records a number; it does not build one.
- —You need approvals that actually block. If a deal must not move forward until a named person approves the price, and the point is that the software will not let it move, you need a real approval workflow rather than a notification.
- —You have more than one price book. Regional pricing, contract pricing and customer-specific rates need somewhere authoritative to live, and that is a quoting system, not a field on a deal.
- —You need the quote to carry money. E-signature, a payment link, a tax treatment, an invoice on issue. That is a transaction flow, and a CRM will not become one because you add a discount field.
- —You are past the point where one person reviews deals. Once more than a handful of people can change a price, a rule enforced by software stops being optional and starts being cheaper than the meetings it replaces.
And the admission about our own product, because this post would otherwise be one-sided. BeigeCRM has no discount field, no price book, no quoting and no approval workflow. We checked our own features and pricing pages on 9 November 2026 and the words discount, approval, quote, margin, price book, CPQ and e-signature do not appear on either of them. What we do have is the substrate underneath: the built-in value and currency on every deal record on every plan, custom fields from Professional, audit logs from Professional up that record who changed what and when, and workflow automations on Enterprise that can fire when a deal changes stage, a lead is created, a form is submitted or a field changes. That last one is how you would approximate an approval on our product: change the value, the workflow tells somebody. It is a notification, not a gate, and we would rather draw that line than let you find it later. Our own per-seat pricing on the same date was Starter at $4.16 per seat per month billed yearly at $49.90, Professional billed yearly at $99.90 per seat and Enterprise billed yearly at $199.90 per seat. If what you need is the rule enforced rather than the rule remembered, read our Salesforce comparison, Zoho comparison and HubSpot comparison and buy the enforcement.
Six things to fix about discounting, in order
If you are a small team with a discounting problem and no system, this is the order.
- —Find the number first. Before any tooling, work out where the agreed price actually lives today. For most small teams it is three places: a quote somebody sent, a thread in an inbox, and what the rep said. Until all three land in one place, no rule is enforceable.
- —Put one field on the deal. Custom fields start on Professional and cover discount band, or the exact discount, as a number or a dropdown. One field. A discount percentage, a discount amount and a discount reason are three fields and one of them will go stale.
- —Write the rule down where a rep will see it. A threshold and a name, in one sentence: above ten percent needs the founder, above twenty-five percent needs a conversation. Put it on the pipeline board where the deal lives rather than in a policy document.
- —Turn on the audit log. Audit logs from Professional up record who changed what and when, and they matter the first time a deal value changes and nobody remembers doing it. That is also how you find out who is quietly discounting.
- —Do the weekly read. Filter the pipeline by discount band, look at which deals carry a discount and which of those closed, and write down the one thing you will change. Thirty minutes, every week, is the entire mechanism.
- —Automate the reminder, not the decision. On Enterprise, workflow automations can fire when a field changes. Use it to nudge the approver and to flag a deal that has been sitting in approval too long. Do not use it to pretend the approval is a gate, because it is not.
Then, and only then, decide whether you need to buy enforcement. If the weekly read shows the rule being broken weekly and the conversation is not fixing it, you have learned something about your process that no price book will solve. If the read shows the rule being followed and you still need the software to stop people bending it, that is the moment the enterprise pricing starts to make sense.
