The rejections that end deals in the first meeting. Each one shows up as either a stall ('let me loop in the team') or a hard no. The verbal answer buys the second meeting; the deck fix keeps it from coming up next time.
01
"We don't have budget for this right now."
Why it lands
It's the easiest polite exit. Real budget objections usually mean 'the pain isn't ranked highly enough,' not 'the number is wrong.'
What to say
Ask what does have budget for the current quarter and why. Then map the outcome you deliver to that ranked priority. If you land there, ask to be added as a line item in the next planning cycle rather than push for a signed order today.
Fix on the deck
Put the outcome in dollars on slide 2 ('we saved the median customer $X in month 3'), not in features. Add a slide near the ask showing 'what it costs not to buy' with a live-customer number.
You didn't tie the pitch to a priority the buyer has already committed to in writing (OKRs, board goals, earnings calls).
What to say
Name their public priority back to them and connect the dots: 'you told the street you'd take 300bps out of COGS this year; here's the line item that gets you 40bps of that by Q4.'
Fix on the deck
Swap the generic problem slide for a buyer-specific opening. Cite the buyer's own priority from earnings, OKRs, or a press release.
03
"We can build this internally."
Why it lands
Almost every buyer thinks they can build. What kills the deal is that they've under-modeled the ongoing cost of the internal build.
What to say
Ask what the internal build would take: engineers, months, ongoing maintenance. Convert to loaded cost. Compare to your annual price. Point at two customers who tried the DIY path and switched, and why.
Fix on the deck
Add a build-vs-buy comparison slide that itemizes the DIY cost (people, time, maintenance) against your annual price. Two named-customer switch stories under it.
04
"We're already using [incumbent]."
Why it lands
Displacement sells are 5x harder than greenfield sells. If the deck doesn't answer 'why switch,' the buyer will not switch.
What to say
Ask what they'd change about the incumbent if they could. Then map your top three differentiators to those exact complaints. Don't try to beat the incumbent on their strengths.
Fix on the deck
Add a 'moving from [incumbent]' slide with a migration path: what stays the same, what improves, and how long the switch takes.
05
"We'll need to run this through security review."
Why it lands
Security review is not an objection; it's a delay. Most delays kill deals through decay, not rejection.
What to say
Offer to start the security review in parallel with the pilot, not after it. Have the SOC 2 report, DPA, and pen-test summary ready to send within 24 hours. Ask who the security reviewer is by name and offer a 30-minute call.
Fix on the deck
Add a security-and-compliance slide near the pricing: SOC 2 status, DPA availability, data residency options, uptime SLA. Not a wall of logos.
06
"The ROI numbers seem optimistic."
Why it lands
Every deck oversells ROI. The buyer has been burned before and expects to discount your number by 50-70%.
What to say
Show the ROI math from three named customers with different starting conditions (small, mid, enterprise). Offer a live conversation with one. Anchor to the customer's own numbers, not to a modeled scenario.
Fix on the deck
Replace the modeled-ROI slide with three case cards, each with a starting-state number, a 90-day number, and the named customer contact.
07
"Let me loop in the team and get back to you."
Why it lands
The most common stall. You didn't identify the full buying committee up front, so now the champion has to sell it internally without your help.
What to say
Ask who else needs to see this and offer to run a 20-minute readout with the committee. Ask for one procurement question in advance so you can pre-answer it in the readout.
Fix on the deck
Include a 'who this is for' slide near the front that names the roles who need to review (owner, security, procurement, budget holder), not just the buyer.