How to Write a Website RFP Agencies Can Actually Price

Last updated: October 2026. Procurement teams at mid-sized South African companies often inherit a website RFP template written for office furniture. Vendors are asked for “company profile”, “BBBEE certificate” and “three references” — but not whether Salesforce leads must dedupe, who holds DNS, or how legal approves cookie consent. Agencies then guess, pad, or decline. Marketing ends up comparing three incompatible numbers and choosing the lowest as if risk were equal.

At Dsignr Digital in Rosebank we respond to structured RFPs faster and more accurately than to vague “submit your best price for a modern site” emails. The difference is not length. A usable RFP fits in eight to twelve pages plus appendices, and it forces every bidder to price the same assumptions.

Before you circulate anything, align internally on rebuild versus iteration. If you are still selecting a partner category, read how to choose a web design company in South Africa — the RFP should reflect what that article recommends you verify in writing.

Procurement can help by refusing to open the RFP until marketing and IT co-sign a one-page assumptions sheet: domain owner, CMS preference (if any), launch blackout dates, and languages. That sheet becomes appendix A so vendors cannot claim they were not told about SSO or PayGate testing requirements.

Good RFPs also define what “done” means at handover — admin training recorded, runbook for backups, analytics validated against a baseline week, hypercare hours included. Without that, you compare creative pitches and inherit three different definitions of launch. Procurement can score handover deliverables line-by-line instead of debating subjective “quality”.

Include these sections in the body of the RFP — not buried in an appendix agencies will skip:

• Business outcomes — What must improve in 12 months: qualified leads, self-service downloads, hiring applications, partner onboarding — with current baselines if known.
• Audience and journeys — Primary users (e.g. CFOs, fleet managers, candidates), devices, languages, and proof points they need before contact.
• Functional requirements — CMS roles, approval workflows, search, personalisation (if any), forms, calculators, gated content, and must-have third-party systems.
• Integrations — CRM, marketing automation, SSO, HR ATS, ERP product data — including who provides API keys and sandbox access.
• Non-functional requirements — Uptime expectation, backup RPO/RTO, hosting region, accessibility target (WCAG 2.2 AA is common for corporate), performance budget on mobile.
• Compliance — POPIA consent model, cookie categories, records of processing, privacy policy update responsibility — reference POPIA and your internal legal standards.
• Ownership and handover — Domain registrant, repo access, CMS admin, hosting account, licence keys, documentation deliverables.
• Project governance — Steering cadence, decision makers, max revision rounds, change control, and acceptance criteria for go-live.
• Commercial — Budget band or ceiling, payment milestones, warranty/hypercare period, optional care retainer line item.

A JSE-listed services firm we supported issued an RFP that listed “about 60 pages” but omitted SSO and the SharePoint document library marketing wanted surfaced in search. Bids ranged from R400,000 to R2.1 million. When they reissued with integration tables and a performance budget, the spread narrowed and the evaluation became about delivery method — not guesswork.

Attach a current analytics export (redacted), a sitemap export, and example templates you hate and love. Agencies price ambiguity. Specificity is a gift to yourself.

Ask bidders to price discovery separately if your IA is unsettled — fixed-price rebuilds without discovery often hide change orders at wireframe stage. Tie fee bands to realistic 2026 website cost ranges so procurement knows when a quote is unrealistically low.

Require a single point of contact on your side for written clarifications — usually the marketing product owner with IT copied. Split channels (procurement email + marketing WhatsApp) produce conflicting answers and unfair advantages to vendors who know the right person to ask.

State accessibility and performance as pass/fail gates in UAT, not nice-to-haves. Corporate sites that fail keyboard navigation or mobile performance under load are not ready for launch, regardless of sign-off on visuals.

Long RFPs train agencies to skim. Remove noise and move detail to the right place:

• Pixel-perfect mockups of every page — Belongs in design phase after IA sign-off; include reference URLs instead.
• Mandatory proprietary tech — Unless IT has a written standard, allow equivalent CMS options with security review.
• Unlimited revisions — Undefined “unlimited” destroys scheduling; specify design rounds and change control.
• Guaranteed Google rankings — No ethical agency will commit; specify SEO deliverables (technical audit, schema, Core Web Vitals targets).
• Full marketing copy in the RFP — Provide direction and samples; ask how content support is priced.
• Forty-page legal boilerplate — Keep contract terms for shortlist stage unless your governance requires early exposure.

Procurement at a 300-person insurance broker once required vendors to include named designers’ CVs for every role — fine for staffing RFPs, irrelevant for outcome-based web programmes where the team may change. Several qualified studios no-bid. The fix was a single requirement: named account lead and methodology, with subconsultants disclosed.

Leave out vague “innovative” and “world-class” without definitions. Replace with measurable acceptance tests: “Contact form submits to Salesforce with campaign ID”, “Lighthouse mobile performance ≥ 85 on staging homepage”, “Keyboard-only user can complete job application”.

External brand guidelines belong as attachments, not pasted into the RFP body. Link to Figma or PDF once; do not email 200 MB to six agencies.

Also leave out “optional items” without priority tags — vendors will price them as zero and you will discover gaps at UAT. Use Must / Should / Could on every requirement line, even for content migration and photography.

Finally, do not ask for fixed price on unknown IA. Either fund a discovery phase in the RFP or accept that bids include explicit assumptions you will challenge in shortlist interviews. Mid-market studios that care about delivery will tell you when your scope is under-specified; treat that honesty as a scoring signal, not insubordination.

Publish weightings before responses arrive. Mid-market evaluators we work with use models like this:

Score written answers before presentation day. Presentations should clarify — not introduce — major scope changes. We recommend a 45-minute demo: CMS authoring, staging deploy, form test, and how analytics are validated post-launch.

Include a reference call script for procurement: ask about on-time delivery, how scope changes were handled, and whether the client still controls hosting two years later. References chosen only by the agency are marketing, not diligence.

Weight commercial clarity heavily when you are comparing rebuild programmes. Two bids within R100,000 of each other can differ by R400,000 in year-two care, licence fees, or “content entry” billed hourly. Normalise totals to three-year cost of ownership before you declare a winner.

Blind scoring helps when marketing has a favourite deck. Evaluators should score written responses first, then watch demos. Presentation charisma is a poor proxy for integration discipline on a corporate site that must survive audit.

Website RFPs fail when the launch date is printed before discovery. A realistic mid-market schedule:

1. Week 0–1 — Internal brief, IT/security input, legal POPIA notes, budget approval.
2. Week 2 — Issue RFP; optional pre-bid session (recorded Q&A shared to all bidders).
3. Week 3–4 — Submissions; clarifications in writing only.
4. Week 5 — Shortlist (2–3); reference calls.
5. Week 6 — Presentations and technical deep-dives with IT.
6. Week 7–8 — Negotiation, MSAs, statement of work, kickoff date.

A holding company with multiple operating brands added four weeks because group IT required vendor security questionnaires — predictable if IT is copied on the RFP issue email. Build that into your calendar; do not promise the board a go-live date during RFP week.

State whether implementation may start before full MSA execution via a limited discovery SOW. Many rebuilds stall because legal reviews the master agreement while the marketing window for launch closes.

Communicate the decision process in the RFP: when shortlist is announced, whether pricing may be negotiated, and if best-and-final is required. Silence breeds whisper campaigns from vendors and frustration from internal sponsors who thought the RFP was a formality.

For group structures, name which entity signs the contract and who pays for shared brand assets. We have seen operating companies assume the holding company would fund a group portal — procurement received five bids priced without group IA because the RFP never said who owned the sitemap.

Use a table bidders must complete without rewriting your intent. Example rows (adapt to your estate):

A regional bank marketing team used this format and cut evaluation time in half — procurement could see instantly which agencies had skipped SSO. The winning vendor flagged a Should item as a phase-two cost with numbers, which built trust.

Require vendors to list assumptions and exclusions explicitly. “Includes SEO” means nothing; “includes technical SEO audit, redirect map, XML sitemap, Search Console setup” is priceable. Point SEO evaluators to professional SEO scope so internal teams know what belongs in web RFP versus ongoing retainer.

Add a short “vendor questions” section in your RFP instructing bidders to flag conflicts early — for example, if your hosting policy forbids the agency’s preferred CDN. Early conflict surfacing keeps you from awarding to a team that cannot comply.

Procurement should attach your standard POPIA and data processing clauses only after shortlist, unless group policy requires them upfront. Early legal packs slow small studios; late legal packs slow award. Sequence matters.

Draft the eight sections in What to include, attach analytics and integration facts, and issue to three to five studios — not twelve.

Need a second pair of eyes before procurement goes wide? Book a call with Dsignr Digital or send your draft RFP for a scope sanity check.

Strong RFPs respect vendor time — clear deadlines, shared Q&A, and a decision date you keep. Studios remember buyers who run disciplined processes and bring their best teams on the next programme.