# Consultative selling in Pipedrive: what to ask, what to log

https://salesbond.app/blog/consultative-selling-pipedrive/
Published: 2026-10-02 · Updated: 2026-10-25

Consultative selling is selling by working out the customer’s problem before you talk about price or product. The rep leads with questions, writes the problem down in the customer’s own words, and proposes a solution only for that problem. In a small team this stays manageable when every deal in Pipedrive carries three entries: the problem, the cost of doing nothing about it, and the next step both sides agreed to. The rest of this article is how to get them written and how to check them in fifteen minutes a week.

## Consultative selling is a habit you can audit

Most explanations of consultative selling describe an attitude. Salesloft’s guide walks through five steps: research, questioning, listening, solution-offering and follow-up ( [Salesloft, Consultative Selling 101](https://www.salesloft.com/resources/blog/consultative-selling-101)). Pipedrive’s own article contrasts it with product-based selling and borrows its question structure from SPIN ( [Pipedrive, consultative selling](https://www.pipedrive.com/en/blog/consultative-selling)). Both are fair descriptions. Neither tells a manager what to look at on Monday to know whether any of it happened.

The difference from transactional, or product-based, selling is where the conversation starts. A transactional rep starts from the product and looks for a buyer it fits. A consultative rep starts from the customer’s problem and decides what to offer only once that problem is written down.

That is the problem for a team of three to eight reps with no sales engineer and nobody doing enablement. You cannot sit in on every call. You can read a deal record. So drop “do my reps sell consultatively?” and ask a narrower one: what would a consultative call leave behind in the CRM, and is it there?

The case for caring is mostly about trust. According to Pipedrive, only 58% of consumers trust businesses, and Forrester has found vendor salespeople among the least trusted sources of information in a B2B purchase; the same article reports that 72% of top performers say they always put the buyer’s needs first ( [Pipedrive](https://www.pipedrive.com/en/blog/consultative-selling), citing Edelman, Forrester and LinkedIn). We would not read a method into those numbers. They are about trust, not technique. But they explain why a rep who opens with a demo starts the conversation behind.

Our position: in a small team, consultative selling is proved by artifacts, not by philosophy. Three deal fields, one stage rule, one short weekly review. No new tool.

## What it looks like on a call (and what it doesn’t)

Owen sells scheduling software to clinics. He has a first call with the office manager of Fenwick Dental, four locations. The version of this call we don’t want goes like this: ten minutes of pleasantries, then a screen share, then forty minutes of “and here you can also”. The office manager says “looks great, send me pricing”, and the deal goes to Proposal with a close date three weeks out. Nobody in that call found out what was wrong.

The consultative version starts slower. Owen asks what made her take the call. She says the front desk spends a chunk of every afternoon ringing back no-shows. He asks how much time, roughly. She thinks it is about six hours a week across the four sites. He asks what that time costs them, and she says their coordinators are on around $38 an hour. He does the arithmetic with her on the call: $228 a week, call it $11,856 a year, by her own estimate. Then he asks who else would weigh in on a change like this, and learns the practice owner signs anything that touches the front desk. They agree on an ending: Owen sends a two-page summary of what she told him, she forwards it to the owner, and the three of them meet the following Tuesday.

Notice what Owen did not do. He did not read a question list off a script and he did not ask what keeps her up at night. If you want the structure behind the questions, we wrote it up in [SPIN selling for Pipedrive teams](https://salesbond.app/blog/spin-selling-pipedrive/); here the point is the output. He also did more than listen: he recommended a next step and named a number. Consultative does not mean passive, and a rep who only nods is as unhelpful as one who only demos.

Notice, too, that every number in that call is the customer’s. Owen didn’t bring a benchmark. He brought a question and a calculator, and the estimate came out of her mouth. That is what makes it worth writing down.

## Three fields that prove it happened in Pipedrive

This is the part of the consultative selling process a manager can read after the call. Three custom fields on the deal, all plain text:

1. **Problem (customer’s words).** A quote or near-quote. “Front desk spends every afternoon calling back no-shows across four locations.” Not “inefficient scheduling”, which is the rep translating.
2. **Cost of inaction.** The customer’s estimate, with its unit: “about 6 h/week of coordinator time, roughly $228/week by their numbers.” If the rep asked and the customer did not know, write “asked, they don’t know”. That is a real finding. A blank is not.
3. **Agreed next step.** What both sides do and by when: “Owen sends summary Fri; she forwards to owner; three-way call Tue.” Pipedrive’s next activity records what Owen will do. This field records what the customer committed to, which is the part that predicts anything. If you would rather not add a third field, put the customer’s part into the activity subject instead; we covered why the buyer’s action is the one to watch in [deal review questions that start with the buyer](https://salesbond.app/blog/deal-review-questions-buyer-action/).

The decision maker usually shows up inside the third field (“she forwards to owner”). When it doesn’t, that is itself a finding: the rep has a problem and a cost, and nobody who can sign.

Setup is ten minutes: Settings, Data fields, Deal, add the three custom fields. Make them visible on the deal detail view so a rep sees the blanks every time the deal opens. Then make Problem required for the Proposal stage. On Pipedrive’s Professional plan and higher, a deal field can be required for specific pipelines and stages, and a rep who tries to move a deal into that stage with it empty is prompted to fill it in ( [Pipedrive, Required fields](https://support.pipedrive.com/en/article/required-fields)). An important field (Advanced plan and higher) only flags the missing data without blocking the move ( [Pipedrive, Important fields](https://support.pipedrive.com/en/article/important-fields)); we compared the two in our piece on [choosing a sales methodology for a Pipedrive team](https://salesbond.app/blog/sales-methodology-for-pipedrive-teams/). If your plan has neither, the saved filter below does the same job by hand.

A word on fields versus notes, since reps will ask. The call note is the rep’s memory and belongs to the rep. These three fields are the manager’s evidence and belong to the deal. They overlap on purpose. Our take on where each line of a note should live is in [the minimum call note that saves a deal](https://salesbond.app/blog/sales-call-notes-minimum/), and the short answer is that anything a manager needs to read in twenty seconds goes in a field.

![Two deal cards for the same clinic deal: the demo-first card has empty Problem and Cost of inaction fields, the consultative card has both filled in the customer's words](https://salesbond.app/wp-content/uploads/2026/10/consultative-selling-pipedrive-2.png)

## One stage rule that keeps reps honest

The rule is one sentence: no deal moves to Proposal with the Problem field empty or written in the rep’s words.

The second half matters more than the the first. A required-field setting catches a blank. It does not catch “needs better scheduling”, which is a rep’s summary of what he thinks he heard. The test we use is simple to say on a Monday: would the customer recognise that sentence as theirs? If Fenwick’s office manager read “needs better scheduling” she would shrug. If she read “front desk spends every afternoon calling back no-shows” she would say yes, that’s us.

Why Proposal and not earlier? Because Proposal is where price appears, and the only hard rule in consultative selling is problem before price. It is not fine to quote a number against a problem nobody has written down.

Enforcement in Pipedrive takes a saved filter, not a feature: deals where Stage is Proposal and Problem is empty. Run it before teh weekly check. Any deal it returns goes back to Qualified with one next activity, a call whose purpose is to ask the question that was skipped. Moving a deal back feels like a punishment to the rep the first time. It is a correction to the pipeline report, and the pipeline report is the thing the manager actually runs the business on. If your stages are not clean enough for this rule to mean anything, fix that first; we wrote about [which pipeline stages a small team needs](https://salesbond.app/blog/sales-pipeline-stages/) before any of this.

We don’t score the three fields, and we don’t recommend a methodology checklist alongside them. A manager reads three blanks faster than a number, and three fields leave no room to argue about points. If you are still choosing between methods, [which sales methodology fits a small Pipedrive team](https://salesbond.app/blog/sales-methodology-for-pipedrive-teams/) is the place for that argument, not here.

## A 15-minute weekly check on two deals

Two deals, seven minutes each, one minute to pick them. That is the whole review, and it should stay that size, because a review that grows to an hour stops happening by week four.

Which two: the deal that moved into Proposal most recently, and the deal that has sat in Proposal the longest. The first tells you whether the rule is being followed now. The second tells you what a deal looks like when it wasn’t.

For each deal:

- Read the Problem field aloud. Would the customer say it that way?
- Does Cost of inaction have a number, or an honest “they don’t know”? If it has a number, whose estimate is it?
- Does Agreed next step name something the customer does, not only something the rep does?
- If a proposal went out, does it answer the Problem field or list the product?
- Ask the rep one question. Not a verdict, a question.

Here is what that looked like for Ruth, who manages Owen and two other reps, on Monday 5 October. Owen’s Fenwick deal was created on Tuesday 8 September, so it has been open 27 days. All three fields are filled, the cost is the customer’s estimate, the next step names the owner. Ruth spends her seven minutes checking that the two-page summary actually went out on Friday. It did. Done.

The second deal belongs to another rep, and its Problem field reads “Interested in automation”. Ruth asks her one question: “What did they say when you asked what the current process costs them?” The answer is that she didn’t ask. The deal goes back to Qualified with a call booked for Wednesday whose only purpose is that question. That is the entire intervention.

A disclosure, since we have reached the part where someone usually sells software: we build SalesBond, a sales management layer on top of the CRM a team already uses; we started with Pipedrive. One of the things it does is flag deals that reached a stage with fields like these still empty, so Ruth’s two deals pick themselves instead of her hunting through filters. The reading is still hers. The two-deal habit works without it, and the habit is the thing. If you want to see what your pipeline looks like through that lens, [check your CRM with SalesBond](https://salesbond.app/).

## When to skip it

Not every sale deserves a discovery conversation, and a team that forces one onto every deal trains its customers to dread the first call.

Skip it when the cycle is short and the ticket is small. If a deal typically closes in one call for a few hundred dollars, three fields cost more in rep time than they return in insight, and the customer already knows what the problem is or they would not have called. Skip it on [repeat purchases](https://salesbond.app/blog/repeat-orders-pipedrive-new-deal-per-order/), where the problem was discovered a year ago and the only question is quantity. And skip it on inbound with a defined ask: a buyer who writes “we need twelve seats of the standard plan by the end of the month” does not want to be asked about the cost of inaction, and will tell you so.

Use it where the customer has to change how they work, where more than one person decides, or where a deal normally lives in your pipeline for more than a couple of weeks. Those are the deals where the problem is not obvious to the customer either.

If your team sells both kinds, run them as separate pipelines in Pipedrive and make the three fields a rule on only one of them. A good rule applied everywhere becomes a rule nobody follows.

If you do one thing this week, add the Problem field and read it on the next deal that reaches Proposal. You will know in a minute whether that call was consultative.