
negotiation-concession-planner
Builds a pre-negotiation concession plan for a pricing or contract conversation - every tradeable lever priced by cost-to-us vs value-to-them, tiered, each give paired with a required reciprocal get and its approval level, plus a BATNA-based walk-away. Covers B2B (terms, scope, service, risk, price protection) and B2C (bundles, financing, trade allowance). Use whenever the user mentions a discount request, procurement, redlines, give-get trades, walk-away point, or "the buyer wants 20% off", even without the word negotiation. Do NOT use for quantifying the value (mbfinotti/sales-skills@deal-value-calc) or scripting price rebuttals (mbfinotti/sales-skills@sales-objection-handling).
- Installs
- 26.5K
- Last 24h
- +898
- Trending rank
- #408
- Security
- Pass
Install
Works with every agent the skills CLI supports.
npx skills add https://github.com/mbfinotti/sales-skills --skill negotiation-concession-planner- 01
Install
Run the command in your project. The CLI asks which agents to install for.
- 02
Describe the task
Ask your agent for something this skill covers. It loads negotiation-concession-planner automatically when relevant.
- 03
Review the result
The agent follows the SKILL.md steps, scripts and references bundled with the skill.
Security audits
Independent scans of the skill's instructions and bundled files.
SKILL.md
The instructions your agent reads when the skill is triggered.
Concession Planner
Produce a pre-call concession plan: a tiered ledger of what the seller can trade, priced by cost-to-us vs value-to-them, every give paired with a required reciprocal get and the approval level it needs, bounded by a written walk-away line.
A concession plan is a preparation artifact, not an in-call improvisation. Mid-negotiation, emotional engagement degrades judgment of relative value - so the gives, the gets, the prices, and the limits get written before the conversation starts.
Interview
Ask before planning. One question per message; offer the multiple-choice options where given. Skip anything already answered by prior context.
- What are you selling, and at what price point is the deal on the table?
- Is this B2B or B2C, and which segment: (a) enterprise, (b) SMB / mid-market, (c) consumer?
- Who is the counterpart: (a) the decision maker, (b) procurement / purchasing, (c) a champion or influencer without final authority, (d) unknown?
- What has the buyer actually asked for so far: (a) a price discount, (b) better terms - payment, contract length, risk, (c) more scope for the same price, (d) nothing yet, but you expect pushback?
- What is your discount authority band, and who approves beyond it? Treat the existing approval matrix as an input - this skill never designs it.
- Which non-price levers can you move: term length, payment timing, scope or volume, service level, risk terms (uptime, credits, liability), price protection, bundled goods?
- What do you want in return: (a) references, case study, or logo rights, (b) prepay or multi-year, (c) a faster signature date, (d) referrals or introductions, (e) larger scope?
- What is your walk-away alternative if no deal happens - the next-best use of the same time, capacity, or inventory?
- By what date must this land, and whose date is it: (a) theirs, (b) yours, including your own quarter-end, (c) neither's?
- Do you want a one-off win here, or a position that holds? A concession granted once tends to be expected forever - every renewal starts from it, and your other buyers hear about it. (a) close this one at almost any structure, (b) protect the baseline for the renewal and the deals after it.
- What is your effort ceiling: delivery capacity you can actually commit, approvals you can realistically get in the time available (deal desk, finance, legal), and how much of this you can take back later?
Re-rank the inventory against those three answers before building the ledger, and say which answer moved what:
- A hard, near date promotes the fast-acting levers - cash timing, service access, a delivery commitment - and demotes multi-year structures that need approvals you cannot collect in time.
- A "protect the baseline" answer demotes the headline discount and every price-protection lever, since both are permanent by construction. "Close it now" is the only answer that promotes them above their tier.
- A low effort ceiling deletes levers rather than demoting them: anything needing legal or deal-desk sign-off you cannot get, anything creating delivery work you cannot staff. Strike them from the ledger and name which ones you struck - a ruled-out lever parked at the bottom reappears in the room as an offer.
If the counterpart cannot decide (3b without a mandate, or 3c/3d), flag it before planning: a concession granted to a non-decision-maker gets spent twice, because the real decision maker will ask for it again.
Workflow
-
Build the bargaining mix. List every issue in play - price, terms, scope, service, risk, timing - including the issues the buyer will raise, not only the ones you plan to. Lay out the four levers (volume, cash timing, contract length, deal timing) before touching price, so you can trade across them instead of defaulting to a discount. Pull levers from concession-inventory.md, already priced and ranked, minus the ones question 11 ruled out.
-
Write two separate lists: what you are willing to give, and what you will demand in exchange. Write both now, in full - in the room you will judge relative value poorly and forget half your asks.
-
Price every item on cost-to-us vs value-to-them, and order it by the ratio. Lead with the highest value per unit of cost, not with the cheapest lever.
- Cost to us is margin, the precedent set for every deal after this one, delivery burden, and reversibility - never a currency figure, scored only in magnitudes: near-zero, an hour, a week, a quarter, a standing job.
- Default B2B family order, efficiency axis:
service access > cash timing > scope > headline discount > price protection. - Cost-to-us axis:
price protection > headline discount > scope > cash timing == service access(the tie holds because both spend capacity or working capital you get back inside the term, leaving no clause behind). - Value-to-them axis:
price protection > headline discount > scope > cash timing > service access. - concession-inventory.md carries every lever priced against those axes, the B2C order, and what each order starves.
- Treat that order as a default, not a law: re-rank it against this deal and against who has to execute it. A renewal negotiates up from last time's concessions, a buyer already anchored on a number leaves you only the non-price rows, and a lever class your rep cannot get approved in time drops a tier.
-
Tier the ledger in ratio order: first moves, mid, last resort, highest value per unit of cost at the top of each tier, never the cheapest item first.
- The same concession is worth different amounts to different people:
- Finance weighs payment terms and financial risk.
- Procurement weighs documented savings.
- The business sponsor weighs speed and outcomes.
- Technical roles weigh support and integration.
- Route each concession to the stakeholder who values it most, then re-rank. A lever's value is its value to that best recipient, not an average across the room.
- Pair every item with (a) a named reciprocal get and (b) the approval level it needs. For a lever carrying contractual or regulatory exposure, record its compliance cost and how long it binds you in that approval cell.
- No orphan gives: an unpaired concession is a defect in the plan, not a nice gesture.
- The same concession is worth different amounts to different people:
-
Set the walk-away from your alternative, never from your margin floor. Value the no-deal alternative (your BATNA), derive the reservation price from it, and write it down. Estimate the counterpart's reservation point too: if the two ranges cannot overlap (no ZOPA), walking is the rational plan and no concession sequence fixes it.
-
Plan ranges per issue and plan issues independently, not as a fixed sequence. Set an opening, a target, and a limit for each issue.
Do not script the order you will concede in: field observation of skilled vs average negotiators (Rackham & Carlisle) found heavy sequence planning is what average negotiators do. The order is itself negotiable, and a pre-set order collapses the moment the counterpart opens on your last item.
Plan each issue so you can trade in whatever order the conversation takes. The ratio ranking from step 3 says which lever to reach for first when you do move; it is not a script for the order the issues come up in.
-
Build 2-3 MESO packages (multiple equivalent simultaneous offers): packages of equal value to you but different shape for the buyer - e.g., lower price with shorter term vs higher price with longer term and stronger support. Do not rank them:
A == B == Con cost to us by construction, and if one is genuinely cheaper for you than the others it is not a MESO, it is a discount ladder wearing three hats. Which one they gravitate to reveals their priority ordering without you asking for it. -
Plan the log-rolls. Where your priority ranking differs from theirs, trade your low-priority issues for their high-priority ones. Multi-issue deals create value exactly here, and negotiators miss these trades by default - mark the candidate pairs in the plan explicitly.
-
Shape a decelerating pattern within each issue: shrinking increments toward your limit signal that the limit is real. Honest caveat: the supporting evidence is lab-based and mostly single-issue; in a multi-issue deal, log-rolling (step 8) matters more than taper mechanics. Hold your pre-set target no matter what pattern the other side runs at you.
-
Write the conditional line for every planned trade: "If you can do X, then we can consider Y." Never plan an unconditional give. Draft the exact sentences now from trade-language.md - improvised phrasing under pressure turns trades into gifts.
-
Produce the pre-call one-pager (format below) and rehearse the two or three hardest asks out loud - the get requests, not the gives.
-
Run the Measurement check below; iterate on the plan until it passes.
If your harness has persistent memory, store the walk-away line, authority band, and remaining unspent tiers after each round - the next conversation on the same deal starts from the updated plan, not from scratch. Without memory, tell the user to keep the one-pager and mark spent concessions on it.
B2B vs B2C
Every workflow step above applies identically to both - only the concession currency differs.
- B2B currency is contract terms whose cost arrives later: term length, payment timing, ramped pricing, scope, support tier, uptime and service credits, renewal-uplift caps, price holds, liability caps. That delay is why sellers systematically under-price them.
- B2C currency is bundled goods with a known unit cost: delivery, installation, extended warranty, trade allowance, financing terms, priority scheduling, accessories, a gift card instead of a headline discount (protects the reference price). Cheaper to price accurately, easier to give away thoughtlessly.
- B2C compresses the timeline: single session, counterpart in the room. Keep the plan to one page and memorize the tiers - there is no pause to consult a ledger.
Both catalogues, ranked and priced: concession-inventory.md.
Pre-call one-pager
Output the plan in this shape (filled examples in concession-ledger-example.md):
DEAL: <what, list price, counterpart, their role, timing pressure each side>
WALK-AWAY: <reservation point + the alternative it derives from>
DEAL SPACE: <estimate of their reservation point; ZOPA yes/no>
TRADE LEDGER (rows in ratio order within each tier - best value per unit of cost first)
| Lever | Tier | Cost to us | Value to them | Best recipient | Required get | Approval | Range (open → limit) |
STRUCK LEVERS: <ruled out by the effort ceiling or authority - listed once, never carried in the ledger>
MESO PACKAGES: A == B == C on cost to us, different shape
LOG-ROLL CANDIDATES: <our low-priority issue ↔ their high-priority issue>
HARDEST ASKS TO REHEARSE: <2-3 get requests, verbatim>
Write "Cost to us" in magnitudes only - near-zero, an hour, a week, a quarter, a standing job - never as a currency figure. The deal's own prices belong on the DEAL and WALK-AWAY lines, not in the axis cells.
Failure modes
These are not ranked, and deliberately so: they are not alternatives you pick between. Several can fire in the same call, and which one arrives first is the buyer's choice rather than yours - an order here would read as a queue to work through and leave the rest unguarded.
- Unilateral discounting - a give without a get teaches the buyer the next ask is also free. Fix: conditional line on every trade, no exceptions.
- Conceding before pushback - moving before the buyer has actually pressed is bidding against yourself. Hold the plan until an ask lands.
- The sucker pattern - one big opening concession then nothing signals the open was padded. Open small; keep increments shrinking.
- Salami slicing and the last-minute nibble - many small asks, or one "tiny" ask after handshake. Counter procedurally: get their full list on the table before moving, keep all issues linked, and re-open the whole package if a new ask appears after agreement.
- Conceding to the wrong stakeholder - giving procurement what the sponsor never asked for converts a relationship asset into a commodity input. Route per step 3.
- Negotiating with a non-decision-maker - every concession will be re-requested by the person who actually decides. Confirm authority before spending tiers.
- Quarter-end capitulation - the seller's own commission timing drives the deepest discounts, and buyers schedule to it. Decouple the plan from your fiscal calendar; cap what quarter-end is allowed to unlock.
- Discount stacking - promotions, bundle incentives, competitive matches, and discretionary discount compound past what any single approval intended. Compute the combined concession before granting the last piece.
- Verbal-only concessions - anything not written on the order form dies with the champion. Every granted trade and its get goes into the written recap and the order form.
- Argument dilution - extra weak reasons hand the counterpart something to attack. One strong reason per position; stop talking.
Procurement counter-tactics
Procurement is measured on reportable savings against a baseline - they need a documented win more than a genuinely cheaper deal. A credible anchor plus a documented, low-real-cost concession package satisfies their scoreboard without margin loss. Operational rule: never reduce price without removing scope.
The table below is a lookup, not a menu - each row is keyed to the move the buyer makes, so ranking the counters would be false precision: you never choose between them.
| Buyer move | Mechanism | Counter |
|---|---|---|
| "You'll have to do better than that" | Vague pressure inviting you to cut against yourself | Ask what specifically must improve, and by how much; trade, do not move |
| Budget bogey | Friendly fixed-budget anchor that makes you solve their problem | Confirm who decides and who pays; fit scope to the number; present a pre-built MESO at that budget |
| Claimed limited authority | "I can't approve that" buys time and free movement | Mirror it - your pricing is set above your level too; withhold firm concessions until their authority is present |
| Competitor price claim | Real or bluffed cheaper quote | Ask for the quote in writing; price the scope difference instead of matching the number |
| Unbundling / line-item pricing | Exposes where margin concentrates | Re-price components so the bundle discount disappears when unbundled |
| Timing to your quarter-end | Buys your calendar-driven desperation | Anchor timeline on their compelling event; cap end-of-quarter discount authority |
Measurement
Plan readiness - the plan is not done until all of these pass; iterate until 100%:
- Every listed concession has (a) a named reciprocal get, (b) a cost-to-us magnitude, not a currency figure, (c) the approval level required - including the review a compliance-exposed lever triggers.
- Rows sit in ratio order within each tier, and the levers the effort ceiling ruled out are struck and named, not sitting at the bottom of a tier.
- The walk-away line is stated in writing and derived from the alternative, not the margin floor.
- Every planned trade has its conditional sentence written out.
- At least two MESO packages exist, roughly equal in value to the seller.
Outcome KPIs to track after the negotiation:
- Concession-to-get ratio: share of granted concessions with a documented reciprocal commitment on the order form.
- Realized price vs list, per deal and per segment.
- Discount distribution shape: bunching just under an approval threshold means the matrix is being gamed, not respected.
- Win rate and cycle time by discount band - confirms price gains are not buying losses elsewhere.
- B2C: front-end vs back-end gross per unit, and retained vs booked (a deal can post strong gross and lose it to refunds and early payoffs).
References
- mbfinotti/sales-skills@deal-value-calc - quantify the deal's underlying value and ROI (the value-to-them inputs for step 3)
- mbfinotti/sales-skills@sales-objection-handling - in-call rebuttals to price and competitor objections
- mbfinotti/sales-skills@deal-champion-mapping - map which stakeholder receives which concession
- mbfinotti/sales-skills@sales-meeting-recap - paper the granted trades and their gets after the call
FAQ
What does the negotiation-concession-planner skill do?
Builds a pre-negotiation concession plan for a pricing or contract conversation - every tradeable lever priced by cost-to-us vs value-to-them, tiered, each give paired with a required reciprocal get and its approval level, plus a BATNA-based walk-away. Covers B2B (terms, scope, service, risk, price protection) and B2C (bundles, financing, trade allowance). Use whenever the user mentions a discount request, procurement, redlines, give-get trades, walk-away point, or "the buyer wants 20% off", even without the word negotiation. Do NOT use for quantifying the value (mbfinotti/sales-skills@deal-value-calc) or scripting price rebuttals (mbfinotti/sales-skills@sales-objection-handling).
How do I install negotiation-concession-planner?
Run npx skills add https://github.com/mbfinotti/sales-skills --skill negotiation-concession-planner in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/negotiation-concession-planner/ (personal) or .claude/skills/negotiation-concession-planner/ (project).
Which AI agents can use negotiation-concession-planner?
Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.
Is negotiation-concession-planner safe to install?
Security partners have reviewed it: Gen Agent Trust Hub passed; Socket passed; Snyk passed. As with any skill, read the SKILL.md and bundled scripts before installing.
Who maintains negotiation-concession-planner?
It is published by mbfinotti in mbfinotti/sales-skills. It has 26,549 recorded installs.
More from mbfinotti/sales-skills
sales-icp-definition
mbfinotti/sales-skills
Defines the company's ideal customer profile (ICP) at sales-leadership altitude - the firmographic, technographic, behavioral and intent criteria, a weighted scoring rubric with explicit disqualifiers, and the refresh cadence that targeting keys off. Works from closed-won/lost deal data, or from founder-led discovery when deal data is thin. Covers B2B account ICPs and the equivalent B2C demographic/psychographic profile. Use whenever the user mentions the ideal or target customer, buyer profile, "who should we sell to", or targeting that is too broad, even without the letters ICP. Do NOT use for TAM/SAM/SOM sizing (mbfinotti/sales-skills@sales-market-sizing) or account fit scoring (mbfinotti/sales-skills@sales-account-segmentation).
sales-pipeline-coverage-modeling
mbfinotti/sales-skills
Models how much pipeline a team needs relative to quota - coverage ratios derived from win rates (raw multiplier, stage-weighted, conversion-inversion), segment-level coverage targets, in-quarter timing and the point of no return, seasonality indexing, and pipeline-gap math that turns a ratio into new-pipeline-required. A macro modeling exercise for sales leadership and RevOps, covering B2B and high-velocity/B2C motions. Use whenever the user mentions pipeline coverage, 3x pipeline, a pipeline gap, forecast shortfall, or "we missed quota with 4x coverage", even without the word coverage. Do NOT use for deriving the quota itself (mbfinotti/sales-skills@sales-quota-setting) or inspecting one deal (mbfinotti/sales-skills@deal-red-flags).
sales-account-tiering
mbfinotti/sales-skills
Designs the tier layer downstream of an existing account fit score - where the cutoffs sit, tier names, rep-to-account capacity caps, the coverage model per tier (touch cadence, channel mix, QBR frequency, executive involvement), coverage-ratio health metrics, and the recalibration cadence. Covers B2B account tiering and B2C key-account tiering through retail/distribution channels. Use whenever the user mentions tiers, strategic/key/growth/long-tail accounts, accounts-per-rep ratios, 1:1 or 1:few or 1:many ABM coverage, or "everything drifted into Tier 1", even without the word tiering. Takes the fit score as input. Do NOT use for building that score (mbfinotti/sales-skills@sales-account-segmentation).
sales-market-sizing
mbfinotti/sales-skills
Estimates TAM, SAM, and SOM for a market or sub-segment to ground sales capacity, territory, and quota planning - top-down, bottom-up on named accounts or population math, value theory, triangulation, a capacity-based SOM ceiling, and a per-layer refresh cadence. A macro planning exercise for sales leadership and RevOps, covering B2B and B2C. Use whenever the user mentions TAM, SAM, SOM, market size, addressable market, "how big is this market", or the number behind next year's quota, even without those acronyms. Sizes for planning, not pitching. Do NOT use for defining the ICP (mbfinotti/sales-skills@sales-icp-definition) or turning SOM into quotas (mbfinotti/sales-skills@sales-quota-setting).
sales-hiring
mbfinotti/sales-skills
Employer-side hiring workflow for SDR/BDR and AE roles, producing an outcome-based scorecard, a structured interview loop with question bank, a scored mock-call work sample, and a 30-60-90 ramp plan with certification gates. Recommends SDR vs AE vs full-cycle from ACV, cycle length and inbound volume, and rests on selection-validity evidence - structured interviews, independent scoring, no brainteasers. Use whenever the user mentions hiring a rep, sales interview questions, a hiring scorecard, a mock call interview, rep onboarding, or a ramp plan, even without the word hiring. Do NOT use for candidate-side prep (mbfinotti/sales-skills@sales-career) or comp plan design (mbfinotti/sales-skills@sales-comp-design).
sales-kickoff
mbfinotti/sales-skills
Before starting any sales project, and before answering a sales request that spans more than one sales topic or names no skill at all, run this router first. It routes the task to exactly one skill in the sales-skills collection, or says plainly that none fits, and bootstraps or resumes the project's shared sales-context.md artifact, producing a short-list plus an ordered skill chain. Fires on the state of the conversation rather than the subject matter, at a sales project start, at a periodic sales check-in or recurring sales review, on a mid-project re-route, or on any broad or ambiguous sales request such as "which sales skill do I need" or "where do I start with sales". Covers both altitudes, CRO-altitude planning (motion, ICP, market sizing, segmentation, tiering, org structure, quota, coverage, comp) and execution (outbound, cold calling, discovery, objections, MEDDPICC, recaps, call review, hiring, career). Run it even when sibling skills are already in daily use elsewhere.
Popular business & finance skills
sales-enablement
coreyhaines31/marketingskills
When the user wants to create sales collateral, pitch decks, one-pagers, objection handling docs, or demo scripts. Also use when the user mentions 'sales deck,' 'pitch deck,' 'one-pager,' 'leave-behind,' 'objection handling,' 'deal-specific ROI analysis,' 'demo script,' 'talk track,' 'sales playbook,' 'proposal template,' 'buyer persona card,' 'battle card,' 'battlecard,' 'competitive one-pager,' 'win-loss analysis,' 'why are we losing deals,' 'loss reasons,' 'how do I respond to this objection,' 'prospect just said,' 'help my sales team,' 'sales materials,' or 'what should I give my sales reps,' 'cold call script,' or 'voicemail script.' Use this for any document or asset that helps a sales team close deals. For public competitor comparison pages, see competitors. For running buyer interviews or churn research, see customer-research. For marketing website copy, see copywriting. For cold outreach emails, see cold-email. For the offer being sold (bonuses, guarantees, pricing structure),
revops
coreyhaines31/marketingskills
When the user wants help with revenue operations, lead lifecycle management, or marketing-to-sales handoff processes. Also use when the user mentions 'RevOps,' 'revenue operations,' 'lead scoring,' 'outbound pipeline stages,' 'lead routing,' 'MQL,' 'SQL,' 'pipeline stages,' 'deal desk,' 'CRM automation,' 'marketing-to-sales handoff,' 'data hygiene,' 'leads aren't getting to sales,' 'pipeline management,' 'lead qualification,' or 'when should marketing hand off to sales.' Use this for anything involving the systems and processes that connect marketing to revenue. For cold outreach emails, see cold-email. For email drip campaigns, see emails. For pricing decisions, see pricing.
sales-funnel-blueprint
autonnel/autonnel-skills
Turn an offer into a concrete multi-step sales funnel spec - page-by-page structure, price ladder, copy outline and the metrics each step must hit. Use when asked to build a sales funnel, marketing funnel, landing page flow, lead magnet funnel, webinar funnel, tripwire or VSL funnel, when planning a product launch page flow, or when someone asks "what pages do I need" for selling something online.
pricing
coreyhaines31/marketingskills
When the user wants help with pricing decisions, packaging, or monetization strategy. Also use when the user mentions 'pricing,' 'pricing tiers,' 'freemium,' 'free trial,' 'packaging,' 'price increase,' 'value metric,' 'Van Westendorp,' 'willingness to pay,' 'monetization,' 'how much should I charge,' 'my pricing is wrong,' 'pricing page,' 'annual vs monthly,' 'per seat pricing,' 'should I offer a free plan,' 'pricing page teardown,' 'pricing page audit,' 'is my pricing page AI-readable,' or 'can AI read my pricing.' Use this whenever someone is figuring out what to charge, how to structure their plans, or wants to audit a pricing page (for humans and for the AI agents that shortlist tools). For in-app upgrade screens, see paywalls. For offer construction (bonuses, guarantees, value framing, naming) on services/courses/coaching/high-ticket B2B, see offers.
cross-border-ecommerce
nexscope-ai/ecommerce-skills
Cross-border e-commerce expansion advisor. Scores target markets on 8 weighted dimensions (market size, ecommerce penetration, competition, regulatory complexity, logistics infrastructure, payment ecosystem, cultural distance, IP protection), compares 5 fulfillment models with cost and transit data, provides country-by-country tax/duty compliance guides (EU VAT/IOSS, UK VAT, US sales tax, CA GST, AU GST, JP consumption tax), maps local payment preferences by market, and builds a phased expansion roadmap. No API key required.
pricing-strategy
coreyhaines31/marketingskills
When the user wants help with pricing decisions, packaging, or monetization strategy. Also use when the user mentions 'pricing,' 'pricing tiers,' 'freemium,' 'free trial,' 'packaging,' 'price increase,' 'value metric,' 'Van Westendorp,' 'willingness to pay,' 'monetization,' 'how much should I charge,' 'my pricing is wrong,' 'pricing page,' 'annual vs monthly,' 'per seat pricing,' or 'should I offer a free plan.' Use this whenever someone is figuring out what to charge or how to structure their plans. For in-app upgrade screens, see paywall-upgrade-cro.