Short answer
DAM reference checks are structured calls with existing customers of a shortlisted vendor that test implementation time against plan, support quality, renewal pricing and daily workarounds. DAMSelection rule of thumb: run two to three calls per finalist, include at least one customer the buyer found independently of the vendor, and record every answer as dated evidence in the scoring matrix before the final decision.
What a DAM reference check proves
A DAM reference check proves how a vendor behaves after signature, which no demo or proposal can show. Demos show the platform. References show the implementation, the support desk, the renewal conversation and the workarounds users live with after two years.
Reference checks have limits. A vendor-nominated reference is a selected success story, and one customer's experience depends on its own partner, scope and team. Use references to confirm or lower scores from the demos and the proof of concept. A reference call never raises a score above the demo evidence.
Reference checks answer four questions the selection team cannot answer alone:
- Did the implementation finish on the planned date and budget, and what caused the gap.
- How does support perform on a severity-one incident.
- What happened to the price at the first renewal or the first storage tier change.
- Which workarounds do users still apply every week.
Choose the right DAM references
The right DAM references match the buyer on scale, stack and use case, and they have lived with the platform long enough to have renewed. A reference live for three months can describe the project. A reference live for two years can describe the platform, the vendor and the bill.
| Reference type | Why it matters | How to find it |
|---|---|---|
| Vendor-nominated, similar profile | Confirms the vendor delivers at the buyer's scale | Ask the vendor for two names matching scale, stack and region |
| Independent customer | Removes the vendor's selection bias | Professional network, user communities, conference speakers |
| Customer past first renewal | Reveals renewal pricing and tier changes | Ask the vendor for a customer in year three or later |
| Same PIM or creative stack | Tests the connectors the buyer will use | The Fit Map shows integration depth per PIM |
| Former customer | Explains why customers leave | Network and community groups, with discretion |
Specify the profile when requesting references: asset volume, number of users, asset types, PIM and e-commerce platforms, hosting region and industry. A vendor who offers only references from a different segment or scale gives the panel a signal in its own right.
Find independent references
Independent DAM references come from the buyer's own network, so the vendor has no say in who speaks. DAMSelection rule of thumb: at least one of the two or three calls per finalist is independent.
Four routes work in practice:
- Ask the selection team, agencies and the PIM partner who runs the platform at a comparable organisation.
- Search professional networks for DAM managers and librarians who list the platform in their profile.
- Check vendor case studies and event agendas, then contact the named customer directly.
- Ask in DAM and content operations user communities, where practitioners compare platforms openly.
Approach an independent reference with a short, specific request: who you are, which decision you face, a 30 to 45 minute call, and confidentiality for anything said. Offer to share the outcome of your selection in return. Never record a call without explicit consent.
Reference call question list
The best DAM reference questions ask for specific events and numbers, because general questions produce general praise. Send the themes ahead, work through the prompts in order, and ask for an example whenever an answer stays abstract.
| No. | Theme | Prompt |
|---|---|---|
| 1 | Context | Describe your library: asset count, asset types, storage volume and active users. |
| 2 | Context | Name the systems connected to the DAM: PIM, e-commerce, CMS and creative tools. |
| 3 | Context | Describe your role and how long you have worked with the platform. |
| 4 | Implementation | Describe the planned and the actual go-live date, and what caused the difference. |
| 5 | Implementation | Compare the implementation budget at signature with the final cost. |
| 6 | Implementation | Name who configured the platform: your team, the vendor or a partner. |
| 7 | Implementation | Describe how the metadata schema was designed and how often it has changed since go-live. |
| 8 | Implementation | Describe the migration: volume, method, duration and what was left behind. |
| 9 | Daily use | Name the workaround your users apply most often. |
| 10 | Daily use | Describe how fast users find an approved asset today compared with before. |
| 11 | Daily use | Describe how search and AI tagging perform on your own asset types. |
| 12 | Daily use | Name one task that still happens outside the DAM, and the reason. |
| 13 | Support | Describe your last severity-one incident: response time, resolution time and communication. |
| 14 | Support | Describe how the vendor handled a product change you disagreed with. |
| 15 | Support | Describe any change of account manager, ownership or product name since signature. |
| 16 | Commercials | Describe the price change at your first renewal, as a percentage if you can share it. |
| 17 | Commercials | Describe what happened when your library crossed a storage or user tier. |
| 18 | Commercials | Name any cost that surprised you after year one: AI credits, external users, environments or egress. |
| 19 | Looking back | Name one thing you would negotiate differently in the contract. |
| 20 | Looking back | Name one thing you would configure differently from day one. |
| 21 | Looking back | Say whether you would choose the platform again, and the main reason. |
Prompts 4, 16 and 19 carry the most selection value. They test the implementation plan, the five-year cost curve and the contract, the three areas where a wrong choice costs most. Use the answers to prompts 16 to 19 as input for pricing negotiation and the contract clauses checklist.
Run the DAM reference call
A DAM reference call runs best with two interviewers, a fixed agenda and 45 minutes. One interviewer asks; the other takes notes in the evidence template. Two people also reduce the risk that one listener hears only what confirms a favourite.
Practical rules for the call:
- Keep the vendor off the call and out of the scheduling thread once contact is made.
- Ask for numbers and dates before opinions.
- Repeat key answers back to confirm them: "So the go-live moved by three months because of the migration."
- Note hedges such as "it depends" or "we are working on that", and follow up with "give an example".
- Close with permission to send one follow-up question by email.
Run reference calls during the score checkpoint of the Selection Route, after the scripted demos and in parallel with the proof of concept. The panel then knows which scores need confirming and asks targeted questions.
Record answers as evidence
Record each DAM reference answer in the scoring matrix as dated evidence linked to the criterion it affects. The DAMSelection scoring model requires a dated call note for reference evidence, and a score without evidence is left blank.
Worked example: an evidence log with invented entries.
| Date | Reference | Prompt | Answer summary | Criterion | Score effect |
|---|---|---|---|---|---|
| 2026-10-02 | Independent, retail, 300,000 assets | 4 | Go-live three months late, schema redesign mid-project | Metadata and taxonomy flexibility | Confirms 3 |
| 2026-10-02 | Independent, retail, 300,000 assets | 16 | Renewal increase above the level described during the sale | Administration and total cost profile | Lowers 4 to 3 |
| 2026-10-05 | Vendor-nominated, manufacturer | 13 | Severity-one response within the contracted time | Security, hosting and compliance | Confirms 4 |
Store call notes outside the vendor's reach, and anonymise them in the final report. When two references contradict each other or the demo, put the point to the vendor in writing and record the answer. The scoring matrix guide explains how reference evidence interacts with demo evidence.
Warning signs in DAM reference calls
Some reference answers predict the same problems as demo red flags, and the panel records them as negative evidence. Watch for six signs:
- The vendor offers only references live for less than a year.
- The reference cannot name the renewal increase or refers all commercial questions to procurement.
- The reference runs a much smaller library or a different use case.
- Core configuration still depends on the implementation partner after go-live.
- The reference describes a major workaround as "normal for DAM".
- A vendor representative asks to join the call.
One warning sign rarely decides a selection. Two or more across independent references justify a direct question to the vendor and a lower score on the affected criterion. Compare the pattern with the demo red flags recorded earlier.
Frequently asked
What questions should I ask a software reference?
Ask for events and numbers: planned versus actual go-live, implementation budget versus final cost, the last severity-one incident, the price change at first renewal, the most common workaround and what the customer would negotiate differently. Ask for an example whenever an answer stays general, because general questions produce general praise.
How many reference checks are enough for a DAM selection?
Two to three reference calls per finalist give enough evidence for a DAM selection under the DAMSelection rule of thumb. At least one call should be with a customer the buyer found independently. Run calls only for the final two or three vendors, after the scripted demos.
How do I find references the vendor did not provide?
Use the selection team's network, agencies and PIM partners, professional network searches for DAM managers who list the platform, named customers in vendor case studies and event agendas, and DAM user communities. Request a short confidential call and offer to share your selection outcome in return.
When should reference checks happen in a DAM selection?
Reference checks belong in the score checkpoint, after the scripted demos and in parallel with the proof of concept. At that stage the panel knows which scores need confirming and can ask targeted questions. Calls earlier in the process produce generic answers and waste the references' time.
Can a good reference call raise a vendor's score?
A reference call confirms or lowers a score and never raises it above the demo evidence. References describe one customer's experience with its own partner and scope. A demo or proof of concept shows the platform on the buyer's own scenario, which carries more weight.