Most enterprise photography RFPs are written by procurement teams optimizing for variables that do not predict operational success. The winning vendor on paper produces a beautiful calibration shoot, then collapses the first week their bookings exceed twenty a day. By month three the program is quietly using two backup vendors, the RFP discount has evaporated, and procurement is rerunning the exercise.
The structural problem is that traditional RFPs evaluate portfolio quality and price, and treat operational fit as a soft attribute. At enterprise scale, the order is the opposite. Operational fit decides the program; portfolio quality is the table-stakes filter.
The four-part RFP structure
Every part is required. Skipping any one of them is how the RFP ends up picking the wrong vendor.
Part 1: capacity and coverage test
Before any creative evaluation, confirm the vendor can deliver the projected volume across the geographic footprint the brokerage operates. For a 40-office firm doing 25,000 listings a year, that is roughly 480 shoots per week averaged, with spikes to 700 in March-April and September-October. The vendor needs to produce a defensible capacity plan: how many active operators, what coverage map, what the spike-week protocol is.
Capacity is the variable that disqualifies single-vendor consolidation candidates fast. Three quarters of the national vendors who pitch enterprise brokerages cannot produce the answer to this question with real numbers.
Part 2: spec calibration shoot
Send the vendor your actual spec for the highest-volume service (typically standard residential HDR photography). Have them shoot a calibration set on three properties, with the same shot list, the same processing standards, the same delivery window. Score the calibration against the spec rubric. Anything below 90% spec compliance is a fail. The portfolio they sent in the proposal is not relevant; this is.
Part 3: SLA stress test
A week of real bookings with deliberate edge cases. Same-day rush on day one. A reshoot request on day two. A weekend spike on day three. A controlled-airspace drone shoot on day four. A twilight on a difficult property on day five. Track on-time arrival, complete shot list capture, processing delivery window, and communication quality. Score on the same SLA framework you will use in production.
Part 4: finance and operations review
Insurance limits and coverage scope. Payment terms (net 30, net 45). Integration capability: can the vendor accept bookings through API, or only through email? Asset delivery: do they push to your library, or send a Dropbox link the coordinator has to relay? Cost-center tagging at invoice level. This is the part procurement is best at, and it should not be the only part procurement runs.
The RFP that picks the right vendor evaluates the program the vendor will actually run, not the portfolio they want to show. Calibration shoot, SLA stress test, capacity plan, and operations review all carry weight.
A scoring rubric that holds
Weighting matters. The temptation is to weight portfolio at 40% and SLAs at 10%. The right enterprise weighting inverts that.
- Capacity and coverage: 30%. The single highest-impact variable on whether the program survives the first spike week.
- Spec compliance on calibration: 25%. Will the vendor deliver against your standard, repeatably.
- SLA reliability in the stress test: 25%.The leading indicator of in-production performance.
- Operations and integration: 15%.Invoicing, asset library, integration depth.
- Pricing: 5%. Among vendors who clear the other four gates, price differentiates at the margins. Below the gates, price is irrelevant because the vendor will not perform.
The tiered pool, not the single national vendor
The other structural mistake is exiting the RFP with one winner. Single-vendor consolidation has the cleanest commercial story (one contract, one rate card, one relationship), and it has the highest operational risk (zero redundancy, capacity ceilings, geographic gaps). The right exit is a tiered pool with overlapping coverage.
- Primary preferred vendor. Top scorer on the RFP. Gets first-call routing on the markets they cover strongly. Earns volume tier discounts at scale.
- Secondary vendors. Two to three operators who scored above the gates with complementary coverage and capacity. Handle spike weeks and primary-vendor conflicts. Earn the volume the primary cannot absorb.
- Marketplace pool. Vetted vendors below the secondary tier who handle thin-market coverage and new-market expansion. Same spec, same SLAs, no primary-vendor commercial commitment.
What the RFP should not do
Two patterns kill enterprise RFPs.
- Optimizing for the lowest price. Below the operational gates, price is decorative. The vendor who undercut by 15% is the vendor who collapses on the spike week. Reversing that decision two quarters in is more expensive than the entire price differential.
- Locking out incumbents. The vendors already in the brokerage’s offices, working under informal terms, have institutional knowledge the new national vendor lacks. The RFP should evaluate them alongside the bidders, not exclude them because they did not respond to a procurement portal.
AssetOSX runs this RFP framework as part of every enterprise rollout, and operates the tiered marketplace pool that the framework presupposes. The model is summarized on the about page and tied to the broader vendor SLA framework we covered earlier.
