Every salesperson has heard "it's too expensive" and felt the urge to defend the price before the buyer has finished the sentence. That reflex is the problem. Most objections are not the real reason a deal is stuck; they are the first words a buyer reaches for. This guide sorts objections into six types, gives you a five-step way to handle any of them, thirty response scripts you can adapt, a quick-reference table for the moment it happens, and a way to track which objections keep coming up so the whole team improves, not just the rep who happened to be on the call.
Quick answer: Handle a sales objection by not answering it straight away. Let the buyer finish, acknowledge the concern without agreeing or arguing, ask one question to find the real issue, respond to that issue briefly, and confirm it is resolved before moving on. Most objections fall into six types: pricing, timing, competitor, authority, need and trust. Diagnose the type first, because each has a different real cause and a different fix.
Key takeaways
- An objection is information, not an attack. The buyer is telling you what has to be true before they move forward.
- Ask before you answer. A confident answer to the wrong concern makes things worse, so find the real concern first.
- Six types cover almost everything you will hear: pricing, timing, competitor, authority, need and trust. Each has its own diagnostic questions.
- Separate stalls from objections. "Send me some information" is usually a polite exit, not a request for a PDF.
- The best objection handling happens in discovery, before the objection is raised.
- Track objections across calls. A team that knows which objections recur, and at which stage, can fix the pitch, the pricing or the product instead of rehearsing the same rebuttal forever.
What is a sales objection?
A sales objection is a concern a buyer raises that stands between them and the next step: signing, booking a demo, bringing in a colleague, or simply agreeing to keep talking. It can be stated directly ("we can't afford this") or wrapped in a polite postponement ("let's revisit next quarter").
Three things are worth separating from the start:
- An objection is a genuine concern that, if resolved, would let the deal move. "Your tool doesn't connect to our CRM" is an objection.
- A stall is a way of postponing a decision without stating the real reason. "Send me some information" is often a stall.
- A rejection is a clear, considered no. "We've chosen another vendor and signed" is a rejection, and the professional response is to accept it gracefully and ask what tipped the decision.
Objection handling is the skill of working out which of these you are facing and responding to the real concern underneath. It is not the skill of winning an argument. A buyer who loses an argument to a salesperson does not buy; they stop taking the calls.
Why do buyers raise objections?
Because buying is risky and the buyer carries the risk. They have to justify the spend, live with the implementation and explain it to their boss if it goes wrong. Objections are how a careful buyer tests whether you have thought about those risks too.
That is why an objection is usually a better sign than silence. A prospect who raises a price concern is at least picturing paying. The deals that quietly die are the ones where nobody said anything difficult, the call ended pleasantly and the follow-up email went unanswered.
What is the best framework for handling objections?
There is no single correct framework, but every good one has the same shape: slow down, understand, then answer. LAER is a widely taught four-step model: Listen, Acknowledge, Explore, Respond. The version below adds the step most reps skip, confirming that the objection is actually resolved.
Step 1: Pause and let them finish
Do not interrupt, and do not start composing your answer while they are still talking. Gong, which sells conversation-analysis software, published an analysis of 67,149 recorded sales demos in its Gong Labs research on handling objections. It reported that successful sellers paused longer after an objection than during the rest of the call, while average reps launched into what Gong called a "knee-jerk" monologue that stretched 21.45 seconds. This is vendor research, not a peer-reviewed study, and it shows what successful reps tend to do rather than proving that pausing causes wins. The practical lesson still holds: a two-second pause costs you nothing, and a twenty-second defensive speech can cost you the deal. Long answers also drag your talk-to-listen ratio in the wrong direction at exactly the moment the buyer has something to say.
Step 2: Acknowledge without agreeing or arguing
Acknowledging means showing you heard the concern and that it is reasonable to raise. It does not mean conceding the point. "That's a fair question to ask at this stage" works. "You're right, it is expensive" gives the point away, and "Actually, we're one of the cheaper options" starts a debate.
Step 3: Explore with one question
This is the step that separates good objection handling from scripted rebuttals. The words a buyer uses are often not the real concern. "It's too expensive" can mean there is no budget, the value isn't clear, a competitor quoted less, or they want a discount before signing. Each needs a different response. As Gong's write-up puts it, a strong answer to the wrong objection makes the objection worse; its analysis found successful reps tended to respond to objections with questions rather than assume they understood. Ask one open question to find out which concern you are dealing with, then a follow-up.
Step 4: Respond to the real concern, briefly
Once you know the actual issue, answer it in as few sentences as you can. Use their words, refer back to something they told you earlier in the call, and offer proof that fits: a specific example, a number from their own situation, a trial, a reference. Then stop talking.
Step 5: Confirm and agree the next step
Ask whether you have answered it: "Does that address the concern, or is there more to it?" If yes, move to a concrete next step. If not, you have learned there is a second objection behind the first, and you go back to Step 3. Skipping this step is how reps leave calls believing an objection was handled when the buyer was simply being polite. Restate the answer in writing afterwards, too; the follow-up email after a sales meeting is the natural place to do it.
| Step | What you do | What it sounds like |
|---|---|---|
| 1. Pause | Let them finish, then wait two seconds | (silence) |
| 2. Acknowledge | Show it's reasonable to raise | "That's a fair thing to ask about." |
| 3. Explore | Ask one question to find the real concern | "When you say that, what's behind it?" |
| 4. Respond | Answer that concern briefly, with proof | "You mentioned earlier that... here's how that changes the picture." |
| 5. Confirm | Check it's resolved, then agree a next step | "Does that cover it, or is there more to it?" |
What about feel-felt-found?
Feel-felt-found is a classic three-part response: "I understand how you feel. Other customers felt the same way. What they found was..." It is popular because it is easy to remember and pairs empathy with social proof.
It also has real problems. It is so widely taught that many buyers recognize it, and once they do, the conversation feels scripted. "I understand how you feel" can sound presumptuous when you have not asked how they feel. Worst of all, it jumps straight to a response without exploring, so it often answers the wrong objection, and it tempts reps to invent the "others" who "found" something. If you use it, use the structure rather than the words: acknowledge in your own language, ask a question first, and share a real, specific customer example only if you have one.
What are the six types of sales objections?
Almost every objection you will hear belongs to one of six types. Naming the type tells you what to ask next.
| What the buyer says | Type | Likely real concern | First question to ask |
|---|---|---|---|
| "It's too expensive." | Pricing | Value is unclear, or there is a real budget limit | "Too expensive compared with what?" |
| "Can you do a better price?" | Pricing | Negotiating, or needs a win to take to their boss | "If price weren't an issue, is everything else in place to go ahead?" |
| "Now's not a good time." | Timing | Other priorities, or the problem isn't painful enough yet | "What would need to change for this to be the right time?" |
| "Call me next quarter." | Timing | A budget cycle, or a polite brush-off | "What happens next quarter that makes it a better time?" |
| "We're happy with our current provider." | Competitor | Switching feels riskier than staying | "If you could change one thing about it, what would it be?" |
| "We're looking at a couple of other options." | Competitor | Comparing, and unsure which criteria matter | "What will the decision come down to?" |
| "I need to talk to my boss." | Authority | Not the decision maker, or needs help selling it internally | "What will your boss want to know first?" |
| "It's a committee decision." | Authority | Several people with veto power and unknown criteria | "Who else is involved, and what does each of them care about?" |
| "We don't really need this." | Need | The problem hasn't been quantified, or genuinely isn't there | "How are you handling this today?" |
| "It doesn't do X." | Need | A real gap, or a nice-to-have dressed as a must-have | "How important is X compared with the rest of what we discussed?" |
| "I've never heard of you." | Trust | Fear of choosing an unproven vendor | "What would you need to see to feel comfortable?" |
| "I don't trust it to work for us." | Trust | Fear of failure, or a past bad experience | "Has something like this let you down before?" |
The six sections below take each type in turn: what it really means, questions to diagnose it, five response scripts and what not to say. The scripts are starting points. Rewrite them in your own words, because the buyer will hear the difference.
How do you handle pricing objections like "it's too expensive"?
What a pricing objection really means
A pricing objection is rarely about the number alone. It usually falls into one of four buckets. A budget objection means they genuinely cannot pay this amount this year. A value objection means they have not yet seen enough value to justify the price, which is the most common bucket and the most fixable. A comparison objection means a cheaper alternative is on the table. A negotiation move means they intend to buy and want a better deal first.
The difference between price and value is the heart of it. Price is what they pay; value is what they get relative to what the problem currently costs them. If you have not established what the problem costs, any price is too high.
Questions to diagnose a pricing objection
- "Too expensive compared with what: a budget you've set, another option, or what you expected?"
- "Is it the total, the monthly amount, or the timing of the payment?"
- "Setting price aside for a moment, is this the solution you'd want?"
- "Roughly what is the current problem costing you each month?"
Five responses to "it's too expensive"
1. Find out what they are comparing against. Use when you don't yet know which bucket it is.
"That's fair to raise, and I'd rather talk about it now than at the end. When you say expensive, is that against a budget you've set, against another option you're looking at, or against what you expected it to cost?"
2. Return to the cost of the problem. Use when it's a value objection and they told you the cost of the problem earlier.
"Earlier you said your team loses about a day a week to [problem]. If that's right, what is that worth over a year? I want to make sure we're comparing the price with the problem, not with zero."
3. Isolate the price. Use when you suspect a negotiation move or a hidden second objection.
"If the price worked for you, is there anything else that would stop you going ahead?"
If the answer is no, you are negotiating. If they name something else, that is the real objection.
4. Adjust the scope, not just the price. Use for a real budget limit.
"Understood. Rather than discount the full package, would it make sense to start with [smaller scope, fewer seats, one team] and expand once you've seen it work?"
5. Trade, don't give. Use when they ask for a discount and you have room to move.
"I may have some flexibility. What I'd need in return is [an annual commitment, a case study, a signature by a specific date]. Would that work on your side?"
What not to say about price
- Do not discount immediately. It tells the buyer the first price was not real and invites a second round.
- Do not argue that you are cheap. "We're actually less than [competitor]" turns the conversation into a price comparison you may lose.
- Do not apologize for the price. If you don't believe it is fair, they won't either.
How do you respond to "now's not a good time"?
What a timing objection really means
A timing objection is a statement that something else is a higher priority, or that the cost of waiting seems low. Sometimes it is entirely legitimate: a hiring freeze, a busy season, a budget that resets in January. Often it means the problem has not been made urgent, or it is a polite way of saying no.
Timing objections are the type most often disguised as stalls. The pattern to watch for is a deferral with no specific reason attached.
Questions to diagnose a timing objection
- "What's taking priority right now?"
- "What would need to change for this to be the right time?"
- "What happens if this stays as it is for another six months?"
- "Is there a date or event that makes later better, like a budget cycle or a contract renewal?"
Five responses to "now's not a good time"
6. Ask what is driving the timing. Use first, every time.
"That makes sense, timing matters. Can I ask what's driving it? Is it bandwidth on your side, budget timing, or something else on the roadmap?"
7. Make the cost of waiting concrete. Use when the problem is real but not felt.
"Totally fair. Just so we're both clear on the trade-off: you mentioned [problem] is costing roughly [their number] a month. If we pick this up in six months, is that a cost you're comfortable carrying until then?"
8. Shrink the first step. Use when the objection is really about bandwidth.
"If the worry is your team's time, what if the first step were just a 30-minute session with [the person who'd use it], so you can judge the effort before committing to anything?"
9. Answer "send me some information". Use when it arrives as a polite deferral.
"Happy to. So I send you something useful rather than a generic brochure, what's the one question you'd want it to answer? And shall we put fifteen minutes in the diary for after you've read it?"
10. Accept the timing and book the date now. Use when the reason is genuine.
"That's completely reasonable. Rather than leave it open, shall we book a short call for the week of [date]? If things change before then, you can move it."
If they would rather choose the time themselves, send a scheduling link. Whether that comes across as rude or helpful depends mostly on how you frame it.
What not to say about timing
- Do not invent urgency. Fake deadlines and "this price is only available today" destroy trust the moment the buyer checks.
- Do not accept "later" without a date. "I'll circle back" with no booked meeting is how deals evaporate.
- Do not push past a genuine constraint. If they are in a hiring freeze, pressing harder makes you the vendor they avoid when the freeze lifts.
How do you handle "we're happy with our current provider"?
What a competitor objection really means
A competitor objection covers two situations: the buyer already uses something (an incumbent vendor, an in-house tool or a spreadsheet), or they are comparing you with alternatives. The first is mostly about the risk and effort of switching. The second is about criteria: they don't yet know what the decision should come down to, or they know and you haven't shown how you meet it.
Staying put is the default for most people. Status quo bias is the tendency to stick with the current option even when another might be better. In their 1988 paper Status Quo Bias in Decision Making, economists William Samuelson and Richard Zeckhauser reported decision-making experiments in which people disproportionately stuck with the status quo, and found the bias was substantial in real choices of health plans and retirement programs. "We're happy with what we have" is often that bias speaking, not a considered verdict on your product.
Questions to diagnose a competitor objection
- "What made you choose them originally?"
- "If you could change one thing about how it works today, what would it be?"
- "When does your current contract renew?"
- "What will the decision come down to between the options you're looking at?"
Five responses to "we're happy with our current provider"
11. Respect the choice, then look for the gap. Use with a satisfied incumbent customer.
"Good, it's always easier when things are working. Out of curiosity, if you could change one thing about how it works today, what would it be?"
12. Lower the stakes of comparing. Use when switching feels like too big a step.
"I'm not suggesting you rip anything out. Would it be useful to see how [the specific thing they mentioned] would work with us, side by side, so you know your options at renewal?"
13. Ask for the decision criteria. Use when they are actively comparing.
"That's sensible, you should compare. What will the decision come down to? If I know what matters most, I can show you exactly how we handle it, and be honest where another option might suit you better."
14. Differentiate on what they care about, not on everything. Use when they name a competitor.
"They're a solid option. The difference people usually notice is [one specific, verifiable difference that maps to their stated priority]. Is that something that matters for you?"
15. Plan around the contract. Use when they are locked in.
"Makes sense. When does the contract come up? It might be worth a short conversation a couple of months before, so you have a real alternative when you negotiate."
What not to say about competitors
- Do not criticize the competitor. The buyer chose them, or is considering them, and criticism reads as criticism of the buyer's judgement.
- Do not state a competitor's features or prices that you have not checked recently. Buyers often have the competitor's proposal open in another tab.
- Do not try to win on every dimension. Pick the one or two that match their priorities.
How do you respond to "I need to talk to my boss"?
What an authority objection really means
An authority objection means the person in front of you cannot, or will not, decide alone. In B2B that is normal. A 2015 Harvard Business Review article, Making the Consensus Sale by Karl Schmidt, Brent Adamson and Anna Bird, describes reps rarely finding a unilateral decision maker today: the authority to decide usually rests with groups of people in different roles, all of whom have veto power.
So "I need to talk to my boss" can mean several things. They really do need sign-off. They are not yet convinced themselves and are using the boss as a shield. Or they are convinced but don't know how to make the case internally. Your job is to find out which, and to help your contact sell it when you are not in the room.
Questions to diagnose an authority objection
- "Who else will be involved in the decision?"
- "What will your boss want to know first?"
- "How did the last purchase like this get approved?"
- "Where do you personally stand on it?"
Five responses to "I need to talk to my boss"
16. Check where your contact stands. Use first, before you plan the internal sell.
"Of course. Before you do, can I ask where you stand on it yourself? If it were your call alone, would you go ahead?"
17. Offer to equip them. Use when your contact is a supporter.
"What will they want to know first? I can put together a one-page summary in your words, covering the problem, what it costs, what we'd do and what it would cost, so you don't have to translate it."
18. Ask to meet the decision maker together. Use when the stakes are high or your contact seems unsure.
"Would it help if the three of us got 20 minutes together? You'd stay in the driving seat, and I can take the detailed questions so they don't come back to you."
19. Map the whole buying group. Use with "it's a committee decision".
"That's helpful to know. Who sits on it, and what does each of them care about most? Finance, IT and the people who'll use it every day usually ask different questions, and I'd rather answer them up front."
20. Agree the process and the date. Use to stop the deal drifting.
"So I don't chase you at the wrong moment, what does the approval process look like from here, and when do you expect a decision?"
What not to say to an authority objection
- Do not go over your contact's head without their agreement. You may win the meeting and lose your champion.
- Do not say "I thought you were the decision maker." It embarrasses them and solves nothing.
- Do not hand over a 30-page deck and hope. The boss will skim it, and the person who has to explain it will not have the words.
How do you handle "we don't need it"?
What a need objection really means
A need objection says the buyer does not see a problem worth solving, or does not see your product as the way to solve it. It covers "we don't need this", "we already do this in spreadsheets", "it's not a fit" and "it doesn't have feature X".
Sometimes it is true, and the honest response is to agree and leave the door open. More often the problem exists but has never been quantified, or the buyer has adapted to it so thoroughly that the workaround feels free. A need objection late in a deal usually means discovery was rushed or skipped.
Questions to diagnose a need objection
- "How are you handling this today?"
- "What does that cost in time, money or risk?"
- "Who feels this problem most?"
- "If you did nothing about it for a year, what would happen?"
Five responses to "we don't need it"
21. Ask how they handle it today. Use first.
"That's fair, and if you don't need it I won't waste your time. How are you handling [the job it does] at the moment?"
22. Quantify the workaround. Use when they describe a manual process.
"So someone pulls that together by hand each week. Roughly how many hours does it take, across the team? I'm curious whether it adds up to more than it feels like."
23. Find the person who feels the pain. Use when your contact isn't the one affected.
"It sounds like it works fine from where you sit. Is there anyone on the team for whom this is more of a headache, maybe [role]?"
24. Weigh the missing feature. Use for "it doesn't do X".
"You're right, we don't do X today. Can I ask how central it is? Is it something you'd use every day, or something that would be nice to have alongside the things you mentioned earlier?"
25. Agree, and leave the door open. Use when there genuinely is no need.
"Honestly, from what you've described, I don't think we're the right fit right now, and I'd rather tell you than push it. If [a trigger, such as the team doubling in size] happens, I'd be glad to pick it up again."
What not to say to a need objection
- Do not tell them they need it. A need the buyer has not said out loud does not survive their first internal meeting.
- Do not say a missing feature is on the roadmap unless it is, with a date you can stand behind.
- Do not demo more features. More features do not create a need; they create noise.
How do you respond to "I don't trust it"?
What a trust objection really means
A trust objection is about risk to the buyer personally: choosing a vendor they have never heard of, a product that might not work, a company that might not be around next year, or a tool that touches sensitive data. It shows up as "I've never heard of you", "do you have references?", "what about security?" and "I'm not sure it'll work for us".
Trust objections are closely tied to indecision. In The JOLT Effect (2022), Matthew Dixon and Ted McKenna draw on what their publisher describes as a study of more than two and a half million sales conversations, and argue that once purchase intent is established, what buyers really care about is not failing. A buyer who likes your product but fears being the person who picked the wrong vendor needs that fear addressed, not more benefits.
Questions to diagnose a trust objection
- "What would you need to see to feel comfortable?"
- "Has a tool like this let you down before? What happened?"
- "Who on your side reviews security or data handling, and what do they usually ask for?"
- "What would make this a safe first step for you?"
Five responses to "I don't trust it"
26. Ask what proof they need. Use first.
"That's a sensible concern, and I'd ask the same. What would you need to see to feel comfortable: a reference customer, a trial, our security documentation, or something else?"
27. Uncover the past experience. Use when the hesitation sounds personal.
"It sounds like you might have been burned before. What happened last time? I'd like to understand it, so I can tell you honestly whether the same thing could happen here."
28. Offer a real reference. Use when you have a relevant, willing customer.
"Would it help to talk to [a customer in their industry or of a similar size]? I'd rather you hear it from them than from me. I'll make the introduction and stay off the call."
29. Reduce the size of the bet. Use when the fear is of committing.
"What if we started smaller, with [a pilot, one team, a trial period], and agreed up front what success looks like? If it doesn't meet those criteria, you've lost very little."
30. Answer security questions with documents, not reassurance. Use when data or compliance comes up.
"Good question, and it shouldn't be answered with 'trust us'. I'll send [our security documentation, data processing terms, and the certifications we actually hold]. Who should I send them to, and is there a questionnaire your team uses?"
What not to say to a trust objection
- Do not invent references, customer counts or reviews. Beyond being dishonest, fabricated testimonials in marketing can fall foul of rules such as the US Federal Trade Commission's Consumer Reviews and Testimonials Rule.
- Do not claim certifications or guarantees you do not have. The security reviewer will ask for the document.
- Do not say "trust me." It is the one phrase that guarantees they won't.
Is it a real objection or a stall?
A stall sounds like an objection but is designed to end the conversation without conflict. "Send me some information", "let me think about it", "circle back next quarter" and "looks great, I'll be in touch" are the classics. The publisher's description of The JOLT Effect puts it bluntly: in sales, the worst thing you can hear from a customer isn't "no", it's "I need to think about it".
The test is specificity. A real objection names a concern you can work on. A stall stays vague, and it stays vague when you ask about it.
| Signal | Real objection | Stall |
|---|---|---|
| Specificity | Names a concrete issue ("it doesn't connect to our CRM") | Vague ("let me think about it") |
| Response to a question | They explain and engage | They deflect or wrap up the call |
| Next step | They agree to one | They avoid committing to a date |
| Repeats | The same concern returns until it is resolved | A new reason appears each time |
Two questions separate them reliably:
- The isolation question: "If we solved that, is there anything else that would stop you moving forward?" A real objection gets "no, that's the main thing." A stall gets a pause, then a different reason.
- The honesty invitation: "In my experience, 'let me think about it' sometimes means there's a concern people don't want to raise. If there is one, I'd much rather hear it now." Said warmly, this gives the buyer permission to tell you the real objection.
If it turns out to be a no, take it. A clear no is worth more than three months of follow-ups to someone who has already decided.
How do you prevent objections in discovery?
The cheapest objection to handle is the one you dealt with before it was raised. Neil Rackham's SPIN Selling is based on research into more than 35,000 sales calls made by 10,000 salespeople in 23 countries over 12 years. Its publisher's description lists "objection handling is an important skill" among the conventional beliefs the book argues are false for high-value sales, and the book gives a full chapter to preventing objections. The underlying idea is that many objections are provoked by pitching a solution before the buyer has agreed there is a problem worth solving.
In practice, each of the six types has a discovery question that surfaces it early, while it is still a fact to work with rather than an objection to overcome:
- Pricing: Ask about the cost of the problem and the budget before you show a price. "What's this costing you today?" and "Is there a budget set aside, or would this need a new one?"
- Timing: Ask what is driving the conversation now. "Why is this on your list this quarter?" If there is no answer, you have found a timing objection early.
- Competitor: Ask what they use today and what else they are considering. "What have you tried so far, and what else are you looking at?"
- Authority: Ask who else is involved and how decisions like this get made. "Walk me through how you bought the last tool like this."
- Need: Quantify the problem in their words, and summarize it back to them before you propose anything.
- Trust: Ask how they evaluate vendors. "Is there a security review, and what does your team usually ask for?"
The discovery call guide covers the full call structure and thirty questions. Two other moments matter. Demos invite objections when they show everything instead of the few things the buyer asked about, which the guide to running a sales demo addresses. And timing objections multiply when a new lead waits days for a first reply; the speed-to-lead guide explains why that first response window matters.
How do you track objections across a team?
One rep's memory of "the objections I usually get" is anecdote. A team log of every objection, by type and stage, is data you can act on. It tells you whether pricing objections cluster after demos (the demo isn't showing value), whether authority objections appear late (discovery isn't mapping the buying group), or whether the same missing feature keeps coming up (a product conversation, not a sales one).
A simple objection log you can start today
- Agree the categories. Use the six types above so everyone tags the same way.
- Log every objection after the call. Record the buyer's exact words rather than your paraphrase, plus the type, the deal stage and the response you used.
- Record the outcome. Resolved on the call, still open, or deal lost. Update the open ones when they move.
- Review weekly. Count objections by type and by stage. Look for clusters, not individual calls.
- Fix one per month. Take the most frequent unresolved objection, agree a better response as a team, and practice it.
- Send product and pricing feedback where it belongs. If the same "it doesn't do X" appears in a large share of lost deals, that is a roadmap input, not a coaching problem.
A spreadsheet with these columns is enough to start. The rows below are illustrative:
| Date | Deal | Stage | Type | Buyer's exact words | Response used | Outcome |
|---|---|---|---|---|---|---|
| 2026-10-14 | Example deal A | After demo | Pricing | "This is more than we budgeted for this year." | Scoped to one team first | Open |
| 2026-10-15 | Example deal B | Discovery | Authority | "Our ops director will have to sign this off." | Offered a one-page summary | Resolved |
The weakness of a manual log is that reps forget, paraphrase, or quietly skip the objections they handled badly. That is where recordings and transcripts help.
How does PepoSmart track objections from call transcripts?
PepoSmart is an AI scheduling and meeting-intelligence platform. Its AI notetaker joins Zoom, Google Meet and Microsoft Teams meetings as a visible participant and produces a recording, a speaker-labelled transcript, a summary, action items with an owner and priority, a sentiment and buyer-intent read, a coaching scorecard and a follow-up email draft for review. The AI meeting notes page describes the full set.
On top of the transcript, deal intelligence does the tagging step of the log for you:
- Objections are detected and sorted into the same six categories this guide uses: Pricing, Timing, Competitor, Authority, Need and Trust.
- Risk signals are detected in six further categories: stalled deal, ghosting, champion leaving, budget cut, negative sentiment and internal politics.
- Competitor mentions, and whether budget was discussed, are picked up as well.
- A deal-risk score from 0 to 100 combines the detected objections (weighted by severity), risk signals, competitor mentions and whether budget was discussed.
The categories and scoring inputs are published on the product facts page.
Treat every detection as a prompt for a human, not a verdict. Objections and risk signals are detected from the transcript by pattern and model analysis, so they can miss implicit statements, such as a buyer who goes quiet when price comes up, and they can flag phrases that were not meant as objections, such as "I'm worried about" in a sentence about something else entirely. Open the transcript at the flagged moment and decide for yourself. The same principle applies to your CRM: when HubSpot, Salesforce or another supported CRM is connected (Professional plan and above), PepoSmart suggests a deal-stage change, and nothing is written to the CRM until a user approves it.
Two other features turn single calls into team patterns:
- Chat with meetings answers plain-English questions across the meetings PepoSmart recorded and indexed for you, such as "Which meetings discussed pricing?" or "What objections come up most?", and cites the meetings each answer came from. It can be wrong, because it inherits any transcription errors, so open the source before acting on an answer.
- Coaching scorecards score each recorded call from 0 to 100 on talk ratio, questions asked, filler words and engagement, where engagement loses points for long monologues. That makes the knee-jerk monologue after an objection visible. The full formula is in the published call-score methodology.
Before the next call, AI call prep assembles past meetings with the contact, the sentiment trend and the commitments still outstanding, with CRM context on Professional and above, so a rep walks in knowing which concerns are still open.
Plan availability. Deal intelligence, coaching scorecards, chat with meetings and AI call prep are available on Starter and above; the team coaching views are on Business. Every plan, including Free, includes 2 AI recordings for the lifetime of the account. Beyond those, paid plans add recordings with credit packs (10 for $19, 20 for $27 or 40 for $39, each credit valid for 30 days). The sales solution page shows how the pieces fit together for a sales team.
Recording calls also carries obligations that vary by jurisdiction. The notetaker is visible to every attendee, but obtaining any consent your location or company policy requires is the host's responsibility. The guide to whether it is legal to record a meeting covers the basics.
How should a sales team practice objection handling?
Reading scripts does not build the skill. Saying them out loud, under mild pressure, does. Two habits make the difference: regular role-play and regular call review.
Run a 20-minute weekly objection drill
- Pick one objection type for the week. Use whichever type tops your log.
- Use real wording. Pull three verbatim objections from recent calls. Real buyers phrase things in ways nobody writing a script would predict.
- Assign three roles. Buyer, seller and observer. Rotate each round.
- Play it for three minutes. The buyer should not give in after one good answer, because real buyers often have a second objection behind the first.
- The observer scores the five steps. Did the seller pause? Acknowledge without conceding? Ask a question before answering? Keep the response short? Confirm and agree a next step?
- Debrief for two minutes. One thing that worked, one thing to change. Then rotate.
Review real calls, not just role-plays
Once a week, each rep picks one recorded call where an objection came up and listens to the two minutes that follow it, ideally with a manager or a peer. Look for the same five behaviors, and note the length of the first answer; many reps are surprised by how long they talked. Coach one behavior at a time. A rep told to pause, ask more questions, talk less and stop saying "basically" all at once will change none of them. The talk-to-listen ratio guide explains how to read the numbers without turning them into a target to game.
Keep a living objection playbook
Store the team's best responses in one shared document, organized by the six types. For each objection, record the buyer's typical words, the diagnostic question, the response that has worked best on your own calls and a real example. Update it monthly from the log. The scripts in this guide are a starting point; the version written from your own calls will be better.
What PepoSmart does not do, and what we don't claim
- It only sees meetings it recorded. Phone calls and in-person meetings cannot be recorded, because the notetaker joins as a participant in an online meeting. If much of your selling happens by phone or face to face, a manual objection log will capture more than a meeting notetaker can.
- Detection is not judgment. It can miss an objection that was implied rather than said, and flag one that wasn't meant. A person still has to read the moment and decide.
- The deal-risk score is not a forecast. It combines the signals listed above from recorded calls. It knows nothing about the conversation over lunch or the email from the buyer's finance team, so use it to decide which deals to look at, not which deals will close.
- The call score measures conversational mechanics. It does not tell you whether a response was right, and it should not be used on its own to evaluate a person.
- Recording volume is bounded. Two lifetime recordings are enough to try the notetaker, not to track a team. Tracking objections across many calls means buying credit packs on a paid plan.
- It does not handle the objection for you. The scripts, the practice and the playbook are still the team's work.
We also do not publish a win-rate improvement figure for objection handling or for deal intelligence. A defensible number would need a controlled study with a baseline, and we have not run one. Be wary of anyone quoting a precise uplift for a skill as context-dependent as this.
Summary
Sales objections fall into six types: pricing, timing, competitor, authority, need and trust. Handle any of them the same way: pause, acknowledge without conceding, ask one question to find the real concern, respond briefly to that concern and confirm it is resolved. Separate stalls from real objections, prevent the predictable ones in discovery, and log every objection by type and stage so the team fixes patterns rather than rehearsing the same rebuttal. If you want the tagging done from your call transcripts, create a free PepoSmart account to try the notetaker on two meetings; deal intelligence is on Starter and above, and each paid plan starts with a 12-month free trial on a new subscription. See the pricing page for current plan details.
