These prompts help working salespeople craft objection responses on the spot. Copy any prompt, fill in your variables, and get a polished response you can use immediately in your next conversation or follow-up email.
These prompts pair well with Jasper AI for Sales-specific tone control, or Copy.ai for fast iteration.
Price and Budget Objections
You are a sales professional responding to a price objection. The prospect said: “{exact_objection_quote}”. Your product is {product_name} priced at {price_point}. The main competitor they’re comparing to is {competitor_name} at {competitor_price}. Your key differentiators are: {three_unique_value_points}. The prospect’s role is {job_title} at a {company_size} company in {industry}. Their main business challenge is {primary_pain_point}. Write a 150-200 word response that acknowledges their concern, reframes price as investment, presents one concrete ROI calculation, and asks a qualifying question about their decision criteria.
When to use it: Right after a prospect says your solution is too expensive or over budget.
Pro tip: Always include a specific ROI number in your reframe. Vague “you’ll save money” statements don’t move deals forward.
You are following up after a prospect went dark following a price discussion. Meeting date: {last_meeting_date}. Proposed solution: {solution_name} for {quoted_price}. Their stated budget was {their_budget}. Key stakeholder you presented to: {contact_name}, {job_title}. Their biggest concern during the demo was {main_concern}. Competitor they mentioned: {competitor_if_any}. Decision timeline: {their_timeline}. Write a 250-300 word follow-up email that addresses the price gap, offers a modified solution, includes social proof from a similar company, and suggests a 15-minute call to discuss options.
When to use it: When a qualified prospect stops responding after seeing your proposal or quote.
Pro tip: Offer a stripped-down version rather than a discount. It shows flexibility without devaluing your full solution.
You are in a live sales call where the prospect just said: “{price_objection_quote}”. Your solution: {product_service_name}. Annual contract value: {contract_value}. Their current solution: {current_solution} costing {current_cost}. Implementation timeline: {timeline_weeks} weeks. Team size affected: {number_of_users}. Their main KPI they want to improve: {target_metric}. Industry: {industry}. Write a 100-150 word verbal response using the “Feel, Felt, Found” framework that keeps the conversation moving toward next steps.
When to use it: During discovery calls or demos when price resistance surfaces unexpectedly.
Pro tip: Pause for 3 seconds after delivering your response. Let them process instead of immediately jumping to discounting.
You are preparing talking points for a budget conversation. Prospect company: {company_name} in {industry}. Contact: {contact_name}, {job_title}. Their team size: {team_size}. Current annual spend on {solution_category}: {current_spend}. Your solution price: {your_price}. Payback period: {payback_months} months. Competitor pricing: {competitor_price}. Their fiscal year end: {fiscal_year_end}. Create a 300-400 word script that opens with a budget-qualifying question, presents three pricing options, includes a risk-reversal offer, and closes with a trial close.
When to use it: Before important budget discussions with decision-makers who haven’t seen pricing yet.
Pro tip: Always present your middle option first, then frame your premium and basic options around it.
You are responding to a CFO who said: “{cfo_objection_quote}” during a final decision meeting. Your champion inside the company is {internal_champion} who wants to move forward. Business case metrics: {roi_percentage}% ROI over {timeframe}. Risk if they don’t solve the problem: {risk_cost_or_impact}. Their current quarterly burn on this problem: {quarterly_cost}. Implementation start date they need: {start_date}. Write a 200-250 word response that speaks CFO language, includes hard numbers, addresses implementation risk, and suggests a pilot program.
When to use it: When financial decision-makers are concerned about spend approval or budget allocation.
Pro tip: CFOs care more about cash flow timing than total cost. Lead with quarterly impact, not annual savings.
Timing and Urgency Objections
You are responding to a timing objection. The prospect said: “{timing_objection_quote}”. Current quarter: {current_quarter}. Their stated timeline: {their_preferred_timeline}. The business problem they’re trying to solve: {problem_description}. Cost of delayed implementation: {delay_cost_monthly}. Their busy season: {busy_period}. Decision-making team: {team_members}. Your implementation timeline: {implementation_weeks} weeks. Write a 150-200 word response that creates urgency without being pushy, offers flexible start dates, and identifies the real reason behind their delay.
When to use it: When prospects want to push decisions to next quarter or “when things slow down.”
Pro tip: Ask about their planning cycle. Many timing objections are really budget cycle or resource allocation issues in disguise.
You are writing a follow-up email to restart a stalled deal. Last contact date: {last_contact_date}. Reason they postponed: {stated_reason}. Original timeline: {original_timeline}. Solution: {solution_name}. Key benefits they were excited about: {top_benefits}. Stakeholder you were working with: {contact_name}. Their role: {job_title}. Trigger event that might change their priorities: {recent_company_news_or_season}. Write a 200-250 word re-engagement email that references their original goals, introduces new urgency, shares relevant industry insight, and requests a brief catch-up call.
When to use it: Reconnecting with prospects who went quiet after expressing initial interest but delaying decisions.
Pro tip: Reference specific metrics or goals they shared in earlier conversations. It proves you were listening and differentiates your follow-up.
You are handling a “we’ll revisit this next year” objection in a Q4 sales conversation. Current date: {current_date}. Prospect: {company_name} in {industry}. Contact: {contact_name}, {job_title}. Problem they’re facing: {current_problem}. Cost of the problem: {problem_cost_monthly}. Your solution: {solution_name}. Implementation time: {implementation_timeline}. Their new fiscal year starts: {fiscal_year_start}. Competitor activity in their space: {competitive_pressure}. Write a 180-220 word response that reframes timing, presents year-end benefits, addresses budget concerns, and offers a January start option.
When to use it: During Q4 conversations when prospects want to defer until the following year.
Pro tip: Many companies have Q4 budget surplus they need to spend. Ask directly about remaining budget allocation.
You are preparing for a call with a prospect who keeps rescheduling meetings. Company: {company_name}. Contact: {contact_name}, {job_title}. Number of reschedules: {reschedule_count}. Stated reason: “{stated_reason}”. Original pain point discussed: {pain_point}. Your solution: {solution_brief}. Their team size affected: {affected_team_size}. Industry pressure they’re facing: {industry_challenge}. Create a 250-300 word email script that addresses their time constraints, proposes a micro-commitment, offers asynchronous options, and includes a polite challenge about their priorities.
When to use it: When qualified prospects keep pushing meetings but haven’t explicitly said no.
Pro tip: Offer a 10-minute “quick question” call instead of a full demo. Lower commitment often gets you back on their calendar.
You are responding to: “We’re too busy with {current_priority} to think about this right now.” Your solution helps with: {solution_benefit}. Time to implement: {implementation_time}. Monthly cost of their current problem: {monthly_cost}. Their team size: {team_size}. Busy period duration: {busy_period_length}. Your fastest implementation option: {quick_implementation_option}. Write a 120-180 word response that acknowledges their priority, connects your solution to their current focus, offers a minimal-disruption option, and secures a specific follow-up date.
When to use it: When prospects are genuinely swamped with other projects or initiatives.
Pro tip: Position your solution as helping them handle their current priority more efficiently, not as another competing priority.
Authority and Decision-Making Objections
You are responding to: “I need to run this by {decision_maker_name}” during a sales conversation. Your contact: {contact_name}, {contact_title}. Decision maker: {decision_maker_name}, {decision_maker_title}. Solution discussed: {solution_name}. Key benefits your contact is excited about: {benefits}. Typical objections from this type of decision maker: {likely_objections}. Budget range: {budget_range}. Timeline: {timeline}. Write a 200-250 word response that positions your contact as an internal champion, provides ammunition for their conversation, offers to help with the presentation, and secures next steps.
When to use it: When your primary contact needs to get approval from someone you haven’t met yet.
Pro tip: Ask your contact what questions the decision maker typically asks. This uncovers the real decision criteria.
You are preparing your champion for a presentation to their executive team. Champion: {champion_name}, {champion_role}. Executives attending: {executive_names_and_roles}. Meeting duration: {meeting_length}. Your solution: {solution_name}. Business case: {roi_or_benefit}. Implementation effort: {effort_level}. Budget required: {budget_amount}. Main risk if they don’t act: {risk_description}. Competitor alternative: {competitor_name}. Create a 350-400 word briefing document with three key talking points, anticipated objections and responses, and specific metrics they can reference.
When to use it: Before your champion presents your solution to decision-makers without you in the room.
Pro tip: Include one compelling customer story that mirrors their situation. Executives relate to peer success more than product features.
You are writing a follow-up email after your contact said they presented to their team but need “more time to discuss internally.” Last presentation date: {presentation_date}. Your solution: {solution_name}. Team members involved in decision: {team_member_roles}. Feedback they shared: “{feedback_received}”. Concerns raised: {concerns}. Timeline they mentioned: {timeline}. Competitor they’re considering: {competitor}. Write a 180-220 word email that uncovers the real issues, offers additional resources, suggests a group Q&A session, and creates gentle urgency.
When to use it: When deals stall in internal discussions after your champion makes the presentation.
Pro tip: Offer to join their next internal discussion as a resource, not a presenter. It removes pressure while keeping you involved.
You are requesting a meeting with the actual decision maker after working with an influencer. Current contact: {current_contact}, {contact_role}. Actual decision maker: {decision_maker}, {decision_maker_role}. Relationship between them: {relationship_dynamic}. Problem you’re solving: {problem}. Solution fit: {solution_fit_level}. Budget confirmed: {budget_status}. Timeline pressure: {timeline_pressure}. Write a 150-200 word request that respects your current contact, positions the meeting as helpful for everyone, suggests a specific agenda, and makes it easy to say yes.
When to use it: When you need to upgrade your contact level to close the deal.
Pro tip: Frame it as helping your contact look good to their boss, not as going around them.
You are responding to: “The team isn’t aligned yet on whether we need this.” Company: {company_name}. Main contact: {contact_name}. Team members involved: {team_member_roles}. Different perspectives: {different_viewpoints}. Current problem impact: {problem_cost}. Your solution: {solution_name}. Implementation complexity: {complexity_level}. Write a 200-250 word response that offers to facilitate alignment, suggests a stakeholder interview process, provides a decision framework, and maintains momentum while they work through internal dynamics.
When to use it: When different stakeholders have conflicting priorities or views on the problem.
Pro tip: Offer to speak with each stakeholder individually to understand their specific concerns. It shows you care about consensus-building.
Competitor and Alternative Solution Objections
You are responding to: “We’re looking at {competitor_name} and they seem to offer {competitor_advantage}.” Your solution: {your_solution}. Key differentiator: {main_differentiator}. Competitor weakness: {competitor_weakness}. Prospect’s most important requirement: {top_requirement}. Their team size: {team_size}. Industry: {industry}. Budget range: {budget}. Write a 180-220 word competitive response that acknowledges the competitor’s strength, highlights your unique advantage, shares a relevant customer example, and focuses on their specific needs rather than general feature comparisons.
When to use it: When prospects are actively evaluating direct competitors alongside your solution.
Pro tip: Never badmouth competitors. Instead, position the choice as different approaches to solving their problem.
You are writing a competitive battle card summary for an active deal. Prospect: {company_name}. Your solution: {solution_name}. Competitor: {competitor_name}. Decision criteria they’ve shared: {decision_criteria}. Your strengths vs competitor: {your_advantages}. Competitor’s likely pitch: {competitor_strengths}. Prospect’s biggest pain point: {main_pain_point}. Timeline: {decision_timeline}. Create a 300-350 word competitive strategy that positions your solution favorably, anticipates competitor objections to your approach, provides proof points, and includes questions that highlight competitor weaknesses.
When to use it: Preparing for final presentations when you’re head-to-head with a known competitor.
Pro tip: Focus on business outcomes, not features. Ask questions about implementation support and long-term partnership, not just product capabilities.
You are responding to: “We’re considering building this internally instead.” Their team size: {dev_team_size}. Internal capability: {technical_capability}. Timeline if they build: {build_timeline}. Your solution timeline: {your_timeline}. Cost to build internally: {estimated_build_cost}. Your solution cost: {your_cost}. Ongoing maintenance needs: {maintenance_requirements}. Their core business: {core_business}. Write a 200-250 word response that respects their capability, presents build vs buy considerations, highlights hidden costs, and positions your solution as letting them focus on their core business.
When to use it: When technically capable companies are considering internal development over purchasing.
Pro tip: Ask about opportunity cost. What strategic projects would they delay to build your solution internally?
You are handling the objection: “We’re not sure we need a solution at all - maybe we can work around this.” Current problem: {problem_description}. Cost of current workarounds: {workaround_cost}. Team time spent on workarounds: {time_cost}. Growth plans that would make problem worse: {growth_plans}. Your solution: {solution_name}. ROI timeline: {roi_timeline}. Write a 150-200 word response that quantifies the hidden cost of status quo, projects future impact, shares a similar customer story, and suggests a low-risk way to test your solution.
When to use it: When prospects are considering doing nothing instead of investing in a solution.
Pro tip: Calculate the cost of their time spent on workarounds. Most prospects underestimate this hidden expense.
You are competing against a much cheaper alternative. Prospect: {company_name}. Your solution: {solution_name} at {your_price}. Cheaper alternative: {cheaper_option} at {lower_price}. Quality/capability difference: {capability_gap}. Their risk tolerance: {risk_level}. Company stage: {company_maturity}. Compliance requirements: {compliance_needs}. Team expertise: {team_skill_level}. Write a 200-250 word response that acknowledges budget constraints, explains total cost of ownership, identifies risks of the cheaper option, and offers a middle-ground alternative or pilot program.
When to use it: When price-focused prospects are comparing you to significantly cheaper alternatives.
Pro tip: Ask about the cost of getting it wrong. Sometimes the risk of a failed implementation outweighs the savings.
Frequently Asked Questions
How do I customize these ChatGPT prompts for different industries?
Replace the industry variable with specific terminology and pain points from your sector. Add industry-specific compliance, regulations, or competitive dynamics to make responses more relevant and credible to prospects.
What’s the best way to handle objections that combine multiple concerns like price and timing?
Use the price objection prompts but add timing variables like fiscal year end and budget cycles. Address the easier objection first (usually timing) to build momentum before tackling the bigger concern (price).
How can I make these objection responses sound more natural in conversations?
Practice the key phrases out loud before calls. Adapt the language to match your speaking style and remove overly formal phrases that don’t fit how you normally communicate with prospects.