Objection Library From Real Conversations
Copy the buyer’s sentence exactly, classify it, ask a first question, write an honest reply, and mark when you concede. Built from win and loss notes, not from imagination.
A buyer says, “The price is higher than I expected.” You say something. It might be good. It might be defensive. The next time a buyer says the same thing, you say something different, because you do not remember what you said, or what happened after.
An objection library fixes the memory problem, not the sales problem. It collects what buyers actually say, sorts it, and gives you a first question and an honest reply for each. Not a script. A place to start when you are in the call and the sentence lands.
It is built from raw notes. If you have not been writing them, start with win and loss notes without fake attribution. The blank page is the objection library template.
Start with their sentence, not your category
Most objection lists are written by guessing. “Too expensive.” “Not the right time.” “We need to think about it.” Those are labels, not sentences. A real buyer says something more specific: “We already have someone who updates the site,” or “My partner has to approve anything over that number.” The specific sentence tells you what to ask next. The label does not.
So the first rule is mechanical. Copy the sentence exactly, with the note id and the date. If you do not remember the exact words, write UNKNOWN and do not improve it. Paraphrasing is how your fear of a particular objection sneaks into the library.
Six types, one per entry
Sorting by type does two things. It stops you from filing a timing issue under price. It tells you the first move.
| Type | Sounds like | First move |
|---|---|---|
| Price | About the number or the fence | Ask what they compared it to. Do not discount on reflex |
| Timing | A date, or “not now” | Write the date. Offer a dated follow-up |
| Trust | Wants proof or a reference | Open the proof you have and say what it does not show |
| Fit | Not sure it matches their case | Check the who-line. Concede if it does not match |
| Authority | Needs someone else to agree | Ask who and when. Offer a short summary for them |
| Status quo | Doing it themselves, or doing nothing | Ask what it costs them now, in their words |
On price, be careful. A price objection is often a fence objection: they did not like what is in or out. Reread how to price a productized service before you change a number because of a sentence or two.
The entry: eight lines
Each entry has the same eight lines. The structure keeps you from skipping the uncomfortable ones.
flowchart TD
W["Their words, exact"] --> T["Type"]
T --> M["What it might mean (Hypothetical)"]
M --> Q["First question"]
Q --> R["Honest reply"]
R --> P["Proof, and what it does not prove"]
P --> C{"Do you concede?"}
C -->|Yes| X["Polite exit line"]
C -->|No| N["Next step on the call"]- Their words: exact, with note id and date.
- Count: the notes where this or a close version appears. A number you can point to.
- Type: one of the six.
- What it might mean: one or two guesses, each labeled Hypothetical until a buyer confirms it. Never write a motive as fact.
- First question: curious, not defensive. “What were you comparing it to?” works better than a rebuttal.
- Honest reply: plain words. No pressure line, no scarcity you cannot back up.
- Proof: a page, file, or example you can open, plus one line on what it does not prove.
- Concede rule: the condition where the right answer is “you are right.”
Candidates first, entries later
Not every sentence earns an entry. Keep a Candidates section for sentences that appeared once or twice. Write the promotion rule at the top, in your own words. For example: appears in several notes, across different weeks, from different buyers. The rule is a choice, not a law. The point is that you wrote it before you saw the data you wanted to be true.
- Same buyer twice: one buyer repeating a sentence is one voice. Count it once.
- Same week: a cluster in one week may be a seasonal pattern, a bad email, or an event. Wait for it to repeat in other weeks.
- Different wording, same idea: group them under one entry and keep each exact sentence beneath it. Do not merge wording into a tidy phrase that no buyer said.
Hypothetical, labeled
Hypothetical. A studio keeps seeing a version of “We already have someone who updates the site.” Several notes across different weeks. It earns an entry.
| Line | Entry |
|---|---|
| Their words | “We already have someone who updates the site.” (note ids and dates listed) |
| Type | Status quo |
| What it might mean | Hypothetical: the updater covers small edits and they see no gap. Hypothetical: they are protecting a relationship. |
| First question | What do they handle now, and what do you keep working around? |
| Honest reply | “That can work well. We are a fit when the site structure or the offer page is the problem, not the edits.” |
| Proof | A scoped project on the work page where structure was the job. Does not show any outcome for them. |
| Concede rule | If the issue is edits and the updater handles them, say it is not a fit. |
The honest reply admits the updater might be enough. The concede rule gives permission to say so. That is the entry doing its job, which is to keep you from arguing a buyer into a project that will not help them.
Keep it alive, keep it small
A library dies in the same way a battle card dies: it grows and nobody opens it. A monthly five-minute review is enough.
- Used on a call? If not, shorten the entry or move it back to Candidates.
- Disproved by a buyer? Rewrite it the same day.
- Typed the same reply three times? Turn it into a saved reply or a short standard operating procedure (SOP).
The comparison lines that tell you what to do when a buyer names an alternative belong on a sales battle card, one page per alternative. The library covers what they said. The card covers who they are weighing you against. When replies get repetitive, SOPs before automation is the next step. If every objection turns out to be a missing slot, the constraint is capacity, and capacity before you buy demand is the tree.
If an entry keeps pointing to a page you do not have, such as a clearer scope or a process explanation, that is a website job. Our approach is on websites, and if you want to talk through your own library, start a conversation.
Frequently asked questions
What is an objection library?
A short set of entries, each starting with a sentence a buyer actually said. Each entry has a type, a first question to ask, an honest reply, proof you can open, and a condition where you concede. It is built from your notes, not from a list of imagined objections.
How many notes do I need before I write an entry?
Choose your own promotion rule and write it on the template. Our starting point is that the same sentence, or a close version, shows up in several notes across different weeks. One mention is a candidate. Do not turn one disappointing call into a policy.
Is an objection always a no?
No. Many are questions in disguise, or a request for something the proposal did not say. Treat them as information. Some are also correct, and the right reply is to agree and exit.
Where do these entries live?
Next to the call notes, in the same sheet or document. If you have a customer relationship management (CRM) tool, a linked note works. The only requirement is that you can open it during a call in under ten seconds.
Is this a script?
No. A script makes you sound like you are reading one. These entries hold the question to ask, the honest reply, and the proof. Say it in your own words. If an entry reads like pressure, rewrite it.