The Approved Price List: How to Stop Reps from Improvising Numbers

Post 22 Sep 2026 pricingsales operationsCRMquotingdiscount approval

Improvised pricing is an operational problem, not an ethical one. A rep makes up a number because the approved price isn't available at the exact moment it's needed, or because what is available is outdated and untrustworthy. The fix is a single price list containing the reference price, its effective date, discount tiers, and a ladder showing who signs off on each band. The conversation then shifts from "how much can I give him?" to "which tier does he fall into?"

Where Improvisation Actually Comes From: Three Operational Causes

One: the price isn't available in the moment. The rep is in a meeting, and the price list is an Excel file on the office desktop or buried in an old email attachment. So they quote a number remembered from a previous deal.

Two: the price is available but not trusted. A file with no effective date and no named owner. The rep can't tell whether it's the January version or the updated one, so they either stop to ask or guess. Most guess.

Three: there's no clear discount ceiling. When no cap is written down, every discount becomes internally negotiable — and reps quickly learn that the fastest route is to grant the discount first and seek a blessing afterwards.

What an Approved Price List Must Contain

Five fields per item is the minimum. Nothing more is needed.

FieldWhy
Product/service codePrevents confusion between similar items
Selling unitHour, licence/year, metre, visit — the single biggest source of error
Reference priceThe price before any discount, in SAR, excluding VAT
Effective dateSeparates the current version from the old one
Item ownerOne person accountable for the accuracy of the number

Pricing Levels: List, Band, Exception

Three distinct things that are frequently conflated:

  • Price list: a reference price for an entire customer category (government, distributors, individuals). Approved once and left in place.
  • Discount band: an allowed percentage within the list, derived from an objective criterion — volume, contract length, upfront payment.
  • Exceptional deal: a departure from both, for one specific opportunity. It must be documented with a reason and an expiry date, otherwise it quietly becomes a permanent price by default.

Discount Ceilings and the Approval Ladder

Write the ladder once and post it where everyone can see it:

DiscountApproverResponse time
Up to 5%The repImmediate
6–12%Sales managerWithin one business day
13–20%CEO or financeTwo days
Above 20%Committee / documented exceptionCase by case

Response time is not a detail. A slow ladder is the number one reason people go around it. If approving 8% takes a week, the rep will grant it verbally and sort out the paperwork later. In Effistar, the ladder is tied to a rule that automatically routes each discount request to the right approver and logs the decision on the opportunity itself.

Rescue stalled deals · last run 2 hours ago Live simulation
1 You describe it 2 Hibab draws it 3 It runs
Y You, in plain words, as you'd say it to a colleague
H I've drawn the rule from your system's triggers, actions and your organization's catalogs, review it, then save.
Trigger Deal with no activity 7 days with no activity and no next task
Condition Value above 50,000 and its stage is neither Won nor Lost
Action Hibab analyses it Reads its history and writes why it stalled and what's next
Action Notify the owner In their language, on the channel they prefer
Action Follow-up task Opens tomorrow 09:00 for the deal owner
Trigger Condition Action · parallel actions run together
Run log
  1. Trigger caught deal Al Waha Specialist Hospital, 7 days with no activity
  2. Condition met: value SAR 210,000 stage Qualification
  3. Hibab: “Stalled after the technical presentation, pricing hasn't reached finance yet”
  4. Notified the deal owner on WhatsApp, in their language
  5. Opened a follow-up call task for tomorrow 09:00
## When to Update Prices — and What Happens to Open Quotes

Set a fixed cycle (quarterly, for instance) and use a future effective date rather than an immediate one. The rule that prevents most disputes: quotes issued before the effective date remain valid at the old price until the expiry printed on them. Which is why every quote, without exception, must state a validity period — 14 or 30 days.

Connecting the Price List to the Quote

The rule is simple: no number is ever typed manually into a quote. The rep selects the item and quantity, the price is pulled from the list, and the discount percentage they enter is routed through the ladder. Any line item outside the list is flagged for approval. This alone eliminates 80% of improvisation — not because it blocks it, but because it makes the straight path easier than the workaround.

Signals That Your Price List Is Being Bypassed

  • A rising share of "manually entered" line items in quotes.
  • Discounts clustering exactly at the top of each band (5% and 12% precisely) — a sign that orders are being split to avoid the next approver.
  • Exceptions with no expiry date.
  • A recurring gap between quoted price and invoiced price.

A Two-Week Plan

Week one: Identify your top 20 best-selling items, fill in the five fields, assign an owner to each item, and write the approval ladder on a single page.

Week two: Load the list into the system, disable manual price entry, activate automatic routing of discount requests, and run a 30-minute session with the team explaining the ladder and response times. Then review after one month: how many quotes fell outside the list, and why.

Want to see this inside your organization? Request an invite