UserGems’ new signal, Champion Referrals, is turning one month old! Our sales and CS teams collaborated on two playbooks, generating 10 demos from Champion Referrals! Of those, we’re in the final sales stages with a couple of opportunities.

We want to share with you what we learned from using this new signal during the last four weeks so you can achieve similar results. Follow along to learn how to set up your own best-in-class champion referral motion! 

What is the Champion Referral signal?

Champion Referrals give teams a new way to turn referrals into a scalable source of pipeline. 

Champion Referrals offer a warm and credible path into your target accounts, which makes it much easier to book meetings and accelerate opportunities.

Once you define your target account list (e.g. ABM accounts, high-intent accounts, etc.), Champion Referrals:

• Identifies if any of your Customers used to work at those accounts
• Suggests persona-matching prospects at those accounts who might have worked with your Customers (Their employment time overlap)
• Sends a Slack or Email alert to your SDR/AE with the information and a suggested email blurb that they can send to the Customer.

UserGems Champion Referral Playbooks

The UserGems team has tried several outreach combinations using this new signal. We’ve figured out that there are two main playbooks that work the best to drive booked meetings.

Here are the two playbooks:

1. Targeted Champion Referrals - This playbook relies on a highly personalized workflow for high-value champions
2. Champion Referrals at Scale - This playbook automates the referral process so that referrals where there is less or a relationship can be requested at scale

‍

Here’s how we execute these two playbooks at UserGems!

Champion Referrals Playbook #1: Targeted Champion Referrals

The Targeted Champion Referrals playbook is for your product's most high-value champions. These are users who often have a relationship with their CSM and act as the main point of contact between your company and theirs.

Step 1: Defining the audience

At UserGems, our audience for this playbook are contacts our CS team has specifically denoted as ‘Champions’ in Salesforce. If you don’t have this field in your CRM, you could define your Champions by pulling in all Closed Won Opp contacts. Not every one of these contacts will have a relationship with their CSM, but it’ll cast a wider net. 🎣

Step 2: Setting up the workflow

When we set up our Champion Referrals workflow for this playbook, we included the following criteria:

• Run workflow when current champion recently worked at target account (we limit to the last 2 years)
• Only run the workflow on a contact 1x every 6 months
• Set a maximum of 1 referral request per account per week
• Set a maximum of 2 referral requests total per day per CSM

We don’t want to exhaust the goodwill of our customers, but we do want to take advantage of their referrals. It’s a balancing act. After all, on average, some 92% of customers say they would give referrals!

Step 3: Adding an action

The goal of this playbook is to identify which of our current champions have worked at a target account and then ask them for a referral. It’s a little more complicated than simply sending them an automated email, however, because they already have a relationship with someone on our CS team. We don’t want to step on our CSMs’ toes, so we need to get them involved.

The action for this workflow uses one of our custom workflow actions: Group Slack DMs

When the workflow identifies a champion whose work history matches a Target Account, we set it up so that a Slack message containing relevant information is sent to the:

• Customer’s CSM
• Target Account (the customer’s past account) SDR

Here’s an example of an automatic Slack message. It contains relevant information for the CSM to use when contacting the Champion to ask for a referral.

The ‘Send email’ link in the Slack message opens to a pre-filled email that the CSM can send to the champion. This action automatically cc’s the SDR on this email to eliminate extra steps for CS and enable the SRD to follow up 1 - 2 times as a reminder.

Results

We’ve seen a response rate of over 80% to this playbook! The response rate is likely so high because these contacts have a personal relationship with our CSMs, though, and it’s just polite. 

When a Champion follows up on a referral request, even if it’s to decline the offer, they often include valuable information. Champions might include insights about acquisitions, reorgs, new company priorities, who they might want to contact but don’t have a relationship with, etc. SDRs can use these insights to prospect into the account more strategically so it’s still a win in our book!

Champion Referrals Playbook #2: Champion Referrals at Scale

The second Champion Referrals playbook that we run at UserGems helps us automate and scale the entire process. It works in the background so that our CSMs don’t need to be involved and our SDRs can generate more meetings.

Step 1: Defining the audience

The audience for this playbook is all the other users and evaluators of your product who aren’t your main points of contact. They might love your product and be valuable voices, but they are unlikely to have a personal relationship with your CSMs. This group of contacts is much larger than your main champion list and can benefit from even more automation.

Step 2: Setting up the workflow

This workflow handles a larger number of contacts, so it’s important to establish rules and limits to keep referral requests in check.

These are our entry criteria for this workflow:

• Only run the workflow when the current user has worked at a target account in the last 2 years
• Only run the workflow on a contact 1x every 6 months
• Set a maximum of 1 referral request per account per week
• Set a maximum of 10 referral requests per SDR per week 

We set a maximum number of requests per account because we don’t want to ask too many people from the same account for referrals at the same time. This can result in crossed wires and cause confusion for our champions and our SDRs.

The maximum number of requests per SDR is set based on our sales teams’ bandwidth and the limits of your sequencing tools. If your team is hungry for as many leads as possible, try increasing this limit! Just remember that you don’t want to overload your reps with outbound initiatives. Too many requests and your efforts just become noise.

Step 3: Adding an action

The signal-based action we attach to this workflow is an automated email via Outreach, our sales engagement platform.

When the workflow identifies a (non-champion) user who has worked at a Target or ICP account, it automatically adds them to a sequence in Outreach. This sequence emails the contact three times from the SDR. Twice within a couple of days, and once again after 30 days if there’s been no reply.

‍

Tip: For C-Suite prospects, try changing the “From” field in your email automation platform to your CEO, COO, or CMO’s contact for a better response rate!

‍

Here are some best practices we’ve discovered when sending these emails!

Mention the CSM’s name in the email

Use a custom field in your sequencing tool to pull it from your CRM.

Offer an incentive: this is required to get results

Try offering a monetary incentive to both the referrer and the referee. Try a $50-$100 Visa, Amazon, or DoorDash gift card.

Establish a referral program. The UserGems referral program offers referrers 10% of ARR on Closed-Won deals in the first year. Check out our referral program for inspiration: https://www.usergems.com/referral 

Results

This scalable playbook has resulted in about the same number of meetings booked as the manual Targeted Champion playbook! Of course, the overall response rate is lower without the established CSM relationship, but it’s working to drive opportunities.

We recommend testing both of these Champion Referrals playbooks to see what works best for your organization, as everyone’s customer base is different. 

If you have questions about setting up your own best-in-class champion referral motion, let's chat!