B2B Website Redesign RFP Timeline

A practical RFP timeline at a glance

You can compress this schedule when one decision-maker owns the project and the scope has few dependencies. Add room when legal, security, brand, product, sales, and regional teams share approval authority.

Weeks 1–2: Set the commercial brief

Name one internal owner. That person keeps the schedule, collects decisions, and resolves conflicts between reviewers. A committee can contribute expertise, but it cannot run the process without a clear owner.

Define the business problem in operational terms. Useful goals include improving the route from high-intent pages to sales, supporting a new product structure, giving marketing control over routine updates, or replacing a site that the team struggles to maintain. Skip unsupported conversion targets. Baseline data and a measurement plan should determine those targets later.

Agree on five items before you contact agencies:

• The reason the company needs a redesign now
• The audiences and buying journeys the site must support
• The pages, products, regions, and languages in scope
• A credible budget range and target launch window
• The people who recommend, approve, and sign

Discuss the budget range during internal alignment. Agencies need it to decide whether the project fits their team and whether the requirements match the available investment. Hiding it does not produce sharper pricing. It produces more assumptions.

Weeks 2–3: Audit the current website and operating constraints

Give agencies a usable view of the existing system. They do not need a complete discovery engagement inside the RFP, but they need enough evidence to identify risk.

Build a compact inventory covering:

• Page count, content types, and known migration exceptions
• CMS roles, publishing workflow, and approval rules
• CRM, forms, analytics, consent, search, and other integrations
• Redirect, metadata, structured data, and organic search requirements
• Accessibility standard and browser or device support
• Hosting, security, privacy, and legal constraints
• Existing brand, messaging, research, and design-system assets

Mark each item as confirmed, assumed, or unresolved. That label helps agencies separate fixed requirements from discovery work.

If the team cannot answer a high-risk question, state that the selected agency must resolve it during a paid discovery phase. Do not bury the gap and ask for a fixed implementation price anyway.

Weeks 3–4: Build the RFP and qualify the shortlist

Write the RFP around decisions and evidence. Include the commercial brief, current-state inventory, scope boundaries, known dependencies, submission format, evaluation criteria, and selection schedule.

Ask agencies to explain:

• Who will do the work and how much access you will have to them
• How research changes information architecture, messaging, and conversion paths
• How design decisions become a maintainable component system
• How developers will handle CMS structure, integrations, migration, analytics, and QA
• Which assumptions affect price or schedule
• What your team must supply and approve
• How they handle changes after scope approval
• What support exists after launch

Create the scoring model before proposals arrive. Weight the criteria against project risk. A content-heavy international site may place more weight on CMS architecture and migration. A lead-generation site may emphasize research, conversion paths, CRM integration, and analytics.

Shortlist agencies through a focused qualification call. Three strong candidates create a cleaner process than a long list of weak fits. Confirm service model, relevant capabilities, team availability, budget fit, and willingness to work within the selection schedule.

Week 5: Run one briefing process for every agency

Send the same RFP package to each shortlisted agency. Hold a briefing call that gives the team access to the business owner and the people closest to content, technology, and measurement.

Let agencies submit written questions by a set date. Share material answers with every participant. This keeps the comparison fair and prevents one proposal from benefiting from context that others never received.

Watch the questions. Strong agencies test goals, decision rights, content ownership, technical dependencies, migration risk, and how the company will measure the site. A team that restricts its questions to page count and visual references may see the project as production work rather than a connected business system.

Weeks 5–7: Give agencies time to develop the proposal

Allow about two to three weeks after the briefing and question period. A complex project may require more.

A useful proposal should define:

• The agency's understanding of the problem
• Recommended phases and deliverables
• Working team and responsibilities
• Client responsibilities and approval points
• Assumptions, exclusions, and dependencies
• Fee structure and payment schedule
• Change-control approach
• Indicative schedule
• Discovery outputs and how they affect implementation scope

Require a common response structure, but leave room for agencies to challenge the brief. You want comparable proposals, not identical thinking.

Avoid speculative homepage designs. They reward fast surface work before the agency has research, content, and technical context. Ask for relevant work, process artifacts, system examples, and a clear explanation of the decisions behind them.

Weeks 8–9: Score evidence, then interview finalists

Have each reviewer score proposals before the group discussion. Separate scoring reduces the chance that the most senior voice sets the answer before everyone examines the evidence.

Use the interview to test the working relationship and clarify risk. Ask the people assigned to your account to attend. Walk through one realistic problem, such as a late content dependency, an integration limitation, or a disagreement about scope. Listen for ownership, decision discipline, and clear tradeoffs.

Check references against the work you plan to buy. Ask how the agency handled communication, approvals, scope changes, technical risk, launch pressure, and post-launch support. A generic satisfaction question will not tell you much.

Normalize the proposals before comparing fees. One agency may include strategy, copy, migration, analytics, and support while another excludes them. Build a comparison sheet that shows inclusions, assumptions, client labor, and expected follow-on costs.

Weeks 10–11: Select the partner and finish commercial review

Choose the agency that best fits the project's risks and operating needs. The lowest number can become expensive when it excludes the work required to launch.

Confirm these terms before announcing the decision:

• Final scope and discovery boundaries
• Named team and substitution rules
• Approval process and response times
• Intellectual property and third-party licenses
• Payment schedule
• Change requests
• Warranty and support
• Security, privacy, and data handling
• Cancellation and pause terms

Bring legal and procurement into the process before the RFP goes out. If they first see the agreement after selection, insurance, security review, or payment terms can stall kickoff.

Tell unsuccessful agencies once the agreement is signed. Give concise feedback tied to the published criteria.

Weeks 11–12: Prepare the kickoff before the contract start date

Use the contracting window to collect access and schedule the people the project will need. Prepare CMS, analytics, CRM, hosting, design, research, and content access. Do not email credentials. Use the access method the selected team provides.

Set recurring working sessions and reserve executive review dates. Create a decision log with an owner and due date for each open item. Confirm which discovery outputs must receive approval before design or development begins.

The kickoff should start the work. It should not reopen agency selection or reveal stakeholders who never saw the brief.

Decisions that should not wait for the RFP

Some teams postpone difficult choices because they expect agencies to solve them. Agencies can guide the decision, but the RFP still needs a named owner and a clear path to resolution.

Resolve or label these items:

• Who owns website strategy after launch
• Who creates, approves, and migrates content
• Which systems hold customer and campaign data
• Which conversion events matter
• Which regions and languages launch first
• Which accessibility standard governs acceptance
• Who can approve scope, budget, and schedule changes

An unresolved item belongs in discovery with a budget and decision date. It should not sit inside a fixed-price assumption.

Frequently asked questions

How long should a website redesign RFP process take?

Plan enough time for internal alignment, agency qualification, proposal work, interviews, references, contracting, and kickoff. A focused team may complete the process in eight to twelve weeks. Complex governance or procurement can extend it.

How much time should agencies get to respond to a website RFP?

Give qualified agencies about two to three weeks after the briefing call and question period. Complex migrations, integrations, or procurement requirements may need more time.

Should we select an agency before the website scope is final?

You can select a partner before every implementation detail is final if the engagement includes a paid discovery phase. State which decisions discovery must resolve. Avoid asking for a fixed build price based on unknown scope.

When should legal and procurement join the RFP process?

Bring them in before issuing the RFP. Confirm contract requirements, security reviews, insurance, payment terms, and approval steps so the winning agency does not encounter a hidden delay after selection.