Client Requirement / RFP


Phase: Pre-sales and initiation | Audience: Client-facing | Project: WEB-2026-01 Corporate Website Development


Understand it first

In simple words: An RFP (Request for Proposal) is a document the client writes to explain what they need and to invite companies to send a quote. It is the starting point of most client projects.

Think of it like: Before renovating your kitchen, you write down what you want (new cabinets, better lighting, budget around ₹2 lakh) and send it to three contractors to get quotes. That note is your RFP.


When is it created?

Before the project exists, during pre-sales (5 Sep 2026)

Who prepares it?

The client (Head of Marketing)

Who approves or uses it?

Read by every company that wants to bid, including us

What happens next?

We study it and prepare our Technical and Commercial Proposals


How it connects to other documents

  1. Its requirements (FR-01 to NFR-03) are answered one by one in the Technical Proposal.
  2. Its budget range (₹5–8 lakh) guides the price in the Commercial Proposal.
  3. Its objectives later become success measures in the Project Charter.


The sample document

Below is the actual document for project WEB-2026-01. Read the purpose first, then go through each numbered section.

Issued by: [Client Name] Pvt. Ltd.


Purpose: Issued by [Client Name] Pvt. Ltd. inviting vendors to propose the design and development of a new corporate website.

Item


Detail


Document no.

WEB-2026-01/RFP

Version

1.0

Date

5 Sep 2026

Owner

Head of Marketing, [Client Name]

Audience

Client-facing

Phase

Pre-sales and initiation


1. Background

Our current website was built in 2018. It is not mobile-friendly, loads slowly, and every text change needs a developer. Enquiries through the website have fallen, while over 70% of our visitors now arrive on mobile phones.


2. Objectives

#


Objective


How we will measure it


O1

Work well on every device

All pages usable on phones, tablets and desktops

O2

Let marketing update content without developers

Marketing team publishes a blog post unaided

O3

Generate more enquiries

30% more contact-form enquiries within 6 months of launch

O4

Load fast

Pages load in under 3 seconds on a 4G connection


3. Scope requested

About 10 pages: Home, About Us, four Services pages, Portfolio, Blog (listing and post), and Contact Us.


4. Requirements

ID


Requirement


Priority


FR-01

Responsive design for mobile, tablet and desktop

Must

FR-02

Content management system for editing pages and blog

Must

FR-03

Contact form with email notification to sales team

Must

FR-04

Blog with categories

Must

FR-05

Portfolio gallery of completed projects

Should

FR-06

Google Analytics tracking

Must

FR-07

On-page SEO (titles, descriptions, sitemap)

Must

FR-08

Secure site (HTTPS)

Must

NFR-01

Page load under 3 seconds on 4G

Must

NFR-02

Basic accessibility (readable contrast, alt text, keyboard use)

Should

NFR-03

Works on latest Chrome, Safari, Edge and Firefox

Must


5. Timeline and budget

  1. Vendor selection by 30 Sep 2026; project start in early October.
  2. Website live by mid-December 2026, before the January sales season.
  3. Indicative budget: ₹5–8 lakh including GST.


6. Proposal submission

  1. Submit a technical proposal and a commercial proposal as separate documents.
  2. Deadline: 19 Sep 2026, 6:00 pm, by email to [procurement email].
  3. Questions may be sent until 12 Sep 2026; answers will be shared with all vendors.


7. Evaluation criteria

Criterion


Weight


Understanding of requirements and solution

30%

Relevant experience and team

20%

Project approach and timeline

10%

Commercials

40%

Total

100%


WEB-2026-01/RFP · v1.0 · Client-facing. Bracketed items such as [Client Name] are placeholders.


Key takeaways

  1. The RFP is written by the client, not by the PM.
  2. Read the objectives and evaluation criteria carefully: here commercials carry 40% of the score.
  3. 'Must' requirements are non-negotiable; 'Should' ones are nice to have.


Common mistakes to avoid

  1. Skipping the evaluation criteria and writing a proposal that does not address them.
  2. Missing the submission deadline or the question window.
  3. Assuming requirements that the client never wrote down.


Next lesson: 7. Technical Proposal