RFI vs RFP: which one should you run first for your office fit-out?

Most people use "RFI" and "RFP" almost interchangeably when they're sourcing consultants for an office fit-out. That's a mistake - the two documents do genuinely different jobs, and picking the wrong one first is a quiet, common reason a straightforward project turns into a slow one.

What an RFI actually is

A Request for Information is a narrowing step. It's informational and non-binding: you send it to a longer list of firms - Architects, Interior Designers, MEP Consultants, whoever the category is - and ask each one for the basics. An overview of the firm, a couple of relevant past projects, roughly who'd be on your team, and a rough sense of budget and timeline.

Nobody submits a real, priced proposal in response to an RFI. You're not asking anyone to commit yet - you're asking enough of the right questions to turn a list of ten names into a shortlist of three or four worth the effort of a real bid.

What an RFP actually is

A Request for Proposal is the real ask. This is the binding document: full scope, real requirements, a real deadline, and firms respond with an actual priced proposal you can compare and act on. An RFP is what leads to an award.

The difference matters because writing and evaluating a full RFP takes real time - both yours and every firm's. Every firm you send a full RFP to has to treat it seriously: pull a team together, estimate real numbers, write a real response. Sending a full RFP to ten firms when you only had a rough sense of who you wanted isn't thorough, it's wasteful - for you and for the eight firms who never had a real shot.

So which one do you actually need?

Run an RFI first if:

• You're starting from a longer list - referrals, a Google search, a few names a colleague mentioned - and haven't had a real conversation with most of them yet.
• You genuinely don't know who's good at this specific kind of work yet (a 30,000 sq ft tech office is a different job than a 5,000 sq ft boutique studio, even within the same consultant category).
• This is your first time running this kind of project and you'd rather learn from a handful of quick conversations before committing to a formal bid process.

Go straight to an RFP if:

• You already know exactly who you want to invite - a firm you've worked with before, or a strong referral you trust.
• The category is small enough, or the project simple enough, that a full brief to 3-4 known firms is barely more work than an RFI would have been anyway.
• You're on a real deadline and the narrowing step would just add a week you don't have.

Neither path is more "correct" - they solve different problems. An RFI protects your RFP from being sent to the wrong list; skipping it is fine when you're already confident about the list.

The mistake worth actually avoiding

The failure mode that actually costs people time isn't picking RFI when RFP would've done, or vice versa - it's running an RFI and then promoting straight to a full RFP without actually using the RFI for anything. If you shortlist three firms purely off a portfolio thumbnail and never ask a single follow-up question, you've spent a week on a step that taught you nothing you couldn't have gotten from the original list. An RFI is only worth the time it takes if you actually use it to ask something - even a short one.

Bottom line: an RFI narrows a list you're not sure about; an RFP is the real, binding ask to a list you trust. Match the step to how confident you already are about who belongs on it, and you'll spend your time on the part of sourcing that actually needs it.