RFI or RFP for DAM selection

RFI and RFP defined

An RFI and an RFP are two procurement documents used at different stages of a software selection. Both ask vendors for written answers, and they differ in purpose, depth and commitment.

An RFI (request for information) is a procurement document that collects basic facts from many vendors to decide which ones to consider further. An RFP (request for proposal) is a procurement document that asks a few vendors for a priced proposal against the buyer's scope, scenarios and requirements.

The numbers in the table are DAMSelection rules of thumb from PIMvendors selections. A related document, the RFQ (request for quotation), asks for price on a fully specified scope. RFQs suit renewals and add-on purchases better than a first DAM selection.

Where each fits on the Selection Route

The RFI and the RFP sit on either side of checkpoint 4, Shortlist, on the Selection Route. The RFI feeds the shortlist decision, and the RFP opens the test checkpoint.

1. Map: audit assets, users and tools.
2. Define: write requirements and scripted scenarios.
3. Justify: build the business case and the five-year cost model.
4. Shortlist: apply four filters, using desk research and, where needed, an RFI.
5. Test: send the RFP, run scripted demos, then a proof of concept with the final one or two vendors.
6. Score: score against published criteria and check references.
7. Sign: negotiate and contract.

The RFP needs requirements and scenarios from checkpoint 2. An RFP sent before those exist turns into a feature questionnaire, and every vendor answers it with "fully supported".

When a DAM RFI helps

A DAM RFI helps when public information cannot answer the shortlisting filters. DAMSelection assessment: an RFI earns its cost in five situations.

• Hosting and residency are unclear: you need to know where primary data, backups and AI processing run, and vendor websites do not state it.
• Industry fit is niche: packaging artwork approval, regulated claims or broadcast video need specific capabilities.
• Integration depth is unknown: the PIM or e-commerce platform has no documented connector listed in the PIM and DAM Fit Map.
• The longlist stays long: more than eight vendors remain after desk research.
• Procurement rules require it: public bodies and some regulated companies must consult the market formally.

When to skip the RFI

A DAM RFI adds two to three weeks including preparation, so skip it when desk research already answers the filters. The DAMSelection vendor directory, the shortlisting guide and the Shortlist Engine cover segment, hosting, pricing archetype and integrations for 30 vendors.

Skip the RFI in these cases.

• The four shortlisting filters leave five or fewer vendors.
• Vendor documentation answers hosting, residency and connector questions.
• The selection runs on a fixed deadline, such as a contract end date.

A short call with each remaining vendor often replaces an RFI. Use the same 12 items in every call and record the answers.

A light DAM RFI in 12 questions

A light DAM RFI asks for 12 items that map directly to the shortlisting filters, so every answer has a use. Vendors answer in one to two pages within one week.

1. List the customer segments and industries the product serves most, with two reference customers of similar scale.
2. State where primary data, backups and AI processing are hosted, by region.
3. List current security certifications with scope and expiry date.
4. State the deployment models offered: multi-tenant SaaS, single-tenant or self-hosted.
5. List connectors for our PIM, CMS and e-commerce platform, and name who builds and maintains each.
6. List the metadata standards supported for import and export, such as IPTC and XMP.
7. Name the pricing archetype: per seat, per storage tier or platform tier.
8. Give an indicative five-year price range for the attached volume sheet.
9. List the AI functions generally available today and how each is charged.
10. List the languages of the user interface.
11. Describe support hours and channels on European business days.
12. Describe how a customer exports all assets and metadata at the end of a contract.

Send the 12 items as a numbered form. Ask for evidence links, such as documentation pages, for items 2, 3, 5 and 12.

How to score RFI answers

DAM RFI answers score as pass or fail against the four shortlisting filters, so the result is a shorter list. Weighted scoring belongs to the RFP and the demos, where the evidence is stronger.

The pass rules in the table are examples; write your own before sending the RFI. A vendor that leaves an item blank fails that item, which keeps the process fair to vendors who answered in full.

Running a DAM RFI in two weeks

A DAM RFI runs in two weeks when the buyer prepares the form, the volume sheet and the pass rules before sending. DAMSelection rule of thumb: six steps cover it.

1. Day 1: confirm the longlist from desk research and name one contact per vendor.
2. Day 1: send the 12-item form, the one-page volume sheet and the response deadline.
3. Days 2 to 4: answer vendor questions and share every answer with all vendors.
4. Day 7: close responses and log late or incomplete answers.
5. Days 8 to 9: two panel members score each answer against the pass rules, separately.
6. Day 10: agree the shortlist, record the reason for each exclusion and inform every vendor.

Tell excluded vendors which filter they failed. A short, factual reason keeps the relationship intact for later selections and reduces challenges in public procurement.

What the RFP adds

The DAM RFP adds what an RFI cannot collect: a priced commitment against your scope and a promise to demonstrate your scenarios. The RFP template gives the full ten-section structure.

The RFP answers then face two tests: the scripted demo and, for the final one or two vendors, the proof of concept.

Public-sector rules for RFIs

Public-sector DAM buyers in the EU can run an RFI as a preliminary market consultation, which Directive 2014/24/EU allows under Article 40. Contracting authorities may consult the market to prepare the procurement and to inform vendors of their plans and requirements.

Fact: Article 40 permits the advice gathered to shape planning and the procedure, provided it does not distort competition or breach non-discrimination and transparency. Article 41 sets measures for cases where a vendor took part in preparing the procedure. Ask procurement counsel to confirm the national rules that apply.

Common mistakes with RFIs and RFPs

Most RFI and RFP problems in DAM selections come from sending the wrong document at the wrong stage. The list covers the patterns seen in PIMvendors practice.

• An RFP with 250 feature lines sent to 12 vendors, producing a spreadsheet of "yes" answers.
• An RFI that asks for full pricing, which vendors cannot give without scope.
• No volume sheet, so prices cannot be compared.
• Scenarios missing from the RFP, so demos fall back to each vendor's standard show.
• Different questions for different vendors, which breaks comparability.