// I need to

ModernizeUpgrade without breaking it RescueFix what someone else started Build NewTurn an idea into a product Reach More PeopleGet found, get used, include everyone

// Company

Case StudiesExpertiseAbout + CareersResourcesContact Book a call →

Why I Am Not Bidding On Your (Crappy) RFP: An argument against the pervasive reliance on RFPs

Poorly written RFPs can lead to development headaches and fail to gather the information they're supposed to. Here's how to avoid common RFP mistakes.

Kendall Wyman Aug 18, 20155 min read

From the Art+Logic archive · written in 2015. The tools may have moved on; the thinking still holds.

Why I Am Not Bidding On Your (Crappy) RFP: An argument against the pervasive reliance on RFPs

Poorly Written RFPs Can Lead to Development Headaches

I decided to write this piece when I received, after the perfunctory exchange of NDA and cordial emails, yet another (crappy) request for proposal (RFP) from a potential client. I thought about attempting to explain to the client just why their RFP was poor and warning them about the consequences of choosing a vendor based on responses generated from their RFP. I would have concluded with my heartfelt plea of “look-I’m-not-advocating-for-us-here-but-you”, but I didn’t have it in me at the moment. I’ve grown weary of writing those emails.

Although I do have empathy for why RFPs exist, let me just outline what I (and any other reputable software development firms) see in this particular RFP so that, perhaps, if any of these look familiar, you might be able to go back and reconsider your request. But more importantly, I actually want you to have a chance at developing a piece of custom software that will make you a hero and not get you fired for leading the company down a path of rampant budget extensions, schedule delays, poorly implemented features and a whole boatload of hurt feeling reports and righteous indignation.

What NOT To Do With An RFP

Our hapless example of a poorly presented RFP:

The vast majority of an RFP should be devoted to the requirements for the application. Spend your time here; spend your words here. I promise we won’t think less of a potential client for over-sharing. Please, draw me pictures, give me workflow outlines created on legal pads, give me user stories, give me your raw notes and research. We are not asking you how to build the application or to be sophisticated in your terminology, that’s the software development team’s job and they are very good at doing that. What I need is for you to expose the very knowledge I don’t possess: knowledge about your process, who your users are and what they need to do their job or accomplish their goal. Heck, I’ll even take free-association word clouds over stuff like “Social Collaboration Functionality”.

Now, back to the RFP:

RFPs Seldom Gather The Information They’re Supposed To

As I mentioned above, I understand why these documents exist. Our clients, in most cases, have been tasked with soliciting, vetting and securing a service provider to build an application that represents an enormous investment of time and money for their company. They may only have one chance to get it right. Failure is not an option. They know they will have people to report to about progress and budget, timeline and “when will it be done?!?!”, and the idea of doing that in a vacuum of information makes their stomachs churn at night. It’s not like they can stop by the job site and see the building materials arrive, watch the foreman organize the crew, see the building take shape before their eyes in a manner that, well, makes intuitive sense as being a successful structure. This is software and it is the domain of ephemera and “code” that somehow gets written and then “compiles” into applications that somehow “run”. The language of development and the processes used to run software development projects can be intimidating and slightly foreign. Clients have heard of developers acting like belligerent gatekeepers and there are plenty of stories of feckless developers disappearing behind a puff of smoke and bug reports.

So the RFP represents safety and control and I get that. But it really doesn’t accomplish your objective, despite how good it feels to write it out and format it in Ariel.

And the perception of the success of the RFP as represented above persists because there are companies that make a practice of responding to these RFPs using a strategy that sort of loops clients into thinking they are getting what they asked for only to immediately throw that aside to engage in a more productive process. It’s not as nefarious as it sounds; it’s an attempt to end-around an antiquated and unhelpful tool that businesses cling to in an effort to actually provide the services that a company needs. But this approach does have drawbacks as, once the client is committed and the contract signed and some groundwork laid, this approach puts the vendor in the position of requiring a new estimate and change-of-scope documents, and a revision of schedule and expectations, all of which immediately puts the client and the vendor in an adversarial relationship rather than a collaborative one, and that doesn’t actually sound like success to me.

Click here to read what Kendall suggests you should do instead of relying on an RFP. She includes a detailed outline of questions to consider when hiring a development team.

keep going

More to explore in Build New.

All Build New resources →
let's talk

Got a problem like this one?

Tell us what's stuck. A real person replies within one business day.

Talk to our team →

Talk to people who know software, not a sales script.

Your first call is with Aja, our VP of Sales. He'll help make sure you're solving the right problem. Here's what you'll cover together:

  1. What you're trying to accomplish

    The business goal first, then the technology.

  2. Possible approaches

    And the tradeoffs of each, in plain language.

  3. Risks you may not have considered

    Technical and business, before they cost you.

  4. Whether AI changes the math

    What's practical, and what's just hype for your project.

  5. Sensible next steps

    Even if the right next step is not us.

book-a-call.ics

Loading the scheduler…

Open the booking page →

Some problems are easier to explain in writing. Send us a few lines about what you're working on, and we'll reply within one business day. Helpful to include:

  1. What the software does, or should do
  2. What's stuck, or what's worrying you
  3. Any deadline or budget you have in mind
note.md

Loading the form…