WEB DESIGN & DEVELOPMENT / A PRACTICAL ANSWER
When do you need a website RFP?
The short answer
A website RFP is useful when several providers must respond to the same structured requirements or your organisation needs a documented selection process. A smaller project may need only a clear brief and comparable proposals. Use the document to clarify the buying decision, rather than specifying technology before the problem is understood.
What to agree
Describe the business situation, audiences, required journeys, constraints and selection criteria. Include existing systems, content responsibilities and the information available for discovery. Let suppliers identify assumptions and suggest alternatives where the requirement is still uncertain.
How to decide
Keep mandatory requirements separate from preferences. Decide how responses will be assessed before they arrive, and leave room for clarifying questions. Requiring a large unpaid design exercise can reward presentation effort while revealing little about the actual delivery relationship.
ILLUSTRATIVE EXAMPLE / NOT A CLIENT RESULT
Make it concrete.
A firm replacing an established content platform may need formal security, procurement and integration responses. A three-page service website may be easier to commission through a short brief, a conversation and a scoped proposal.
Before you commission
- Give every shortlisted supplier the same inputs.
- State the criteria and decision timetable.
- Ask for risks, dependencies and exclusions explicitly.
A plain-text worksheet. Downloading does not send us your details.
FROM THE QUESTION TO THE WORK
A useful next step.
Bring the decision, the existing situation and the information you have. We can help define a scope before you commit to a wider project.
Explore the relevant service