Handle Objections with ACERS
Use ACERS in this order every time. The sequence matters because each move earns permission for the next one. Do not jump to the pitch before you understand the concern.
Acknowledge
Recognize the concern respectfully. Do not argue with it, minimize it, or rush past it.
Clarify
Ask what sits underneath the first objection. Find the real constraint, risk, or decision criterion before you answer.
Empathize
Show that the concern makes sense from the buyer's point of view. This is not agreement or empty reassurance. It is a clear statement of the common ground you now understand.
Reframe
Offer a more useful way to see the issue. Challenge an assumption, widen the context, or connect the concern to a result the buyer values.
Sell
Tie the reframe to specific value, reduce the perceived risk with credible proof, and propose the smallest sensible next step.
In a live conversation, pause after Clarify and listen. Do not prepare the Sell step while the buyer is still explaining the concern. If the product is not a fit, say so rather than forcing a reframe.
For written or visual sales assets, use the same sequence without pretending the reader spoke to you. Acknowledge a concern supported by research or customer evidence. Clarify who faces it and what decision it affects. Empathize with evidence, not invented feelings. Reframe the decision, then Sell with proof and one clear call to action.
Example:
I understand why a new integration can look like extra work. Which part is the bigger concern: implementation time or the support burden after launch? It makes sense to protect a small team from another system it has to maintain. The useful comparison is not setup effort alone, but setup effort against the manual work it replaces. The first step is a workflow review that estimates the migration effort before you commit. Let us map your current workflow and confirm whether the product fits.
Arm the Champion for Objection Handling
To secure a deal, arm the champion with the tools they need to handle objections from decision makers. Do this by proactively addressing concerns and catering to each stakeholder group.
Good partners anticipate objections before they surface and reassure clients by drawing on their experience. Examples:
- IT concerns: name the objection, then answer it with proof. Where does our data go, and who can reach it? Answer with the security review you have already passed and the access controls you can show them. How much work is this for my team? Answer with the integration another client of their size ran, and how long it took.
- End-user apprehension: address by offering a training program that wins their support.
Honesty Wins
Honesty is valued in sales situations. Prioritize delivering results, and acknowledge that different approaches work well for different types of companies.
For example: for a small, non-growing e-commerce business, a shared inbox is a free and easy option worth recommending, even when it means not selling your own product.
Features Carry Multiple Value Points
Each feature can have multiple value points, and a combination of features can provide value as well. When mapping features to value, don't stop at one benefit per feature: enumerate every value point a feature delivers, and look for value that only emerges when features combine.