Most colocation is still bought by email. A shortlist is assembled from reputation and a conference conversation, three providers send PDFs with different assumptions in them, and the decision gets made on the number that looks lowest. That works until the deployment is large enough that being wrong is expensive.
A structured request for proposal fixes the comparison problem. It does not make providers cheaper. It makes their offers comparable, which is a different and more valuable thing, because the most common procurement failure in this market is not overpaying. It is signing with a facility that cannot actually do what the deployment needed.
When an RFP Is the Right Instrument
An RFP costs both sides real effort, so it should be used where the effort is repaid.
It is worth running when the requirement is material enough that a provider will invest in responding, when more than two credible providers exist, when the term is long enough that switching later is painful, or when internal governance requires a documented competitive process. Deployments with unusual density, specific compliance obligations or firm growth commitments benefit most, because those are exactly the requirements that informal quoting glosses over.
It is the wrong instrument for a handful of racks with no special requirements, or where you already know which facility you want and are negotiating rather than selecting. Running a theatrical RFP with a predetermined outcome wastes everyone's time and is quickly recognized.
Describe the Load, Not the Cabinets
The single most common defect in a colocation RFP is specifying the solution instead of the requirement. Asking for twenty racks invites twenty different interpretations. Describing the load lets each provider propose the configuration their facility actually does well.
State the total power in kW and whether that figure is nameplate, expected average, or contracted. Those three numbers are frequently different and conflating them is the root of most billing surprises later. State the density per rack, since 8 kW and 60 kW are different products from different facilities, and say whether density is uniform or concentrated. Give the growth profile with dates, because reserved capacity is a cost and unreserved capacity is a risk, and the provider cannot price that trade-off without knowing it.
Then state the requirements that actually constrain: redundancy level, acceptable maintenance windows, connectivity and carrier diversity, compliance and audit obligations, physical access rules, and remote hands expectations. The last one is routinely omitted and routinely becomes the daily experience of the contract.
Ask Questions That Have Falsifiable Answers
Most RFP questionnaires invite marketing. The fix is to ask for evidence rather than assertions.
Instead of asking whether the facility is reliable, ask for the incident history over a defined period with dates, durations and causes. Instead of asking whether there is sufficient power, ask what firm capacity is contracted at the point of delivery and what remains uncommitted today. Instead of asking whether they can support high density, ask what the highest density currently deployed in production is and in which room.
Ask what happens at the boundaries, because that is where facilities differ most. What is the escalation path at three in the morning? What is included in standard support and what is billed? What notice is given for planned maintenance, and what was the actual count of unplanned events last year? How is power billed, metered or allocated, and can that be audited? Our guidance on colocation SLA metrics and negotiation covers which of those commitments carry meaningful remedies and which are decorative.
Score Before You See the Prices
Agree the evaluation criteria and their weights before responses arrive, and ideally before the RFP is issued. This is the discipline that most distinguishes a real process from a performed one, because weights set afterwards are always set to justify a preference that already exists.
A workable structure separates four things. Technical capability covers whether the facility can physically do it: power, density, cooling, connectivity, growth headroom. Operational maturity covers whether they will do it well: incident history, staffing, monitoring, documentation, change control. Commercial terms covers total cost and the clauses that govern the relationship. Risk covers financial stability, concentration, exit terms and anything that makes leaving difficult.
Score the technical and operational sections before opening commercials where your process permits it. A provider that fails the technical threshold is not cheaper, they are unsuitable, and seeing the price first makes that much harder to hold.
Compare Total Cost, Not Rate Cards
Responses will arrive in incompatible shapes. Normalizing them is the analytical work of the exercise.
Build a model over the full term including recurring space and power, the power billing mechanism and its assumptions, cross-connect and bandwidth charges, setup and installation, remote hands beyond the included allowance, escalation clauses, and the cost of exit. Then run the same model under a realistic utilization case and a growth case, because offers that look similar at contracted load frequently diverge sharply at eighty per cent utilization or after a second-year expansion.
Escalation deserves specific attention. A rate that increases annually by a published index behaves very differently over five years from a fixed rate, and the gap is usually larger than the difference between the headline numbers being compared.
Visit, and Visit Properly
No RFP response substitutes for walking the building. Schedule site visits for the shortlist and treat them as evidence gathering rather than hospitality.
Look at housekeeping and cable management, which are honest proxies for operational discipline. Ask to see maintenance records and the incident log rather than a summary of them. Meet the technicians who will actually handle your hardware, not only the account team. Look at the room you would occupy, not the showcase room. Ask what is currently out of service and why.
A provider comfortable with that level of scrutiny is demonstrating something that no questionnaire response can. One that deflects it has told you something too.
Mistakes That Recur
Writing requirements around one incumbent's specification, which produces a field of non-responsive bids and a predetermined winner. Weighting price so heavily that the technical evaluation cannot influence the outcome. Omitting the exit terms, which is where leverage is highest before signing and lowest afterwards. Giving a response window too short for a serious provider to engage with, which filters for the eager rather than the capable. And accepting an availability percentage without reading what it excludes, since planned maintenance carve-outs frequently make a headline figure meaningless.
Run the facility diligence in parallel rather than after selection. The physical and technical checks in a proper site selection assessment often change the shortlist, and they are much cheaper to act on before a decision than after.
Frequently Asked Questions
How long should a colocation RFP take?
Allow providers at least two to three weeks to respond to anything substantial, and expect six to twelve weeks end to end including clarifications, site visits, scoring and negotiation. Compressing the response window below two weeks mainly filters for providers willing to answer quickly rather than carefully, which is not the quality being selected for.
How many providers should be invited?
Between three and six for most requirements. Fewer than three provides no meaningful comparison. More than six creates evaluation work that rarely changes the outcome and reduces the effort each provider puts into responding, because their perceived odds fall.
Should the RFP state a budget?
Stating a realistic range usually produces better responses than withholding it, because providers can propose a configuration that fits rather than guessing. What should not be disclosed is a competitor's pricing, which converts a selection process into a bidding war and tends to produce offers that are cheap in the places you did not examine.
What is the most commonly omitted requirement?
Remote hands. Facility specifications get defined carefully and the day-to-day support relationship is left undefined, even though it is what the client experiences every week. Specify what routine intervention is included, what is billable and at what rate, and what the response targets are, including whether the clock runs outside business hours.
Is the lowest price per kW usually the best value?
Rarely, and the reason is structural rather than cynical. The headline rate excludes the components that differ most between facilities: power billing mechanism, cross-connects, remote hands beyond the allowance, escalation, and exit costs. A total cost model over the full term under a realistic utilization case reorders the field often enough that comparing rate cards should be treated as a first filter rather than a decision.
Responding to an RFP, or Writing One?
Rax Data & Energy answers technical questionnaires with evidence rather than adjectives. Talk to our team about your requirement.
Contact Rax Data & Energy