Skip to main content

Market-neutral small-business guide

How Much Price Flexibility Can a Sales Team Have?

Derive delegated price authority from a documented floor, contribution impact, approval evidence and explicit escalation rules.

Build authority from the floor, not from a benchmark

Inputs and boundaries that must be explicit before comparing scenarios
Input or boundaryUnit and sourceDecision use
List priceCU per unit on one indirect-tax basis; approved price recordStarting point for the exception calculation.
Variable costCU per unit on the same basis; reconciled cost recordShows direct contribution after a proposed discount.
Documented floorCU per unit; business-owned scenario and approvalEscalation or stop boundary, not evidence of customer willingness to pay.
Authority bandPercentage or CU range; explicit internal assumptionDefines who may approve which exception and for how long.
Scope and evidenceCustomer segment, quantity, term, inclusions and reason; decision recordPrevents an exception from silently changing the offer or becoming permanent.
Keep every row on one currency, unit, period and indirect-tax basis. Scenario values are user assumptions, not market benchmarks.
Core calculation

discounted price = list price ร— (1 - discount rate); unit contribution = discounted price - variable cost per unit

list price
Approved starting price on the declared basis (CU/unit) โ€” business record
discount rate
Proposed exception expressed as a decimal (ratio) โ€” user input
variable cost per unit
Cost that changes with the unit inside the stated scope (CU/unit) โ€” business record or labelled assumption

The calculation shows contribution inside the chosen cost boundary. It does not prove that the floor covers every business cost or that a customer will accept the price.

Worked example: set representative, manager and stop bands

The example uses a CU100 list price, CU55 variable cost and a business-chosen CU88 floor. The 5% and 12% authority boundaries are fictional.

Reproducible fictional scenario in neutral currency units
StepInputs and arithmeticResult and interpretation
1. List-price contributionCU100 - CU55CU45 unit contribution before any exception.
2. Representative boundaryCU100 ร— (1 - 5%) = CU95; CU95 - CU55CU40 unit contribution. A representative may approve up to 5% only when the recorded scope and reason pass.
3. Manager boundaryCU100 ร— (1 - 12%) = CU88; CU88 - CU55CU33 unit contribution. Discounts above 5% require manager review and cannot go below the chosen CU88 floor.
4. Below-floor request13% discount gives CU87; CU87 - CU55CU32 contribution but below the approved floor: stop, escalate or change scope.
5. Record the exceptionCustomer segment + quantity + term + approver + reason + expiryA reproducible decision record; not an open-ended price promise.

Test what would change the decision

Sensitivity and boundary cases
CaseRecalculation or evidenceDecision consequence
Variable cost rises to CU62At CU88, contribution falls from CU33 to CU26.Recalculate the floor and authority bands before approving another exception.
Quantity changes delivery costReplace the unit-cost assumption with the reconciled quantity scenario.Do not apply the same band when the order changes the cost boundary.
Repeated manager exceptionsReview observed contribution and reasons by approved aggregate category, without collecting customer identifiers in product analytics.Change the offer, price architecture or policy instead of normalising undocumented exceptions.

Turn a price exception into a controlled decision

Use this sequence

  • Confirm the current list price, cost scope, floor and indirect-tax basis. (not complete)
  • State the customer segment, quantity, term, inclusions and reason for the exception. (not complete)
  • Calculate the proposed price and unit contribution before choosing an approver. (not complete)
  • Approve only within the named band; escalate or stop outside it. (not complete)
  • Record the approver, reason, scope, decision date and expiry in the business system. (not complete)
  • Review observed exception patterns and contribution before changing the bands. (not complete)

Mistakes that invalidate the comparison

  • Copying an industry discount percentage without reconciling the business floor.
  • Giving a representative a percentage band but no scope, approver or expiry.
  • Treating positive unit contribution as proof that every wider cost is recovered.
  • Letting an exception change service, quantity, payment or support terms without recosting.
  • Coordinating prices, discounts or future pricing policy with competitors.

Use the registered calculation owner

Questions and limitations

Is 5% a recommended sales discount allowance?
No. It is a fictional boundary used to show the workflow. A real band must be derived from the business cost, floor, offer and approval evidence.
Can a positive contribution justify a below-floor sale?
Not automatically. The floor may include a wider cost or minimum-contribution decision. Reconcile the full approved boundary before making an exception.
Should competitor discounts determine the band?
No. Competitor information may inform independent market research, but the business must set its own prices and must not coordinate pricing with competitors.

Sources and evidence scope

  • Choose a pricing strategy โ€” business.gov.au: Primary small-business guidance for reconciling cost, goals, market evidence, customer value and capacity. It supplies no universal margin, package mix, discount band or demand response.
  • Price fixing โ€” U.S. Federal Trade Commission: U.S.-specific competition guidance supporting only the caution against competitor coordination. It is not global legal advice.

Change history

  1. โ€” Initial public release of the article after pre-launch factual, editorial, source and presentation review.