Skip to main content

Objection Handling

Principle: Every objection is an unmet need or unaddressed fear. Don't argue. Acknowledge → Reframe → Evidence → Confirm.

The A.R.E.C. pattern:

  1. Acknowledge — show you heard, don't dismiss
  2. Reframe — restate as a need, not as resistance
  3. Evidence — proof, reference, demo, calculator
  4. Confirm — did that address it?

Top 20 objections — rep playbook​

1. "You're too expensive."​

Acknowledge: "Price is always part of the conversation, and I appreciate you bringing it up directly." Reframe: "When you say expensive, are you comparing total cost — including the 4 other vendors you said you use — or just the line item?" Evidence: (Pull up TCO calc) "Today you're at ₹X with eZee + a separate POS + channel + payment gateway. With KeyNova you're at ₹Y. Net savings ₹Z over 3 years." Confirm: "Does that change how you'd think about the line-item price?"

If pricing pressure persists: clarify what discount level we'd need to win vs walk away. Never volunteer discount before "no" three times.

2. "We just need a PMS. We don't need all those modules."​

Acknowledge: "Totally fair — most properties feel that way until they see the operational overhead of stitching modules from different vendors." Reframe: "What you're really saying is — pay only for what you use. Right?" Evidence: "On Pro tier you pay per-key, regardless of which modules you turn on. POS and banquet are included in the price you'd already pay. So unless you're saying you wouldn't ever use POS — in which case let's talk about why not — you're paying for it either way." Confirm: "Does that frame make sense?"

3. "We're already using eZee / IDS / Hotelogix. Why switch?"​

Acknowledge: "Switching costs are real and I respect that." Reframe: "Most of our switch customers didn't switch because they hated their old vendor. They switched because the gap between their old platform and a modern one became too costly to ignore. What's pushing you to evaluate alternatives?" Evidence: "When [reference customer] switched from [competitor], they recovered switching cost in [X] months through [savings]. Want to talk to their GM?" Confirm: "Would a switch-cost-and-payback analysis help?"

4. "We're afraid of data loss / migration."​

Acknowledge: "Migration is the single biggest fear we hear. It's legitimate." Reframe: "What specifically concerns you — guest history, financial data, OTA mappings, or all of the above?" Evidence: "We have a migration toolkit for [their current vendor]. Last 12 migrations averaged [X] days with zero data loss. We do parallel-run for 30 days at our cost. Here's the migration spec doc and 3 reference calls." Confirm: "If we could guarantee parallel-run for 30 days and refund-if-data-loss, does that address the risk?"

5. "Our staff doesn't use English / can barely use computers."​

Acknowledge: "Front-desk and housekeeping training is a real cost." Reframe: "Sounds like the question is — will my staff actually adopt it?" Evidence: "Hindi UI is built-in. We also support Tamil, Telugu, Vietnamese. Housekeeping uses a mobile app with icons + voice prompts. Lighthouse customer [X] cut new-hire training from 2 weeks to 4 days. Want to see the Hindi UI live?" Confirm: "If we run a 1-day training session for your staff during pilot, does the adoption concern go down?"

6. "We need data residency in India."​

Acknowledge: "DPDPA and data residency are real concerns and you're right to ask." Reframe: "You're asking whether your guest data ever leaves India." Evidence: "Our entire production stack is in AWS ap-south-1 (Mumbai). Database, cache, file storage, log storage — all India. DR replica in ap-south-1 second AZ. Field-level encryption on PII. Compliance whitepaper here. Want to talk to our CISO?" Confirm: "Does our architecture document satisfy your data-residency requirement?"

7. "We need on-premise. Cloud isn't safe."​

Acknowledge: "Many properties feel that way at first." Reframe: "What's the underlying concern — internet outage, control, or security?" Evidence:

  • For outage: "Our offline mode caches the last 7 days of operations; check-in/out works offline; sync when connectivity returns."
  • For control: "You own your data, full export anytime, contractually committed."
  • For security: "We've passed [audits], ISO 27001 in flight. Most on-prem deployments are less secure than ours." Confirm: "Want to compare your current on-prem security posture against our cloud one with your IT lead?"

Note: If they insist on on-prem, disqualify. We are cloud-only.

8. "Our internet drops several times a day."​

Acknowledge: "Common, especially in remote resorts." Reframe: "You need the system to keep running when the internet doesn't." Evidence: "Local-first PWA + IndexedDB cache. Check-in/out, folio posting, KOT all work offline up to 4 hours. Auto-sync on reconnect. We can also provide secondary 4G LTE failover via partners." Confirm: "Want to see the offline mode live?"

9. "We need an integration with [door lock vendor / IPTV / accounting]."​

Acknowledge: "Integration completeness is critical." Reframe: "Tell me about the integration — what data flows in which direction?" Evidence: "We integrate with [list]. If [their vendor] is not on the list — open API + webhook framework, custom integration scope ₹X. Free if you're a lighthouse customer." Confirm: "Can we get on a call with [your IT lead] to scope the integration?"

10. "Procurement / Legal will take 6 months."​

Acknowledge: "Procurement timelines are real." Reframe: "What's typically the bottleneck — vendor onboarding, security review, contract redlines, or financial approval?" Evidence: "Our security pack is already aligned with [common Indian RFP templates]. Standard MSA is light. We pre-fill vendor onboarding forms. Last 6 enterprise deals closed procurement in [X] weeks median." Confirm: "Can we kick off the security review in parallel with the POC so procurement isn't the long-pole?"

11. "We need a guarantee on uptime / SLA."​

Acknowledge: "Uptime is operations-critical." Reframe: "What SLA does your current system give you? What's the cost of downtime to you?" Evidence: "Our target is 99.9% with multi-AZ Postgres + Redis. Status page live at status.keynova.ai. We offer 99.95% with financial credits on Enterprise tier." Confirm: "Does an SLA addendum address the concern?"

12. "We can't be the first hotel to use this."​

Acknowledge: "Pioneer risk is real." Reframe: "You're saying you want proof we work at properties like yours." Evidence: "Reference customers: [list]. Most relevant to you: [name + property + city + key count]. Want to schedule a reference call?"

If genuinely no reference exists in their segment: "You'd be our first [segment X], yes. That comes with founder commitment, weekly check-ins, and we'll make you a lighthouse — public case study, joint PR, 35% discount Year 1."

13. "Your competitor includes [X] which you don't."​

Acknowledge: "Good catch — let me give you a straight answer." Reframe: "Is [X] a must-have for your operations, or a nice-to-have?" Evidence: "If must-have, we have a workaround [explain] or roadmap commit [date]. If nice-to-have, the trade-off you're making is — [our advantages they don't have]." Confirm: "Want to walk through the trade-off side-by-side?"

14. "I need to think about it." / "Send me a proposal."​

Acknowledge: "Of course — big decision." Reframe: "Help me — what specifically do you need to think about? Pricing, fit, timing, internal buy-in?" Evidence: depends on answer Confirm: "What would need to be true for you to feel ready to decide?"

If "send me a proposal" arrives without champion confirmation: don't send. Send the next-step doc instead, with conditions for proposal.

15. "We're going to wait and see what happens next quarter."​

Acknowledge: "Timing is a real factor." Reframe: "What event are you waiting for — board decision, fiscal year, e-invoice mandate, new property?" Evidence: "If it's e-invoice — you don't want to be doing implementation in November while everyone else is doing the same thing. We can lock pricing now, ship implementation in [month], you start in [later month]." Confirm: "Would locking pricing now and deferring implementation help?"

16. "Our IT team / consultant says they prefer [competitor]."​

Acknowledge: "Internal advocates carry weight." Reframe: "What does your IT team prioritise — control, integration, security, cost?" Evidence: "We've put our architecture / security pack against [competitor] in 12 deals. Net result: we win on [API / security / India compliance]. Can I send your IT lead the technical comparison doc?" Confirm: "Would a technical deep-dive with our SE + your IT lead help align them?"

17. "We're worried about your company being too small / new."​

Acknowledge: "Vendor viability is a real concern." Reframe: "What's the worst-case scenario you're protecting against — us going out of business, us getting acquired, or us not being able to scale with you?" Evidence:

  • Out of business: "We've raised [funding], runway through [date], here's our investor list."
  • Acquired: "Most acquisitions in this space are upgrades for customers (e.g., bigger company taking over). Our preferred outcome is independent growth."
  • Scaling: "Architecture handles [X] hotels / [Y] reservations/sec. Future-proofed." Confirm: "Does our financial + technical profile address vendor-viability risk?"

18. "Your roadmap is missing [feature]."​

Acknowledge: "Honest call — when do you need it?" Reframe: "Is it a must-have for go-live, must-have for Year 1, or nice-to-have?" Evidence:

  • Must-have go-live: "Realistic estimate is [date]. If that doesn't work for you, let's be honest about whether we're the right fit."
  • Must-have Year 1: "We can commit a delivery date in our SOW for [date]."
  • Nice-to-have: "On the roadmap, not committed. Influence-able by being a design partner." Confirm: "Does a roadmap commit in the SOW address it?"

19. "Discount more."​

Acknowledge: "I hear you — and I want to be fair to both sides." Reframe: "What number, exactly, would close the deal today?" Evidence: "List for your scope is ₹X. Best I can do without VP Sales approval is ₹Y (10%). If you want me to go higher, I need from you: [longer term / prepay / case study / reference / multi-property]." Confirm: "If I can get you to ₹Y on those terms, do we have a deal today?"

Floor: rep cannot go below tier floor (see [[Pricing and Packaging]] section 6) without VP Sales approval. Don't break floor over email. Use a live call.

20. "Let me talk to my [boss/board/family/CA]."​

Acknowledge: "Of course — important decisions get pressure-tested." Reframe: "What questions are they likely to have that I can answer for you in advance?" Evidence: Send a one-page exec summary tailored to that stakeholder's role Confirm: "Can we get [them] on a 20-minute call so they get my answers first-hand rather than your version of my version?"

Quick-fire — short objections + short responses​

ObjectionQuick response
"Too many features, I'll be overwhelmed.""We turn on modules incrementally. Week 1: PMS. Week 4: POS. Week 8: banquet. You set the pace."
"I don't have time to evaluate.""30-min demo + 7-day sandbox. Total: ~5 hours of your time over 2 weeks. We'll come to your office."
"Your dashboard looks too fancy.""We have a simplified mode. Want to see it?"
"What if you change your pricing?""Contractual price-lock for the contract term. Annual escalation capped at 8% on renewal."
"We don't trust the cloud.""100% of new hospitality SaaS is cloud. ITC, Marriott India both run cloud PMS today."
"We had a bad experience with [competitor].""I'm sorry to hear that. What specifically broke? Let me address that directly."
"Reviews on G2 are mixed.""Specific negative review you want me to address? Most are from 2023 and predate [fix]."
"Your sales rep was pushy last year.""Apologies. Different team now. Different style. What would help you reset?"
"We tried SaaS once, it failed.""What failed — adoption, integration, support? Let me address that root cause."
"We use Tally for accounting.""We push GL entries to Tally daily. Already integrated with Tally Prime."

How to prevent objections (best technique)​

The best objection handling is pre-empting. Build into your discovery:

  • Always ask "What would make you NOT choose us, even if you loved the product?" in discovery
  • Address the top 3 likely objections proactively during demo
  • In proposal, anticipate procurement objections (security pack, MSA, data residency)
  • Send reference calls before objections come up
  • Quote TCO not unit price before prospect asks about cost

Loss-causing objection patterns to surface to product/exec​

If an objection comes up in > 20% of deals and we don't have a great response, it's no longer an objection-handling problem — it's a product or messaging problem. Escalate to:

  • CMO for messaging changes
  • Head of Product for roadmap changes
  • CFO for pricing changes

Mechanism: quarterly Objection-Trend Report compiled by Sales Ops, presented at Q-end exec offsite.

Last reviewed: 2026-05-16