# Conceptual selling: what to log in your CRM so the method survives a rep leaving https://salesbond.app/blog/conceptual-selling-crm-fields/ Published: 2026-10-23 · Updated: 2026-10-23 Conceptual selling, also called concept selling, is the sales method Robert Miller and Stephen Heiman built on one idea: buyers buy the concept of a solution, not its features. In a CRM it only works if a rep records, for each deal, what the buyer wants to change and who influences the decision. That is four places in the deal record, not a methodology module. If they are empty, the rep may well be selling the concept on calls, but the company has no record of it. The day that rep leaves, the method leaves with them. ## Two meanings of “conceptual selling” (pick yours) Search for conceptual selling, conceptual sales or concept selling and you get two different things wearing the same name. The first is the Miller Heiman method. Robert B. Miller and Stephen E. Heiman wrote it up in [*The New Conceptual Selling*](https://archive.org/details/newconceptualsel0000mill), the 2005 revised edition of their 1987 *Conceptual Selling*. Today Korn Ferry teaches it as [Conceptual Selling® with Perspective](https://www.kornferry.com/capabilities/leadership-professional-development/training-certifications/strategic-selling-conceptual-selling-with-perspective) and describes it plainly: it helps salespeople prepare for time spent with customers, and the result is “purposeful meetings and win-win outcomes.” Korn Ferry runs it in one program with its companion, Strategic Selling®, which is about sales that need approval from several decision makers. Most guides boil the idea down the way [Storylane](https://www.storylane.io/blog/concept-selling-how-to-do-it-right-tips-and-strategies) does: customers buy the concept of the solution rather than the solution itself, the difference it will make for them rather than the bells and whistles. The rep’s job is to find out what the buyer is trying to change and sell against that, instead of walking through a feature list. The second comes from sales training circles and treats conceptual selling as selling an idea. Tom Reilly’s [whitepaper](https://tomreillytraining.com/wp-content/uploads/2017/11/Conceptual-Selling-Whitepaper.pdf) sorts those ideas into four categories: perceptual, emotional, change and fundamental need. Useful for thinking about why a buyer says yes. Not something you can put in a deal record. This post is about the first meaning. We picked it because it produces something a manager can check: the buyer’s concept either is in the deal or it isn’t. The second meaning produces a better rep. The first produces a better deal record, and the record is what outlives the rep. ## What conceptual selling asks a rep to know about a deal Here is a scene from a Monday pipeline review. A deal has been in Proposal for three weeks. The manager asks what the buyer is trying to fix. The rep says: “They need better reporting.” The manager asks who at the buyer said that. Pause. “The ops lead, I think, and the CEO is involved.” Conceptual selling asks a rep to know three things about every deal: what the buyer wants to be different, in their own words; who shapes the decision and what each of them wants; and the one goal both sides have agreed the deal is for. The rep in that review has none of the three. Nothing they said is false, but “better reporting” is not a concept. It is our product category with “they need” in front of it. A buyer’s concept is something only this buyer could have said: “The board pack takes Priya four days and the numbers never match what sales presents, so the CEO has stopped trusting either.” That sentence has a person, a cost and a consequence in it. It tells you what change the buyer is actually buying. This is our reading of the method as a list of things a rep must know, not a summary of the book. The objectives Korn Ferry lists for its program point the same way, though: position solutions with the true decision makers, look at each decision maker’s receptivity to change, and end every meeting with clear actions for both sides. If you have read our post on [consultative selling](https://salesbond.app/blog/consultative-selling-pipedrive/) the first question will look familiar. The difference is in the second and third. Consultative selling is about how the rep runs the conversation. Conceptual selling, as we practice it, insists that the concept belongs to a group of people, not one contact, and that the deal has a single stated goal both sides can repeat. A rep who knows the concept from one person has half of it. ## Four things to log in the CRM (and where) The three questions become four places in the deal record. The field names below are ours; call them whatever your team will recognize on a busy Monday. 1. **Buyer’s concept.** A large text field on the deal. One to three sentences in the buyer’s words about what they want to change, with the test from the previous section: it must contain something that could only be true of this account. A sentence you could paste into another deal is our pitch, not their concept. Keep it out of the notes box, because an empty field looks like exactly what it is. 2. **Who shapes the decision.** Not a field: contacts linked to the deal, each with a role label (decides, influences, uses, can block) and one line on what that person wants. The one line is teh part reps skip. The CEO who has stopped trusting the numbers and the ops lead who spends four days producing them want different things from the same purchase, and a proposal written for one of them lands flat with the other. A deal with one linked contact is a [single-threaded deal](https://salesbond.app/blog/single-threaded-deals/) with a concept field: a start, and still fragile. 3. **Shared deal goal.** A short text field, one sentence, written so that the buyer would agree with it if you read it back: “Monthly board pack produced in one day from the CRM, with sales and finance on the same number, before the Q2 planning cycle.” It stops the rep selling one outcome while the buyer evaluates another. If you cannot write it, you have not agreed it. 4. **Concept last heard.** A date field. The last date someone at the buyer said the concept and the goal still stand. It moves after a call where that came up and at no other time. ![Schematic deal panel with buyer's concept, shared goal and last-heard date, next to three linked contacts with roles](https://salesbond.app/wp-content/uploads/2026/10/conceptual-selling-crm-fields-2.png) If you make one of these mandatory, make it the shared goal, not the concept: no deal leaves your evaluation stage without it. A concept can be written from one good call. A goal the buyer would agree with cannot be written until someone has asked the buyer, and that is the cheap moment to learn that they wouldn’t. ## A 5-minute deal check for managers Pull up the deal, read the four places, and ask in this order. Stop at the first question the rep cannot answer and give them that one as the task. - Read me the concept field. Who at the buyer said it, and could it be true of any other account? - Which linked contact wants something different from the rest, and what? - Say the shared goal out loud. Would the person in “decides” nod? - When did they last confirm it, and what has changed on their side since? It takes about five minutes a deal because the manager is reading what the buyer said, not reconstructing it from the rep’s confidence. A rep who gets stuck on the second question goes back to the buyer with a name to find, not a lecture about multi-threading. Compare this with a [SPIN selling](https://salesbond.app/blog/spin-selling-pipedrive/) review, where the check is whether the rep asked the right sequence of questions. Here the check is whether the buyer’s answers made it into the record. A rep can run a textbook call and leave the concept field empty. This review catches that second failure, and it’s the one that costs you when the rep hands over the territory. A disclosure, since this is where tools come up: we build SalesBond, a sales management layer on top of the CRM a team already uses; we started with Pipedrive. An empty concept field and a stale “Concept last heard” date are the same kind of signal as a missing next activity or a close date that has already passed, and that is how we think about which deals need attention this week. [Check your CRM with SalesBond](https://salesbond.app/) if you would rather get that list than build the saved filters yourself. ## What not to log Every time a team adopts a method, someone proposes a field for each chapter. Resist it. Do not log the rep’s questions. Which questions were asked, in what order, how long the buyer was allowed to talk: that belongs in call coaching, not in the deal. A deal record full of process notes tells the manager how the rep behaved and nothing about what the buyer wants. Do not log a “concept confidence” score, a “concept quality” rating or anything else the rep assesses about their own work. It will be 4 out of 5 on every deal in commit. The date field already tells you how fresh the the concept is, and the manager’s four questions tell you how good it is. And do not log features the buyer asked about. They feel like evidence of interest. They are the opposite of a concept, and a rep who fills the record with them is back to selling bells and whistles, with better paperwork. So where to start? Take the five deals closest to your commit line. Read the concept field, or the notes where it should be, and count how many could be pasted into another account. If it’s more than two, add the fields this week. The next rep who inherits those deals should not have to ask the buyer to repeat what they already said once.