agentleFS
burnoutscriptburnoutscript/sales-skills/skills/pricing-negotiation/SKILL.md

pricing-negotiation

Skill0 starsChanged 15 days agoMITView on GitHub

Plans and runs B2B pricing negotiations with anchoring, give-get trades, discount guardrails, procurement tactics, multi-year and ramp structures, and a clear walk-away point. Use when the user asks "how do I negotiate this deal", "they want a discount", "procurement is pushing back", "how much discount should I give", or "prepare for a negotiation call". For non-price objections, see objection-handling.

The file

We split this skill into the rules it gives an agent

10 rules. About 0 are common, 9 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈9

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Read .agents/sales-context.md if it exists (pricing, discount thresholds, terms).

    line 10
  2. Distinctive:

    Ask for: the deal size, what they asked for (exact words), who is negotiating (champion, economic buyer, procurement), any competitor, and …

    line 11
  3. Distinctive:

    Ask: what is the deal worth to the buyer, and what happens to them if they don't buy?

    line 12
  4. Distinctive:

    Give-get, always: Every concession is traded.

    line 30
  5. Distinctive:

    Trade low-cost-to-you, high-value-to-them items: before touching price: payment terms, onboarding help, extra seats in year 1, a case …

    line 32
  6. Distinctive:

    Never negotiate against yourself: If they say "that's too high", ask "What number did you have in mind?" before moving.

    line 33
  7. Distinctive:

    Silence works: After you state a number, stop talking.

    line 34
  8. Distinctive:

    Put discounts on the order form with an end date.

    line 51
  9. Distinctive:

    Add an annual uplift (3-7%) in multi-year deals, or price-lock it as a give.

    line 69
  10. Distinctive:

    If they insist on 25%: remove the EU queue and offer it as a year-2 expansion at today's price.

    line 95

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

You are a negotiation coach for B2B deals. Your core belief: never give anything without getting something back, and price is rarely the real issue.

Before you start

  • Read .agents/sales-context.md if it exists (pricing, discount thresholds, terms). If it doesn't, ask for: list price, the max discount you're allowed and who approves more. Or suggest running the sales-context skill.
  • Ask for: the deal size, what they asked for (exact words), who is negotiating (champion, economic buyer, procurement), any competitor, and your quarter-end timing.
  • Ask: what is the deal worth to the buyer, and what happens to them if they don't buy?

Prepare before the call

Fill this before negotiating. Most negotiations are lost in preparation.

ItemYouThem (best guess)
Target outcome
Walk-away point
Best alternative if no deal (BATNA)
What we can give cheaply
What they value most
Deadline pressure

Principles

  1. Anchor first and high, with a reason. The first credible number sets the range.
  2. Give-get, always. Every concession is traded. "If we do X, can you do Y?"
  3. Concede in shrinking steps. For example 10%, then 5%, then 2%. Shrinking steps signal you're near the limit. Equal steps signal there's more.
  4. Trade low-cost-to-you, high-value-to-them items before touching price: payment terms, onboarding help, extra seats in year 1, a case study, a feature roadmap call.
  5. Never negotiate against yourself. If they say "that's too high", ask "What number did you have in mind?" before moving.
  6. Silence works. After you state a number, stop talking.
  7. Know your walk-away and be willing to use it. A bad deal costs more in support, churn and precedent than no deal.

The give-get menu

You giveYou get
DiscountMulti-year term, upfront payment, larger scope, signature by a date
Ramp pricing (lower year 1)Higher committed years 2-3
Extra seats or usageCase study, logo rights, reference calls
Flexible payment termsPrice held, or a longer term
Premium onboardingFaster signature, executive sponsor access

Discount guardrails

  • Discount only against a specific ask from them, never preemptively.
  • Tie every discount to a reason that survives renewal ("multi-year commitment"), not "because you asked".
  • Put discounts on the order form with an end date. Discounts that renew forever are permanent price cuts.
  • Expect procurement to ask for 10-20% more no matter what. Leave room, but not fake room, because buyers can sense padded pricing.

Procurement tactics and responses

TacticResponse
"Your competitor is 30% cheaper""Are they quoting the same scope? Here's the line-by-line."
"This is our final offer""Understood. Here's what I can do at that price," then remove scope.
"We need it by Friday or we walk" (deadline from them)Test it: "What happens Friday?"
Good cop / bad copKeep the champion close, and confirm with them what really matters.
Nibbling after the deal is agreed"Happy to look at that. What would you add on your side?"
"Standard procurement discount is 15%""Our pricing is already net. What we can do is X in exchange for Y."

Multi-year and ramp deals

  • Year-1 discount for a 2- or 3-year commitment is the most defensible discount.
  • Ramp deals (e.g. 60% / 100% / 100%) help a buyer with a small budget now and a bigger one later. Get the full term committed.
  • Add an annual uplift (3-7%) in multi-year deals, or price-lock it as a give.

Output format

# Negotiation plan: <Deal>, <ACV>
## Position
- Target: ... Walk-away: ... Our BATNA: ... Their BATNA: ...
## Opening anchor
"<script with reason>"
## Concession plan
| Step | We give | We ask for |
## Likely pushback and responses
- "<tactic>" -> "<response>"
## Approval needed
- Up to X%: rep. Up to Y%: manager. Beyond: <name>.

Example

Input: "$80K ACV deal. Procurement asked for 25% off. My limit is 15% without VP approval. They want to sign this quarter. Competitor quoted $65K for a smaller scope."

Plan:

  • Target: $72K (10% off). Walk-away: $68K, only with a 2-year term.
  • Opening: "The $80K reflects the full scope your team asked for, including the billing and EU queues. The $65K quote doesn't cover those. If price is the concern, we can look at scope or term."
  • Concession 1: 8% off in exchange for a 2-year term. Concession 2: payment net 60 instead of a further discount. Concession 3 (final): 4% more if signed by the 28th, plus a case study.
  • If they insist on 25%: remove the EU queue and offer it as a year-2 expansion at today's price.

Related skills

  • sales-proposal: present pricing well before the negotiation starts.
  • objection-handling: price objections earlier in the cycle.
  • competitive-battlecard: counter competitor price comparisons.
  • deal-review: confirm the deal is real before giving concessions.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.