1. Introduction and company background
This section tells vendors who you are, why you are buying, and what a good outcome looks like. Keep it to one page. Vendors use it to decide whether to bid and how to pitch, so vague context produces generic proposals.
Include:
- A short description of your organization, size and relevant operations
- The business problem or trigger for the purchase
- What success looks like in 12 months
- A single point of contact for all questions
Example wording: "We are a 400-person logistics company operating three warehouses in the Midwest. Our current inventory system cannot support real-time stock visibility across sites. We are seeking a vendor to implement and support a warehouse management system that gives all sites a shared, live view of stock by Q3. All questions must go to Jane Doe, Procurement Lead, at procurement@example.com. Contact with other staff during this process may result in disqualification."
The single point of contact rule matters. It keeps communication fair and gives you an audit trail.
2. Scope of work and objectives
The scope defines what the vendor will deliver. It is the section most likely to cause disputes later, so write it as if it will be pasted into the contract, because parts of it often are.
Cover:
- Deliverables: the specific outputs, not just activities
- In scope and out of scope: list both explicitly
- Volumes and assumptions: users, sites, transactions, hours
- Dependencies: what you will provide (data, access, staff time)
Example wording: "The vendor will configure, test and deploy the system at three sites, migrate up to 250,000 SKU records from our existing database, and train up to 40 staff. Out of scope: hardware procurement, integration with our payroll system, and ongoing data cleansing after go-live. We will provide a named project manager available for up to 10 hours per week."
The out-of-scope list prevents the most common argument in vendor relationships: "we assumed that was included."
3. Requirements
Break requirements into a numbered matrix so every vendor answers the same questions in the same format. Free-text requirements lead to free-text answers that are hard to score.
Structure each requirement with:
- A unique ID (e.g., FR-012 for functional, TR-004 for technical)
- A clear statement of the requirement
- A priority: Mandatory, Important or Nice to have
- A response column with fixed options: Fully meets, Partially meets, Roadmap, Does not meet
- A comments column for explanation or evidence
Typical categories: functional, technical and integration, security and data protection, service levels and support, implementation, and vendor profile (financial stability, references).
Example wording: "FR-012 (Mandatory): The system must allow users to view stock levels across all sites in a single screen, updated at least every 5 minutes. Respond with one of the listed options. If 'Partially meets' or 'Roadmap,' describe the gap and the expected delivery date."
Limit Mandatory items to true deal-breakers. If everything is mandatory, nothing is, and you may disqualify good vendors over minor gaps.
4. Pricing and commercial terms
Provide a fixed pricing template, usually a spreadsheet, and require vendors to use it. Without one, each vendor will bundle costs differently and you will spend days normalizing numbers.
Ask for pricing broken out by:
- One-time costs: implementation, migration, training
- Recurring costs: licenses or subscriptions, support, hosting
- Variable costs: per user, per transaction, overage rates
- Rate card for change requests or additional work
- Price escalation terms for renewal years
Ask for a total cost of ownership over a fixed period, commonly three to five years, so vendors with low entry prices and high renewals are visible.
Example wording: "Complete all tabs of Attachment B. Prices must be in USD, exclusive of tax, and valid for 120 days from the submission deadline. State any annual price increase as a percentage cap. Costs not listed in Attachment B will not be payable under the resulting contract."
That last sentence is doing real work. It pushes hidden fees into the open before you sign.
5. Evaluation criteria and process
Tell vendors how you will score them. This improves response quality and makes your decision defensible to internal stakeholders and, in the public sector, to auditors.
Publish the categories and their weights. A common structure:
- Functional and technical fit
- Pricing and total cost
- Implementation approach and timeline
- Vendor experience and references
- Security and compliance
Weights vary by purchase. Many buyers put price somewhere between 20 and 40 percent for complex services, and higher for commodity purchases, but set weights based on what matters for this contract.
Describe the stages too: initial compliance check, scored written evaluation, shortlist demos, reference checks, best and final offer.
Example wording: "Proposals that do not meet all Mandatory requirements will not be scored. Remaining proposals will be scored by a panel of four evaluators using the weighted criteria in Section 5.2. Up to three vendors will be invited to present a scripted demo. We reserve the right not to award a contract."
Score independently first, then meet to reconcile. Group scoring from the start tends to follow the loudest voice.
6. Timeline and submission instructions
Give dates for every step and precise instructions for how to submit. Ambiguity here produces late or incomplete bids and awkward decisions about whether to accept them.
Include:
- RFP issue date
- Intent to bid deadline
- Question deadline and date answers will be shared with all bidders
- Submission deadline, with time and time zone
- Shortlist, demo, and award dates
- Target contract start date
Example wording: "Submit proposals as a single PDF plus the completed Attachment B spreadsheet to procurement@example.com by 5:00 p.m. Eastern on May 15. The main proposal must not exceed 30 pages, excluding attachments. Late submissions will not be considered. Questions received by April 28 will be answered in a consolidated document sent to all registered bidders by May 2."
A response window of two to four weeks is typical for mid-complexity purchases. Allow more for large or regulated contracts.
7. Contract terms and attachments
Include your key contract terms, or the full draft contract, in the RFP. Ask vendors to state any exceptions in their proposal. Negotiating terms after you have picked a winner removes most of your leverage.
Key terms to flag up front:
- Payment terms and invoicing requirements
- Service levels and service credits
- Liability caps and indemnities
- Data ownership, security and breach notification
- Termination rights, including for convenience, and exit assistance
- Renewal and price increase limits
Example wording: "The resulting agreement will be based on the draft in Attachment C. Vendors must list any proposed changes in the Exceptions table in Attachment D, with a reason for each. Exceptions not raised in the proposal will not be accepted during contract negotiation."
Standard attachments: requirements matrix, pricing template, draft contract, exceptions table, NDA, and any security questionnaire.
Let pingpong run it for you
pingpong drafts the RFP, finds and invites vendors, collects proposals through a private portal, scores them with five AI models and flags the gotchas above. It drafts every negotiation message for your approval, then keeps watching the market so you renegotiate before renewal. $100 for the first month, then $799 a month.
Common questions
How long should an RFP be?
Long enough to define scope, requirements and evaluation clearly, and no longer. For most mid-sized purchases, the main document runs 10 to 25 pages, with requirements and pricing in separate attachments. Cut background material vendors do not need to price or propose.
Should I include a budget in the RFP?
It depends on your goals. Sharing a budget range helps vendors propose realistic solutions and screens out bids that are far off, but it can anchor prices upward. Many buyers share a range for complex services where scope is flexible and withhold it for well-defined, competitive purchases.
How do I keep RFP responses comparable across vendors?
Use fixed templates for requirements and pricing, and make their use a submission condition. Set page limits and a required proposal structure that mirrors your evaluation criteria. This lets evaluators compare vendors side by side instead of hunting through different formats.