Short answer
Procurement and legal in a DAM selection own the pricing archetype, renewal terms, exit rights and data protection. Procurement and legal support Checkpoint 3: Justify, write the commercial section of the RFP and lead Checkpoint 7: Sign. DAMSelection rule of thumb: the seat joins at Checkpoint 3 at the latest, so commercial questions reach vendors with the RFP and the security review runs alongside demos.
What procurement and legal own in a DAM selection
Procurement and legal own four outcomes in a DAM selection: a fitting price model, capped renewals, an executable exit and data protection terms that pass review.
Pricing archetype
A pricing archetype is the basic model a vendor uses to price a DAM: per seat, per storage tier or platform tier. Procurement maps the usage profile from the content audit to each archetype. The DAM pricing guide explains where each archetype fits.
Renewal terms
Procurement owns the terms that apply after year one: renewal price caps, notice windows, metered rates at higher tiers and multi-year commitments. DAMSelection assessment: buyers who negotiate only the first-year licence often face larger increases at renewal or at the next storage tier.
Exit
Legal owns the right to leave with every asset, rendition and metadata field. The contract states export format, timing, cost and the assistance period after termination. Legal also checks that exported metadata arrives in a documented, structured format that a spreadsheet or another DAM can read. The exit strategy guide lists what portability covers.
Data protection
Legal owns the data processing terms. A DAM holds personal data in photos, model releases and user accounts. Article 28 of the GDPR, Regulation (EU) 2016/679, sets the terms a controller agrees with a processor such as a SaaS DAM vendor.
Checkpoints procurement and legal lead
Procurement and legal lead Checkpoint 7, write the commercial section at Checkpoint 4 and support Checkpoint 3.
| Checkpoint | Procurement and legal role | Output |
|---|---|---|
| 1 Map | Informed | Contract dates and notice periods of the current system |
| 2 Define | Contributor | Commercial and legal requirements with priorities |
| 3 Justify | Support | Pricing archetype comparison in the five-year cost model |
| 4 Shortlist | Contributor | Commercial section of the RFI or RFP |
| 5 Test | Parallel track | Security and procurement review started |
| 6 Score | Scorer and veto holder | Commercial scores and contract risk list per finalist |
| 7 Sign | Lead | Negotiated contract, data processing agreement and exit terms |
The current system's contract matters at Checkpoint 1. A notice window that closes before the new DAM goes live forces a costly extension. Procurement records the date and plans backwards from it.
Commercial requests procurement makes
Procurement asks every shortlisted vendor the same commercial questions in writing, so answers compare line by line. The RFP template holds the commercial section.
- State the price per unit for every metered line: users, external users, storage, egress, AI credits, portals, connectors and environments.
- State the price at the next two tiers for storage and AI credits.
- State the maximum renewal increase per year and the notice window.
- State whether AI credits expire and what happens to unused credits.
- State the export format for assets, metadata, relationships and history, and its cost at termination.
- Provide the sub-processor list, hosting regions and the process for notifying changes.
- Provide the data processing agreement and the clause on use of customer assets for AI model training.
- State service levels, support response times and the service credits attached to them.
- State the ownership structure of the vendor and any change in the last three years.
Procurement scores completeness as well as price. A vendor that refuses to state metered rates scores lower on cost predictability.
Data protection and switching rules
Procurement and legal apply two EU regulations to every SaaS DAM contract: the GDPR for personal data and the Data Act for switching between cloud services.
| Regulation | What procurement checks | Fact from the official source |
|---|---|---|
| GDPR, Regulation (EU) 2016/679 | Processor terms and transfers outside the EU | Article 28 sets controller and processor terms. Chapter V governs transfers to third countries. |
| Data Act, Regulation (EU) 2023/2854 | Switching terms and switching charges | The Data Act applies since 12 September 2025. Chapter VI covers switching between data processing services. |
Fact: the European Commission states that the Data Act removes switching charges, including data egress charges, from 12 January 2027. Until that date, providers may charge for the costs incurred in switching and data egress. Legal checks the vendor's switching terms against Chapter VI before signature and asks counsel to confirm how the rules apply to the specific contract.
Documents procurement and legal use
Procurement and legal work from five documents during the selection.
| Document | Purpose | DAMSelection resource |
|---|---|---|
| Five-year cost model | Compare vendors on full cost by archetype | TCO Calculator |
| Commercial section of the RFP | Collect comparable price and term answers | RFP template |
| Security and procurement review | Collect certificates, sub-processors and terms | Security review guide |
| Contract clause list | Track the clauses that limit long-term risk | Contract clauses guide |
| Renewal calendar | Plan reviews before each renewal window | Renewal playbook |
The renewal calendar starts at signature. The DAMSelection Renewal Radar works backwards from the renewal date: review at 180 days, market test at 90 days, and negotiate or give notice at 30 days.
Worked example: renewal cap over five years
A renewal cap limits how far the licence can grow after year one. The figures in this worked example are hypothetical.
A contract starts at EUR 50,000 per year. Without a cap, the vendor raises the price 9 percent per year. With a cap, increases stay at 3 percent per year.
| Year | No cap, 9 percent | Cap, 3 percent |
|---|---|---|
| 1 | EUR 50,000 | EUR 50,000 |
| 2 | EUR 54,500 | EUR 51,500 |
| 3 | EUR 59,405 | EUR 53,045 |
| 4 | EUR 64,751 | EUR 54,636 |
| 5 | EUR 70,579 | EUR 56,275 |
| Five-year total | EUR 299,235 | EUR 265,456 |
The cap saves EUR 33,779 over five years in this example, before any change in storage or AI credit rates. Procurement negotiates the cap and the metered rates together.
Risks procurement and legal catch
Procurement and legal catch five risks that other seats rarely read in the contract.
- Auto-renewal with uplift: a contract renews at a higher price when the notice window passes unnoticed. Procurement calendars every window.
- Metered overage: storage, egress and AI credits beyond the allowance carry list prices. Procurement fixes the rates for the contract term.
- External user pricing: brand portal users can count as paid seats. Procurement confirms the user definition with the brand manager.
- Export by API only: an exit that requires custom engineering costs time and money. Legal specifies a bulk export format and assistance period.
- Ownership change: DAM ownership changes often affect roadmaps, a DAMSelection assessment. Procurement checks ownership history and asks for change-of-control terms.
How procurement and legal work with the other seats
Procurement and legal turn the findings of the other seats into contract terms.
- With the CMO: agree the five-year budget and the walk-away price.
- With the IT architect: align the data processing agreement, hosting regions and service levels.
- With the brand manager: confirm external user counts and portal pricing.
- With the DAM manager: confirm the export format covers every metadata field.
The DAM selection roles overview shows how the five seats divide the checkpoints.
Procurement and legal checklist
The procurement and legal checklist covers eight steps before signature.
- Record the current contract's notice window and end date.
- Write the commercial section of the RFP with every metered line.
- Model five-year cost by pricing archetype with the CMO.
- Start the security and procurement review during Checkpoint 5.
- Check processor terms and transfers against the GDPR.
- Check switching and egress terms against the Data Act.
- Negotiate renewal caps, metered rates and exit terms together.
- Calendar the renewal at 180, 90 and 30 days before the date.
Frequently asked
When should procurement get involved in a DAM selection?
Procurement should get involved in a DAM selection at Checkpoint 3: Justify, when the team models five-year cost by pricing archetype. Early involvement puts the commercial questions in the RFP and starts the security review in parallel with demos.
What contract terms matter most for a DAM?
The DAM contract terms that matter most are renewal price caps, metered rates for storage, egress and AI credits, external user definitions, export format and assistance at exit, data processing terms and service levels with credits. Each term limits a cost or risk that grows over the contract.
How do you negotiate a DAM contract?
A DAM contract is negotiated on the five-year cost profile: renewal caps, metered rates at higher tiers, external user pricing and multi-year terms. Two competing quotes from finalists strengthen the position. The [pricing negotiation guide](/dam/select/pricing-negotiation/) covers tactics.
Does the EU Data Act affect DAM contracts?
The EU Data Act affects SaaS DAM contracts through its switching rules in Chapter VI, which apply since 12 September 2025. The European Commission states that switching charges, including data egress charges, end from 12 January 2027. Legal counsel should confirm how the rules apply to a specific contract.
What should a DAM exit clause include?
A DAM exit clause should include the export format for original files, renditions, metadata, relationships, rights fields and audit history, plus the timing, cost and length of termination assistance. Testing a sample export during the proof of concept confirms that the clause works.