What a reference library holds
A reference library has two kinds of record. The first describes the customer company: industry, size, location, how long they have been a customer, which products they use and what they use them for. The second describes each person at that company who has agreed to take part: their role, their story, what they are willing to do and how they prefer to be contacted.
Around those records sit the supporting materials (testimonials, case studies, video) and the status information: whether consent has been given, when it was last confirmed and how recently the person was asked for something.
Why it matters
Without a library, reference knowledge lives in individual heads and inboxes. That works for a small team and fails as soon as a salesperson needs a reference nobody nearby happens to know. A library turns scattered knowledge into something anyone on the team can search, and it makes it possible to see who is being overused.
An example
A rep needs a healthcare customer who is willing to take a call. In the library, the rep filters by industry and willingness and finds Example Health, with Jordan Placeholder listed as the contact, an approved testimonial and a note that Jordan prefers requests to be approved first.
Common mistakes
- Recording only the company. The reference is lost when the one person who knew the contact leaves.
- Having no field for consent or for the date it was last confirmed.
- Building a spreadsheet nobody maintains, which sales stops trusting after the first out-of-date entry.
- Using free-text categories, so the same industry appears under several spellings and filters miss records.
A spreadsheet is a reasonable place to start. The customer reference library template has the columns most teams need. When the list outgrows a spreadsheet, a purpose-built reference library adds search, approval and privacy settings.