Why discounting needs a rule of its own
The pricing and packaging guide names discount governance in one paragraph, and this tutorial is where that paragraph becomes written rules. Four other pages lean on that answer without restating it. The price change communication guide tells sales to set limits in advance. The competitor response guide says to answer a rival's price cut with packaging options that address the buyer's problem before any lower number. The placement guide for new features treats sellers giving an add-on away as a sign the placement is wrong. And the renewal preparation tutorial leaves negotiating price and discounts to the pricing guide. This tutorial is where those references land.
The scope is the negotiated deal, where a seller can move the price, the terms or what is included. Offers published to the market, such as a sale or a limited-time price, follow the guide to planning promotions and the pricing guide's section on price claims. The two meet in one place: a discount a business advertises is a price statement of the kind the pricing guide records as covered by the UK's Competition and Markets Authority and by the Advertising Standards Authority's codes, and what a seller says across the table should be as honest as what is printed. None of this is legal advice.
Product marketing is a natural author of the rules without being their only owner. The pricing guide reports the Product Marketing Alliance's view that pricing communication is part of the product marketer's remit, and it describes a pricing group in which product marketing runs the process, finance can veto what the numbers do not support and a single named executive approves changes. The discount rules are that group's output, and the product positioning hub treats pricing and packaging as a deliverable derived from the positioning.
Having no rule is costly. The price change guide makes the fairness point: where the limits are unwritten, the buyers who push hardest end up with the best terms, which is unfair to the rest and costs the business. The sales cycle diagnosis adds that a discount offered to speed a deal up can teach buyers to hold out for the next one while leaving the questions that were slowing the deal unanswered. And a discount that was a trade cannot be told from one that was a surrender if nobody wrote down which it was.
Before you start
Agree the purpose with sales leadership and finance before any sheet is drawn. As general practice, a rule that sales leaders see only as a restriction may be worked around, and the argument that can work is that it makes approvals quicker for the deals that fit, protects sellers from the buyer who asks for more each time, and gives them something to offer besides a lower number.
Gather what the rules will stand on: the plans and prices as the pricing page shows them; from finance, the contribution marginRevenue left after every cost that varies with each sale. of each plan, so that the lowest price the economics allow is a fact; a recent period of closed deals, won and lost; and any win-loss notes.
Fix the vocabulary. A discount is any reduction from the list price. A concession is anything else of value given to close: free months, waived set-up fees, extra users, an add-on included without charge. Concessions are discounts under another name, and, as general practice, a rule that covers only the first may invite the second. Decide which deals the rule covers (new business, renewals, expansions) and where the record will live, preferably in fields on the deal record that sellers already use and that finance can read.
The steps
Agree who decides, who approves and who records
Write the decision rights down before writing the rules. The RACI matrix framework gives the form: list the decisions that cause arguments in rows, the roles that touch them in columns, and name exactly one accountable role per row. The rows worth writing here are setting the rules, setting the floor under each plan, approving a concession at each level of the ladder, approving an exception, keeping the record and reviewing the pattern. Adapt the pricing guide's arrangement, where product marketing runs the process, finance can veto proposals the economics cannot carry and a named executive signs off changes; the guide itself says sales owns how deals close. The rest is a choice to make here, not something the guide sets: this tutorial assumes the pricing group owns the rules, finance owns the floor, the named executive approves exceptions that change the rules and product marketing keeps the record. As general practice, agree how long each approver has to answer and who the request goes to next if they do not. A request left waiting is a delay in the deal, and the sales cycle diagnosis notes that delays in negotiation can be a matter of pricing.
Read the discounts already given
Pull the closed deals from a recent period and, for each, the list price, the agreed price, any concession beyond price, the reason the seller gave, who approved it, the segment and plan, whether a competitor was named and when in the quarter it closed. Where a reason or an approver was never recorded, rebuild what you can from contracts and a short talk with each seller, and treat the gap as the first finding. Split the result by segment and by plan instead of averaging it, and read won and lost deals together: a discount seen only on won deals cannot show whether it was needed. Where counts are small, keep the count beside each figure, as the reading small numbers guide advises, and read them as a direction rather than a measurement. The aim is a plain description of what happens today: how often sellers discount, to whom, why, and how often a discount bought anything.
Sort the reasons into what the discount is standing in for
As general practice, a recorded reason may not be the whole story. Group the reasons and ask what each points to, because some are better answered somewhere other than in the price.
Reason on the deal What it may really be Where it is dealt with The buyer's budget is tight A package larger than the need, or a pricing metric the buyer cannot predict The options in step five and the tiers and metric that the pricing guide sets out A competitor is cheaper A comparison that shows only the price side The battlecards guide, and the competitor response guide's order of answers It must close this quarter The seller's target rather than the buyer's need The exception route in step eight The champion needs a better number to show colleagues A missing business case or a quote that hides what is included The business case kit in the late-stage deal content guide A capability is missing A product gap The feature requests tutorial and the roadmap rules An add-on or feature was given to close A placement that does not fit the segment The placement guide A reason that appears again and again on one plan is a packaging signal before it is a discount problem; step ten returns to it.
Write the trades the business will accept
The pricing guide prefers a rule that makes every discount buy something: a longer commitment, more volume, a case study or earlier payment. Turn that into a short list sellers can quote. For each trade, write what counts, who confirms it has been delivered and what happens to the concession if it is not. A promise to consider a larger purchase later is not a trade; a signed longer term is. When the business is paid in a case study or a reference, the exchange is a material connectionA relationship between an endorser and a brand, such as a fee, free product, commission or employment, that endorsement guidance expects to be disclosed. that the references and advocacy guide says should be disclosed clearly and recorded in the reference pool, drawing on the FTC's endorsement guidance, and the customer's words must still be their own account of their experience. Never list a promised feature date as a trade: a commitment about future capability goes through the approved route in the roadmap guide, not through a price negotiation.
Write the options that solve the problem without a discount
The pricing guide makes this product marketing's part of the job. Sales need answers that deal with the buyer's budget problem and leave the list price alone: a narrower tier, a staged start or another add-on. Write them as a short menu, each with the situation it fits, what it changes in the price and what it takes out. A smaller tier suits a buyer who needs less than the plan they were shown. A phased start, with one team or site first, suits a buyer whose problem is the size of the first commitment. A different add-on, or a bundleSeveral products sold together as one item at a single price, used to raise order value; a kit is a bundle designed as a starting point for new customers. of two, suits a buyer who wants one capability the plan leaves out. For a service business, the packaging a service as a product guide shows how a package states its scope and exclusions, and a narrower package stated that way is this tutorial's version of the smaller tier. Check every option against the fences the packaging was built on: the good-better-best pattern asks each fence to follow value, and an option that hands an upper plan's feature to a lower plan for nothing removes the fence the next buyer meets. Options agreed in advance need no approval, which is much of their point.
Set the approval ladder by size and by reversibility
The pricing guide describes a ladder in which the representative decides small concessions and a manager, finance or an executive decides the larger ones. The ladder here adapts that pattern: the seller's own discretion covers only the pre-approved options on the menu, and the first band goes to the sales manager, so that nothing is conceded without a recorded trade. Sales leadership can add a seller-discretion rung for the smallest concessions if it prefers, provided the trade is still recorded. Define the bands as shares of the list price, set with finance from the floor under each plan. The pricing guide sends readers to a break-even calculation to see what extra volume a price cut has to bring before profit moves. A calculator that converts a margin into the sales needed to cover a campaign cost is on this site, but it does not model a discount, so any arithmetic beside each band is for finance to run. Then add a second axis, because size is not the only risk. The one-way and two-way doors idea puts the cut between what is cheap to undo and what changes customers' expectations of price. As this tutorial's reading of the idea, a concession with an end date and a delivered trade is a two-way door; a lower baseline at renewal, a long price lock or a new standing price for a group of buyers is a one-way door and belongs higher up. An approval matrixA table that says which reviews each type of marketing work needs, such as legal, brand or budget, and who gives each, matched to the risk of the work. works by risk rather than by seniority, and the ladder should too.
What the seller asks for Who decides Why A pre-approved option from the menu The seller Priced and agreed in advance, and it keeps the fences A discount in the first band with a listed trade The sales manager Small, tied to a trade, and it lapses if the trade is not delivered A discount beyond the first band, with a listed trade Finance with the head of sales Closer to the floor, so the economics need a second look A concession that resets what other customers expect The named executive, through the pricing group Hard to undo, and other customers will hear of it Anything below the floor Not available Finance owns the floor, so changing it is a decision for finance through the pricing group, not a deal decision Write down what the rule never allows
As general practice, a short list of absolutes may be easier to follow than a long list of conditions. Candidates: a discount with no recorded reason or trade; a concession that is not recorded, such as free months or waived fees; a discount that depends on a promised feature or date; a price shown in writing as the usual price or a former price when it was never genuinely charged, the reference priceThe price a promotion compares against to show a saving, such as a 'was' price; the site's pricing guides say it should be one customers were genuinely charged. practice that the pricing guide records the Competition and Markets Authority's consumer protection work as covering; a time limit that is not real; a number matched to a competitor's without the answers the competitor response guide puts first; and a deal split across invoices to stay under a limit. Send any promotion with comparative or reference pricing to whoever handles compliance before it runs, as the pricing guide asks, and the guide records the Advertising Standards Authority as applying its codes to claims about price. A negotiated figure that is not published is a commercial decision, but it should still be honest.
Build the exception route
Some deals will not fit, and the rule is only as good as the route they take. Write what a seller brings to an exception request: the deal facts, the budget problem in the buyer's own words, the options already offered and why they failed, the trade on offer, the effect on other customers on the same plan and the date the deal needs an answer. Say who decides and by when, and make the answer a record, not a message. In this tutorial's design, an exception can go beyond what the ladder allows, but not past the absolutes in the previous step or below the floor. The marketing decision log template is a ready-made decision logA running record, one row per decision, of what changed and why, what was expected, who decided and when the result will be checked., and, as this tutorial's choice, one row per exception can use the template's own columns. Give every exception an end date or a review date, so that a concession made once does not quietly become the price. Exceptions of the same kind are a finding about the rule and go to the pricing group together. As this tutorial's own fairness test, customers in the same situation on the same plan should be offered the same thing.
Brief sellers and put the rule where they work
Write the rules on a single page: the options menu, the trades, the ladder, the never list and the exception route. Put it where sellers already look for content, and add matching fields to the deal record: list price, agreed price, the reason from a short pick-list, the trade, the option offered and the approver. Make them required to close a deal that carries a concession, because, as general practice, a rule that depends on memory may be followed only by those who remember. Brief sellers in the way the sales content and training guide lays out, with a short session and a role-play of the moment that matters: a buyer asks whether the seller can do better on price. The rehearsed answer asks what the budget problem is, offers the options first and names the trade second. Remind sellers that the person asking may not be the person deciding: a buying committeeThe group of people in an organisation who influence, evaluate and approve a purchase. includes a champion who wants the purchase and others who can approve or block it.
Read the pattern on a regular rhythm and let it change the packaging
Review the record at the pricing group's own rhythm. Read the share of discounted deals that carry a recorded trade, the exceptions by reason and by seller, the options offered against those taken, the concessions by segment and plan, the time deals spend in negotiation alongside sales cycle lengthAverage time from opportunity creation to a closed deal., and the win rateShare of closed sales opportunities that were won. of deals with and without a concession, grouped by the cohortA group of customers who share a starting event and period, tracked together over time. in which they were opened and read once the deals in each have reached a decision, with the caution that an association is not a cause. Then let the pattern decide what changes. A budget reason that keeps appearing on one plan is a question for the packaging guides: perhaps the entry plan is too large for the segment. A competitor reason points to the battlecard, and a champion's request to the business case kit. A seller giving away the same add-on again points to a placement that does not fit, as the placement guide warns. When the rule itself is wrong, change it in the decision log and tell sellers what changed and why. Revisit it after any price change, new plan or withdrawn plan. The pricing guide asks for price levels to be reviewed on a planned rhythm using discounting patterns among other evidence, and the record built here is that evidence.
A marina software firm writes its discount rules (illustrative)
Parneth Berth Software stops discounting by habit
Parneth Berth Software, an invented maker of berth-booking software for marinas, has 4 sellers and 3 plans: Dock, Harbour and Fleet. Its product marketer read the previous 12 months: 62 won deals, 47 of them discounted and 15 at list. It read the lost deals for the same months beside them. A reason was recorded on only 19 of the 47: 9 said the buyer's budget was tight, 6 named a cheaper competitor and 4 said the harbour master needed a better number to show the trustees. 31 of the 47 closed in the last fortnight of a quarter, and in 11 Harbour deals the text-confirmation add-on had been included free.
The pricing group, made up of the head of sales, the finance lead, the managing director and the product marketer, wrote a one-page rule. The options menu offered the Dock plan with an agreed move to Harbour, a start at one marina before a group-wide rollout, and the add-on at list price. The trades were a two-year commitment, annual payment in advance and a case study with the discount disclosed beside it. Sellers could use the options freely, the sales manager approved the first band with a trade, the finance lead and head of sales approved anything beyond it, and the managing director approved any change to renewal terms. Free months and waived set-up fees counted as discounts.
Over the next two quarters there were 28 won deals. 11 closed at list or with only a menu option, and 17 carried a discount, each with a reason and a trade recorded: 9 two-year commitments, 6 annual payments in advance and 2 case studies, both disclosed. 5 exceptions were requested and 3 granted, each with an end date; the free add-on appeared once, as one of those exceptions. Budget was the reason on 9 of the 17, nearly all on the Dock plan, so the product marketer took it to the pricing group as a packaging question about the entry plan, not as a request to raise the limits. The team noted that two quarters of 28 deals were too few to call a trend.
Common mistakes
- Writing rules without a record. A ladder nobody can check is a suggestion; the deal record needs the reason, the trade and the approver, and the fields should be required.
- Banning discounts outright. A ban without options may invite unrecorded concessions and leave nothing to read.
- Counting only the price cut. Free months, waived fees, extra users and included add-ons are discounts under other names and belong in the rule.
- Trades that nobody checks. A longer commitment that was never signed, or a case study that never appeared, leaves a plain discount behind; say what lapses when a trade is not delivered.
- Conceding the add-on to close a deal. It removes a fence and signals a placement that does not fit; fix the placement, not the habit.
- Paying for a feature with a price. A discount for a promised feature turns a roadmap statement into a commitment; route it through the approved route instead.
- Letting the exception become the price. An exception without an end date or a review date is the new list price in waiting.
- Not reading the pattern. The same reason on the same plan is information about packaging, which a rule that is not reviewed does not collect.
