What to Put in a Website Redesign RFP So Agencies Can't Hide

A website redesign RFP is supposed to create a fair comparison. Too many create fog. You send a page list, a wish for something “more modern,” and a polite invitation to propose. Agencies answer with cinema: moodboards, motion reels, confident timelines, and a premium adjective glued to a soft plan. Everyone looks serious. Nobody is forced to say what they would refuse, what they need decided before pixels, or what their price actually buys.

That is how agencies hide: not by lying, but by answering a document that never asked for judgment.

This piece is the solicitation layer. It is not the same artifact as the website redesign brief we wish every client sent. The brief is your internal clarity. The RFP is what you send out so proposals become comparable, and so soft partners cannot win the room with atmosphere alone. Steal what follows. Pair it with a filled brief. Score responses on what they reveal, not how expensive the deck looks.

Vague asks produce unusable proposals

Agencies can only answer what you ask. If the RFP is a sitemap with adjectives, you will receive page counts with adjectives. If you never require a brand-status read, every studio will assume they can invent meaning under deadline. If evaluation criteria reward atmosphere more than decision stories, cinema wins, and identity loses for the next two years.

Soft RFPs invite soft partners. Serious partners waste cycles guessing what “premium” means. Soft partners bid to the fog, then compress judgment in week six of wireframes. A sharp RFP does not limit creativity. It limits costume.

Brief first, RFP second

Write the brief for yourselves before you solicit anyone: problem, audience transformation, brand status (locked / partial / contested / thin), goals and out-of-scope, success without vanity theatre, constraints, decision makers, content ownership, timeline honesty, and a budget band honest enough for self-selection. If you cannot fill those lines, you are not ready to solicit proposals. You are ready to diagnose.

Then package that clarity into a solicitation: what agencies must respond to, how proposals will be scored, what proof you will accept, and what questions they must answer in writing. The brief teaches you. The RFP tests them. Do not paste a page inventory into an RFP and call it strategy.

What the solicitation has to force

State why this rebuild exists in business English, not “redesign the website.” Example shape: inbound misreads what we sell; sales spends the first call correcting the site; the brand looks like three companies depending on the PDF. Ask agencies to restate the problem in their own words. Soft partners echo adjectives. Serious partners sharpen or reframe.

Mandate a fixed response outline so decks cannot hide behind design. Require, in order: problem restatement; brand-status assessment; recommended sequence from discovery through build; scope inclusions and explicit exclusions; decision access needed; timeline with dependencies named; investment band with what the band can and cannot responsibly include; proof that identity stays coherent across touchpoints; risks and refusals. An agency that ignores the outline and sends a cinematic reel with a price on the last slide has already scored itself.

Force honesty on brand status. Ask every respondent to classify your identity posture from the materials you provide (locked, partial, contested, or thin) and to say what that means for sequence. Locked means identity is decided enough to express. Partial means some truths are firm and some are soft. Contested means leadership does not yet agree. Thin means the public presence is carrying more identity weight than the organization has actually decided. Require them to say whether they would lead with discovery before a full rebuild, propose an interim site with explicit claim limits, or proceed to expression. Pretending you are locked when you are thin is how sites get rebuilt twice.

Treat identity as an inside-out problem. Why, purpose, and uniqueness define the brand; colours chosen to please a market average do not. Serious engagements still run real discovery even when a company “already has a brand” in the market sense: purpose, beliefs, personality, positioning, the change you create for the people you serve, voice, and visual direction. That is a source of truth, not a logo pack or a questionnaire plus a moodboard.

List what must ship and what this project is not. Musts might include positioning legible in under a minute, a content model marketing can maintain, one voice across site and sales leave-behinds, and systems a junior marketer can extend on a Tuesday. Non-deliverables might include full product redesign, unlimited campaign creative, or “premium motion” with no identity spine. Ask agencies to add their own exclusions. Partners who will not name exclusions are selling agreeableness.

Publish the scorecard and weight substance over atmosphere: problem restatement and willingness to reframe; brand-status read and sequence honesty; systems thinking over page counting; proof beyond a staged homepage video; investment honesty and scope realism; decision access and post-launch content ownership; clarity of refusals and risks. Cinematic presentation does not add points. Performance, accessibility, schema, and CMS reality belong under hygiene, not as a substitute for identity judgment.

Proof, process, and scoring without seduction

Ask for decision stories, not only deliverable reels: what they refused; what changed after discovery; how a system held after launch; how meaning showed up in navigation, not only in a hero. Point to public work you respect, including systems-minded work like Smithen as a coherence reference, not a copy brief. Ignore proof that is only atmosphere, and case studies that never say what was decided.

Require written answers that force a reveal. If discovery shows the website is not the primary problem, what do you do? What do you need decided before you will design? Where does AI help, and where do humans decide under brand rules? What would you refuse to build even if we asked? Who on our side must be in the room for identity decisions to stick? These questions separate builders from diagnostic partners. FutureCraft’s bias is brand-first: if identity is thin, we say so before we sell pages. Other capable studios may be right for locked-identity execution. The RFP should surface the match early.

Require a timeline that admits dependencies (discovery before definition before design before scale), named content ownership after launch, and a budget band tied to what that band can responsibly include. You do not need on-page rate-card theatre; you do need proposal honesty so serious partners can self-select. Point respondents to a real intake when ready: our start-a-project path is built for that filter. Treat budget fog as a disqualifier.

Cap page or slide count. Ban appendixes that reintroduce theatre after a thin core. Require one plain-language summary page with brand-status classification on page one, no motion. Set a question deadline. State that proposals ignoring the outline will not be scored.

When the room arrives, read problem restatements first, before the lookbook. Rank who sharpened your brief. Then read brand-status calls. Anyone who flattens thin or contested into “we’ll modernize the visual language” has told you their plan: invent identity on the page. Next, read refusals and risks. Empty risk sections are confidence cosplay. Compare investment narratives: what disappears when the band tightens? Soft partners cut judgment. Serious partners cut scope out loud. Only then look at craft, and ask whether it expresses a decision or only a mood.

For a wider selection frame, pair this with how you choose a web design agency and whether branding should lead the website.

What to paste on the RFP cover

If more than two lines are blank, fix the document before you circulate it.

[ ] Purpose paragraph in commercial English[ ] Mandatory response outline (no freeform-only decks)[ ] Brand-status classification required from every bidder[ ] Sequence ask: discovery first vs expression-ready[ ] Deliverables and explicit non-deliverables[ ] Published evaluation criteria (substance weighted)[ ] Proof rules: decision stories over cinema[ ] Written answers to refusal / primary-problem prompts[ ] Timeline with dependencies + post-launch ownership[ ] Investment band honesty required in the response[ ] Submission caps and “outline ignored = unscored” rule[ ] Link or attach the filled redesign brief

If brand status is thin or contested, add one line: whether you want discovery before a full rebuild, or an interim site with explicit claim limits.

Keep the redesign brief as your internal spine. Put brand status, ownership, proof, sequence, and investment honesty in the solicitation so agencies cannot hide behind atmosphere.

Brief ready? Don’t send it into theatre. Start a project with the filled brief and this RFP outline attached. Soft paths: digital experiences, Smithen, or the redesign brief. If identity is thin, say so. Discovery may lead pixels. That is how the redesign sticks.