Mastering the RFI Process: Best Practices and Proven Strategies

An RFI (or request for information) is usually the first step in the technology procurement process. It is a tried and trusted way to research the options available in the market and then narrow them down to a shortlist. But how do you run the best RFI process? One that will genuinely engage the market and deliver the outcomes you need?

In this article, we look at what an RFI is, what it should contain, how long to give suppliers, and what you should (and should not) do to get the most out of the process. We also cover some of the most common mistakes that buyers make, and when it makes sense to bring in outside support.

Viewpoint Analysis runs RFI processes (we call them Rapid RFIs) for companies of all shapes and sizes, so this is a subject we know something about.

What is an RFI?

RFI stands for Request For Information. It is a document that sets out the buyer's need and invites interested vendors to respond with how they can help satisfy that need. It is a great way to quickly assess the options available and to determine a shortlist ahead of a more formal process, typically an RFP (Request for Proposal).

At this stage in the process, you are not asking vendors to commit to a solution or price. You are exploring the art of the possible. The RFI is your opportunity to cast the net wide and understand what the market looks like before you invest significant time in a detailed evaluation.

What is the Difference Between an RFI and an RFP?

It is worth briefly clarifying the difference between an RFI and an RFP, because the two are sometimes confused.

The RFI comes first. It is a relatively lightweight document designed to assess the market, gather information, and narrow a longlist down to a shortlist. It is exploratory in nature and vendors understand that. The bar for engagement is deliberately low, because you want to hear from as many relevant vendors as possible at this stage.

The RFP (Request for Proposal) comes next. It is issued to a smaller shortlist of vendors that have been identified through the RFI process. It is more detailed, more formal, and asks vendors to commit to a proposed solution and pricing. It is a much more significant commitment of time for both parties.

Understanding this distinction matters because it changes how you write and manage each document. An RFI that reads like an RFP will put vendors off. An RFP that is as lightweight as an RFI will not give you the rigour you need to make a confident decision.

💡 Want to learn about IT procurement and the different phases - RFI, RFP, and more? Our Enterprise Software Selection Playbook is a great place to start.

How Detailed Should an RFI Be?

Many procurement teams spend too long on the RFI document and make it overly complex and cumbersome. Not only does this risk delaying the issue of the document (as internal teams debate what should go in it) but it can actively dissuade potential vendors from responding. That is the very last thing any RFI should do.

An RFI should be short and to the point. It needs to provide enough information for the vendor to understand the requirement and no more. A good length is somewhere between five and ten pages. Our free RFI Template (available at viewpointanalysis.com/rfi-template) shows how a well-structured RFI might look.

Think about it from the vendor's perspective. Their sales team is already juggling a full pipeline. If your RFI arrives looking like a PhD thesis, the easiest decision they can make is to no-bid it. Keep it clear, keep it concise, and make it genuinely easy to respond to.

What are the Risks with Sending Out an RFI?

An RFI is generally not something that vendors welcome with open arms. It is a process to become part of a process. They are being asked to invest time and effort before they even know if they are on the shortlist.

In most cases, the vendor sales team will be laser-focused on the current quarter or financial year. They want to be working on the deals most likely to close soon. An RFI represents the beginning of a long road, and vendors know it.

There is also an inherent imbalance in the RFI process. It is designed almost entirely for the benefit of the buyer. The buyer gathers market intelligence, narrows the field, and retains full control. The vendor gets very little in return at this stage beyond the hope of being shortlisted.

The practical implications of this are simple: make the process as easy and appealing as possible. A well-structured, clearly written RFI with realistic timescales will attract significantly more quality responses than one that is difficult to navigate and unclear in its intent.

💡 How about a different approach to an RFI? Take a look at the Technology Matchmaker Service - it's a slimmed-down RFI process where we bring the vendors to pitch to you. No RFI response.

Longlist Builder

Not sure which vendors to include in your RFI? Use the Viewpoint Analysis Longlist Builder to quickly identify the technology options most relevant to your project.

Answer a few questions about your requirements and we will send you a tailored longlist of potential vendors, completely free of charge:

What Information Should Go in an RFI?

The contents of an RFI should include the essential information a vendor needs to decide whether to respond. Beyond the basics, the document should be interesting to read and should genuinely sell the benefits of getting involved. The sales team reading it will face a binary choice: respond or no-bid. At the RFI stage, it is absolutely crucial to hear from a broad audience, so making the process compelling is every bit as important as making it informative.

Here are the main elements that should be included:

•       Company Information: A short summary of your business. What does the company look like, how is it structured, and where does this requirement sit? Keep it brief but make it real. Vendors want to know they are talking to a credible organisation with a genuine project, not a fishing exercise.

•       Project Need: Why are you issuing the RFI? What problem are you looking to solve? How important is that problem, and who cares about it internally? The more clearly you can articulate the business challenge, the better the responses you will receive.

•       The Process: What process are you going to follow? What is the vendor getting into? If you plan to buy, when will you do that? When do you aim to deliver the project and why that date? And critically, when will you be letting vendors know if they have made the shortlist? State this clearly and then stick to it.

•       Dates: When do you want responses back? Be realistic. Giving vendors too little time will reduce both the number and quality of responses. Factor in lead time.

•       Decision Criteria: How will you select who progresses to the next stage? Help the vendor understand what good looks like. If they know how you are going to score responses, they can focus their effort in the right places.

•       Response Format: What format would you like responses in? Keep it simple. Gone are the days of printed copies and ring binders. Email or a shared document portal is usually more than sufficient.

•       Contact Information: Who should vendors contact if they have a question, and how? Keep communication channels open throughout the process.

•       Invitation to Engage: Ideally this should happen before the RFI is issued, but if not, make sure there is an opportunity for vendors to speak with your key decision-makers before they commit to responding. Would you spend hours completing a document for an organisation you have never spoken to?

Frame the RFI as a Problem Statement

One of the most effective ways to write an RFI is to frame it as a problem statement rather than a requirements list. At this stage in the process, you should not be prescribing solutions. You should be laying out the challenge you face and inviting vendors to show you how they would approach it.

This is a subtle but important distinction. A requirements-led RFI will attract responses that mirror your assumptions back to you. A problem-led RFI invites vendors to bring their expertise and experience to the table. You may discover approaches you had not considered, or solutions that would not have appeared on your longlist under a more prescriptive process.

Think of it this way: if you already knew exactly what you needed, you probably would not need an RFI. The RFI is precisely the tool for exploring options and unlocking ideas from the vendor community. Let it do that job.

How Long Should You Give Suppliers to Respond?

How long to give vendors to respond depends on several factors:

•       How much advance notice they have received that the RFI is coming

•       How quickly you need to make your shortlist decision

•       How much time is reasonably needed to assemble a quality response

•       The time of year and the likelihood that the right people are available

•       The complexity of the product or service you are looking to buy

As a general guide, two to four weeks is a reasonable minimum for most technology RFIs, assuming vendors have been given some advance notice. For highly complex requirements, or where you are approaching a large number of vendors, you may need to allow more time.

Remember, this is not a test. Vendors will not react well to aggressive timescales or unreasonable demands. A compressed timeline that results in poor-quality responses is no better than a longer one that generates rich, considered replies. Treat vendors as partners in the process from the very beginning.

Technology Matchmaker Service

Viewpoint Analysis can run the entire RFI process on your behalf through our Rapid RFI service. We interview your team, write the RFI document in vendor-friendly language, approach the right vendors, handle all the initial sales calls, and manage the process end to end.

Common Mistakes to Avoid in the RFI Process

Having run many RFI processes, we have seen the same mistakes appear repeatedly. Here are the most common ones to watch out for:

•       Sending the RFI to the wrong vendors: This is perhaps the most costly mistake of all. If you approach vendors who are not a genuine fit for your requirement, you waste their time and yours. Worse, you may shortlist the wrong organisations and carry those mistakes forward into the RFP. Build your longlist carefully before you issue anything.

•       Making it too long and complex: A lengthy, complex RFI will reduce your response rate. Vendors will no-bid rather than invest significant resource in a process that feels burdensome. Aim for clarity and brevity at all times.

•       Being too prescriptive too soon: Specifying the solution in detail at the RFI stage limits the quality of responses you will receive. Keep the requirement outcome-focused rather than solution-focused.

•       Not communicating with vendors beforehand: Sending an RFI cold, without any prior engagement, is unlikely to generate the level of interest you need. Where possible, brief vendors ahead of time, hold a pre-RFI Q&A session, or at least ensure there is an opportunity for vendors to ask questions before they commit to responding.

•       Setting unrealistic timescales: Rushed timescales signal disorganisation and disrespect. They also produce weaker responses. Build a realistic timeline and stick to it.

•       Not being clear about the selection criteria: If vendors do not know how they will be evaluated, they cannot tailor their responses effectively. Transparency at this stage improves the quality of what comes back.

•       Failing to follow up: One of the most damaging things a buyer can do is simply disappear after issuing an RFI. Vendors that invest time in responding deserve timely, clear communication at every stage of the process. If your timelines slip, communicate that proactively.

Who Should Write and Manage the RFI?

In most organisations, responsibility for the RFI sits with the project lead, often supported by a cross-functional team including procurement, IT, finance, and the business stakeholders who will ultimately use the solution.

This multi-stakeholder involvement is healthy, but it can also slow things down. Internal debates about what to include, who should have sign-off, and how to describe the requirement can add weeks to the process. Having a clear owner and a simple approval process will help keep things moving.

If writing or managing the RFI process internally presents a challenge, there are specialist partners who can take care of it for you. At Viewpoint Analysis, our Rapid RFI service is designed to do exactly that. We work with your team to understand the requirement, translate it into vendor-friendly language, identify and approach the right vendors, manage the process, and present you with a clear shortlist. The internal team simply needs to show up for the vendor presentations and make the decision.

How to Evaluate RFI Responses Effectively

Once the responses are in, the challenge shifts to evaluation. Here is a practical approach to getting the most out of what vendors have submitted:

•       Score against your criteria: Use the decision criteria you set out in the RFI document as your scoring framework. Be consistent in how you apply it across all responses.

•       Involve the right people: The evaluation team should include representatives from the different stakeholder groups that will be affected by the solution. Different perspectives will surface different insights.

•       Look beyond the written response: Some vendors write well. Others deliver well. Consider inviting borderline candidates to a brief qualifying call before making your shortlist decision. A conversation can reveal things a document cannot.

•       Avoid incumbent bias: If you have an existing vendor relationship, be conscious of the tendency to view responses through that lens. The RFI exists to open up the market, not to confirm existing preferences.

•       Document your decisions: Keep a clear record of how and why you made your shortlisting decisions. This is important both for internal governance and for communicating feedback to vendors who ask why they were not selected.

What Comes After the RFI?

Once you have evaluated responses and identified your shortlist, the next step is typically an RFP (Request for Proposal). The RFP is issued to your shortlisted vendors and invites them to propose a specific solution and commercial terms.

The quality of your RFI process will directly affect the quality of your RFP process. If you have identified the right vendors and asked the right questions at the RFI stage, you will be in a much stronger position when you move into the more detailed evaluation.

For organisations that need to move quickly, our 30-Day Technology Selection service compresses the RFI and RFP stages into a single, streamlined 30-day process. You can find out more at viewpointanalysis.com/30-day-technology-selection.

How Viewpoint Analysis Can Help

Viewpoint Analysis specialises in helping enterprise IT buyers find and select the right technology quickly. Our Rapid RFI service takes care of the entire RFI process on your behalf:

•       We interview your team to understand the requirement

•       We identify the right vendors to approach from our extensive technology network

•       We write the RFI document in vendor-friendly language

•       We manage all initial vendor engagement and qualification calls

•       We host the vendor presentations

•       We guide you to a clear, confident shortlist decision

The result is a faster, better-quality market assessment with less internal effort. Your team focuses on evaluating the options rather than managing the process.

We also offer the Technology Matchmaker Service for teams that need a rapid initial view of the market before committing to a full RFI process, and the 30-Day Technology Selection for those who need to move from longlist to vendor decision in under a month.

T

o find out more or to discuss your specific requirement, visit viewpointanalysis.com/request-a-call or email contactus@viewpointanalysis.com.

Summary

Running a successful RFI process is less about producing a perfect document and more about understanding the dynamics of the market you are approaching. Vendors have choices. The more you can do to make engagement easy, the more quality responses you will attract.

Keep the document short and outcome-focused. Be transparent about the process, the timeline, and the selection criteria. Communicate proactively and consistently. Treat vendors as partners from the very beginning, even at this early stage.

Do those things well, and the RFI will do its job: giving you a clear, confident shortlist to take into the next phase of your selection process.

Let us know if we can help or if you have any RFI-related questions at contactus@viewpointanalysis.com