Business

RFP for a Custom Software Project: A Template and How to Fill It In

November 11, 2026 · 5 min read · Etzal Group Team

A company sends a two-paragraph email to five vendors asking for "a quotation for an inventory system". Five proposals come back. One is four pages and one is sixty. One prices by the day, one by the module and one gives a single figure. They cannot be compared, so the choice goes to the vendor with the best presentation. A structured RFP for a custom software project prevents this. It takes about two weeks to write and saves months.

What an RFP is for

  • Comparable answers. Every vendor responds to the same questions in the same format.
  • Fewer assumptions. Vendors price what you described, not what they imagined.
  • A defensible decision. You can show why the chosen vendor scored highest.
  • A basis for the contract. The scope in the RFP becomes the scope in the agreement.

The template

1. About us

Three or four sentences: what the company does, its size, where it operates. Vendors propose differently for a distributor with twelve branches than for a single-site clinic.

2. The problem and the goals

Describe the situation today and why it has to change. Then state goals as outcomes with numbers:

  • "Reduce order processing time from two days to four hours."
  • "Give branch managers daily stock figures without phone calls."

Avoid describing the solution. "We need a system with a dashboard" tells vendors what to build. "Managers cannot see stock until month end" tells them what to solve.

3. Scope

  • In scope. Processes, users, locations and modules.
  • Out of scope. What you are not asking for in this phase.
  • Users and roles. Who will use it and roughly how many.
  • Volumes. Transactions per day, records, growth expected.
  • Integrations. Each system it must connect to, with what data and how often.
  • Data migration. What must be moved from the old system and how far back.

If you have a requirements document, attach it. If you do not, list the main processes and say that detailed requirements will be defined in a first phase.

4. Constraints

  • Technology you must use or avoid.
  • Hosting requirements and data location.
  • Security and compliance requirements, including personal data rules.
  • Languages and devices.
  • Deadlines that cannot move, such as a fiscal year start.

5. What we expect from the vendor

  • Discovery and requirements.
  • Design, development and testing.
  • Data migration.
  • Training and documentation.
  • Go-live support and warranty.
  • Ongoing maintenance.

Say which of these you want priced separately.

6. Response format

This section makes proposals comparable. Ask every vendor to answer in the same order:

  1. Understanding of the problem, in their own words.
  2. Proposed approach and architecture.
  3. Project plan with phases and milestones.
  4. Team: named people, roles, experience and share of time.
  5. Relevant projects, with a client contact for reference.
  6. Price, in the breakdown you specify.
  7. Assumptions and exclusions.
  8. Warranty, support terms and maintenance fee.
  9. Ownership of source code and documentation.
  10. Risks they see and how they would handle them.

Set a page limit. It forces vendors to prioritise.

7. Price format

Prescribe the table:

  • Price per phase or per module.
  • Day rates per role, for changes.
  • Third-party costs listed separately: licences, hosting, messaging fees.
  • First-year running costs.
  • Payment schedule linked to milestones.

Identical tables are what let you place proposals side by side.

8. Evaluation criteria

Tell vendors how you will choose, with weights. For example:

  • Understanding of the problem and approach: 25%
  • Team and relevant experience: 25%
  • Price and total cost of ownership: 25%
  • Plan, risk and delivery method: 15%
  • Support and handover terms: 10%

Publishing the weights discourages a low price built on a weak team.

9. Timeline and process

  • Date the RFP is issued.
  • Deadline for questions, and the date answers are sent to all vendors.
  • Proposal deadline.
  • Presentation dates.
  • Decision date and intended start.

Give vendors at least two to three weeks. Shorter deadlines favour whoever has a generic proposal ready.

10. Terms

  • Confidentiality.
  • That the RFP is not a commitment to buy.
  • Who to contact, and that all questions go to that person.
  • Proposal validity period.

Running the process fairly

  • One contact point. Answers to any vendor's question go to all vendors.
  • A briefing session. One call where all vendors can ask questions saves a week of emails.
  • Same information for everyone. A vendor who learned more through a private conversation has an unfair advantage and your comparison is spoiled.
  • Score independently, then discuss. Each evaluator scores alone before the group meets.
  • Check references. Call the client contacts. Ask what went wrong and how the vendor reacted.

Mistakes that ruin an RFP

  • Describing a solution instead of a problem.
  • No volumes. A system for 20 users and one for 2,000 are different projects.
  • A wish list with no priorities. Mark what is essential and what is optional.
  • No response format.
  • Hiding the budget and the criteria.
  • Too many vendors.
  • Unrealistic deadlines.
  • Choosing on price alone, then discovering the exclusions.

When an RFP is the wrong tool

For a small project, or when requirements are still unclear, a full RFP is heavy. Two lighter options:

  • A paid discovery phase with one or two vendors, producing a requirements document and a fixed quotation for the build.
  • A request for information to shortlist, followed by conversations.

An RFP works best when you know the problem well and the project is large enough to justify the effort on both sides.

We respond to RFPs and also help clients write them, as part of scoping in our Enterprise Software work. If you have a draft and want it reviewed before it goes out, send it to us.

Summary

Describe the problem and the goals, the scope and volumes, the constraints and what you expect from the vendor. Prescribe the response and price format, publish the evaluation weights, give a realistic timeline, and treat all vendors alike. Proposals that follow one structure can be compared, and that is the purpose of the document.

Frequently asked questions

How long should a software RFP be?

Eight to fifteen pages is enough for most mid-sized projects. Long enough to describe the problem, the scope and how you will choose, and short enough that vendors read all of it. Attach detailed requirements as an appendix instead of lengthening the main document.

How many vendors should receive the RFP?

Three to five. Fewer gives you no comparison. More than five means you will not read the proposals properly, and good vendors decline when they learn that ten others were invited. Shortlist first with a brief conversation or a request for information.

Should the RFP state the budget?

Giving at least a range usually produces better proposals. Without it, vendors guess, and you receive answers sized for three different projects. If you prefer not to state a figure, describe the scale clearly through number of users, transactions and integrations.

Author

Etzal Group Team

Etzal Group Team, helping businesses grow with technology. Contact us.

Related service

Free consultation

Not sure where to start? We will map the right system for your business, free.