If you have ever sent the same website brief to five development agencies and received quotes ranging from a few thousand to well over fifty thousand, you already know the problem. The agencies were not pricing the same project. Each one filled the gaps in your brief with its own assumptions, and the numbers reflect those assumptions far more than they reflect skill or honesty.
The short answer to how you write a website development RFP that gets accurate, comparable quotes: describe the business outcome first, list the features and integrations you actually need with a clear must-have versus nice-to-have split, state your budget range and deadline honestly, define what "done" means, and ask every vendor to answer the same structured questions in the same format. A good request for proposal is not long. It is specific in the places where ambiguity costs money and open in the places where you want the agency's expertise.
This guide gives you a section-by-section RFP template, the details that move a quote the most, a scoring method for comparing proposals, typical timelines for the process, and the mistakes that make good agencies decline to bid. It works for marketing websites, WordPress and WooCommerce builds, custom Laravel platforms and web applications alike.
Why most website RFPs produce quotes you cannot compare
Vague briefs create wide price spreads for a predictable reason: every unknown is a risk, and agencies price risk differently. One agency assumes you will supply all content and photography; another assumes it will write and source everything. One assumes your product catalogue can be imported from a clean spreadsheet; another assumes it will need to be cleaned by hand. One assumes "integrate with our CRM" means a contact form that pushes leads; another assumes a two-way sync with custom fields and error handling.
None of them are wrong; they answered different questions. The typical causes are:
- Feature lists without depth. "Customer accounts" can mean a login page or a full portal with order history, saved addresses, invoices and role permissions.
- No budget signal. Without a range, agencies cannot tell whether you want a lean template-based site or a fully custom build, so they guess.
- Unclear ownership of content and data. Content migration and copywriting are frequently the largest hidden line items.
- Undefined integrations. Each third-party system adds discovery, development and testing time, and the effort varies by an order of magnitude depending on what the integration must do.
- Free-form responses. When every proposal uses a different structure, you end up comparing marketing documents instead of plans.
The fix is answering the questions agencies would otherwise guess at, and asking for responses in a fixed shape.
Before you write: three decisions to make internally
An RFP written before these decisions are settled tends to change halfway through the process, which forces vendors to re-quote and wastes everyone's time.
1. Who owns the project and who signs off
Name one decision-maker and list the people who must approve design, content and launch. Agencies price stakeholder complexity. A project with one owner and a weekly review is cheaper and faster than one that needs sign-off from marketing, sales, IT and a regional team at every stage.
2. What success looks like in measurable terms
Decide what the new site must achieve: more qualified leads, a higher conversion rate, fewer support tickets, faster page loads, less time spent by your team on manual updates, or a platform your agency clients can resell. You do not need to share every internal target, but you need to know them, because they decide which features are essential.
3. Your realistic budget and deadline
Agree internally on a budget range and whether the deadline is fixed (a product launch, a trade show, the end of a hosting contract) or flexible. If you have no idea what a project like yours costs, run a rough estimate first; a tool such as the project cost estimator gives you a starting range before you speak to anyone.
The website development RFP template, section by section
The structure below fits most projects in roughly six to twelve pages. Use the headings as they are, and delete anything that does not apply rather than padding it.
Section 1: Company overview and project background
Two or three short paragraphs. Who you are, who your customers are, what you sell or offer, and why you are doing this project now. Include the trigger, such as a rebrand, a platform that has reached its limits or a migration, because it tells an agency where the real risk sits.
Section 2: Goals and success measures
List three to five goals in priority order. Make them concrete enough to design against, for example "increase demo requests from organic traffic", "let the marketing team publish landing pages without a developer" or "support wholesale pricing for approved trade accounts". If you have baseline figures you are comfortable sharing, such as current conversion rate or monthly order volume, include them.
Section 3: Audience and key user journeys
Describe your main audience groups and the three to five journeys that matter most: a first-time buyer finding a product and checking out, a returning customer reordering, a prospect booking a call, an editor publishing a case study. Journeys are more useful to an agency than a list of page names because they reveal the logic behind each page.
Section 4: Current setup
This section removes more uncertainty than any other. Include:
- Current platform, hosting provider and approximate age of the site.
- Approximate number of pages, blog posts, products, product variations, customers and orders that need to move.
- Plugins, apps or custom code the site relies on today.
- Monthly traffic range and where it comes from, especially organic search.
- Known problems: slow pages, checkout errors, fragile updates, security issues.
- Who has access to the domain, hosting, analytics and code repository.
If you are migrating, say so clearly. Migration work, including redirects and data mapping, is often underestimated, and the agencies that ask the most questions about it are usually the ones that will do it properly.
Section 5: Scope and functional requirements
Write requirements as a table or list with three columns: the feature, a one-sentence description of what it must do, and a priority. Use a simple priority scale:
- Must have: the site cannot launch without it.
- Should have: important, but could follow shortly after launch.
- Nice to have: only if budget allows.
Ask vendors to price must-haves and should-haves separately. This single change makes quotes far easier to compare and gives you a natural way to trim scope without starting over.
Section 6: Integrations
List every system the site must connect to, and for each one state the direction and the data involved. Typical examples are CRM, email marketing, ERP or inventory, payment gateways, shipping and fulfilment, accounting, booking tools, analytics and single sign-on. "Send new orders to the ERP every five minutes and pull back stock levels" is quotable. "ERP integration" is not.
Section 7: Content, design and brand
State who is responsible for copywriting, photography, video and content entry, and how much content exists already. Say whether you have brand guidelines, a design system or an existing Figma file, or whether brand work is part of the project. If you need multiple languages or currencies, list them here.
Section 8: Technical and non-functional requirements
Cover the expectations that apply across the whole build:
- Preferred platform, or an explicit request for the agency's recommendation with reasons.
- Performance targets, for example Core Web Vitals in the good range on mobile.
- Accessibility level, commonly WCAG 2.2 AA.
- Security and compliance needs, such as GDPR consent handling or PCI scope for payments.
- Browser and device support.
- Hosting preference and who will manage it after launch.
- Code ownership, repository access and documentation expectations.
Section 9: Budget, timeline and commercial terms
Give a budget range, a target launch date and whether the date is fixed. State your preferred engagement model: fixed price for a defined scope, time and materials, a paid discovery phase followed by a fixed build, or a build followed by an ongoing retainer. Mention payment milestones you expect, warranty period, and whether you want post-launch support quoted.
Section 10: Proposal requirements and evaluation process
Tell vendors exactly what to submit and how you will judge it. This is covered in detail below because it is the part that makes proposals comparable.
Section 11: Timeline for the RFP itself
List the dates: RFP issued, deadline for questions, answers shared with all vendors, proposal deadline, shortlist presentations, decision and project start. Share every answer to a vendor question with every vendor, so the playing field stays level.
Should you include your budget in the RFP?
Yes, in almost every case. Many buyers hold back the budget hoping to get a lower price, but it usually has the opposite effect. Without a range, agencies either quote defensively high to cover the unknowns, or quote low with thin scope and recover the difference through change requests later.
A range lets an agency show you what it would build for that money, which is the comparison you actually want. A useful way to frame it is: "Our budget for design and build is between X and Y. Please tell us what you would recommend within that range, and what you would add or remove if it were 20% higher or lower." The answer reveals how each vendor thinks about trade-offs.
Typical 2026 ranges for agency-built projects, depending heavily on region, scope and content effort:
| Project type | Typical budget range | Typical build time |
| Small marketing site on WordPress (10 to 20 pages, existing brand) | $4,000 to $15,000 | 4 to 8 weeks |
| Larger content or lead-generation site with custom blocks and integrations | $15,000 to $45,000 | 8 to 14 weeks |
| WooCommerce store with custom theme and standard integrations | $10,000 to $50,000 | 8 to 16 weeks |
| B2B or high-volume ecommerce with ERP sync, custom pricing or portals | $40,000 to $150,000+ | 3 to 6 months |
| Custom web application or SaaS MVP on Laravel | $30,000 to $120,000+ | 3 to 6 months |
These are planning ranges, not quotes.
The details that move a quote the most
If you only have time to be precise about a few things, be precise about these. Each one regularly changes estimates by a large margin.
- Content migration volume and condition. Moving 200 clean posts is a scripted job. Moving 2,000 posts with inconsistent formatting, embedded shortcodes and broken images is a project of its own.
- Number and depth of integrations. Each two-way integration needs mapping, error handling, retries and monitoring.
- Custom versus adapted design. A design built from scratch for every template costs more than adapting a design system or a premium theme.
- Product complexity in ecommerce. Variable products, bundles, subscriptions, tiered or customer-specific pricing and multi-warehouse stock all add logic and testing.
- User roles and permissions. Every additional role, such as wholesale buyer, sales rep or regional editor, multiplies the scenarios that must be built and tested.
- Multilingual and multi-currency. These affect content structure, SEO setup, checkout and ongoing editorial workload.
- Approval process. More stakeholders mean more review rounds, more meetings and longer timelines.
- Post-launch expectations. Whether you want a warranty period only, or ongoing maintenance, monitoring and improvements on a retainer.
What to ask vendors to submit
Give every agency the same response template. Limit the length, for example ten pages plus appendices, so you are reading plans rather than brochures. Ask for:
- Understanding of the project: a short summary in their own words, plus any risks or gaps they see in your brief. The quality of this section tells you more than any portfolio.
- Recommended approach and platform: with reasons, and alternatives they considered.
- Phased plan: discovery, design, build, content, testing, launch and handover, with duration for each.
- Itemised pricing: broken down by phase and by must-have versus should-have scope, with assumptions listed explicitly.
- Team: who will actually work on the project, their roles and how much of their time is allocated. Ask whether any work is subcontracted.
- Relevant work: two or three comparable projects, ideally with a reference you can contact.
- Process: how they handle communication, change requests, QA, staging environments, code review and deployment.
- Support and maintenance: warranty terms and optional ongoing support pricing.
- Exclusions: what is not included, stated plainly.
The assumptions and exclusions lists are the most valuable part of any proposal. Two quotes at the same price can describe very different projects, and the difference is usually hidden there.
How to score and compare proposals
Decide your scoring weights before proposals arrive, so the most polished pitch does not quietly reset your priorities. A simple weighted scorecard works well:
| Criterion | Suggested weight | What a strong answer looks like |
| Understanding of goals and risks | 25% | Identifies gaps in your brief and asks sharp questions |
| Approach and technical fit | 20% | Clear platform reasoning, realistic phasing, sensible trade-offs |
| Relevant experience | 15% | Comparable projects, checkable references |
| Team and process | 15% | Named roles, QA and deployment practices, clear communication rhythm |
| Price and transparency | 15% | Itemised, assumptions listed, change process defined |
| Support and long-term fit | 10% | Clear warranty, maintenance options, code ownership |
Have at least two people score independently, then discuss any large disagreements.
Normalise the prices before comparing
Before you compare totals, line up the quotes against your scope list. Mark which features each vendor included, excluded or treated as optional, and add a rough allowance for anything missing. The cheapest proposal on paper is often the most expensive once the excluded content migration or integration work is added back.
Treat outliers as information
A quote far below the others usually means a misunderstanding of scope, a template-based approach, or a plan to recover margin through change requests. A quote far above the others may reflect a more thorough approach or an agency that does not want the work. Ask both to explain their assumptions before you rule them in or out.
A realistic RFP timeline
A typical sequence for a mid-sized project:
- Week 1 to 2: internal decisions, requirement gathering and drafting the RFP.
- Week 3: send the RFP to four to six pre-qualified agencies.
- Week 3 to 4: question period; share all answers with all vendors.
- Week 5 to 6: proposals due; score independently.
- Week 6 to 7: shortlist two or three for a presentation and a working session.
- Week 7 to 8: reference checks, contract negotiation and kick-off.
For smaller projects the whole process can run in three to four weeks.
Consider a paid discovery phase instead of a full RFP
For complex builds, such as custom web applications, B2B ecommerce with ERP integration or a platform migration, no RFP can capture every detail up front. In those cases a short paid discovery phase with one or two shortlisted agencies often produces a more reliable plan than a long tender.
Discovery typically takes two to four weeks and costs a fraction of the build, commonly in the range of 5% to 10% of the expected project budget. The output is a prioritised scope, technical architecture, risk list and a fixed or tightly ranged estimate. You own the output, so you can take it to another vendor if the fit is not right. A lighter RFP is then used mainly to choose who runs discovery.
Common RFP mistakes that drive good agencies away
Experienced agencies decline many RFPs. These are the patterns that most often make them pass:
- Asking for free design work. Requesting homepage mock-ups as part of the proposal attracts agencies with spare capacity rather than the best fit, and speculative designs are made without any real research.
- No budget and no decision-maker. Together these signal that the project may not happen.
- Unrealistic deadlines with fixed scope. A fixed date, fixed scope and fixed price leaves no room to absorb the unknowns every project has.
- Too many vendors. More than six bidders tells each agency its odds are low.
- No time for questions. The questions agencies ask are one of the best signals you get about how they think.
Special case: RFPs for agencies hiring a white-label partner
If you run a marketing or design agency and are looking for a development partner to build under your brand, the RFP looks slightly different. You are choosing a team for a stream of projects, not one build, so the questions shift toward process and fit:
- How do they handle client-facing confidentiality, unbranded staging environments and handover documentation?
- Can they work inside your project management tool and communication channels?
- What are their typical turnaround times for small changes versus new builds?
- How do they price: per project, per hour, or a monthly retainer with a block of hours?
- What coding standards, QA checklists and review practices do they follow?
- Will you have a consistent lead developer or project manager?
A small paid pilot project is often the best final step: it shows you real communication, code quality and timekeeping in a low-risk setting. If this is your situation, SquartUp's white-label WordPress and WooCommerce development page outlines how that kind of partnership usually works.
How SquartUp responds to an RFP
When SquartUp receives a brief, the first thing we send back is usually a list of questions rather than a price, because the questions are where accurate estimates come from. We then itemise the proposal by phase and priority, list our assumptions and exclusions explicitly, and recommend a paid discovery phase where the scope is too uncertain to fix responsibly. It is a habit built over 50+ projects for 25+ clients in 12+ countries. You can see the kinds of work we take on in our case studies and the full range of services.
Ready to get a quote you can trust?
If you have a draft brief, an RFP in progress or just a rough idea of what you need, send it over. We will review it, point out the gaps that would make quotes hard to compare, and give you a clear, itemised estimate. Contact SquartUp to start the conversation.