An RFP (request for proposal) gives web designers a shared brief for responding to your website project. It is useful when you need to compare suppliers, or when a build involves several audiences, integrations or decision-makers. A good website design RFP explains the business problem, who the site must serve, what it needs to do and how you will choose a partner; it does not prescribe every design choice. Start by gathering input from the people who own the website, create its content and rely on its enquiries or sales. Separate essential requirements from preferences, and identify what is not included, such as writing, migration or ongoing maintenance. Before inviting proposals, establish a realistic project budget and decide whether to share a range so suppliers can recommend a suitable scope. Ask respondents to state assumptions, exclusions, dependencies and recurring third-party costs rather than treating a headline build fee as the full cost of ownership. Give every supplier the same information and a reasonable response deadline. The guide below explains what to include, how to request comparable proposals and how to assess them fairly. Your RFP should reduce ambiguity while leaving capable suppliers room to recommend a practical approach.
Content
Define the outcomes
Start with the business need, not the website features
Before asking suppliers to recommend a design or platform, explain why your business is considering a website project now. Describe the problem or opportunity in practical terms: perhaps customers struggle to find accurate service information, staff spend time answering the same basic questions, or the current site is difficult to update. Include relevant context, such as a change in services, an outdated brand or a need to make important information easier to access. Be specific about what is not working, without assuming that a particular feature is the answer.
This gives potential suppliers a shared starting point and helps them propose work that addresses the underlying need. For example, if visitors are unsure which service suits them, the need may be clearer service explanations and a straightforward path to making an enquiry—not simply more pages. Note important boundaries too, such as internal approval processes, limited staff time for supplying content, or a fixed date linked to a business event. These details can affect the recommended approach and should be visible from the outset.
Describe the people the site needs to serve
Identify your intended audiences and what each needs to do or understand. Avoid relying only on broad labels such as “the general public”. Consider the different groups who use your site—for instance, prospective customers comparing services, existing customers looking for practical information, or referral partners checking your credentials. For each priority audience, describe their likely questions, the information they need and the next step you want to make clear. If audiences have different needs, state which ones matter most so suppliers can make informed decisions about content structure and navigation.
Use what you already know to support these descriptions: common questions from phone calls, customer feedback, search queries or observations from staff can all be useful. You do not need formal research to write a useful brief, but distinguish evidence from assumptions. If you are unsure about an audience’s needs, say so. A supplier can then identify that uncertainty and suggest a suitable way to investigate it, rather than treating an untested assumption as a settled requirement.
Define how you will recognise success
Turn the business need into a small set of outcomes that you can review after launch. Outcomes describe a change that matters to the business or its audiences, rather than a list of deliverables. “Publish a new website” is a deliverable; “make it easier for prospective customers to understand our services and submit a relevant enquiry” is an outcome. You can include both, but keep them distinct so the project is not judged only by whether the site was built.
For each outcome, decide what evidence would help you assess it, who will review that evidence and when. Depending on the goal, evidence might include whether customers can find key information in usability checks, whether enquiry forms capture the details staff need, or whether staff can make routine content updates. If you have relevant baseline information, record it and explain how it was gathered. Avoid promising a particular level of traffic, sales or search visibility: these depend on factors beyond the website project and should not be treated as guaranteed outcomes.
Keep the initial success measures achievable and relevant to the project. A clear account of the business need, priority audiences and review criteria helps suppliers explain their recommendations and gives both sides a common basis for decisions during delivery and after launch.
Set the project scope
Turn the project into a clear scope
Give suppliers enough detail to estimate the work without dictating every design decision. Start with the pages your website needs, such as a home page, service pages, an about page, contact details, FAQs or case studies. Note whether existing pages are being replaced, rewritten, moved or retained. A page list helps suppliers understand the size of the project and identify gaps, but it should not prevent them from recommending a simpler structure if it meets your goals.
Describe features in terms of what visitors or staff need to do. For example, say whether people need to submit an enquiry, download a document, filter listings or make a booking. Specify what the feature must achieve rather than naming a particular plugin or technical solution, unless you have a sound reason to require it. If you have a preference, label it as such so suppliers can explain alternatives and trade-offs.
Be equally clear about content and integrations. State who will write, edit, approve and supply text, images and other materials, and whether existing content needs review or migration. List systems the website must connect with, such as a customer database, booking platform or payment provider. For each connection, describe the information that needs to pass between systems and identify any access, fees or assistance you already know will be required. Suppliers may need to confirm technical details before giving a firm estimate.
Separate requirements into essentials and optional items. Essentials are necessary for launch or for the website to perform its agreed business role. Optional items can be priced separately, deferred or removed without making the core project unusable. This distinction lets you compare proposals fairly and avoid spending the available budget on features that are useful but not critical.
- Essential: pages, functions and integrations that must be included in the initial delivery.
- Optional: enhancements that may be considered if budget and timing allow.
- Constraints: requirements suppliers must account for, such as an existing domain, WordPress platform, content-management needs, privacy obligations, accessibility expectations or a fixed launch date.
Hypothetical example: A local consultant might require service pages, enquiry forms and an editable WordPress site, while treating online booking as an optional priced item. The RFP could also state whether the consultant will provide page copy, whether existing enquiries need to be transferred, and whether the booking system already in use needs to connect to the new site. This gives suppliers a consistent basis for estimating the core project and makes the cost of adding booking easier to assess.
Establish and communicate a workable budget
Set a budget before issuing the RFP, rather than choosing a figure solely because it matches a supplier’s proposal. Start with the amount your business can responsibly commit to the project, then check it against the likely scope and the value of achieving the stated outcomes. Include the one-off build and any work your team may need to buy separately, such as copywriting, content migration or specialist integration. Also consider costs that continue after launch, including hosting, maintenance, licences and renewals. Separate these recurring expenses from the initial project allowance so you can judge affordability over time.
Ask internally who approves the spend and whether the budget needs to include GST. Decide how much flexibility you have for scope changes or unexpected work; do not commit the full available funds to optional features before essentials are covered. If the project could be delivered in stages, identify what must be in the first release and what could reasonably wait. This helps you distinguish a genuine minimum viable scope from a wish list, and gives suppliers a useful basis for proposing alternatives.
In the RFP, sharing a realistic budget range is usually more useful than asking suppliers to guess what you can afford. Explain whether the range is for the initial project only or also includes specific ongoing costs, and state whether GST is included. Make clear that the range is a planning guide, not a request to spend the maximum: suppliers should price the work they recommend and explain what is included. If you are not ready to disclose a figure, ask for a core proposal plus separately priced options or staged approaches, and compare these against your internal limit. A range cannot replace a detailed scope, but it can help suppliers avoid proposing work that is either unaffordable or too limited to meet your needs.
Hypothetical example: Suppose a small business has provisionally allocated $12,000–$16,000 for the initial website project. Those figures are illustrative assumptions, not a market estimate. Its RFP could state that this range excludes ongoing hosting and maintenance, then ask suppliers to price required pages and forms as the core scope, with booking and additional content work shown separately. The business can then assess scope choices against its approved allowance rather than comparing unexplained headline totals.
Record assumptions as well as requirements. If you do not yet know how much content needs rewriting, say so and ask suppliers to identify the assumption in their proposal. Flag known dependencies, including access to the current website, domain or third-party accounts. Where a constraint is firm, explain why it matters; where it is negotiable, say so. A scoped RFP should make priorities and financial boundaries visible while leaving room for a supplier to recommend a practical approach.
Clarify delivery and support
Agree how the work will be delivered—and supported
A proposal is easier to assess when it explains not just what will be built, but how the work will progress and what happens after launch. Ask each supplier for a proposed sequence of stages, such as discovery, design, development, content entry, testing and launch. For each stage, request an estimated duration, the work or approval needed to move forward, and any dependencies. Ask suppliers to state when their schedule can begin and what could affect it; do not treat an indicative timeline as a guaranteed launch date.
Set out your own responsibilities too. Identify who will make decisions, supply website text and images, provide access to existing systems, and approve designs or content. Agree how feedback will be collected and how quickly your team expects to respond. If several people need to approve the work, name a project contact who can consolidate their feedback. Ask the supplier to describe the decisions and materials they need from you, and when delays or changes might affect the schedule or cost.
Plan migration, testing and handover
If the project involves replacing an existing website, define the migration rather than assuming it is included. Note what should be transferred, such as pages, images, blog posts, forms or other relevant content, and identify features that need to be recreated or reviewed. Ask how existing page addresses will be handled, including whether redirects are proposed where URLs change, and how the new site will be checked before launch. Clarify who will arrange domain and DNS changes, and whether business email relies on settings that must be preserved. Request a plan for checking the live site and a way to raise issues after launch.
Specify the handover and training you need. Ask whether training is included, who it is for, which routine tasks it covers, and whether it will be delivered as a live session, written instructions or another agreed format. State who will receive administrative access and what documentation you expect. This helps your team understand how to manage everyday website content and where to turn when a task requires technical assistance, without assuming every supplier includes the same level of training or ongoing help.
Make ongoing support and costs explicit
Ask suppliers to explain hosting and ongoing maintenance separately from one-off project work. Request the hosting arrangement, account ownership, renewal frequency and any relevant limits or exclusions. For maintenance, ask what work is included—for example, updates, backups or checks—and what is excluded or charged separately. Clarify how support requests are submitted, the stated support hours, any response-time terms, and how urgent issues are handled. Ask who is responsible for monitoring backups and whether a restoration process is described; do not assume that having a backup automatically means restoration is included.
Request a clear view of ongoing and potential costs: recurring hosting or maintenance fees, renewal charges, third-party licences or services, and the rates or approval process for work outside the agreed scope. Ask which services are optional, what happens if you change supplier, and whether you retain access to the domain, website files and relevant accounts. Check how these recurring commitments fit your operating budget as well as the initial project allowance. A written breakdown gives you a realistic basis for comparing total costs and helps prevent proposals from appearing equivalent when they include different levels of support.
Finally, ask what is required from your business after launch. Your team may be responsible for routine content changes, approving updates or renewing third-party services, while a supplier may offer separate support for technical work. Clarify how either arrangement works and how you can request help if needs change. A clear division of responsibility makes it easier to plan staff time and ongoing expenditure, and reduces the risk of assuming that an activity is covered when it has not been included in the proposal.
Request comparable proposals
Give every supplier the same response framework
To compare proposals fairly, ask each supplier to respond to the same brief in a consistent format. Set out the headings you want them to use, such as understanding of your goals, proposed approach, deliverables, timing, costs, assumptions, exclusions and dependencies. This makes it easier to see where proposals differ, rather than trying to compare documents that describe different scopes in different ways. You can also ask suppliers to identify which requirements their proposal meets and where they recommend an alternative.
Provide the same project information to every invited supplier, including your requirements, constraints, budget guidance and any known dates or decision processes. If you answer a supplier’s question or clarify the brief, share the answer with all suppliers. This reduces the risk of one proposal being based on information the others did not receive. Give suppliers a clear submission deadline and contact point, and explain whether you will accept questions after the brief is issued.
Ask for a clear breakdown of delivery and cost
Ask suppliers to explain how they would deliver the work, including the main stages, the decisions or approvals they need from you, and what they expect you to provide. Clarify who is responsible for supplying and approving text, images and other content, and who will arrange access to existing website or domain accounts. Ask how the proposed approach addresses your stated requirements, rather than accepting a list of services without an explanation of how they fit the project. If a supplier proposes options or stages, request the scope and price for each so you can assess them against your priorities.
Request itemised costs that distinguish project fees from ongoing or third-party expenses. Ask suppliers to identify which costs are one-off, recurring or dependent on usage, and to state whether GST is included. If a feature is optional, ask for its cost to be shown separately so you can compare the core proposal with possible additions. Ask what would trigger extra charges, how changes to scope are handled, and whether ongoing work is included or would need a separate agreement. Do not assume that a low initial fee includes hosting, maintenance, licences, content work or future support; ask what is and is not covered.
Ask each supplier to list assumptions, exclusions and dependencies explicitly. Assumptions might concern the condition of your existing website, the availability of content or the number of revision rounds included. Exclusions could include work you have not requested or that the supplier does not intend to provide. Dependencies are things the project relies on, such as your team supplying materials or granting access by an agreed date. Request the likely effect if an assumption proves incorrect or a dependency is delayed, including any change to scope, timing or cost.
Set a clear process for questions and submissions
Explain how proposals should be submitted, who will receive them and what the deadline is. If you expect a presentation or meeting as part of the process, say whether it is required and what suppliers should prepare. Keep the process proportionate to the project: a small business RFP need not demand lengthy documentation that does not help you decide. Be clear about the expected level of detail, any page or file requirements, and when you expect to make a decision. If the timetable is provisional, state that rather than implying a commitment you cannot meet.
For a practical comparison, ask suppliers to flag any requirement they cannot meet, any item that needs further investigation, and any alternative they recommend. They should explain the trade-off and identify whether the alternative changes the price or scope. If the proposal depends on information that is not yet available, ask the supplier to explain what needs to be confirmed and how that uncertainty affects the estimate. This gives you specific points to discuss instead of discovering material differences after selecting a supplier.
Before issuing the request, check that the response format is detailed enough to support a decision but not so burdensome that it discourages suitable small suppliers. A concise, shared structure, transparent budget guidance and a clear cost breakdown help you compare proposals on scope, delivery and fit—not price alone. They also provide a clearer basis for agreeing the work if you proceed.
Evaluate and shortlist
Set a consistent basis for assessment
Decide how you will assess proposals before you read them. Start with any essential requirements that a supplier must meet, such as a necessary integration, a workable delivery timeframe or a clear plan for transferring your existing website. Treat these as pass-or-fail checks, and explain them in the RFP so suppliers know what matters. Then assess the remaining proposals against criteria that reflect your project’s priorities. Possible criteria include understanding of your business and audiences, quality of the proposed approach, relevant experience, accessibility and security considerations, project management, support arrangements and price.
Write down what good evidence would look like for each criterion. A supplier’s claim that a proposed feature is straightforward is less useful than an explanation of how it will work, what is included and what your team needs to provide. If you use scores or weights, agree on them in advance and apply them consistently. Any numerical weights are your own assessment choices, not an objective measure of supplier quality. Keep notes that link each score to information in the proposal or a follow-up answer, rather than relying on general impressions.
Use a shared assessment sheet so everyone involved considers the same requirements. Record whether each essential item is met, where the proposal addresses each criterion, what remains unclear and any risks or dependencies. If a proposal leaves an important point unanswered, mark it as unknown rather than assuming the supplier will include it. This makes it easier to identify a shortlist based on the evidence available and to explain your decision internally.
Ask questions that reveal how the work will be delivered
Prepare a consistent set of questions for shortlisted suppliers. Ask them to explain how they would handle your highest-priority requirements, what decisions or materials they need from you, and how they would manage changes if the scope develops. Ask who will lead the work, how progress and approvals will be handled, and what happens if a key milestone is delayed. Questions about content migration, testing, launch, training and post-launch support can expose differences that are easy to miss in a high-level proposal.
Ask suppliers to clarify assumptions and exclusions in writing. For example, establish whether content entry, redirects, third-party charges, hosting, maintenance and staff training are included, optional or outside the proposal. Ask what ongoing work is available after launch, how it is requested and charged, and who will be responsible for routine updates. These questions help you understand the practical commitment on both sides without assuming that a particular service or feature is included.
Give each shortlisted supplier the same information and a reasonable opportunity to respond. Record answers alongside the original proposal, noting any changes to scope, timing or cost. If a supplier revises an offer, ask for the updated inclusions and exclusions rather than comparing a revised price with an earlier, differently scoped proposal. Where the budget range has not produced a suitable core proposal, discuss which requirements could be staged or revised, while keeping essential outcomes in view.
Compare value, not just the headline price
Compare proposals on a like-for-like basis. Check the total project cost against the requested scope, then identify likely ongoing costs and optional items you may need. A lower initial price may reflect a narrower scope, more responsibilities for your team or costs that begin after launch; a higher price is not automatically better value. Consider how well each proposal addresses your stated outcomes, the clarity of its delivery plan and the evidence supporting its claims. If proposals differ substantially in approach, note the trade-offs rather than forcing them into a simple price ranking.
Before selecting a supplier, resolve material uncertainties, document the agreed scope and responsibilities, and confirm that the proposal aligns with your RFP and approved budget. Check that any optional work, recurring services and exclusions are understood by the decision-makers. The aim is a shortlist—and ultimately a decision—that you can justify from clear, comparable information and that fits both the project’s needs and your business’s capacity to manage it.
Conclusion
Conclusion
A focused, fair RFP gives potential website partners the same clear brief to respond to, making proposals easier to compare on their approach, assumptions, costs and fit—not price alone. It helps you define the outcomes, distinguish essential scope from optional work, establish an affordable budget and clarify what support you may need after launch. Sharing a realistic budget range, with its boundaries explained, can help suppliers recommend an appropriate scope; asking for priced options is useful when you prefer not to disclose a figure.
Before sending your RFP, check that the requested information is relevant to your decision and that each supplier has a reasonable opportunity to answer it. Set a response deadline, explain how you will assess proposals, and invite suppliers to identify uncertainties rather than make unsupported assumptions. When you have shortlisted a partner, use the proposal and follow-up questions to confirm responsibilities, deliverables, timing, costs and ongoing support in writing. That shared record can form a practical starting point for agreeing the project plan and working relationship. A clear brief will not remove every uncertainty, but it can help both sides begin with a common understanding of what the website project is expected to achieve and what the business can commit to delivering.
Explore related information: Booking Website Design & Development; Web Design Sunshine Coast.



