# A deal naming convention for Pipedrive that survives five reps and a hundred open deals https://salesbond.app/blog/pipedrive-deal-naming-convention/ Published: 2026-10-06 · Updated: 2026-10-06 A deal naming convention in Pipedrive needs only three parts: who the deal is with, what they are buying, and one thing that tells it apart from the next deal with that customer, such as the month or an order number. “Kestrel / 40 licenses / Nov 2026” says all three in one line. Keep stage, price, status and close date out of the name, because they already have their own fields in Pipedrive, and a copy in the name goes stale the first time the field changes. Below is the convention we would hand to a five-person team, the rules for the awkward cases, and how to fix the hundred deals that are already named wrong. ## Five deals called “Kestrel” “We never got the revised quote.” Oskar, who runs a small sales team, has the customer on the phone and Pipedrive open. He types Kestrel into search and gets five open deals. Two are called “Kestrel deal”. One is “Kestrel”. One is “Kestrel – Noor”, because the rep who created it wanted everyone to know it was hers. The last is “Kestrel Q3”, from a year nobody remembers. He opens all five. Three have no notes in the last month. The quote the customer means is attached to the fourth, owned by a rep who is on holiday. By the time he finds it the customer has asked twice whether he is still there. And Oskar is the manager, the person who knows this account best. To the new rep starting next week, those five deals are five identical doors. Oskar is fictional. His search results are not. Nobody chose these names. Pipedrive’s import generates a title from the contact person or the organization when the spreadsheet has none ( [Pipedrive: importing data with spreadsheets](https://support.pipedrive.com/en/article/importing-data-into-pipedrive-with-spreadsheets)), and a rep adding a deal by hand in a hurry types the company name and moves on. “Kestrel” is what a deal ends up called when nobody asked “what is this deal?” A convention just asks it once, for everyone. ## What a deal name actually has to do Most CRM naming conventions are written for the person creating the record. A deal name has four jobs, and only one of them is for that person. It is the search key. When the customer calls, the first thing anyone does is type a word into search, and the name is what comes back. If five results look alike, search has failed, however good the rest of the record is. It is the row label in the list view. The deals list view shows one deal per row, and you choose the visible columns with the gear icon ( [Pipedrive: list view](https://support.pipedrive.com/en/article/list-view)). Owner, value, stage and close date each get a column. The title is the only one that has to tell a human what the deal is, in the width of a column, without opening it. It is the line in the report. A manager scanning the pipeline before the weekly review sees a title, a value and a stage. “Kestrel” next to 12,000 means nothing. “Kestrel / 40 licenses / Nov 2026” next to 12,000 tells her the size is plausible and the timing is the thing to ask about. And it is the handover. Reps leave, go on holiday, get reassigned. The deal outlives their memory of it, and the first thing the next person reads is the title. A good title is a one-line briefing; a bad one is a locked room. None of the four jobs is “identify the owner”. That is what the Owner field is for. “Kestrel – Noor” solved Noor’s problem and created Oskar’s. ## A deal naming format that fits in a column Three parts, in a fixed order, with a fixed separator: **Who / What / Which one** Who is the customer as the organization is named in Pipedrive, not a nickname. What is the thing they are buying, in two or three words a stranger would understand. Which one is the distinguisher: the expected close month, an order or quote number, a site, a product line. It exists so that the second deal with the same customer gets a different name without anyone having to invent one. A few deals named this way: - Kestrel / 40 licenses / Nov 2026 - Kestrel / Onboarding package / PO 4471 - Brightwater Clinics / Annual support / 2027 renewal - Hollis & Sons / Warehouse scanners / Leeds site - Hollis & Sons / Warehouse scanners / Bristol site - Tandem Freight / Fleet upgrade / Pilot The separator matters more than it looks. Pick one character and stick to it. Hyphens are a poor choice, because plenty of company names already contain one (“Smith-Jones Ltd”) and the eye loses track of where one part ends. Slashes almost never turn up in a company name, which is why we use them. Keep the whole thing short enough to read in the title column at its normal width. In practice that means about the length of the examples above. If the “What” needs a sentence, it is not a deal name, it is the first line of the deal’s notes. ![The Who / What / Which one deal name format split into three parts, with fields that stay out of the name](https://salesbond.app/wp-content/uploads/2026/10/pipedrive-deal-naming-convention-2.png) ## What does not belong in the name Anything Pipedrive already stores as a field. Stage. A deal called “Kestrel / 40 licenses / Proposal sent” is wrong the moment it moves, and nobody goes back to rename it. Stage is a list view column and a whole column in the pipeline view. In the name it is a lie waiting to happen. Price. “Kestrel 12k” freezes a number that will change twice before the deal closes, while the Value field next to it carries the the real one. Two numbers for the same deal means one of them is wrong, and the reader can’t tell which. Status words: “HOT”, “urgent”, “follow up”, “stalled”. These are opinions with a date on them, and the date is never written down. Pipedrive has a Label field for this kind of marker, and a label can be changed across many deals in one bulk edit ( [Pipedrive: list view, filter and bulk edit items](https://support.pipedrive.com/en/article/bulk-editing-and-filtering)). A word buried in a title can’t. The close date. “Kestrel Q3” was true once. Expected close date is a column, and it sorts. The month in our “Which one” slot is a distinguisher, not a promise: if the deal slips to January, the name still tells it apart from the October order, and the field carries the new date. The rep’s name. Owner is a column. So here is the test for any candidate word: if it could be a column, it is a field. The name is for the one thing no field holds, which is what the deal actually is. ## Second deals, repeat orders and renewals The convention earns its keep the second time a customer buys. A second, separate deal with the same customer usually has a different “What”, so the names already differ. “Kestrel / 40 licenses / Nov 2026” and “Kestrel / Onboarding package / PO 4471” sit next to each other in search and nobody confuses them. When the “What” is the same thing bought again, the “Which one” does the work, and it should be something the customer would recognise too: their PO number, the site, the month they asked for delivery. Not “2”, not “new”, not “again”. Repeat orders get a new deal each time rather than a reused won one, for reasons we laid out in [one deal per order in Pipedrive](https://salesbond.app/blog/repeat-orders-pipedrive-new-deal-per-order/). The naming payoff is a tidy history in search: “Brightwater Clinics / Consumables / Mar 2026”, then Jun, then Sep. The rep sees the cadence at a glance, and so does a manager who has never spoken to Brightwater. Renewals should say so. “Brightwater Clinics / Annual support / 2027 renewal” tells the reader this is not new business, which changes how everyone treats the forecast and the conversation. The year of the term being renewed is the natural distinguisher. One rule under all three: never rename a won or lost deal to make room for the new one. Closed deals are history, history keeps its name. ## Fix the old ones in one sitting A convention that only covers deals created from today on leaves Oskar’s five Kestrel deals exactly where they were. So the last step is a cleanup, and it is smaller than it looks. Before touching anything, export the deals list. The reason is the one we gave in [before you bulk-edit 150 Pipedrive deals](https://salesbond.app/blog/pipedrive-bulk-edit-safety/): the export is your copy of the old names, and it costs nothing. Then open the deals list view, show open deals only (a saved filter with the columns you want is worth setting up once; [here is how we share them](https://salesbond.app/blog/pipedrive-quick-filters-deal-list-url/)), and sort by organization so every “Kestrel” sits next to every other “Kestrel”. Make the Title, Organization, Value and Expected close date columns visible with the gear icon. Now rename each deal in place: hover over the title, click the pencil icon, type the new name ( [Pipedrive: list view](https://support.pipedrive.com/en/article/list-view)). The four visible columns give you the “What” and the “Which one” without opening the deal. Bulk edit can set the Title field for many selected deals at once, but it gives all of them the same value ( [Pipedrive: list view, filter and bulk edit items](https://support.pipedrive.com/en/article/bulk-editing-and-filtering)). Under this convention that is almost never what you want, since the “Which one” slot exists to make names differ. The pencil, one row at a time, is the tool. A hundred deals is one sitting with a coffee, not a project. Do it with the rep who owns them, because the “What” is sometimes only in thier head, and this is the conversation where it gets written down. While you are sorted by organization you will find pairs that are not two deals at all but the same opportunity entered twice. Those get merged, not renamed, and [which deal to keep as primary](https://salesbond.app/blog/pipedrive-merge-two-deals-primary-deal/) is its own small decision. You will also find organizations spelled three ways. That is the [duplicate organizations problem](https://salesbond.app/blog/duplicate-records-in-pipedrive/), and the “Who” slot can’t be consistent until the organization names are. Last, write the convention down where the team will see it: one line in your CRM rules, “Who / What / Which one”, with two of your own deals as examples. After that the only enforcement you need is the weekly pipeline review, where a deal called “Kestrel” gets asked what it is, out loud, once. ## Five doors, one label each A deal name is the cheapest field in the CRM to get right and the most expensive one to get wrong, because everyone else on the team pays for it every time they look. We build SalesBond, a sales management layer on top of the CRM a team already uses; we started with Pipedrive. Deal Health checks every open deal against more than 20 rules and tells you which deals need attention and why. It does not grade your deal names. But when it points at a deal, somebody has to find it in the list, and “Kestrel / 40 licenses / Nov 2026” is found on the first try while “Kestrel deal” is found on the fourth. [Check your CRM with SalesBond](https://salesbond.app/) if you want the list of deals that need attention this week; the names are up to you.