← The Sales Station ~ dish 08 of 10 · the sales station

Objection-Response Library, Live

An objection hits. The rep types it in. The station returns the response your best closer would give. Grounded in your playbook, not HubSpot's blog.

The job

A prospect says: “Your price is 30% higher than what we are paying now.” The rep has two options. Fumble. Or the rep types the objection into the station. The station returns three response options (consultative, aggressive, collaborative), all from patterns it’s seen in your won deals.

The objection-response library is not about defeating the prospect. It’s about keeping the conversation in play. A generic objection response ends the call. A response grounded in your actual playbook keeps the conversation moving.

Plated well: the prospect objects. The rep reads the station’s suggestion. Uses it or adapts it. The conversation continues instead of stalling.

The recipe

All seven ingredients still apply. The leverage on this dish is Examples (Ingredient #4). Objection responses work because the station learned them from your actual calls, not from a template library.

Training sets what your house philosophy is on objections (defensive? consultative? price-focused?). Examples are the load-bearing ingredient: transcripts or notes from past calls where you heard this objection and moved past it. The station learns your patterns. Guardrails protect against tone mismatches (never aggressive when collaborative works at your company). Output Over Process says: tell the station to return “options the prospect can’t dismiss, grounded in what you actually sell.”

How to build it

  1. Collect common objections. What do you hear three times a month? Price. Timeline. Competitor comparison. Need clarity. List them.

  2. For each objection, find three past calls where you heard it and won. Pull the response you gave. Mark what worked. Why?

  3. Annotate the pattern. What was your moves philosophy? Did you lower price? Did you reframe value? Did you acknowledge the competitor?

  4. Write the house philosophy. If a prospect objects on price, what’s your play? Accept it as a real concern? Reframe? Justify? Your philosophy shapes the responses.

  5. Feed the examples. The station reads three responses to “your price is too high” from your actual calls. It learns your voice.

  6. Set the guardrails. The station never promises to lower price without a caveat. The station never dismisses the prospect’s concern. The station never invents a reason they are wrong.

  7. Test on paper first. Type in an objection: “Your implementation is too slow.” Have the station generate responses. Do they sound like you? If not, sharpen the examples.

What breaks it

  • Generic examples. You show the station responses from HubSpot’s sales blog instead of transcripts from your actual calls. The station learns the internet’s playbook, not yours.

  • Philosophy missing. You collect examples but never articulate the philosophy. When should the rep be consultative vs. aggressive? The station doesn’t know. It guesses.

  • Incomplete objection library. You built responses for price and timeline but not for “we’re happy with our current provider.” The rep hits an unmapped objection. The station has nothing. Expand the library to cover 80% of the objections you hear.

  • No tone calibration. The station has three responses but doesn’t know which tone fits your prospect. Is this a CEO? A skeptical procurement person? A collaborator? That context shapes the response. Build variant responses for different prospect personalities.

  • Chef absence at the pass. The station has been generating objection responses for a month. The rep never came back to say whether they worked. Did the prospect buy after hearing that response or did they object again? That feedback updates the library.

When it’s working

By week two, the rep is less likely to fumble an objection. By week four, the rep is grabbing the station’s response and using it because it works. By week eight, the rep is adapting the station’s response instead of rewriting it from scratch.

The signal: objection rate is the same. Win rate is higher. Conversations that would have stalled are now moving.

Monday Move

Collect three objections you hear regularly. For each, find two past calls where you won after hearing it. Feed those to the station. Have a colleague type in an objection. Does the response sound like you? If not, add more examples from your own playbook. If yes, you are ready to deploy.

Dish 8 of 10 on the Sales Station. Build-note leverage: Examples (Ingredient #4). Chef stays in DIALING stance.