15 real objections (price, timing, competitor, ROI, security, switching cost) with responses, redirect questions, and case-study assignments. Plus red flags.
Your sales call goes well right until minute 28 when the prospect says 'we need to think about it' or 'send me a comparison with Competitor X' and the deal goes cold for six weeks. Your reps don't have a shared answer. The founder handles objections one way, the AE handles them another, and the SDR just promises to send the case study. This tool builds a real objection playbook off your actual lost-deal patterns — the 15 objections that actually come up, grouped by the categories that matter (price, timing, competitor mention, internal champion missing, ROI proof, integration concerns, security, switching cost) — each with a tight response, a redirect question to keep the conversation moving, and the asset to send after the call. Plus a red-flag section that tells your reps when an objection is real and when it's the prospect politely saying no.
Brief used: “We sell a $1,800/mo employee onboarding tool to HR ops leads at 100-500 person companies. Competitors: Sapling (legacy, $$$), Notion templates (free, lazy default), BambooHR onboarding module (bundled if they already use BambooHR). Last 3 lost deals: (1) 'price is high vs Notion templates', (2) 'we're already on BambooHR, why switch the onboarding piece', (3) 'we're hiring fewer people this year, not a priority'. Price is firm, not negotiable below $1,500.”
## Sales Objection Playbook — Employee Onboarding Tool ### Category 1 — Price **1. 'That's expensive vs Notion templates.'** Response: 'Notion templates work great until you hit week 3 of onboarding 5 new hires at once and someone's manager skips the IT-access step. The math we hear from customers is: 1 missed onboarding task costs 4-6 hours of manager time fixing it after the fact. At your hiring pace, that's the tool paying for itself in the first month.' Redirect: 'When you onboarded your last 3 hires, how long did week 2 actually take you?' Asset: Customer story — [HR ops lead at 180-person company] doc. **2. 'Can you do $1,200/month?'** Response: 'Pricing is firm at $1,800. What I can do is shorten the contract to month-to-month for the first quarter so you're not locked in if it doesn't pay off, or roll in the 'managers playbook' add-on that's normally $300.' Redirect: 'If price weren't the blocker, what's the next thing you'd want to check before signing?' Asset: Month-to-month terms one-pager. ### Category 2 — Timing **3. 'We're hiring fewer people this year, not a priority right now.'** Response: 'Lower hiring volume actually makes onboarding more important — when you're hiring 30 a year instead of 100, every hire has to land, and the cost of a regretted hire is higher. The tool's value isn't volume, it's consistency. But I get that 'not a priority' is a real signal — when would be the right month to revisit?' Redirect: 'What would have to change for this to move up your list?' Asset: Send the 'small-team onboarding playbook' as a value-add, no ask. **4. 'Let's revisit in Q3.'** Response: 'Happy to. Two things before you go — first, can I send you the implementation timeline so when Q3 hits you're not starting from scratch? Second, who else on your team should be in the loop now so this isn't a cold reintroduction in 4 months?' Redirect: 'If I followed up in mid-Q3, what would you want to see in that email to actually open it?' Asset: Implementation timeline PDF. ### Category 3 — Competitor mention **5. 'We're already on BambooHR. Why switch the onboarding piece?'** Response: 'BambooHR's onboarding module is fine if you want a checklist of tasks tied to your HRIS. The reason customers add us is the manager-facing layer — the prompts to managers in week 1, 2, 4 to actually do 1:1s, the structured feedback collection at day 30 and 60. BambooHR doesn't have that, and most customers tell us their managers were the broken part of onboarding, not the paperwork.' Redirect: 'When you ran your last hire through BambooHR, did the manager actually do the 30-day check-in?' Asset: BambooHR vs us comparison page (focus on manager layer, not feature count). **6. 'How do you compare to Sapling?'** Response: 'Sapling is built for 1000+ person companies — strong if you have a People Ops team running it, heavy if you don't. We're built for the HR ops lead who's running onboarding alone. Lighter setup, no implementation consultant, you're live in 2 weeks instead of 8.' Redirect: 'How many people on your team would be running this day-to-day?' Asset: Sapling comparison — speed-to-live framing. ### Category 4 — Internal champion missing **7. 'Let me run this by my boss.'** Response: 'Of course. What would help — can I put together a 1-pager you can forward, or would it be easier if I joined the next conversation so they can ask questions directly?' Redirect: 'What's the one question they're most likely to ask that I should answer in writing?' Asset: Forward-able 1-pager (build per deal). **8. 'We need to involve IT/finance/legal.'** Response: 'Smart. Two things I can send today — the SOC 2 report and the standard MSA. That usually unblocks 80% of the IT and legal questions before the meeting.' Redirect: 'Who on those teams is the bottleneck historically?' Asset: SOC 2 + MSA package. ### Category 5 — ROI proof **9. 'Can you show me ROI?'** Response: 'I can show you what other customers measured, but the honest answer is the ROI here isn't a clean number — it's hours saved by managers and the regretted-hire rate. If you tell me your average manager hourly cost and your hiring volume, I'll run the math with you live on the next call.' Redirect: 'What number would your CFO want to see to sign this off?' Asset: ROI calculator (input their numbers, not generic). ### Category 6 — Integration **10. 'Do you integrate with [HRIS / Slack / Google Workspace]?'** Response: 'Yes to Slack, Google Workspace, and the major HRIS (BambooHR, Rippling, Gusto, HiBob). If you're on something niche, tell me and I'll check before I commit.' Redirect: 'Which one is the most critical for go-live?' Asset: Integrations doc. **11. 'We use a custom HRIS / homegrown system.'** Response: 'We have an open API and a Zapier connector — most custom HRIS integrations get built in week 1 of the trial. We don't promise a native integration but we do promise it'll work.' Redirect: 'Who on your side would own that 4-hour setup?' Asset: API + Zapier setup guide. ### Category 7 — Security **12. 'What's your security posture?'** Response: 'SOC 2 Type II, data encrypted at rest and in transit, SSO via Okta and Google, role-based access. Happy to send the full security pack.' Redirect: 'Is there a specific control your IT team flagged?' Asset: Security one-pager + SOC 2. **13. 'We can't store employee data in [region/cloud].'** Response: 'We're on AWS [region]. If that's not acceptable, we have a workaround for EU-only customers — happy to walk you through it.' Redirect: 'What's the policy line that's driving this?' Asset: Data residency doc. ### Category 8 — Switching cost **14. 'Switching mid-year sounds painful.'** Response: 'It's lighter than it sounds — we import from your current tool (templates, checklists, in-flight onboarding) in week 1. Most customers go live in 2 weeks with their existing data intact. No one onboards twice.' Redirect: 'What part of switching is scaring you most — the migration, the team retraining, or the timing?' Asset: Migration playbook. **15. 'We've already invested in our current setup.'** Response: 'Sunk cost — I get it. The framing I'd push back on is: the question isn't 'was the old tool worth it' but 'is the next year of onboarding worth running on the current tool'. If the answer's yes, we shouldn't be selling you.' Redirect: 'Honestly, what's working about your current setup that we shouldn't break?' Asset: Migration playbook + 'when not to switch' honest blog post. ## Red flags — walk away politely - 'We don't have budget' AND no champion AND no clear renewal date — this is a no, not a 'not now'. - 'Send me everything' with no follow-up question — they're researching the category, not buying. - 4+ stakeholders introduced, none own the decision — political org, will take 6 months minimum, qualify by ACV before continuing. - 'Can you build [custom feature] for us' as a pre-condition — you're selling a product, not a contract. Walk unless ACV justifies it. ## Top 5 cheat sheet (for new-rep onboarding) 1. Price vs Notion → talk hours, not features. 2. BambooHR already → talk manager layer. 3. Not a priority → don't push, send value, ask when. 4. Let me run this by boss → offer to be in the room. 5. ROI question → calculator with their numbers, not generic.
Static example — your run uses Claude live on your specific brief.
Founder-sellers running their first 50 sales calls who keep getting blindsided by the same objections, sales leaders building a real enablement layer for the first 3 AEs, anyone whose answer to 'how do you compare to X' changes depending on who's asking. Not for: closed-won-rate enterprise teams who already have a battlecard library — you're past this stage.
A playbook your reps will actually open before calls: (1) top 15 objections covering price, timing, competitor mention, internal champion, ROI proof, integration, security, and switching cost, (2) 2-3 sentence response per objection — written like a person talks, not a script, (3) a redirect question after each response to move the conversation back to discovery, (4) an asset or case-study recommendation to send after the call, (5) a red-flag section listing the objections that mean 'walk away politely', (6) a tone note for each (when to push, when to step back), and (7) a one-page cheat sheet pulling out the top 5 for new-rep onboarding. All output tied to the actual lost-deal patterns you described, not generic enterprise-sales templates.
You're closing your first 30 customers and the same three objections kill half the calls. Get tight responses you can deliver naturally instead of freezing mid-sentence.
You just hired your first salesperson. They need shared answers to the 15 objections that come up most. Hand them a playbook instead of asking them to take notes during your calls.
A specific competitor started showing up in deals. You need a clean answer to 'why not Competitor X' that doesn't trash them and doesn't sound defensive.
Quarterly close-loss review shows the same patterns. Build the playbook against the real reasons, then test response quality on the next 10 calls.
The 15 cover the patterns that show up across B2B SaaS, but the tool tunes them to your specific lost-deal reasons. If your deals die on something niche (regulatory, RFP process, geographic restriction), describe it in the input and the playbook will include it instead of forcing the generic version.
They will if it's tight enough to memorize, not a 40-page binder. That's why this one tops out at 15 objections plus a 5-item cheat sheet. Anything longer becomes a doc nobody opens. Keep it on the wall above the AE's desk.
No — this is internal-only. The point is your reps land the response naturally on a call, not that the prospect reads your objection-handling logic. If a prospect ever sees the doc, that's a fire-drill conversation.
Quarterly, after a close-loss review. New objections show up when you change pricing, launch features, or a new competitor enters. The 'red flags' section in particular gets sharper every quarter as you see more deals.
Yes. You get an anonymous preview instantly with no signup. Drop your email and you unlock 3 full-length runs per month for Sales Objection Playbook — no credit card. Unlimited runs are $49 one-time, or $19/mo for every tool.
Paid ($49 one-time) unlocks unlimited runs for Sales Objection Playbook, longer outputs from Claude Sonnet, full exports, and priority generation. $19/mo unlocks every tool on JustNeeda.
Free runs render in-browser and can be copy-pasted. Paid unlocks copy-to-clipboard, Markdown, and plain-text exports — and history of every run tied to your account.
No. Every run hits Claude live with your specific input. We don't reuse outputs across users. Your input stays private to your session and account.