A clear RFP gets you proposals you can line up side by side. This template gives you the structure vendors expect, from scope and budget to how you'll choose a partner. Fill in the brackets, delete what doesn't apply, and send it.

Get the editable template

RFP for custom software development

What's inside the template

Eight sections, in the order vendors expect to read them.

  1. Introduction and executive summary. Who you are and what you're asking vendors to propose on.
  2. Company overview (1 page). Your organization, your industry and why the project exists.
  3. Project description and scope (up to 10 pages). Goals, compliance needs, UX, functionality and system requirements, plus a prioritized scope table.
  4. Estimated budget. A range, so proposals come back sized to reality.
  5. Proposal guidelines. What every response must include: UX approach, technical plan and stack, testing plan, timeline, cost (including ongoing support), team and references.
  6. Selection criteria. How you'll score responses, from technical approach and cost to experience, references and onshore or offshore delivery.
  7. RFP schedule. Dates for questions, answers, submissions, kickoff and launch.
  8. Contact information. One point of contact for vendor questions.

Before you send it

Two short reads that help while you fill it in:

Ready to start? Reach out to us