Do you know how to manage objections?
21/10/2016 11:33 AM by
When attempting to sell a solution to a potential client, you will invariably come
up against some objections. It is essential that you are prepared to handle these
objections so the client is confident in your skills and has no reservations about
choosing you over someone else. The main reason clients raise objections is because
they have concerns about your experience "fit" with their needs.
We recommend you use this objection handling model.
- Ask the question - "What concerns do you have about working with us?"
- Acknowledge the objection - say, "Thanks for raising that", or, "Thanks for letting
us know about that"
- Probe - ask, "Can I ask you a few questions about the concerns that you have?"
"If I could resolve this issue for you, could we move forward?
"You can't always solve objections on the spot - it's ok to say, "Is it alright if I speak to one of my developers about it and let you know about that later today?"
- Answer - Pick the best response to their objection (see below)
- Confirm that they are happy with your answer - "Do you now feel comfortable with
our approach towards your project?"
A typical objection we get is - "Why do you
put 2 developers on the project? This is going to be more expensive isn't it?".
This is basically how we handle this question:
- Explain the benefits:
- "We can complete the project sooner. Is that important to you?"
- "You get more expertise - One guy is more focussed on UI, the other guy is stronger
- "You get better quality code because the guys are able to "put their heads together"
to solve a problem - this saves maintenance costs down the track"
- "We can continue working if 1 guy gets sick"
- If they are still unsure, you can offer a small discount off the hourly rate, or
offer some free support - it's all about managing risk.
Do you feel this rule needs an update?