Value-for-Value Concession Trading Script Pack
Eighteen word-for-word scripts for responding to concession requests across six common negotiation categories, each built on a conditional structure that trades rather than gives. Every script names its failure mode and flags when not to use it.
How to use it
Print or save this pack before any negotiation where concessions are likely. Locate your category (price, payment terms, contract length, scope add-ons, implementation fees, SLA upgrades), pick the script closest to the live situation, and read it aloud twice before the call so it sounds like yours. Do not improvise the conditional clause, that is the whole mechanism.
What's inside
- 18 word-for-word scripts with [bracketed fill-ins] ready for live use
- Six concession categories: price, payment terms, contract length, scope add-ons, implementation fees, SLA upgrades
- Conditional trade structure applied consistently across every script (acknowledge, pause, counter-condition, then agree)
- Named failure mode for each script (e.g. "naked yes", "apologetic discount", "silent capitulation")
- One-line "when NOT to use this" note per script
- A quick-reference table mapping concession type to script number
- Opening notes on the core conditional principle and how to hold the pause
The Principle Before the Scripts
Every concession you give without a condition attached trains the buyer to ask again. The conditional structure used throughout this pack is:
Acknowledge the ask. Pause. Name your counter-condition. Then agree, conditionally.
The pause is not silence for effect. It is the moment you decide which counter-condition applies. If you skip it, you end up with a naked yes or an apologetic discount. Both cost you margin and credibility.
The counter-condition must be specific and named out loud. "If we do X, can you do Y?" is the minimum viable trade. Anything less is a gift.
Quick-Reference Table
| Category | Scripts |
|---|---|
| Price | 1, 2, 3 |
| Payment Terms | 4, 5, 6 |
| Contract Length | 7, 8, 9 |
| Scope Add-Ons | 10, 11, 12 |
| Implementation Fees | 13, 14, 15 |
| SLA Upgrades | 16, 17, 18 |
Price Concessions
Script 1: The Volume Anchor
Situation: Buyer asks for a lower unit price.
"I hear you on the price. Before I go back to see what's possible, help me understand the volume side. If we could get the annual commitment up to [number] units, I can make a stronger case for moving the per-unit figure. Can you confirm that volume is on the table?"
Failure mode to avoid: Naked yes. Going back to check pricing without attaching any condition signals that the number was soft all along.
When NOT to use this: When the buyer has already fixed volume at a contractual cap. Asking for more volume they cannot give makes you look like you haven't listened.
Script 2: The Term Extension Trade
Situation: Buyer asks for a discount on a one-year deal.
"I can look at bringing the price down, but to do that I'd need a longer commitment in return. If you're willing to move to a two-year term, I can take [X]% off the annual figure. Are you in a position to do that?"
Failure mode to avoid: Apologetic discount. Never frame the discount as you doing them a favour. It positions every future price as inflated.
When NOT to use this: When your product roadmap is uncertain beyond twelve months. Locking a buyer into two years on a potentially changing product creates churn risk, not loyalty.
Script 3: The Payment Acceleration Trade
Situation: Buyer is pushing on total contract value with no other lever offered.
"The total contract value isn't something I can move on its own. But if you're able to pay in full upfront rather than quarterly, I can bring the total down by [£X / X%]. Does that work for your finance team?"
Failure mode to avoid: Silent capitulation. This is where a rep reduces price without saying anything, just sending a revised quote. The buyer never learns the condition, never feels the trade.
When NOT to use this: When the buyer is a large enterprise with a mandatory accounts-payable cycle. Asking for upfront payment from someone who structurally cannot do it wastes the concession slot.
Payment Terms Concessions
Script 4: The Early Payment Discount
Situation: Buyer wants to extend payment terms from 30 to 60 days.
"I can look at extended terms, but I'd need something in return to make that work internally. If you pay within 14 days of invoice, I can offer a [X]% prompt-payment discount. If you need the 60 days, the standard price holds. Which works better for you?"
Failure mode to avoid: Unconditional extension. Agreeing to 60-day terms without any condition extends your cash cycle with no benefit.
When NOT to use this: When your finance team has already pre-approved extended terms as part of a strategic account plan. The trade has been pre-spent; using this script creates confusion.
Script 5: The Staged Payment Restructure
Situation: Buyer wants to split annual fee into monthly instalments.
"Monthly billing adds admin overhead on both sides and changes our cash position. I can offer that structure, but I'd need to add a [X]% instalment fee to cover it. Alternatively, we stay on quarterly billing at the current price. Which direction do you want to take?"
Failure mode to avoid: Free restructure. Giving monthly billing for nothing establishes the precedent that your payment terms are fully flexible at no cost.
When NOT to use this: When you are in a competitive bake-off and the competitor is already offering monthly at no charge. The instalment fee will be used against you. In that case, escalate to your manager before responding.
Script 6: The Milestone-Linked Payment
Situation: Buyer wants to tie payments to delivery milestones rather than calendar dates.
"Milestone-linked payments are something I can work with. To protect both sides, I'd want to agree the milestone definitions in writing before we finalise terms. If you can confirm those milestones this week, I can get the contract structured that way. Can you commit to that timeline?"
Failure mode to avoid: Vague agreement. Saying yes to milestone billing without defining the milestones creates a dispute at every invoice.
When NOT to use this: When your delivery process has dependencies outside your control. Milestone payments you cannot guarantee hitting are a liability, not a concession.
Contract Length Concessions
Script 7: The Short-Term Premium
Situation: Buyer wants a six-month contract instead of twelve.
"A six-month term is possible, but the unit economics change at that length. I'd need to price it at [£X per month] rather than [£Y]. If you commit to twelve months, the lower monthly rate applies. Which term do you want to go with?"
Failure mode to avoid: Same price, shorter term. Giving a shorter contract at the same annual rate is pure margin erosion with no upside.
When NOT to use this: When the buyer is trialling ahead of a larger multi-year decision. Charging a short-term premium on a trial that leads to a significant expansion deal may kill the relationship early.
Script 8: The Renewal Lock-In
Situation: Buyer agrees to a one-year term but wants a guaranteed renewal price cap.
"I can give you a price cap on renewal, but I'd need you to sign a two-year agreement now for that to be viable. The cap I can offer is [X]% maximum increase at renewal. A one-year deal doesn't give us enough certainty to lock in that guarantee. Does the two-year structure work?"
Failure mode to avoid: Open-ended price cap. Promising a renewal cap on a one-year deal with no reciprocal commitment is giving away future pricing leverage for free.
When NOT to use this: When your pricing model is under review. Committing to a cap while your cost base is changing is a risk you cannot price accurately.
Script 9: The Early Renewal Credit
Situation: Buyer wants to shorten the current contract before its end date.
"I can look at an early exit, but I'd need a commitment on the next term to offset the shortfall. If you sign the renewal now for [X months / years], I can waive the remaining [N months] on the current contract. Otherwise the exit clause in the agreement applies. Which way do you want to proceed?"
Failure mode to avoid: Free exit. Letting a buyer out early with no counter-condition sets a precedent that your contracts are optional.
When NOT to use this: When there is a genuine service failure on your side. A free exit in that context is not a concession, it is the correct response.
Scope Add-Ons
Script 10: The Feature-for-Commitment Trade
Situation: Buyer asks for additional features not in the current package.
"That feature sits in our [higher tier / enterprise plan]. I can include it, but I'd need a twelve-month commitment to justify absorbing the cost. On a shorter term, we'd need to price it separately. Can you confirm you're on a twelve-month term?"
Failure mode to avoid: Free add-on. Adding scope without a condition devalues everything else in your product and gives the buyer a habit.
When NOT to use this: When the feature is already built and costs you nothing to activate. In that case, use it as a relationship gesture, not a trade, but do it consciously and only once.
Script 11: The User Count Anchor
Situation: Buyer wants more user licences included at the same price.
"Additional licences are priced at [£X per user]. I can include [N] extra users at no charge if you move the total commitment to [£Y] or sign for [Z months]. Otherwise the standard per-user rate applies. What does your user rollout actually look like?"
Failure mode to avoid: Licence inflation. Adding users for free without a counter-condition shrinks your per-unit revenue invisibly.
When NOT to use this: When the extra users are the basis for a much larger expansion. Sometimes absorbing a few licences to get into more teams is the smarter commercial play. Know which situation you are in before responding.
Script 12: The Services Bundle
Situation: Buyer wants professional services hours included in the software price.
"Professional services are a separate cost centre for us, so I can't fold them into the software price directly. What I can do is include [X hours] of onboarding support if you increase the software commitment to [£Y]. That closes the gap without opening up the services model. Does that structure work?"
Failure mode to avoid: Unbundled giveaway. Promising hours without tying them to a revenue condition erodes services margin with no offset.
When NOT to use this: When the buyer genuinely does not need the services and you would be padding the deal. Bundling services the buyer will not use creates a bad-value perception at renewal.
Implementation Fees
Script 13: The Waiver-for-Speed Trade
Situation: Buyer asks to waive the implementation fee.
"The implementation fee covers [specific work: configuration, data migration, training]. I can waive it if we can confirm a go-live date within [X weeks] and you provide a dedicated internal point of contact from day one. If those conditions work, I can remove the fee. Can you commit to both?"
Failure mode to avoid: Unconditional waiver. Waiving the fee without conditions signals it was never real, and it removes the incentive for the buyer to show up ready.
When NOT to use this: When your implementation team is already at capacity. Waiving the fee and then delivering a poor onboarding is worse than charging for it.
Script 14: The Phased Implementation Offset
Situation: Buyer wants the implementation fee deferred to a later invoice.
"I can defer the implementation fee to invoice two if you sign the contract by [date] and we start onboarding within [X weeks]. That keeps the project on schedule and gives you the breathing room you need on the first payment. Does that timing work?"
Failure mode to avoid: Open deferral. Deferring with no deadline attached means the fee drifts and becomes a dispute later.
When NOT to use this: When your finance team records implementation revenue at point-of-sale. This is an accounting conversation before it is a sales concession.
Script 15: The Self-Serve Reduction
Situation: Buyer wants a reduced implementation fee for a simpler use case.
"If your team can handle the configuration using our self-serve setup guide and you don't need our engineers on-site, I can reduce the implementation fee to [£X]. I'd need confirmation that you have the internal resource to do that before we finalise. Do you?"
Failure mode to avoid: Unearned reduction. Reducing the fee without confirming the buyer actually has the internal capability leads to scope creep and unpaid work.
When NOT to use this: When you know from discovery that the buyer's team is stretched. Setting them up to fail on implementation to save a fee is a retention problem, not a sales win.
SLA Upgrades
Script 16: The Response-Time Upgrade Trade
Situation: Buyer wants a faster SLA response time at the current price.
"The [four-hour response] SLA sits in our premium support tier, which is priced at [£X / year]. I can include it if you extend the contract to [X months] or move to [higher product tier]. On the current structure, the standard SLA applies. Which option fits better?"
Failure mode to avoid: Free SLA inflation. Giving premium support commitments at standard-tier pricing sets a service expectation you cannot sustain financially.
When NOT to use this: When the buyer is in a regulated industry where the standard SLA creates a genuine risk for them. Flag it internally first and treat it as a product gap, not a negotiation moment.
Script 17: The Uptime Guarantee Trade
Situation: Buyer wants a higher uptime guarantee (e.g. 99.9% to 99.99%) written into the contract.
"A 99.99% uptime commitment requires dedicated infrastructure on our side. I can include that guarantee if you move to our [enterprise tier / dedicated environment], which is [£X]. On shared infrastructure, I can commit to 99.9%. The gap in annual downtime minutes is [calculated figure], does that change the picture for you?"
Failure mode to avoid: Guarantee without infrastructure. Agreeing to 99.99% on shared infrastructure is a contractual liability you may not be able to honour.
When NOT to use this: When your engineering team has not confirmed the dedicated environment option is available. Never negotiate infrastructure commitments without confirming feasibility first.
Script 18: The Penalty Clause Trade
Situation: Buyer wants financial penalties included for SLA breaches.
"I can include a service credit clause for SLA breaches. To do that, I'd need the SLA thresholds defined precisely in the contract: response time, resolution time, and measurement method, and I'd need both sides to agree on the credit calculation upfront. If we can get that language agreed within [X days], I can include it. Can your legal team move at that pace?"
Failure mode to avoid: Open penalty clause. Agreeing to penalties with vague thresholds hands the buyer a blank cheque for future disputes.
When NOT to use this: When your service delivery has had recent incidents. Accepting penalty clauses while your reliability record is under pressure is a liability you are underpricing.
A Note on Holding the Pause
The scripts above give you the words. The pause gives you the credibility.
After the buyer makes their ask, a count of two to three seconds before you speak is not hesitation. It signals that concessions require thought, that your price has structure, and that you are not going to fold at the first request.
Reps who speak immediately after a concession ask almost always reach for the easiest give. Reps who pause almost always reach for a condition.
The pause is the cheapest negotiation tool you have. Use it every time.