Build a playbook with your best response to each of the five common objections.
Hafiz sells payroll software. He has a method for each of the five objections he hears most often: price, timing, trust, need and someone else. He also has a log of the objections buyers have actually raised with him. What he doesn't have yet is one place to look before a meeting, with his best response to each objection written in his own words. You are probably in the same position.
That place is an objection playbook. It is a single reference with one page per objection, so five pages in all. Writing it takes about forty-five minutes. Practising it with a partner takes extra time on top of that.
Make one page each for price, timing, trust, need and someone else. Give every page the same four headings so you can scan the playbook quickly before a meeting:
Common meanings: what the objection usually hides in your market, drawn from lessons 5.1 to 5.5. Clarifying question: a question that tells you which of those meanings the buyer intends. A response for each meaning: two or three sentences each, including any proof or figures you will use. Confirm question: a question that checks whether your response landed.
Keep each page to one side. If a page runs longer, you are writing a script, and a script breaks as soon as the buyer uses different words from the ones you planned for. A guide is short enough to adapt when the conversation changes.
Open the log you started in lesson 4.4, Start your objection log. At the top of each page, copy two or three real examples of how buyers phrased that objection. Real wording does two jobs. It reminds you what the objection sounds like in the moment, and it stops you writing responses to objections nobody actually raises.
Then fill in the four headings. Use lessons 5.1 to 5.5 as your guide and the log as your evidence.
At the top of Hafiz's price page are two lines from his log: "It's more than we're paying now." and "This is more than we were planning to spend." He lists three common meanings. The buyer may be comparing with the cost of their current system. Their budget may have been set before the night shift or some other change. Or they may not yet see what overtime errors cost them.
His clarifying question is: "When you say more than planned, what had you budgeted for, or what are you comparing it with?" Each meaning has its own response. If the buyer is comparing with the current system, he compares what that system does and does not handle, especially shift overtime. If the budget was set earlier, he offers a one-page note for finance with the buyer's own impact figure, or suggests starting with the overtime module only. If the value isn't clear to them yet, he plays back the impact figures from the buyer's worksheet. His confirm question is: "Does that help with the cost side, or is there something else behind it?"
His someone-else page has the most real examples, because his log showed that this objection cost him the most. Its main response is now an offer to meet the other person, with a one-page summary as the fallback. Lesson 5.5, I need to check with someone else, describes this approach.
Ask a partner to play a buyer and raise each objection twice, in different words each time. They can use real examples from your log or make up their own phrasing. Respond using the method: listen, clarify, respond, confirm. Don't read from the page. The practice is there to show whether your clarifying question and responses work when spoken aloud, against wording you didn't expect.
After each objection, ask your partner, "Did that answer feel convincing?" and write their answer on the page.
When Hafiz practised his trust page, his partner played Kelvin and asked, "How do I know your company won't be bought out next year?" Hafiz hadn't prepared for that wording. His clarifying question still worked: "That's a fair worry. What would happen on your side if it were?" The real concern turned out to be getting left without support during payroll, and his trust page already covered that. A good clarifying question can hold up against wording you never planned for.
When all five objections have been role-played twice, pick the weakest response. That is the one that felt weakest to you or to your partner. Rewrite it from scratch. Changing a few words keeps the same response underneath, so start again with a blank section.
Hafiz's weakest response was on his need page. When his partner said, "Honestly, we're managing fine with spreadsheets," Hafiz found himself listing features. Lesson 5.4, We are fine as we are, warns against doing exactly that. He rewrote the page around two questions. The first asks what has changed since the buyer agreed to meet. The second asks whether the overtime errors they described in discovery still happen. He also added a polite way to leave the conversation if the buyer really is fine.
The finished playbook has five pages, one per objection. Each page has real wording from your log, the common meanings, a clarifying question, a short response for each meaning and a confirm question. Each objection has been role-played twice with varied wording, with your partner's reaction noted, and the weakest response has been rewritten from scratch.
Your log will keep growing, so set a monthly reminder to review the playbook against it. Add new buyer wording, retire responses that no longer work, and keep each page to one side.
Open your objection log and set up the five pages before you start the activity below.
Write the five-page playbook, role-play each objection twice with a partner, and rewrite the response that felt weakest.
Junxiong-WFG Organisation is an authorised representative of AIA Financial Advisers Private Limited (Reg. No. 201715016G).