Pricing Objection Reply
Handle a prospect's pricing objection with value, scope options, and a clear decision deadline.
Customise & copy
Add the context you have. The prompt updates as you work.
Enter the product or service being offered.
Include the prospect's budget, spending limit, or specific pricing concern.
Provide the measurable business outcome the offer is expected to influence.
Enter the competitor only if the prospect mentioned one.
Enter the date or stated deadline by which the project must begin.
Live prompt
5 fieldsWrite a concise reply to a prospect who said, "Your price is too high." Use only the information provided below. Do not invent results, testimonials, customer examples, competitor claims, savings, or facts. Return exactly four numbered paragraphs: 1. Acknowledge the cost concern and accurately reflect the stated constraint: {{budget_constraint}}. 2. Reconnect the price to the specific value metric or ROI driver: {{value_metric}}. Refer to {{product_service}} by name. If a competitor was mentioned, address No competitor mentioned only using facts supplied here; otherwise do not introduce a comparison. 3. Offer one or two non-discount options, prioritizing scope changes, phased delivery, or timing adjustments. Do not offer a price discount or invent payment terms. Keep the options relevant to {{product_service}}. 4. State a clear decision deadline tied to the required project start: {{project_start_deadline}}. If an exact date is supplied, use it explicitly; if not, do not invent a calendar date, but clearly state that a decision is needed by the stated start deadline. Use direct business language with no greeting, sign-off, hype opener, politeness padding, social proof, or explanation of your process. Produce only the four numbered paragraphs, ready to send after one light edit.
Proof before you use it
A real example
Tested on gpt-5.6-luna on 2026-09-10
{
"value_metric": "Shorten remediation planning time and identify HIPAA control gaps before the next external audit.",
"competitor_name": "Deloitte",
"product_service": "Cybersecurity compliance assessment for regional hospitals",
"budget_constraint": "The nonprofit healthcare network can commit up to $25,000 this fiscal year.",
"project_start_deadline": "The assessment must begin before the September 15 audit-readiness review"
}A small ritual that works
How to use it
- 01Enter the product or service name.
- 02Add the prospect's budget constraint and the key value metric or ROI driver.
- 03Name a competitor only if the prospect mentioned one; otherwise use the provided default.
- 04Enter the required project start deadline.
Why it works
The prompt gives the reply a clear four-part sequence: acknowledge the budget concern, connect price to a supplied value metric, offer non-discount options, and establish a deadline. It also limits the source material, prohibits invented claims, and defines how to handle competitor references and dates. These constraints make the intended sales message easy to follow while keeping the language grounded in the provided inputs.
Where it fails
The instructions contain a formatting conflict: the prompt requests exactly four numbered paragraphs, while the surrounding requirement requests a JSON object with named fields. A system that follows both literally cannot satisfy both formats at the same time.
Customisation tips
Make each variable specific enough to support a direct reply. State the budget concern in the prospect's own terms, define a concrete value metric, name the product or service precisely, and provide an actual start deadline when one exists. Leave the competitor field at its default when no comparison was raised. Scope-change and phased-delivery options should reflect choices that are genuinely available for the offering.
Watch-outs
- The value metric must be concrete and supplied in advance; the prompt does not authorize the writer to calculate savings or invent an ROI claim.
- Competitor references are deliberately restricted to facts provided in the inputs, so an empty or default competitor field should not lead to a comparison.
- The deadline language distinguishes between an exact date and a general stated deadline; adding a calendar date when none was supplied would violate the instruction.
- The non-discount guidance permits scope, phasing, and timing adjustments but does not permit invented payment terms or an unapproved discount.
Works in
Was this useful?
Submit your variation
If your version helps, it may be published with your name and a link back to you.
Want to make AI useful across your team? Explore Atul's training.