Customer reference programs

A customer reference program is a working system for matching a customer's experience to a buying situation. Build it from the decisions your team needs to support, then keep each customer usable when a request arrives. The part teams miss is that a list of willing names fails to do the program's job. The database of reference accounts and contacts is the foundation.¹ Everything else builds on a pool of happy customers.² Build the operating path around fit, preparation, and follow-through.

Set the job

Start with the outcome the program must support. This keeps the customer pool tied to work the team can act on.

Begin by becoming familiar with the company's growth goals.³ Use those goals to decide which customer conversations the team needs to support. Ask: Which buying situation needs a peer conversation? What would a buyer need to hear from someone who has lived through it? When should the customer enter the sales process?

For sales, an advocacy program should address new-business referrals and involve advocates in the reference process.⁴ Customer reference programs are likely to be critical to most new-business sales cycles.⁵ A company may need them less when contract value is small and the buyer faces little pressure to make the right decision.⁶

Write the answers into a short request brief. Include the customer situation, the experience the buyer needs to hear, and the form of participation that will help. Move on when the team can describe the request without relying on a particular person's memory.

Build the pool

Once the job is clear, find the customers and contacts who can carry those conversations. Build the pool around the stories buyers need, then widen the perspectives available.

Inventory current customer reference information.⁷ For each account, record the contact, the experience they can discuss, and the situations where their perspective fits. Program members are highly satisfied and loyal customers who can tell the stories the sales team needs today.⁸

A larger advocate pool provides more perspectives for customer references.⁹ Use that principle when you look for coverage. A customer who can speak about implementation may fit a different request from one who can explain business results or the experience of working with the solution.

A customer success participant can explain what the implementation process looks like.¹⁰ That participant can also discuss their experience implementing the solution for other customers.¹¹ Ask: What part of the process can this customer explain clearly? Which question would they answer from direct experience? Move on when each useful record has a clear story attached to it.

Make the pool usable

Names become useful when the team can find the right person, request the right format, and see what happened after the interaction. Put that path in place before requests pile up.

At minimum, the infrastructure includes a field in a CRM or customer success platform to designate and tier advocates, a queue that Marketing and Sales can use for reference or case study requests, an agreed service-level agreement for how quickly requests are fulfilled, and a feedback loop that records usage and outcomes.¹²

Set the routing rule around the request, not around who happens to know a customer. Tag each record by the story, buyer situation, and participation format it can support. A request should tell the team where to look and give the customer a clear reason for being contacted.

Reference activities can include reference calls, case studies, testimonials, peer networking, and event participation.¹³ Choose the format that gives the buyer the clearest answer while keeping the customer's effort reasonable. Move on when a request can travel from intake to customer contact without a private workaround.

Run each request

Treat a reference request as a match and a handoff. The customer needs enough context to speak with confidence, and the buyer needs a conversation that answers the risk in front of them.

Give the customer the buyer's situation, the subject of the conversation, and the expected format before making the introduction. Give the buyer a clear reason for the connection and let the customer describe the experience in their own words.

A person who benefited from the solution can walk through their process step by step.¹⁴ That gives the buyer a process account to examine. Give Validators ways to communicate how they benefit from choosing the solution.¹⁵

A highly enthusiastic client who is willing to speak directly with prospects can be introduced through a separate email.¹⁶ A customer reference can help sell a deal the sales team is trying to close.¹⁷ Move on after the handoff is complete and the next action is clear to the people involved.

Review and maintain

Close the loop after every use. The record should become more useful each time a customer helps.

Keep relationships with previous customers active and use them as references.¹⁸ After an interaction, update the record with what the customer covered, which request it served, and whether the handoff produced the intended outcome. Use those updates to find gaps in coverage and remove contacts who no longer fit the program.

Review the pool when the company's growth goals or sales situations change. A customer who fits one request may be a poor match for another, so keep the story and the request type visible. The program is ready to scale when the team can fulfill demand without repeatedly leaning on the same customer.

What not to do

Keep these failure modes visible when the program starts taking requests.

• Do not launch on instinct alone. Customer reference programs can falter without appropriate considerations and principles.¹⁹
• Do not spread effort evenly across every program element. A reference program has many considerations, and correct prioritization makes the build more manageable and gives it real potential for success.^{20, 21}
• Do not rely on a reference tab where half the names are unresponsive and the same two customers receive every call.²²
• Do not burn out the few customers who are willing to help and fall back on case study PDFs that buyers do not read.²³
• Do not let sales representatives contact personal connections at random times without preparing the customer.²⁴

Turn current customer information into a maintained pool and attach each customer to a story they can explain. Then use the request path to prepare each handoff and capture the result.