Short answer
DAMSelection evaluates DAM vendors in four stages: it classifies each of the 30 tracked vendors into one of five segments, verifies every Passport fact against a dated primary source, scores vendors only through a public scenario model with published weights, and corrects errors through a public form. Facts, DAMSelection assessments and estimates carry separate labels on every page.
How the DAMSelection method works
The DAMSelection method runs in four stages, and each stage leaves a dated record a reader can trace.
- Classify: every vendor sits in one of five segments, explained in the guide to types of DAM systems.
- Verify: every Passport fact links to a primary source and carries a verification date.
- Score: ratings come only from the public scoring model, with scenario weights published.
- Correct: vendors and readers can challenge any fact through the corrections process.
No stage accepts payment, and no stage can be skipped for a vendor. The same four stages apply to all 30 vendors in the vendor directory, whatever their size or segment.
Research sources
DAMSelection ranks sources in three tiers, and only the first two tiers can support a fact.
| Tier | Source types | Use on DAMSelection |
|---|---|---|
| 1. Primary | Vendor documentation, trust centres, certificates, official press releases, EUR-Lex | Supports a Fact |
| 2. Independent primary | Analyst report pages, standards bodies such as IPTC, C2PA and W3C, conference programmes | Supports a Fact about what that body published |
| 3. Secondary | Review sites, news write-ups, blog posts, forum threads | Leads for research only |
Vendor press releases count as primary sources for what a vendor announced. Figures in a press release carry the label "company-reported", because no third party has checked them. Secondary sources never decide a score or a Passport field.
Verification
DAMSelection verifies each Passport field against a primary source and stores the source URL and the date next to the value.
The Passport holds 11 fields per vendor.
- Vendor legal entity, parent company, headquarters and year founded
- Deployment model, hosting regions and data residency options
- Security certifications
- Pricing archetype
- Native PIM connectors and native creative tool connectors
A field without a primary source shows "Not verified" and carries no DAMSelection claim. Every profile is re-verified each quarter. An acquisition, merger or product rename triggers an immediate re-check of the profile and the DAM Market Map. When two primary sources conflict, the more recent one applies and the editor records the conflict.
Scoring
DAMSelection scores vendors only through the public scoring model: named buyer scenarios, 12 fixed criteria, a 0 to 5 scale and weights that sum to 100.
Evidence comes from three places: scripted demos on buyer-style assets, vendor documentation and dated reference calls. The scripts follow the method in scripted DAM demo scenarios, so every vendor faces the same tasks in the same order. A rating without evidence stays blank. Scenario scores show "Scoring pending" until the scripted demo round for that scenario is complete.
Claim labels
DAMSelection marks the status of every claim in plain words, so a reader can see what is sourced and what is opinion.
| Label | Meaning | Where it appears |
|---|---|---|
| Fact | Sourced to a primary source listed in the page's Sources | Passport fields, Vendor Pulse items, regulatory dates |
| DAMSelection assessment | An opinion from the scoring model or from PIMvendors selection practice | Strengths, watch-outs, positions on method |
| DAMSelection rule of thumb | A practical heuristic from PIMvendors projects | Planning guides and checklists |
| Estimate | A modelled range with its assumptions stated | Output of the Five-year DAM TCO Calculator |
| Worked example | Illustrative numbers, labelled as such | Guides that show a calculation |
An unlabelled statement in a guide is general practice knowledge. Any number on DAMSelection is sourced, labelled as a worked example, or labelled as a DAMSelection rule of thumb.
Update cadence
DAMSelection updates each data type on a fixed calendar, and each page shows its Last verified date.
| Content | Cadence |
|---|---|
| Vendor Passport facts | Every quarter, and on any ownership change |
| DAM Market Map | Every quarter |
| DAM Pricing Index | Every quarter, once a cell reaches five quotes |
| Vendor Pulse | Every month |
| State of DAM Selection | Every year, first edition planned for Q2 2027 |
| Correction requests | Checked within ten working days |
Independence
DAMSelection accepts no payment for placement, scores or reviews, and the vendor data model has no sponsorship, partner-tier or payment field.
The neutrality policy lists the five rules and the disclosure register. DAMSelection is written by Stephan Spijkers, founder of PIMvendors, and Chris Jobse, consultant and partner. Both work on vendor-neutral PIM and MDM selections, and they apply the same method to DAM.
Limits of the method
The DAMSelection method has three known limits, and each page states them where they matter.
- Documentation lags releases. A feature shipped last week can show as absent until the vendor updates its documentation or a demo shows it.
- Demo evidence reflects one configuration on one date. A later release can change a rating, which is why every rating carries its date.
- Most DAM pricing is quote-based. DAMSelection publishes price ranges only through the Pricing Index, with a minimum of five quotes per cell.
Who writes DAMSelection
- Stephan Spijkers, Founder, PIMvendors.com
- Chris Jobse, Consultant and partner, PIMvendors.com
Frequently asked
How does DAMSelection choose which vendors to cover?
DAMSelection covers 30 vendors that sell a documented DAM product to European mid-market and enterprise buyers. Selection draws on buyer demand seen in PIMvendors projects and on search demand. Each vendor sits in one of five segments. Vendors cannot buy inclusion, and the list is reviewed every quarter.
Do vendors pay to appear in DAMSelection?
No vendor pays to appear in DAMSelection. The vendor data model has no sponsorship or payment field, the site carries no affiliate links, and placement follows segment and score only. Any commercial relationship between PIMvendors and a vendor appears in the disclosure register of the neutrality policy.
How often are DAM vendor facts checked?
DAMSelection re-verifies every Passport fact once a quarter against its primary source. An acquisition, merger or product rename triggers an immediate re-check. Each field shows its own verification date, so a reader can see how current the fact is before relying on it in a selection.
What does Not verified mean on a vendor profile?
Not verified means DAMSelection has not yet found a primary source for that field. The field carries no DAMSelection claim, positive or negative. Buyers should ask the vendor for the fact in writing and request the source document during the security and procurement review.
Can a vendor change its DAMSelection score?
A vendor can change its DAMSelection score only by producing new evidence under the scoring model's rules: a scripted demo, current documentation or a reference call. Accepted corrections to facts update the page within the corrections process. No payment, partnership or request alone changes a score.