A well crafted RFP can pave the way for not only an optimal end product, but a more efficient process through the entire development cycle

Our team reviews hundreds of ‘Web Development assistance’ RFPs each year. To identify the ‘best’ of these opportunities, we look for a few specific items. These items (language signals, really) can speak volumes about the likely outcome of the project(s) in question. We look for the following three factors because they are telltale indicators that we’ll be able to build a great product that meets or exceeds expectations:

  1. Discovery Call(s) and/or Open Communication- We like to see this kind of openness. Not only is it helpful to get to know each other, this substantive communication goes both ways, allowing you to assess Gulo and our process more thoroughly before reaching any commitment. Perhaps most importantly, open communication to discuss the project requirements in more detail means that the work can be as clearly defined as possible.
  2. Hands-on and/or Eyes-on experience – We want to speak directly with stakeholders who currently interact with infrastructure and/or will be interacting with new build outs. Does the RFP specify who, exactly, the Web Development team will be working with? What is their relationship with the digital infrastructure? Can the chosen Web team reach out to additional stakeholders in the ‘Needs Analysis’ and ‘Usability testing’ phases?
  3. Formal Q & A Period – This is particularly helpful if the precise needs requirements are uncertain at the time of the RFPs posting. This process can unearth them. A formal Q & A is a great way to better conceptualize the project (for yourself as well as the developer!).

As you may notice, our three tips all tie into identifying projects that are likely to yield fantastic results. After all, most web teams want to build web properties that look and function exceptionally well! In our experience, the development of the best digital infrastructure share a common trait: open and efficient communication.

Putting together an RFP for any sizable or mission-critical project is a daunting responsibility. There are countless hurdles, many of them tough to foresee and there is no magic bullet template to follow. More than simply understanding current needs, you also need to forecast the potential needs to come. Every project is unique, none more so than yours.

Complicating matters further is the fact that the most detailed needs assessment is almost always going to occur once the project begins active development. But this doesn’t mean you can’t have a comprehensive RFP that yields the best possible responses from web teams!

So next time you’re putting together an RFP for a web development project, please consider Gulo’s three tips for the most effective communication!


Written by

John Dudley