Short answer
The DAM shortlist sprint takes a buyer from content audit to a scored shortlist of three DAM vendors in six weeks. PIMvendors delivers the audit, a prioritised requirements set, a draft metadata schema, scripted demo scenarios, two demo rounds and a scoring report the selection team can defend to its board and to procurement.
What the sprint delivers
The DAM shortlist sprint produces nine deliverables, each mapped to a checkpoint of the DAMSelection selection route.
| Deliverable | Content | Checkpoint |
|---|---|---|
| Content audit report | Current repositories, asset types, volumes, duplication and gaps | 1 Map |
| Stakeholder map | Personas, decision rights and adoption risks | 1 Map |
| Prioritised requirements | Must, should and could requirements per domain | 2 Define |
| Draft metadata schema | Fields, vocabularies, mandatory rules and the PIM link | 2 Define |
| Longlist filter | Each excluded vendor with the requirement it failed | 4 Shortlist |
| Scripted demo scenarios | Scripts, asset sample and scoring sheet per scenario | 5 Test |
| Round 1 scores | Ratings with evidence from the first demo round | 6 Score |
| Round 2 scores and reference notes | Hands-on ratings and dated reference call notes | 6 Score |
| Shortlist report | Three vendors, scores, risks and open contract questions | 6 Score |
The sprint also supplies cost inputs for the DAM business case. Every rating in the report links to its evidence.
Weeks 1 and 2: audit, requirements and metadata
The first two weeks of the sprint fix what the DAM must hold and how people will find it.
- Interviews with each persona group: DAM manager, brand, creative, e-commerce, IT, legal and procurement.
- A content audit of current repositories, based on a sample the team pulls with PIMvendors.
- Requirements captured with the DAM Requirements Builder and prioritised in a workshop.
- A draft metadata schema built with the Metadata Model Builder.
- An integration inventory covering PIM, CMS, e-commerce, creative tools and identity.
The decision owner signs off the requirements and the schema draft at the end of week 2. Scripts in week 3 depend on that sign-off.
Weeks 3 and 4: longlist, scripts and first demos
Weeks 3 and 4 of the sprint reduce the market to the vendors that pass every must-have requirement, then test them on scripts.
- Filter the 30 DAMSelection vendors on hard requirements such as hosting region, PIM connector and pricing archetype, following the shortlisting method.
- Write scenario scripts from the requirements, using the scripted DAM demo scenarios method.
- Send each vendor the same scripts and the same asset sample, with the same preparation time.
- Run round 1: each vendor demonstrates the scripts on the buyer's assets, in the same order and time box.
- Score round 1 with evidence, and select the vendors for round 2.
PIMvendors chairs every demo and stops any detour into features outside the script.
Weeks 5 and 6: deep demos, scoring and the shortlist report
Weeks 5 and 6 of the sprint test the remaining vendors hands-on and turn the evidence into a shortlist of three.
- Round 2: operators from the buyer's team complete tasks themselves, with the vendor watching.
- Integration sessions: each vendor shows the API calls and connector behaviour for the PIM link.
- A pricing request in one standard format, covering licence, storage, egress and AI credits over five years.
- Reference checks with customers of a similar segment and size.
- Final scoring and the shortlist report, presented to the decision owner.
What the buyer team commits
The DAM shortlist sprint needs a small, available team on the buyer side, and the written scope names each person.
| Role | Contribution |
|---|---|
| Decision owner | Signs off requirements, schema and the shortlist |
| DAM lead or librarian | Owns the asset sample and the metadata decisions |
| IT or enterprise architect | Owns integration and security requirements |
| Business users | Join demos and complete round 2 tasks |
| Procurement | Joins the pricing request and the contract questions |
When the sprint fits
The DAM shortlist sprint fits a buyer with a sponsor, a budget window and a DAM decision that does not depend on another open selection.
| Situation | Route |
|---|---|
| First DAM or replacement, PIM stable | Shortlist sprint |
| PIM selection open at the same time | Combined PIM and DAM selection |
| Public tender required | Sprint outputs feed the tender documents |
| Shortlist exists, contract pending | Go straight to checkpoint 7, Sign |
For tenders, the guide on RFI or RFP for DAM selection explains where scripted demos fit.
After the sprint
The DAM shortlist sprint ends with three vendors, and the next steps are a proof of concept or contract negotiation.
A proof of concept fits when two vendors score close together or one risk needs testing at scale. Contract work uses the requirements and scores from the sprint as the reference. The parent advisory page describes the full engagement range.
Frequently asked
How long does a DAM selection take?
A focused DAM selection reaches a scored shortlist in six weeks with the PIMvendors sprint, when the buyer team is available and the requirements owner signs off on time. Contract negotiation and any proof of concept follow. Delays usually come from late requirement sign-off or missing asset samples.
How many vendors should be on a DAM shortlist?
The DAM shortlist sprint ends with three vendors. Three keeps real price competition in the contract stage and leaves enough depth to test each vendor hands-on. More vendors dilute demo preparation on both sides, and fewer vendors weaken the buyer's negotiating position.
What do we need to prepare before the DAM sprint?
Prepare a named decision owner, a DAM lead, an IT contact and a sample of real assets per scenario, including difficult files. Exports from current repositories and the PIM help the audit. The written scope lists everything PIMvendors needs in week 1, so preparation starts after the scoping call.
Can the sprint replace an RFP?
The DAM shortlist sprint can feed an RFP or replace it, depending on procurement rules. Organisations bound to a public tender use the sprint outputs as tender documents. Private organisations often skip the long RFP and use scripted demos and the scoring report as the evidence base.
What happens if no vendor passes the longlist filter?
If no vendor passes every must-have requirement, the selection team reviews the requirements before any demo. Some must-haves turn out to be should-haves, and others point to an integration or a second system. The sprint report records the decision and the reason.