In short
- Objection handling is your prepared answers to the reasons buyers give for not buying, written once from the positioning so everyone answers the same way.
- Most objections come from a short list: timing, the alternative they use today, price, risk, and "can't we do it ourselves?".
- A good answer agrees with what's true in the objection first, then reframes it with something the buyer can check.
- The same answers go to sales, the website FAQ and your AI tools.
Every founder has heard it on a call. "Sounds interesting, but it's not a priority this quarter." And every founder has answered it differently from one call to the next, depending on the mood and how the call went until then.
Objection handling turns those improvised answers into decided ones.
The answers you give on calls
Objection handling is the list of reasons buyers give for not buying, each with the answer your company gives. It's part of the messaging doc, next to the elevator pitch and the boilerplate, and it's written for the people who talk to buyers: the founders, the salespeople, and anyone who answers a support email.
Where objections come from
Most objections come from a short list:
- Timing: "It's not a priority this quarter."
- The alternative: "We already use something for that." This is where your competitive alternatives come back.
- Price and value: "It's too expensive for what it is." Or "we don't have a budget for this", which comes up a lot when you sell something buyers have never bought before, so there's no line for it in anyone's plan. A product category they already buy from comes with a budget.
- Risk: "You're too small for us", or "what if it doesn't work?"
- Doing it themselves: "Can't we just do this ourselves, with AI?"
The best source for your own list is your calls. The objections buyers raise on recorded sales calls are the ones worth answering, in the words they used.
You don't have to listen to every call again to build it. Put the transcripts of your first calls with prospects into Claude or ChatGPT and ask what buyers pushed back on, who raised it and how often. Answer the ones you hear most first.
How a good answer works
A good answer starts by agreeing with what's true in the objection. The buyer isn't wrong to worry about timing or risk, and arguing with them ends the conversation.
Then it reframes the objection with something the buyer can check. Take the first objection in my own messaging doc, "We need leads, not strategy." The answer there opens with "Totally fair, and that's exactly why we lock positioning first", then reminds the buyer that it takes 3 weeks, and they build the website and pipeline on it within the same month.
Another one I answer on my own homepage: "Why not do it ourselves with Claude or ChatGPT?" AI will write any version of your homepage you ask for. What it won't do is make the call: which segment you focus on, what you stop saying, and which bet the founders commit to.
Why write it down
Unwritten objection handling lives in the head of whoever is on the call. Written down, the best answer becomes everyone's answer.
It also travels further than sales. The objections that come up most belong in your website FAQ, where buyers who aren't ready for a call still get the answer. And once they're in your marketing brain, your AI tools answer the same way when they draft an email or a reply.
How we write it in the sprint
Before session 1, my Positioning Builder reads your demo and prospect call recordings, so the objections buyers really raise are on the table from the start. By session 2 we know your target segment, its alternatives and your USPs, which is most of what an objection answer needs. Between sessions 2 and 3, the Builder drafts the objection handling into the messaging doc. In session 3 we review it with you, and the founders check every answer against what they really hear on calls.
How does your own homepage score? Get a free homepage audit: your homepage scored on the same 7 dimensions of positioning, with a line from your own page behind each score. Free, private, never published.