Pricing Negotiation Guide
pricing_negotiation_guideAssess leverage and generate a value-based negotiation strategy, pushback responses, and discount approval guidance for pricing talks so you can answer discount requests without giving away margin.
Instructions
Helps you decide how to answer a discount request without giving away margin. You give the negotiation scenario, plus deal value, the discount asked, each side's leverage and who approves. You get a leverage assessment, a value based negotiation strategy, answers to common pushback and a discount approval framework. Read-only for business data. It needs no sign-in and stores no inputs or outputs. Hosted usage metadata is recorded. Missing required fields or invalid values return an error naming what to supply or correct. Use this instead of roi_business_case_builder when you need responses and approval guidance for a discount discussion. Ask whether the user has authority to approve the proposed terms.
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"scenario": "<scenario>"
},
"name": "pricing_negotiation_guide"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| scenario | Yes | Negotiation scenario. Format is text using one of the listed labels. For example, "discount_request". | |
| deal_value | No | Current deal value. Format is a JSON number. For example, 12. | |
| your_sector | No | Optional: your company's own industry (not your customers'). When given, it decides the sector notes; when left out, the tool reads it from your words and stays neutral if they are unclear. Format is text using one of the listed labels. For example, "logistics_tech". | |
| your_leverage | No | Your leverage points (unique features, timeline, etc.). Format is text. For example, "renewal decision depends on a documented approval process". | |
| your_solution | No | Your product/solution. Named in the guide and used, with your leverage, to read the sector and how you charge. Format is text. For example, "invoice review service". | |
| business_model | No | Optional: how you charge (software subscription, services, connectivity, per transaction, marketplace, hardware plus software, or investment management). Read from your other inputs when left out. Format is text using one of the listed labels. For example, "saas". | |
| buyer_leverage | No | Buyer leverage points (size, reference potential, etc.). Format is text. For example, "renewal decision depends on a documented approval process". | |
| value_delivered | No | Quantified value your solution delivers. Used in the value reframe, word for word; the guide adds no value figure of its own. Format is text. For example, "200 to 500 employees". | |
| competitor_price | No | Competitor pricing if known. Format is text. For example, "USD 24000 per year". | |
| decision_timeline | No | When decision needs to be made. Format is text. For example, "six weeks". | |
| approval_authority | No | Who has final approval on pricing. Format is text. For example, "commercial director approves discounts above 10%". | |
| discount_requested | No | Discount percentage requested. Format is a JSON number. For example, 12. | |
| pricing_authority_status | No | Optional confirmed fact. Ask whether the user can approve this price or discount. Free-text role titles do not establish authority; unconfirmed authority holds commitment to terms. Format is text using one of the listed labels. For example, "authorized". |