Ready-to-use AI prompts that generate professional objection handling scripts in seconds. Copy any prompt, fill in your variables, and get responses that turn objections into conversations.
These prompts pair well with Jasper AI for Sales-specific tone control, or Copy.ai for fast iteration.
Budget and Pricing Objections
You are a sales professional handling a price objection from a qualified prospect.
Prospect: {prospect_name} Company: {company_name} Product: {product_or_service} Price quoted: {price_amount} Objection stated: “{exact_objection_quote}” Key benefit they mentioned interest in: {main_benefit_discussed} Competitor they might be considering: {competitor_name_or_unknown} Your relationship stage: {first_call / second_meeting / proposal_stage} Budget range they hinted at: {budget_range_or_unknown}
Write a 150 to 200 word response script that acknowledges their concern, reframes value around the specific benefit they care about, and asks one diagnostic question to uncover the real budget situation. Use a consultative tone, not defensive. End with a clear next step.
When to use it: Right after a prospect says your solution costs too much, before you start discounting.
Pro tip: Always include their exact objection quote in the variable - AI responses feel more natural when they echo the prospect’s specific language.
You are a sales rep responding to a prospect who says they need to compare your pricing to cheaper alternatives.
Prospect: {prospect_name} Your solution: {product_name} Cheaper alternative mentioned: {competitor_or_option} Price difference: {approximate_difference} Unique advantage of your solution: {key_differentiator} Implementation timeline: {timeline} Prospect’s biggest pain point: {main_problem} Decision maker involvement: {solo_decision / needs_approval / committee}
Create a 180 to 220 word script that validates their comparison process, highlights the cost of their current problem, and positions the price difference as an investment in avoiding bigger costs. Include one specific question that gets them to quantify their pain point. Close with offering a detailed ROI breakdown.
When to use it: When prospects mention they’re shopping around or found cheaper options.
Pro tip: Focus the ROI question on time wasted or revenue lost, not just money saved - it creates more urgency than feature comparisons.
You are handling a budget timing objection from a prospect who likes your solution but claims they have no money this quarter.
Prospect: {prospect_name} Company: {company_name} Current quarter: {Q1 / Q2 / Q3 / Q4} When they claim budget becomes available: {timeframe} Urgency of their problem: {high / medium / low} Consequences of waiting: {specific_cost_or_impact} Your solution’s implementation time: {timeframe} Payment options available: {payment_flexibility} Seasonal factors affecting their business: {seasonal_impact_or_none}
Write a 160 to 190 word response that empathizes with budget cycles, calculates the cost of waiting, and offers creative payment timing. Include one question about the impact of delaying the solution. Position this as protecting their future budget, not pressuring their current one.
When to use it: When timing objections feel like budget objections in disguise.
Pro tip: Ask about their budget process timeline - many prospects don’t realize they can get budget approved mid-cycle for solutions with clear ROI.
You are responding to a prospect who says they’ll handle the problem internally instead of buying your solution.
Prospect: {prospect_name} Internal alternative they mentioned: {internal_solution} Your solution: {product_or_service} Key advantage over internal approach: {main_differentiator} Time they’d need to build internally: {estimated_timeline} Their team’s current workload: {busy / manageable / unknown} Expertise gap for internal solution: {technical_gap} Risk of internal project failing: {risk_factors}
Create a 200 to 240 word script that respects their internal capabilities while highlighting hidden costs of building internally. Calculate opportunity cost of their team’s time. Ask one pointed question about resource allocation. End by positioning your solution as letting them focus on their core business.
When to use it: When prospects think they can build or do internally what you’re selling.
Pro tip: Don’t attack their internal capabilities - instead focus on what they won’t be able to do while building your solution internally.
You are addressing a prospect who wants the premium features but says they can only afford the basic package.
Prospect: {prospect_name} Basic package price: {basic_price} Premium package price: {premium_price} Premium features they want: {desired_features} Gap in value delivery: {what_basic_misses} Implementation timeline: {timeframe} Upgrade path available: {upgrade_options} Typical upgrade timing: {when_clients_upgrade} Cost of not having premium features: {specific_impact}
Write a 170 to 200 word script that validates starting with basic while highlighting the real cost of missing premium features. Offer a growth path that starts basic but has a clear upgrade trigger. Ask one question about the volume or scale where premium becomes essential. Make upgrading feel inevitable, not optional.
When to use it: When prospects want more than they can afford but something is better than nothing.
Pro tip: Set a specific metric or timeline for the upgrade conversation - it prevents basic customers from staying basic forever.
Authority and Decision-Making Objections
You are handling a prospect who says they need to discuss your proposal with their boss before deciding.
Prospect: {prospect_name} Decision maker they need to consult: {boss_title} Your relationship with decision maker: {met_them / haven’t_met / unknown} Key concerns the prospect has raised: {main_concerns} Proposal value: {proposal_amount} Timeline pressure: {urgent / moderate / flexible} Approval process typical length: {timeframe_or_unknown} Prospect’s influence level: {high / medium / low} What might derail approval: {potential_obstacles}
Create a 180 to 220 word response that supports their approval process without losing control. Offer to help them present to their boss. Ask who else might weigh in and what concerns the decision maker typically has. End by scheduling a follow-up before they have the internal conversation, not after.
When to use it: When you’re talking to an influencer who needs approval from someone you haven’t met.
Pro tip: Always ask what questions their boss will ask them - it reveals the real decision criteria and gives you a chance to arm them with good answers.
You are responding to a prospect who reveals that a committee needs to approve any purchase over your proposal amount.
Prospect: {prospect_name} Committee size: {number_of_people} Committee meeting frequency: {timeline} Your champion’s influence: {strong / moderate / weak} Proposal amount: {dollar_amount} Approval threshold: {committee_trigger_amount} Other vendors being considered: {competition_or_none} Champion’s biggest concern about committee: {main_worry} Timeline if approved: {implementation_start}
Write a 200 to 250 word script that helps your champion sell internally. Ask about each committee member’s priorities and objections. Offer to create a executive summary tailored to committee concerns. Request a brief meeting with key committee members. Position yourself as making their decision easier, not adding complexity.
When to use it: When you discover there’s a formal approval process you weren’t aware of.
Pro tip: Ask for the committee meeting agenda and see if you can present directly - even 10 minutes answering questions live is better than hoping your champion represents you well.
You are handling a prospect who says they’re the decision maker but then mentions needing to “run it by the team” for major decisions.
Prospect: {prospect_name} Team size affected by decision: {number_of_people} Team members’ roles: {relevant_titles} How team input affects decisions: {advisory / veto_power / unknown} Proposal scope: {what_youre_selling} Team’s current pain with status quo: {problems_solution_solves} Prospect’s leadership style: {collaborative / decisive / unknown} Timeline pressure: {urgent / moderate / flexible} Previous team buy-in on need: {yes / no / mixed}
Create a 160 to 190 word response that clarifies the decision process without questioning their authority. Ask specifically what the team needs to know and what their concerns might be. Offer to address the team directly or provide materials that help sell the team. Frame team buy-in as increasing implementation success, not decision approval.
When to use it: When the “decision maker” reveals shared decision-making after you thought you were talking to the final authority.
Pro tip: Ask if anyone on the team has veto power - it reveals whether this is true consensus building or just courtesy consultation.
You are responding to a prospect who says their legal or procurement department needs to review your contract before they can proceed.
Prospect: {prospect_name} Reviewing department: {legal / procurement / compliance} Standard review timeline: {timeframe} Contract complexity: {standard / custom / unknown} Urgency of implementation: {timeline} Main legal concerns they anticipate: {liability / data / pricing / unknown} Procurement requirements: {vendor_requirements} Decision maker’s ability to expedite: {can_prioritize / fixed_process} Implementation delay cost: {impact_of_waiting}
Write a 180 to 210 word script that facilitates the review process instead of fighting it. Offer standard contract language that typically passes review quickly. Ask about specific concerns and review criteria. Request to speak with legal/procurement directly to answer questions. Calculate the cost of delayed implementation to motivate process speed.
When to use it: When legal or procurement review becomes an unexpected step in your sales process.
Pro tip: Ask if they’ve reviewed similar contracts before and what slowed them down - it helps you proactively address the issues that cause delays.
You are handling a prospect who claims they have decision authority but their questions suggest they’re actually gathering information for someone else.
Prospect: {prospect_name} Questions they’re asking: {types_of_info_requested} Level of detail they want: {surface / deep / technical} Urgency of their timeline: {rushed / thorough / unclear} References to “we” vs “I”: {pattern_observed} Budget authority they’ve claimed: {claimed_approval_level} Their role in implementation: {hands_on / oversight / unknown} Previous vendor evaluation experience: {experienced / new_to_this}
Create a 150 to 180 word response that uncovers the real decision structure without calling them a liar. Ask who will be implementing the solution and who typically needs to sign off on this type of purchase. Offer to provide information in a format that’s easy to share internally. Request to meet other stakeholders to ensure you’re addressing everyone’s concerns.
When to use it: When prospect behavior suggests they’re not the real decision maker despite claiming to be.
Pro tip: Ask about implementation team involvement - real decision makers know who will use the solution, information gatherers often don’t.
Timing and Urgency Objections
You are responding to a prospect who says they want to implement your solution but need to wait until next quarter or next year.
Prospect: {prospect_name} Current timeframe they suggested: {proposed_delay} Reason for waiting: {their_stated_reason} Current pain level: {high / medium / low} Cost of status quo per month: {monthly_impact} Your implementation timeline: {how_long_to_deploy} Seasonal factors: {busy_season / slow_period / neutral} What changes in their preferred timeframe: {what_makes_timing_better} Competitor involvement: {other_vendors / no_competition}
Write a 190 to 230 word script that validates their timing concerns while quantifying the cost of waiting. Calculate what the delay costs them in real terms. Ask what could make them move faster and what risks delaying creates. Offer implementation approaches that work around their timing constraints. End with a smaller commitment they could make now.
When to use it: When prospects like your solution but want to delay the purchase decision.
Pro tip: Ask what happens to their problem while they wait - often they haven’t considered that waiting means months more of the current pain.
You are handling a prospect who says they’re too busy to implement any new solution right now, regardless of value.
Prospect: {prospect_name} What’s keeping them busy: {current_priorities} Duration of busy period: {how_long_overloaded} Impact of their current problem: {pain_point_cost} Your solution’s implementation demands: {time_required_from_them} Available support during implementation: {your_team_involvement} Consequence of continued delay: {what_gets_worse} Team availability: {who_could_help_implement} Previous implementation experiences: {good / bad / none}
Create a 170 to 200 word response that acknowledges their bandwidth while repositioning implementation as reducing their workload, not adding to it. Break down what actually requires their time versus what your team handles. Ask what they’re spending time on that your solution would eliminate. Offer a pilot or phased approach that proves value before full commitment.
When to use it: When prospects claim they’re too busy to solve problems that would actually save them time.
Pro tip: Ask them to track time spent on the problem you solve for one week - the number is usually higher than they think.
You are responding to a prospect who wants to wait and see how your solution works for other clients before committing.
Prospect: {prospect_name} Their specific risk concerns: {what_worries_them} How long they want to wait: {timeframe} Other clients they could reference: {available_references} Proof points you can provide: {case_studies / trials / demos} Competitive advantage of early adoption: {first_mover_benefits} Cost of being a late adopter: {disadvantages_of_waiting} Their industry adoption patterns: {early / late / mainstream} Risk tolerance generally: {conservative / aggressive}
Write a 200 to 240 word script that addresses their need for proof without letting them wait indefinitely. Offer current client references and proof points. Highlight competitive advantages of early adoption and risks of late adoption. Propose a pilot program or limited trial that gives them proof with lower risk. Calculate what market position they lose by waiting.
When to use it: When prospects want social proof before making a decision.
Pro tip: Ask specifically what proof they need and by when - many prospects haven’t thought through what would actually convince them to move forward.
You are handling a prospect who says they want to evaluate one more quarter of results with their current solution before switching.
Prospect: {prospect_name} Current solution: {existing_system_or_process} Problems they’ve mentioned with current approach: {specific_issues} What they’re hoping improves: {what_they_want_to_see} Likelihood current solution will improve: {realistic_assessment} Cost of another quarter with current problems: {quantified_impact} Your solution’s proven results: {relevant_outcomes} Implementation time for your solution: {timeline} Switching costs or complexity: {barriers_to_change}
Create a 180 to 220 word response that respects their evaluation process while highlighting the opportunity cost of delay. Ask what specific results would convince them to switch and whether their current solution has shown any improvement trend. Calculate the cost of another quarter with current problems. Offer to run parallel evaluation or pilot to prove results during their assessment period.
When to use it: When prospects want to give their current solution more time despite ongoing problems.
Pro tip: Ask what trend they’d need to see to stick with current solution - often they realize the improvement they’re hoping for is unrealistic.
You are responding to a prospect who likes your solution but says they need to finish their current project before taking on anything new.
Prospect: {prospect_name} Current project: {what_theyre_working_on} Project completion timeline: {when_itll_be_done} Resource overlap between projects: {team_availability} Your solution’s resource requirements: {implementation_demands} Relationship between current project and your solution: {complementary / competing / unrelated} Cost of delaying your solution: {impact_of_waiting} Possibility of phased implementation: {can_you_start_small} Current project success dependence: {how_critical_is_it}
Write a 160 to 190 word script that works with their project timeline instead of against it. Ask about resource overlap and whether your solution could actually help their current project succeed. Explore phased implementation that doesn’t conflict with current priorities. Calculate what they lose by waiting until the project finishes. Offer support that complements rather than competes with current work.
When to use it: When prospects are prioritizing existing commitments over new solutions.
Pro tip: Ask if your solution would make their current project easier or more successful - sometimes you can position as supporting their current work rather than competing with it.
Competition and Alternative Solution Objections
You are responding to a prospect who says they’re seriously considering a competitor and want to understand why they should choose you instead.
Prospect: {prospect_name} Competitor being considered: {competitor_name} What attracted them to competitor: {competitor_appeal} Your key advantages over this competitor: {your_differentiators} Prospect’s most important criteria: {decision_factors} Price comparison: {higher / lower / similar} Implementation complexity difference: {easier / harder / similar} Long-term relationship value: {your_ongoing_advantages} Prospect’s risk tolerance: {conservative / aggressive}
Create a 220 to 260 word script that acknowledges the competitor’s strengths while clearly differentiating your value. Focus on the criteria that matter most to this prospect. Use specific examples of how your advantages translate to better outcomes for their situation. Ask what concerns they have about each option. End by offering a direct comparison or trial that lets them evaluate both solutions practically.
When to use it: When prospects are actively comparing you to a known competitor.
Pro tip: Never badmouth the competitor - instead focus on why your approach is better for their specific situation and goals.
You are handling a prospect who says they found a cheaper solution that seems to do the same thing as yours.
Prospect: {prospect_name} Cheaper alternative: {competitor_or_option} Price difference: {how_much_less} Apparent feature overlap: {what_seems_similar} Hidden differences: {what_cheaper_option_lacks} Long-term cost implications: {support / scaling / integration} Implementation complexity difference: {easier / harder} Your track record vs theirs: {experience_advantage} Risk of cheaper option failing: {specific_risks}
Write a 200 to 240 word response that validates their price sensitivity while uncovering hidden costs of the cheaper option. Ask about support, integration, and scaling requirements. Calculate total cost of ownership, not just purchase price. Highlight risks of going with less proven solutions. Offer to help them do a proper comparison that includes all costs and risks.
When to use it: When prospects found cheaper alternatives that seem comparable to your solution.
Pro tip: Ask about their experience buying the cheapest option for important business decisions - most have been burned before and will recognize the pattern.
You are responding to a prospect who wants to try a free or low-cost alternative first before investing in your premium solution.
Prospect: {prospect_name} Free/cheap alternative: {option_theyre_considering} What appeals to them about trying free first: {their_reasoning} Limitations of free option: {what_it_lacks} Time they’ll waste on inadequate solution: {opportunity_cost} Learning curve for multiple solutions: {switching_cost} Your entry-level option: {lower_cost_alternative} Upgrade path complexity: {how_easy_to_switch_later} Cost of starting over later: {migration_challenges}
Create a 180 to 220 word script that respects their testing approach while highlighting costs of the free-then-upgrade path. Calculate time and effort they’ll waste on inadequate solutions. Ask about their experience with free tools meeting enterprise needs. Offer your own trial or entry option that provides a real upgrade path. Position choosing right the first time as saving money long-term.
When to use it: When prospects want to experiment with free options before buying professional solutions.
Pro tip: Ask how they’ll measure whether the free option is actually working - most haven’t thought about success criteria and will realize they need real features quickly.
You are handling a prospect who says they’re building a shortlist and you’re just one of several vendors they’re evaluating.
Prospect: {prospect_name} Number of vendors on shortlist: {how_many_competitors} Evaluation criteria they’ve shared: {decision_factors} Timeline for decision: {when_theyll_choose} Your unique strengths vs others: {key_differentiators} Evaluation process details: {how_theyre_deciding} Who makes final decision: {decision_maker_info} Budget allocated: {approved_spending} Implementation timeline: {when_they_need_results}
Write a 190 to 230 word response that helps you stand out in their evaluation process. Ask about their specific evaluation criteria and weighting. Offer to provide information in whatever format helps their decision process. Request feedback on where you stand relative to other options. Position yourself as the safest choice that delivers results, not just the cheapest or flashiest option.
When to use it: When you’re clearly in a competitive evaluation process.
Pro tip: Ask what went wrong with their last vendor selection process - it reveals what they’re trying to avoid and gives you a chance to position differently.
You are responding to a prospect who says another vendor promised them everything they want for significantly less money.
Prospect: {prospect_name} Competing vendor: {competitor_name_or_unknown} What competitor promised: {their_offer} Price difference: {how_much_less} Delivery timeline promised: {their_timeline} Your assessment of promise feasibility: {realistic / optimistic / impossible} Red flags you notice: {warning_signs} Value of proven results: {your_track_record} Consequences of vendor failing to deliver: {what_happens_if_they_fail}
Create a 200 to 240 word script that raises appropriate caution about too-good-to-be-true offers without sounding defensive. Ask about the competitor’s track record and references for similar promises. Highlight the cost of vendor failure beyond just money. Request that they verify specific claims and implementation details. Position your solution as the predictable path to results they need.
When to use it: When competitors are making promises that seem unrealistic or too good to be true.
Pro tip: Ask them to get the competitor’s promises in writing with specific deliverables and timelines - often competitors won’t commit when pressed for details.
Frequently Asked Questions
How do I customize these AI prompts for different industries or products?
Replace the generic variables with industry-specific terms and add relevant context about your market. For example, change {implementation_timeline} to specifics like “software deployment time” or “equipment installation period” based on what you sell.
What’s the best AI tool for generating objection handling scripts?
Jasper AI excels at maintaining consistent sales tone across multiple scripts, while Copy.ai offers faster iteration when you need to test different approaches quickly.
How do I handle objections that combine multiple concerns like budget and timing?
Use the budget objection prompts but add timing variables, or combine elements from multiple prompts. The key is addressing the primary concern first, then the secondary one, rather than trying to solve everything simultaneously.