Pricing Objection Handler

Objection response sent from AE address. CRM: objection type logged, response angle noted, follow-up task set. If ROI call booked: calendar invite sent, deal stage updated.

Before you start

Approved objection-handling playbook with company-specific responses
ROI calculator or cost-comparison data available
Escalation path defined (when to loop in AE vs handle autonomously)
Prospect message containing pricing objection (email, chat, or call transcript excerpt)
Deal size and stage from CRM
Prospect's stated use case and company size

The steps

Classify the objection type — Read the prospect message and classify: (a) sticker shock — price is higher than expected, (b) budget constraint — genuinely no budget this period, (c) competitor comparison — they have a cheaper quote, (d) ROI skepticism — not convinced the value justifies the cost, (e) negotiating — testing flexibility. Each type requires a different response. Log classification in CRM.
Acknowledge without conceding — Open with genuine acknowledgment of the concern without apologizing for the price or implying it's negotiable by default. Example: 'Totally fair question — pricing is always worth getting right.' Do not open with 'I understand' (cliché) or 'our pricing is competitive' (defensive). One sentence, then move to value reframe.
Reframe to cost-of-status-quo — Calculate or reference the cost of the prospect's current approach: time spent, headcount cost, error rate, or missed revenue. Use their stated numbers if available from discovery. Example: 'You mentioned your team spends 12 hours/week on this — at a loaded cost of ~$80/hr that's ~$50k/year. Our annual plan is $18k.' Specific math beats vague value claims every time.
Address competitor comparison if applicable — If they mentioned a specific competitor, acknowledge by name. Do not disparage the competitor. Identify one concrete differentiator relevant to their stated use case (integrations, accuracy, support SLA, compliance cert). Offer to walk through a feature-by-feature comparison on a 15-minute call rather than debating it in writing.
Offer a path forward without discounting — Default path: invite a 15-min ROI review call to build a business case together. Secondary path: propose a smaller starting scope (if pricing is modular) rather than discounting. Only offer a discount if it is within AE's pre-approved discretion and the deal size justifies it. Discounting in writing without AE approval is not allowed.
Send response and update CRM — Send the response from AE email. Log objection type and response angle in CRM deal notes. Set 3-day follow-up if no reply. If prospect agrees to an ROI call, book immediately. If deal is >$30k ACV, send draft to AE for approval before sending.

If it goes wrong

Prospect treats ROI math as made up

Only use numbers the prospect gave during discovery. If they didn't share numbers, ask explicitly: 'To show you the real math, can you tell me roughly how many hours/week your team spends on X?'

AE undercuts the response by offering discount immediately

Align with AE before sending on whether discount is on the table. If yes, bake it into the response as a structured offer with conditions (annual commit, pilot scope, etc.) — not a reactive concession.

Prospect goes silent after objection response

Follow up at Day +3 with a different angle (case study, not more pricing talk). If still silent at Day +7, treat as stalled deal and hand to revival SOP.

All OpenLabor playbooks