What a customer reference library is, and why a spreadsheet stops working
Most reference programs start as a spreadsheet and a handful of people who remember which customers said yes. That works while the list is short. It breaks when a sales rep needs a reference this week, in a specific industry, for a specific product, and the person who knows the answer is on vacation.
A customer reference library is the organized record of every customer who has agreed to act as a reference: who they are, what their story is, what they are willing to do, and whether they have approved how you present them. It is the foundation of a reference program, because every other activity (matching, requests, rewards, reporting) depends on that record being accurate.
The spreadsheet has three weaknesses. It goes stale, because nobody owns the updates. It hides consent, because a row cannot tell you whether the customer agreed to a call or only to a logo. And it concentrates requests on the few names everyone remembers.
How the library works in lyynx
Two levels: companies and contacts
lyynx separates the account from the person. A reference company holds the account details: name, logo, industry, company size, location, relationship start date, products used, a use case summary, key results and challenges solved.
Under each company sit one or more reference contacts. These are the individual advocates. Each contact has a name and title, a story headline and summary, a testimonial, a case study, success metrics, answers to common questions, and tags.
The split matters in practice. One account can have a finance leader who will talk about cost and an operations lead who will talk about rollout. They have different stories and different limits, and prospects can browse by company or by person.
Tags, filters and Find a Reference
Tags have colors so they are easy to scan. You can filter the library by industry, size, location, product and tags. For the sales team there is a Find a Reference search with quick filters such as "willing to take a call" and "has a testimonial", so a rep can get to a shortlist without learning how the library is organized.
Tags only help if people agree on them. If you are starting from nothing, read how to build a reference taxonomy that sales actually uses before you create your first twenty.
| Reference | Industry | Tags | Privacy | Status |
|---|---|---|---|---|
| Example Health (Alex Example, VP Operations) | Healthcare | Enterprise Migration | Approval required | Approved |
| Sample Logistics (Sam Sample, IT Director) | Logistics | Mid-market | Public | Approved |
| Placeholder Bank (Jordan Placeholder, Head of Risk) | Financial services | Enterprise Compliance | Private | Pending approval |
| Fictional Foods (Riley Demo, COO) | Food and beverage | Migration | Approval required | Draft |
Assets and video
PDFs, decks and documents can be attached to references, and so can videos from your company video library. A rep who finds the right reference also finds the case study and the recording that go with it.
Approval status on every contact
Each reference contact moves through an approval workflow: draft, pending approval, approved, rejected or revoked. The status answers the question a spreadsheet cannot, which is whether this person has agreed to be shown this way.
Import and recovery
You do not have to retype an existing list. Download the customer reference library template, fill it in, and import it as a CSV file. If someone deletes a reference or an asset by mistake, it goes to the trash and can be restored.
How the library respects the advocate
The profile belongs to the person it describes. You can invite a reference to the platform, and once an advocate logs in they own their own profile fields. Your team can no longer edit those fields and must ask the advocate for an update.
That sounds like a restriction on the vendor. In practice it is what keeps the library trustworthy. A title, a quote or a result that the advocate wrote or approved is one you can share with confidence, and the advocate knows nothing will appear under their name that they did not see first.
The same idea runs through the rest of the record. Each reference carries a privacy level and display settings (see reference privacy controls), and an advocate can revoke consent, which takes the reference out of view until it is approved again.
Who uses it
- Sales uses Find a Reference to get a shortlist that fits the deal, without asking around.
- Customer marketing owns the structure: tags, stories, assets and approvals.
- Customer success adds new references as accounts mature and flags the ones that need a rest.
- Advocates keep their own profile current and decide what is shown.
Team roles keep this orderly. Company admins have full access, and members get granular permissions from templates such as Sales Rep, Content Manager and Read-Only.
Practical tips
- Start with the contacts, not the logos. A reference is a person who has agreed to something. Add the company, then add the individual and what they said yes to.
- Keep the tag list short. If two tags mean nearly the same thing, reps will pick neither. Merge them.
- Write the use case summary for a rep in a hurry. Two or three sentences: the problem, what changed, the result the customer is happy to repeat.
- Invite advocates early. A profile the advocate maintains stays accurate longer than one your team guesses at.
- Treat draft as a real state. Do not move a contact to approved because the account manager "is sure it is fine". Ask.
- Review on a schedule. People change jobs and products change names. A quarterly pass through the library catches most of it.