Objections and responses
Objective. Respond to the common objections - monitoring concerns, spreadsheets, existing WFM, integration effort, ambiguous ROI - by establishing conditions rather than making universal promises.
A ready-to-use objection card for the five objections you will meet most. Each response names the real concern, gives an honest condition-based answer and states a limit out loud. The pattern throughout is the same: acknowledge, reframe to the customer's own evidence, offer a testable next step - never a blanket promise. Keep it open in live calls.
See it in the demo
What it is and when to use it
This is a quick-reference card, not a script to read. Use it in discovery and demo calls when an objection lands, and in prep so you are not improvising. The guiding rule across every response: establish a condition the customer can test, not a universal promise. 'It depends on your data and we can prove it in a pilot' is stronger and more honest than 'yes it will'. The card covers the five recurring objections; adapt the wording to the person, keep the discipline.
The card - five objections
1. 'This is employee surveillance.'
Acknowledge it is a real concern, not an obstacle to brush off. Reframe: the goal is visibility into work and output to run the operation fairly, and capture is governed by policy, access boundaries and employee communication (Employee Monitoring shows capture-policy and agent modes). Limit to state: a non-productive application label is not proof someone did no useful work; the tool informs manager judgement, it does not replace it. Next step: show the capture-policy and privacy framing, and point to the capture-privacy-and-trust kit.
2. 'We already do this in spreadsheets.'
Acknowledge spreadsheets work until they do not. Reframe to their cost: reconciliation effort, stale data, no agreed denominator, no audit trail. Limit: do not claim they will save a specific number of hours - that is their baseline to measure. Next step: a small pilot that produces one trusted, agreed number they cannot get from the sheet.
3. 'We already have a WFM / monitoring tool.'
Acknowledge the incumbent. Reframe to the gap: ask what question they still cannot answer with it (output vs activity, friction causes, capacity vs cash). Limit: do not assert displacement value as a number; it depends on their situation. Next step: a side-by-side on one unanswered question.
4. 'Integration will be too much work.'
Acknowledge integration effort is real. Reframe: describe scope at app-logic level and the smallest useful starting data. Limit: integration specifics and effort are confirm-with-product - do not quote a timeline or guarantee a connector. Next step: route specifics to a specialist and the integration-scope kit.
5. 'I am not convinced of the ROI.'
Agree that a vendor-asserted ROI is not convincing. Reframe: a pilot builds a number from their data that they own, with capacity and cash kept separate. Limit: freed capacity is not cash until they act on it; a modest honest number beats a big blended one. Next step: a one-page pilot charter with a customer-owned baseline.
How to use it
Run each response in three moves: acknowledge the concern as legitimate, reframe to the customer's own evidence or unanswered question, then offer a testable next step. Resist the urge to win the objection with a bigger claim - the claim you cannot defend becomes the next objection. For the surveillance objection in particular, slow down and treat it as a trust conversation, not a feature rebuttal. When an objection touches security, compliance or integration specifics, your honest answer is the condition plus a named escalation, not an invented fact.
Honest caveat
These responses establish conditions; they are not guarantees. Do not convert any of them into a universal promise ('you will save X', 'it integrates with everything', 'it will replace your WFM') - every one of those depends on the customer's situation and must be proven, not asserted. Monitoring, capture, security and integration specifics are confirm-with-product and governed by the customer's own policy and configuration. The objection you handle dishonestly is the one that returns at renewal; a pilot that tests the condition is almost always the right close.
Interpretation check
Every objection is answered by establishing a testable condition, never a universal promise. The claim you cannot defend becomes the next objection, so the honest, condition-based answer plus a pilot is stronger than a bigger assertion.
In the field
KnackGlobal (ProHance displacement): the 'we already have a tool' objection was answered not with a displacement ROI figure but by asking which question ProHance could not answer - output per FTE at acceptable quality and cost - and proposing a side-by-side on that single question rather than a blanket replacement claim.
Practical task
Role-play all five objections with a peer. For each, deliver the acknowledge-reframe-next-step pattern and end on a testable condition. Have the peer flag any answer that slipped into a universal promise.
Self-check
What is the single pattern behind all five responses?
Acknowledge the concern, reframe to the customer's own evidence or unanswered question, offer a testable next step - establish a condition, not a universal promise.
How do you answer 'this is surveillance' honestly?
Treat it as a legitimate trust concern: visibility is governed by capture policy, access boundaries and employee communication, and a non-productive label is not proof of no useful work. The tool informs manager judgement, it does not replace it.
A buyer asks you to confirm an integration timeline to overcome the effort objection. Response?
Do not quote one. Describe scope at app-logic level, state that specifics and effort are confirm-with-product, and route to a specialist and the integration-scope kit.
Why not answer the ROI objection with an industry ROI figure?
Because a vendor-asserted number is not defensible to their finance team. Offer a pilot that builds a customer-owned number with capacity and cash kept separate; a modest honest number beats a big blended one.
Verified vs demo. Capture-policy framing and capacity-vs-cash are demo-shown (Employee Monitoring, Value Leakage); integration, security and displacement specifics are confirm-with-product, and no response may be delivered as a guaranteed number.