sales-value-negotiation
Skill0 starsChanged 41 days agoMITView on GitHub
Use when a B2B buyer requests concessions, a proposal stalls on commercial terms, or several issues permit tradeoffs.
In this repository66 other files it gives its agents.
- AGENTS.mdAGENTS.md
- postgres-locking-joinsSkill
- ai-bug-patternsSkill
- compressed-ndjson-boundariesSkill
- http-resume-integritySkill
- linux-io-latency-triageSkill
- macos-disk-space-recoverySkill
- minimal-sufficient-evidenceSkill
- modularize-large-filesSkill
- patch-reproducer-validitySkill
- prompt-cache-boundariesSkill
- proton-drive-selective-backupSkill
- transactional-outbox-deliverySkill
- conventional-commitsSkill
- git-advanced-mergingSkill
- git-bisect-forensicsSkill
- git-data-recoverySkill
- git-hooksSkill
- git-rerereSkill
- git-reset-mechanicsSkill
- git-revisions-syntaxSkill
- git-rewriting-historySkill
- git-submodulesSkill
- git-worktreesSkill
- github-ssh-keysSkill
- npm-publish-ci-pitfallsSkill
- sapling-stacked-pr-workflowSkill
- go-concurrency-patternsSkill
- go-data-idiomsSkill
- go-error-handlingSkill
- go-interfaces-embeddingSkill
- go-pprof-profilingSkill
- marketing-funnel-diagnosisSkill
- marketing-geo-experimentsSkill
- marketing-incrementalitySkill
- marketing-positioning-testsSkill
- python-descriptors-mroSkill
- python-logging-cookbookSkill
- python-scaling-regression-testsSkill
- python-unicode-gotchasSkill
- rust-compile-time-invariantsSkill
- rust-deterministic-concurrency-testsSkill
- rust-error-identity-boundariesSkill
- rust-regex-search-contractsSkill
- rust-runtime-bug-classesSkill
- rust-tokio-actor-deliverySkill
- rust-tokio-cancellation-safetySkill
- sales-discovery-qualificationSkill
- sales-mutual-action-plansSkill
- sales-pipeline-forecast-calibrationSkill
- ai-triage-evaluationSkill
- container-image-patchingSkill
- dependency-artifact-integritySkill
- dnssec-sentinel-diagnosticsSkill
- iam-policy-change-replaySkill
- rbvm-applicabilitySkill
- rbvm-asset-evidenceSkill
- rbvm-guarded-remediationSkill
- rbvm-priority-decisionsSkill
- rbvm-risk-exceptionsSkill
- The first 60 shown.
The file
Files
Sales Value Negotiation
Negotiate the whole package against realistic alternatives. Scope, delivery, payment timing, support, and risk may matter differently to each side. Use for considered agreements, not every fixed-price transaction.
Diagnose before conceding
| Buyer signal | Test | Useful response |
| “Too expensive” | Affordability, expected value, comparison, or payment timing? | Address the specific constraint |
| “Competitor is cheaper” | Equivalent scope, service, term, implementation, and risk? | Compare like-for-like evidence |
| “We need a guarantee” | Which uncertain outcome, measured how, under whose control? | Clarify risk and feasible proof |
| “Discount and we sign” | Remaining approvals and authorized decision-maker? | Verify conditions before trading |
Prepare defensible packages
- Separate stated interests from hypotheses. Use buyer-validated outcomes and relevant objective benchmarks; never invent ROI, competing offers, or deadlines.
- Identify feasible no-agreement alternatives and their costs. Select the best alternative (BATNA), set a target and minimum acceptable package, and confirm concession authority. A hoped-for deal is not an available alternative.
- Price delivery effort, payment timing, support load, implementation risk, and opportunity cost. Keep private limits out of buyer-facing drafts.
- Construct two or three genuinely acceptable packages with approximately equivalent seller value but different buyer tradeoffs. Present complete alternatives; ask which fits better and why; revise accordingly. Equivalence requires a cost/risk model, not equal sticker prices.
- Make concessions explicit and, where appropriate, conditional on reciprocal changes. Recalculate the entire revised package against the minimum; escalate anything outside authority. Record tentative versus approved terms.
Illustrative arithmetic: a $30,000 project with $10,000 delivery cost and a reduced-scope $27,000 project with $7,000 cost contribute $20,000 each before overhead. They are not equivalent if payment timing, liability, or delivery risk differs. Do not promise identical outcomes without evidence.
Sources
- Harvard PON: preparation and BATNA
- Harvard PON: simultaneous package offers
- Deepak Malhotra: concessions
Pitfalls
- Bundling hides economics if the buyer cherry-picks each package's cheapest term; reprice the combination.
- Giving concessions before diagnosing the obstacle can sacrifice margin without resolving it.
- Artificial scarcity, sham alternatives, and pressure destroy informed agreement.
- A prepared proposal does not authorize sending, accepting terms, or binding either party.
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
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.

