# Sales objections worth logging: a Pipedrive setup that turns them into coaching

https://salesbond.app/blog/objection-handling-pipedrive-log-coach/
Published: 2026-09-29 · Updated: 2026-10-25

Good objection handling starts with a record, not a script. Log every real objection as one field value and one line in the buyer’s own words. After a month, the count by stage and by rep tells you what to coach, which a list of scripts never will.

Objection handling is how a rep answers buyer pushback so the deal keeps moving. Most guides stop at the call. This one covers what happens after it: how to track sales objections in Pipedrive with a short list of types, one field plus one note per objection, a clear line between an objection and a lost reason, and a Friday filter that turns the log into a single coaching question.

## Why scripts don’t fix a pattern

Most advice on handling objections is a list of comebacks. “It’s too expensive” gets three reframes, “send me some info” gets two, and “we’re happy with what we have” gets a clever question. Some of those lines are good. A rep who has never heard a price objection before will be better off with one of them than with nothing. A short [talk track for the moments reps improvise worst](https://salesbond.app/blog/sales-talk-track-pipedrive/), written once and rehearsed, does the same job without turning into a script.

The trouble is that a script treats every objection as a one-off event in one call. A manager’s problem is rarely one call. It’s that the same objection keeps showing up, at the same point in the pipeline, for the same two people on the team, and nobody can see it because it lives in call notes, Slack threads and memory.

If price comes up at the demo stage every week a better price comeback won’t help much. The value wasn’t established before the number came out, and that’s a discovery problem. If “I need to run it by my boss” clusters on one rep’s deals, that rep is probably not reaching the person who signs. You coach those two differently. You can only tell them apart if you have counted.

So we stopped handing out scripts first. We log, look at the pattern, and then pick the one conversation worth practising.

## Six values, not sixty: an objection list that survives a quarter

The list has to be short enough that a rep can pick a value in two seconds, and stable enough that you can compare March with June. Rename or split values every few weeks and your counts stop meaning anything.

These six are our suggestion, not an industry standard. Adjust the wording to your market, then leave it alone for a quarter:

- Price: the number, the budget, or “we can’t justify it right now.”
- Timing: “not this quarter,” “after our re-org,” “check back in spring.”
- Authority: “I need to run it by…” or a new person appears who has to approve.
- Priority: they agree with the problem but something else is more urgent.
- Status quo: they already have a tool, a spreadsheet or an agency that “works fine.”
- Risk: doubts that it will work for them, worries about switching, security questions.

Notice what isn’t there. No “Other.” An “Other” value quietly becomes the biggest bucket within a month, and then your log tells you nothing. If an objection doesn’t fit, the rep picks the closest value and the note carries the nuance. Review the notes at the end of the the quarter; if one kind of “closest fit” keeps repeating, that’s your seventh value.

“Not interested” is missing too. That’s not an objection. It’s the absence of a conversation, and it belongs in your disqualification process.

## Logging an objection in Pipedrive: one field, one line

To log objections in Pipedrive, create two custom deal fields. The first holds a fixed list of options, the six values above; call it something plain like “Open objection.” The second is a text field, “Objection, in their words,” for one line of what the buyer actually said.

Their words, not the rep’s interpretation. “Your competitor quoted us half” is useful. “Price concerns” is not, because the first field already told you that. The same habit pays off later, when someone writes a [sales pitch in the words buyers use](https://salesbond.app/blog/sales-pitch-small-team-pipedrive/).

Competitor quotes like this are the best input for [battlecards for small teams](https://salesbond.app/blog/sales-battlecards-small-teams-pipedrive/): the objection log feeds the card, the card feeds the next call.

The setup takes about ten minutes:

1. Go to Personal preferences > Data fields, choose the deal entity and click “+ Custom field” ( [Pipedrive: Custom fields](https://support.pipedrive.com/en/article/custom-fields) ). Create “Open objection” as a single option field. Pipedrive won’t let you change a field’s type after it’s created, so pick the type before you save.
2. Create “Objection, in their words” as a text field the same way.
3. On the Growth plan and above, add a field description, which reps see behind an info icon next to the field ( [same article](https://support.pipedrive.com/en/article/custom-fields) ). Put the rule there: “Fill when the buyer pushes back and is still talking to us. Their words, one line.”
4. On the deals list, build an advanced filter: status is open and “Open objection” is not empty. Save it as shared so the whole team sees the same list, and add it to Favorites so it sits at the top of the filter dropdown ( [Pipedrive: Advanced filtering](https://support.pipedrive.com/en/article/filtering) ).
5. In the list view, use the gear icon to add the two objection fields, the stage and the owner as columns ( [custom fields article](https://support.pipedrive.com/en/article/custom-fields) ).

The field holds the objection that’s blocking the deal right now. When a new one replaces it, the rep overwrites both fields and drops the old line into a deal note, so the history stays on the deal.

One more habit keeps the log honest: reps log the objection on the day they hear it, not when they tidy up deals before a forecast call. A week later “their words” have turned into “my summary,” and the summary is always kinder to the rep.

## Objection versus lost reason

This is where most logs get muddy, so we keep one rule: **if the buyer is still engaged, it’s an objection. If the deal is closed, it’s a lost reason.**

An objection is something you can still work on. The deal is open, there is a next step, and the buyer is telling you what stands in the way. A lost reason is a verdict after the fact, recorded when the deal is marked lost. They live in different places on purpose: one is for coaching live deals, the other for learning from dead ones. We cover the second in [how to set up lost reasons in Pipedrive](https://salesbond.app/blog/pipedrive-lost-reasons/), so we won’t repeat it here.

The two often share a name. A deal can carry a price objection for three weeks and then be lost for price. That’s fine, even useful, because it shows the objection was never resolved. What you don’t want is reps filling the objection field only at the moment of losing, as a second lost reason. Then you have duplicates, and you’ve thrown away the one thing the objection log gives you: a chance to act while the deal is alive.

And if a buyer has stopped replying, you don’t have an objection at all. You have silence. That calls for a different play (see [what to do when a prospect goes silent after a demo](https://salesbond.app/blog/prospect-went-silent-after-demo/)) and, eventually, a decision on [when to close the deal as lost](https://salesbond.app/blog/when-to-close-a-deal-lost/).

## The Friday view: filter and one coaching question

Open the shared filter from step 4 and sort by objection, then by stage. It takes a few minutes to read, and you read it for one thing: where does the same value repeat?

If you’d rather see a chart than a sorted list, the same fields can feed an Insights report once they hold data ( [Pipedrive: Custom fields](https://support.pipedrive.com/en/article/custom-fields)). One catch: grouping or segmenting a chart by a custom field needs the Premium plan or higher; on other plans custom fields show up only in the table view ( [Pipedrive: Insights](https://support.pipedrive.com/en/article/insights-feature)). The sorted list does the job fine.

Then you pick one question for the week. Not five. For example:

“Three of your deals got ‘I need to check with my CFO’ after the demo. Who did you ask about the budget owner in discovery?”

That question goes into the rep’s one-on-one. If you run a fixed agenda, it fits into the pipeline block ( [our sales 1-on-1 agenda](https://salesbond.app/blog/sales-1-on-1-agenda/)). The buyer’s line from the text field is what makes it land, because the rep hears thier own customer, not a manager’s theory.

## What to do when one objection is 40% of the log

Here’s a hypothetical month for a team of four reps. The numbers are made up to show the reading, not taken from a real account.

![A team meeting discussing sales objections and coaching questions.](https://salesbond.app/wp-content/uploads/2026/09/objection-handling-log-in-pipedrive-2.png)

Price is 16 of 40, so 40% of the log. Behind it: Authority 8, Timing 7, Status quo 5, Risk 3 and Priority 1.

The instinct is to run a negotiation workshop. Look at where price sits, though. Eleven of those sixteen came at the demo stage, before a proposal existed, on every rep’s deals. That points at the process, not at a person: prices are being asked and answered before the buyer has agreed on what the problem costs them. The fix is in discovery and in the demo structure, and it’s a team conversation. Once price does come up on a proposal, the rule is that [no concession goes without a trade](https://salesbond.app/blog/sales-negotiation-trade-concessions-pipedrive/), with the trade noted on the deal.

Authority has a different shape. Six of eight sit on one rep’s deals, at the proposal stage. That’s a one-on-one topic. This rep is building deals with a champion who can’t sign, and finds out late. Coach the question that surfaces the decision maker early.

When one value dominates, check two things before you react. First, is it spread across the team or concentrated? Spread means process, concentrated means coaching. Second, has it been this way for more than a month? A single month can be one big account or one campaign that pulled in the wrong buyers. Two months in a row is a pattern.

Then leave the list alone. After a 40% month it’s tempting to split “Price” into four subtypes. Don’t, at least not mid-quarter. The buyer’s words in the text field already tell you whether it’s budget, a competitor’s quote or an approval limit. Read them.

Start small. Add the two fields this week, ask reps to log only new objections from now on, and hold off on judging anything until you have four Fridays of data. The first month mostly teaches the team to log honestly. The second one starts telling you what to coach.

## FAQ

### Should objections go in lost reasons?

No. Log an objection while the deal is open and the buyer is still engaged; record a lost reason once the deal is closed. Keep both. A price objection that ends in a price loss tells you it was never resolved.

### How many objection categories should a team use?

Five to seven, kept stable for at least a quarter, with no “Other.” If an objection doesn’t fit, pick the closest value and put the nuance in the one-line note.

### How do you track objections by rep and stage in Pipedrive?

Save a shared filter of open deals where the objection field is not empty, add the objection fields, stage and owner as columns, and sort by objection.