# Asking customers for referrals: a small-team routine you can track in Pipedrive

https://salesbond.app/blog/ask-customers-referrals-pipedrive/
Published: 2026-10-05 · Updated: 2026-10-26

Ask a customer for a referral right after they have seen value: a result they mention on a call, a renewal, a thank-you email. Name the kind of company you want to meet, and send them a message they can forward without editing. Then record it. Put the referrer in a field on the new deal, so you can count customer referrals later and tell the referrer how it ended. By a customer referral we mean a paying customer introducing you to a peer, not a partner or affiliate program. That is the routine. Below is how we run it in Pipedrive with a team of five, and where it breaks when one of the three records is missing.

## Why nobody asks, and why signing day is usually too early

Picture a five-person team selling scheduling software to dental practices. Every rep agrees that customer referrals are the best deals they get. Every rep also, when you look at the last quarter, asked for exactly none. Not out of laziness. Asking feels like requesting a favor from someone you have not delivered anything to yet, and that feeling is right more often than the scripts admit.

The usual advice is to ask right after the signature, while the customer is happy. The trouble is what “happy” means on signing day. The customer has paid and received a login. They have not seen a single appointment booked through the the tool, their front desk is still complaining, and they cannot honestly tell a peer that it works. The Follow Up’s three rules start with asking while the moment is warm, and LeadIQ’s guide names two windows: right after closing, and months later, once the customer sees results ( [The Follow Up](https://www.jointhefollowup.com/p/3-rules-of-asking-for-a-referral-in-sales), [LeadIQ](https://leadiq.com/blog/how-to-ask-for-referrals-in-b2b-sales)). We take the second window and skip the first. A referral is the customer vouching for you, and people can only vouch for what they have lived through.

The second reason nobody asks is that nothing in the CRM reminds them. The ask lives in one rep’s personality. When that rep leaves, the referrals leave with her, and the manager finds out at the quarterly review that “referral” is now a column of zeros. A better script won’t fix that. Treating the ask as a CRM event will: a trigger, a record and a follow-up, the same way you treat a proposal.

## Three signals that say “ask now”

We do not ask on a schedule, because a date knows nothing about the customer. We ask when one of these shows up in the account:

- The customer names a result without being prompted. “We stopped double-booking” on a check-in call counts, even when it’s said in passing.
- The customer renews or reorders. They have just made the decision a second time, which is exactly what a referral asks them to say out loud to someone else. Keep in mind that [a reference call is a different ask from a referral](https://salesbond.app/blog/customer-reference-program-pipedrive/): the customer talks to a prospect you already have. How we run renewals is [a separate routine](https://salesbond.app/blog/customer-renewal-process-pipedrive/); here the renewal is only the cue.
- A thank-you arrives in writing, an email or a chat message that names the rep.

The signal has to become a record the same day, or it evaporates. The rep who hears “we stopped double-booking” creates an activity on that person in Pipedrive. We use a Task, subject “Ask for referral”, due within the week. Not a calendar reminder in ninety days, and not a note. Once it’s an activity it has a due date and an owner, so it comes up in the Monday review and gets marked done with a line about what the customer said. A note is read once and never again.

This is also where tooling can help with timing, so a disclosure first: we build SalesBond, a sales management layer on top of the CRM a team already uses; we started with Pipedrive. Its Customer Health works from the won deals already in the CRM. Every customer who buys repeatedly has a buying cycle, and the time since the last purchase puts them on track, overdue or leaving, with a purchase soon flag when an on-track customer’s next order is close. We ask the on-track and purchase-soon customers first. An overdue customer needs a different call before any ask, the one that finds out why they went quiet (we wrote up [how we find inactive customers in Pipedrive](https://salesbond.app/blog/pipedrive-inactive-customers-accounts-filter/)). Ask them for an introduction before that call and you will get a polite no.

## How to ask a customer for a referral: one name, one forwardable email

“Do you know anyone who might be interested?” gets a kind “I’ll think about it” and nothing else. It asks the customer to search their whole contact list. “Who do you know running a practice with two or more locations that still books by phone?” gets a name, because the customer only has to match one picture. Describe the company, not the person, and make it the same picture you sell to best. If you have ever written down what your closed-won deals have in common, you already have it.

Then take the work off the customer, which is also the second of The Follow Up’s rules. Most referrals die between “sure, I’ll introduce you” and the actual introduction, because writing that email is a chore and alot of customers never get around to it. So the rep writes it for them. Ours looks roughly like this:

> Subject: Intro to [our company]?
>
> Hi [name], we have been using [product] for booking since March and it fixed the double-booking problem I mentioned. [Rep] is the person we worked with. Happy to introduce you if useful, or just reply here and I will connect you two.

Three sentences, no pricing, no feature list, nothing to edit except the names. The rep sends it with one line on top: “If it’s easier, just forward this.” When the customer replies “sent”, the ask activity is marked done, and the rest of this article starts.

## The customer said yes. What goes into Pipedrive

Three records, and the first one is a field you create once.

Open the account menu, go to Personal preferences > Data fields, choose lead/deal and add a custom field called **Referred by**, field type Person ( [Pipedrive: custom fields](https://support.pipedrive.com/en/article/custom-fields)). Pipedrive describes that type as a way to “tag a person from your Pipedrive database”. The Organization type does the same for “an organization from your Pipedrive database” ( [Pipedrive: what types of custom fields are there](https://support.pipedrive.com/en/article/what-types-of-custom-fields-are-there)), so use it if your referrers are companies rather than a contact you know by name. We prefer Person, because the thank-you at the end goes to a person. A field created for deals also appears on leads, with the same name, and custom fields can trigger automations and feed custom Insights reports (same custom fields article). What Insights lets you build on a custom field depends on your plan, so check yours before you promise the manager a chart.

Why not a text field? Because a text field gives you “Dana”, “Dana K.” and “dana@northdental” as three referrers who are one person. A Person field points at one record with one spelling, and the filter “Referred by is Dana Kowalski” returns every deal she ever sent you. One catch from the field types page: if you type a name that doesn’t exist yet, Pipedrive creates a new contact, so pick from the list instead of typing fast. Pipedrive’s own article on referral partners suggests the same structure, a custom field on the deal for the referral source that you can filter by later ( [Pipedrive: referral partner](https://www.pipedrive.com/en/blog/referral-partner)). We just point the field at a customer instead of a partner.

![Three deal and person records linked by a Referred by Person field and a Referrer told date](https://salesbond.app/wp-content/uploads/2026/10/customer-referrals-pipedrive-small-team-2.png)

The second record is the deal itself. We skip the leads inbox for these: an introduction from a paying customer is about as warm as a lead gets, so it opens as a deal on day one, the same call we make in [leads vs deals](https://salesbond.app/blog/pipedrive-leads-vs-deals/). Set **Referred by** to the referrer and the source channel to Referral from a customer. The two fields answer different questions. Source channel says which door the deal came through, and we keep that list to five or six values, as described in [how we capture lead source from web forms](https://salesbond.app/blog/pipedrive-lead-source-web-forms/). Referred by says who opened the door. Next quarter you will ask “how many referral deals did we win” and “who sends us the ones that close”, and those are two different reports.

The third record is a date field on the deal, **Referrer told**, empty until the rep has written back to the referrer with the outcome. It stays empty while the deal is open. We’ll come back to it, because that empty date is the point of the whole routine.

That is one custom field plus one date, not a referral module, and it should stay that way: a referral program is a classic excuse to add a field for every idea. Partners who send you clients are a different case, with their own fields and payout rule: [referral partner deals](https://salesbond.app/blog/referral-partner-deals-pipedrive/).

If those partners are many and your CRM is Salesforce, see a [partner program in Salesforce without a PRM](https://salesbond.app/blog/partner-program-salesforce-without-prm/).

## Whose deal is it

The argument starts the day the first referral lands. Marcus owns North Dental. Dana from North Dental introduces South Dental, which sits in Lena’s territory. Who owns the deal, and who gets credit for the ask?

Our rule: the rep who got the referral takes the first call and owns the deal, unless the team has a written territory rule that says otherwise. The owner is set before that first call, not after the deal is won. The referral came through a relationship, and the referrer will ask about it the person who holds that relationship. Lena can still own South Dental’s renewal later; that is a handoff, and we have a [closed-won handoff routine](https://salesbond.app/blog/closed-won-handoff-pipedrive/) for it.

On rewards we won’t give you a number, because we don’t have one with a source behind it. If you reward anything, reward the recorded ask that turned into an introduction, not only the close. A rep controls whether she asks, she does not control whether South Dental buys.

## Counting referral deals without fooling yourself

The filter is the easy part. Deals where **Referred by** is not empty, created in the last twelve months, grouped by status. Save it, share it with the team, and its one click from then on.

The win rate comparison is where people get carried away. In Insights, build two cuts of the same deals report: won and lost deals with Referred by filled, and the same with it empty. Use one win rate definition for both (ours is won divided by won plus lost in the period, open deals left out), or the comparison means nothing.

Then read the counts before the percentages. A team of five might see a dozen referred deals in a year. Twelve deals with eight won is not “a 67% win rate on referrals”. It is eight deals, and one more loss moves the figure by several points. Read it as a list sorted by referrer, and ask what the list can actually answer: which customers have sent us more than one introduction, which referrals went nowhere, and why. The percentage gets interesting after a couple of years, once the sample can carry it. Until then, the count is the number that goes into the quarterly review.

## Tell the referrer how it ended, even when it ended badly

This is the part everyone skips. The referred deal is won, the rep is already onboarding South Dental, and Dana, who made the introduction, hears nothing. Or the deal is lost, the rep is slightly embarrassed, and Dana hears nothing either. Six months later the rep asks Dana for another name and wonders why the answer is lukewarm. She took a small risk with her own reputation. Silence tells her nobody noticed.

So the referrer hears the outcome in every case, and the rep writes it, not the manager. Won: thank her, say when South Dental goes live, ask for nothing. Lost: thank her, say it did not work out this time and that it is no reflection on her, ask for nothing. Two or three sentences each. The day the message goes out, the rep fills **Referrer told** on the deal. That date exists so the manager can run one filter once a month: deals won or lost, Referred by not empty, Referrer told empty. Whatever comes back is the team’s open debt to its customers. In our experience it is never zero the first month you run it.

Start this week with the field. Add Referred by as a Person field and Referrer told as a date, then go through last quarter’s won deals asking who, if anyone, introduced them. You will probably find two or three referrers nobody thanked. Thank them. Then wait for the next “we stopped double-booking” and create the activity.

And if you want to see which of your repeat customers are on track and which are overdue before you pick who to ask, [check your CRM with SalesBond](https://salesbond.app/).