A Discount Exception Needs a Decision Brief

The request arrives just before the executive meeting: “Can we approve twenty percent? They will sign this week.” The CRO has a percentage, a deadline and a seller's confidence. Missing are the customer's actual constraint, the other concessions already offered and what the seller is authorized to do if the buyer changes the terms again.

A useful discount-exception brief makes one commercial decision possible without forcing the approver to rebuild the opportunity. It should state the requested concession, the buyer evidence behind it, the realistic alternatives and the conditions attached to any approval. The goal is not a longer form. It is to make the trade-off visible before a quick yes becomes an unclear promise.

Ask what problem the concession is supposed to solve

A buyer can ask for a lower price for several reasons. There may be a fixed budget, a comparison with a narrower competing offer, a procurement target or uncertainty about value. Those explanations call for different responses. A price concession may address a genuine budget limit. It may do little to resolve a customer who cannot yet explain why the purchase matters.

The brief should distinguish what the buyer said from the seller's interpretation. “The procurement manager requested a lower annual fee” is evidence of a request. “They cannot buy without twenty percent” is a stronger claim that needs support. Ask who owns the budget decision, what constraint they confirmed and whether the proposed concession would resolve it.

This is not an invitation to interrogate the buyer or demand sensitive documents. It is a discipline for internal reasoning. A seller should be able to explain the connection between the proposed term and the customer's decision. Where that connection is uncertain, the next step may be a conversation rather than an approval.

Show the whole concession in one view

Discount percentage is only one part of the proposal. Payment timing, free service, a longer trial, a delayed start, optional cancellation or additional scope can change the commercial trade-off. Put the relevant terms together and identify which are standard, which have already been approved and which require a new decision.

Do not collapse unlike terms into an invented discount-equivalent percentage. A month of delayed payment and a service obligation have different consequences. Finance can assess cash timing and economics using the company's methods; the delivery owner can assess whether the service promise is feasible. The CRO needs those views together, not an apparently precise number that conceals the assumptions.

Salesforce's deal-desk guidance describes coordinating Sales, Finance and other functions around complex commercial terms. Its discount-approval tutorial also shows how a threshold can route a request. Those mechanisms help identify the right approver. They do not supply the reasoning that makes a particular exception worth approving. That reasoning belongs in the brief.

Consider a fictional request with three possible offers

A fictional software company has proposed a twelve-month subscription at $120,000. The buyer asks for twenty percent off. The seller has also discussed $10,000 of additional onboarding work, estimated internally, and ninety-day payment terms. These figures are illustrative; they are not RevTech pricing, margins or customer results.

The requested subscription price is $96,000, a $24,000 reduction from the original proposal. The additional onboarding is a separate delivery commitment, not automatically another $10,000 of discount or cost. The ninety-day terms are another decision again. Listing all three prevents the headline percentage from becoming the entire approval conversation.

The right answer cannot be calculated from the percentage alone. If the buyer has a genuine annual ceiling of $100,000, a payment-timing change does not necessarily solve it. If the obstacle is uncertainty about deployment, cutting the subscription while adding unplanned services may make the economics worse without resolving confidence. The seller needs to test which problem is real.

Suppose the buyer confirms that the budget ceiling is real but also says the additional services are optional. Finance reviews the proposed economics, the service owner confirms standard onboarding is adequate and the CRO chooses to authorize a $100,000 offer under specified terms. That is an illustrative decision, not a recommended price strategy. What matters is that the team can explain what changed and why.

The approval should name the exact offer version and its conditions. If the buyer subsequently requests additional scope or different payment terms, the seller should know whether that variation falls within the authority granted. “Approved twenty percent” is a poor instruction when the commercial package is still moving.

Give the approver an alternative to yes or no

A well-prepared request can end in approval, conditional approval, a counterproposal or a request for a specific missing fact. A rejected request should explain the commercial boundary and what the seller can do next. Otherwise the seller returns with a slightly different percentage while the underlying question remains unresolved.

Use a short recommendation that acknowledges the trade-off. For example: the team recommends a narrower concession because the customer has confirmed a budget constraint, standard delivery meets the stated need and the alternative offer preserves a viable scope. Then identify what could invalidate that recommendation. A recommendation is useful precisely because the approver can challenge it.

Also separate urgency from evidence. A genuine procurement deadline matters. An internal quarter-end goal matters to the seller, but it is not proof the customer will sign. The brief should show the buyer's timing and the consequence of waiting. Approvers can then decide how much uncertainty to accept without treating a calendar date as leverage the business necessarily possesses.

Preserve the reason without creating a pricing precedent by accident

After the decision, retain the requested offer, the approved version, the reason, the decision owner and the conditions. If the offer expires or changes, keep that history. The next account team should not find an old approval and assume it authorizes the same concession on a renewal or another product.

Review exceptions across comparable cases after enough have matured. Look for repeated reasons that indicate the standard offer is hard to use, an approval rule is ambiguous or a particular service promise is repeatedly being given away. A small set of wins does not prove that discounting caused the outcome. Nor does a lost discounted deal prove the original decision was irrational.

The learning question is more precise: did the approved concession address the constraint the team believed it addressed, and were the resulting obligations delivered as agreed? This connects commercial judgment with customer experience. It also makes exceptions useful input to pricing and packaging work without allowing exceptional deals to silently rewrite the offer.

Use prepared context to protect the commercial conversation

RevTech's managed agents can carry agreed research, account preparation and recurring analysis. Its Sales Agent inspects authored rules and presents owned exceptions. A scoped workflow can use those capabilities to help assemble the context surrounding a commercial review, subject to available sources and confirmed configuration. The CRO and designated Finance or legal owners make the pricing and contractual decisions.

This is not a claim that RevTech currently operates a complete deal desk or autonomously approves discounts. The broader Deal Execution platform experience is labelled Coming Soon. Start with preparation you can inspect: the current proposal, documented customer rationale, relevant account history and the specific unanswered question. Do not present an agent's inferred willingness to pay as a buyer-confirmed fact.

For your next exception request, replace “approve this percentage” with a concise decision brief. If the approver can understand the customer's constraint, compare the available offers and state the boundaries of the decision, the preparation has done its job. The seller can return to the customer with a coherent conversation rather than another round of internal ambiguity.

Sources and scope

The decision-brief method and pricing scenario are original illustrations, reviewed October 16, 2026. No discount level, financial result or universal approval policy is recommended.

• Salesforce, What is a Deal Desk?: https://www.salesforce.com/blog/sales/deal-desk/
• Salesforce Trailhead, Create an Approval Process: https://trailhead.salesforce.com/content/learn/projects/build-a-discount-approval-process/create-an-approval-process
• RevTech Sales Agent: https://revtech.ai/ai-agents/sales