Start with the business case
Write down the reason leadership approved the redesign. Use business language rather than a list of disliked pages.
The case may include:
- Buyers struggle to understand the offer or find the right next step.
- Marketing cannot publish or update key content without developer help.
- The current CMS, integrations, or front end create operating risk.
- The site cannot support new products, regions, audiences, or campaigns.
- The team lacks reliable conversion tracking and attribution inputs.
Each reason changes the work. A positioning problem calls for research and messaging. A publishing bottleneck calls for content modeling and governance. An unreliable integration calls for technical discovery, implementation, and testing.
Tie each reason to an acceptance condition. For example, marketing may need to create a landing page from approved modules without engineering support. Sales may need form submissions to reach the CRM with source data intact. These conditions help agencies allocate effort to the system rather than the surface.
Define what the budget must cover
State whether your number covers the complete initiative or the agency contract alone. Leadership needs the complete view. Agencies need to know which costs sit inside their scope.
Use these budget groups.
Strategy and discovery
Include stakeholder interviews, analytics review, technical discovery, content inventory, audience research, positioning work, information architecture, and measurement planning when the project needs them.
Discovery reduces assumptions before design and development. It also exposes work that a page count misses at the start, such as regional publishing rules, CRM routing, gated content, or migration cleanup.
Content and messaging
Decide who writes, edits, approves, enters, and checks the content. A redesign can require page copy, product narratives, case studies, illustrations, photography, metadata, legal review, and migration formatting.
“Client provides content” does not remove the cost. It moves the cost to your team and puts the schedule at risk unless you assign owners and deadlines.
UX and visual design
Separate structural design from aesthetic production. UX work covers journeys, navigation, page hierarchy, wireframes, conversion paths, accessibility requirements, and interaction rules. Visual design covers the interface system, responsive behavior, art direction, and production details.
A custom system costs more effort than applying a theme because the team defines reusable rules for your content and buyers. The budget should reflect whether you need a distinct system or a constrained adaptation.
Development and CMS
List the required templates, reusable sections, content types, permissions, preview behavior, search, localization, personalization, and editorial workflows. Add performance, accessibility, browser support, and security requirements.
Avoid treating every page as a separate development unit. A maintainable custom website uses a defined system of templates, components, and content structures. Ask agencies to explain that system in the proposal.
Integrations and analytics
Name each system that must exchange data with the website. Common examples include a CRM, marketing automation platform, scheduling tool, product analytics, consent manager, search service, job board, and customer portal.
For each integration, document the data, direction, trigger, owner, failure behavior, and test condition. “Integrate HubSpot” could mean embedding one form or building routing, enrichment, consent, attribution, and lifecycle automation. Those scopes should not share a line item.
Migration and launch
Count content records, media, URLs, redirects, metadata, forms, downloads, scripts, and third-party dependencies. Decide what moves, what gets rewritten, what gets archived, and what requires manual review.
Launch work should cover redirect testing, analytics validation, form checks, accessibility review, performance checks, DNS coordination, rollback planning, and post-launch monitoring. The RFP should name who owns each task.
Training and post-launch ownership
Budget for editor training, documentation, warranty support, maintenance, monitoring, and an improvement backlog. A custom website still needs an owner. Your team should know who handles content support, technical updates, integration failures, and future component work.
Add internal costs to the plan
The agency fee is one part of the investment. Your staff will spend time making decisions and producing inputs.
Estimate internal effort for:
- Executive and stakeholder reviews.
- Product, sales, and customer interviews.
- Copywriting and content approval.
- Legal, compliance, privacy, and security review.
- Data cleanup and migration decisions.
- Procurement, finance, and vendor onboarding.
- CMS training and launch support.
Name one decision owner for each workstream. A broad committee with no owner creates meeting cost and delayed approvals. Put that time in the plan before the RFP reaches agencies.
Also list software, photography, fonts, stock assets, translation, research incentives, and specialist reviews. Mark each item as included, excluded, or undecided.
Price uncertainty instead of hiding it
Every redesign starts with unknowns. Your budget process should expose them.
Create a risk register with four fields: unknown, expected effect, owner, and resolution date. Typical unknowns include an incomplete content inventory, undocumented CRM rules, disputed brand direction, unclear localization needs, and a legacy platform with limited access.
Resolve high-impact unknowns before asking for fixed pricing. When that cannot happen, choose one of three treatments:
- Fund discovery first. Use a bounded phase to inspect the system and define implementation.
- Ask for an allowance. Set a provisional amount for a named piece of uncertain work.
- State an assumption. Let agencies price against the same condition and explain what would change it.
A contingency reserve does not replace requirements. It protects the approved budget from work the team could not confirm during planning. Size it against the remaining uncertainty rather than copying a standard percentage from another project.
Give agencies a working range
Include a range or ceiling in the RFP and state what it covers. Agencies can then decide whether the commercial constraint supports the required work.
Budget disclosure improves the proposal in three ways:
- The agency can recommend an approach your team can approve.
- The agency can show which requirements drive cost.
- Your team can compare tradeoffs across proposals.
Ask each agency to split its price by phase and workstream. Require assumptions, exclusions, payment schedule, change-control method, and post-launch terms. If a proposal depends on client-supplied content, a fixed number of templates, or a specific integration method, you should see that condition beside the price.
Do not ask agencies to guess your maximum and then reward the lowest total. Low estimates often move omitted work into your team, a third party, or a later change request.
Compare scope before price
Normalize every proposal against the same budget table.
| Budget area | Agency A | Agency B | Internal owner | Gap or assumption |
|---|---|---|---|---|
| Strategy and discovery | Included | Limited | Marketing lead | Customer research depth differs |
| Content and migration | Migration included | Full content scope | Content lead | Copywriting scope differs |
| Design system | Custom system | Template adaptation | Brand lead | Reuse expectations differ |
| Development and CMS | Included | Included | Technical lead | Preview workflow needs confirmation |
| Analytics and integrations | Allowance | Fixed scope | RevOps | CRM routing assumptions differ |
| Launch and support | 30 days | 60 days | Web owner | Maintenance terms differ |
The cheapest proposal may omit the work tied to your business case. The highest proposal may include depth you do not need. Compare coverage, assumptions, team quality, delivery risk, and ownership before you judge the total.
Use tradeoffs that protect the system
When the preferred approach exceeds the approved budget, reduce scope with intent.
Good reductions include:
- Launching with fewer page types while keeping the component and content model sound.
- Moving lower-priority integrations into a named second phase.
- Reusing approved content where it still supports the strategy.
- Limiting initial localization to the regions with confirmed owners.
Risky reductions remove discovery from an uncertain project, skip migration planning, compress QA, or choose a CMS that recreates the current publishing problem. Those cuts lower the proposal while raising future cost and operating risk.
Protect the work that determines structure, conversion paths, data integrity, and maintainability. Reduce breadth before you weaken the foundation.
Put the budget into the RFP
Give agencies one budget section with these details:
- The approved working range or ceiling.
- The costs included in that number.
- The required launch scope.
- The items your team will fund or produce outside the contract.
- The known risks and unresolved decisions.
- The preferred payment and procurement constraints.
- The method agencies should use to price options.
Ask for one recommended scope inside the constraint. If you want alternates, request a smaller launch scope and a later phase. That produces clearer decisions than three packages with vague labels.
Virdis plans redesigns around strategy, custom design, development, conversion, and long-term ownership. A useful RFP budget gives both sides enough detail to build the right system and defend the investment.
Frequently asked questions
Should we include a budget in a website redesign RFP?
Yes. Give agencies a working range or ceiling and explain what it must cover. That context lets them propose a credible scope, identify tradeoffs, and avoid spending time on an approach procurement cannot approve.
How much contingency should a website redesign budget include?
Set contingency after the team reviews uncertainty in content, integrations, migration, approvals, and technical discovery. A project with incomplete inventories needs more room than one with tested requirements and named owners.
What costs sit outside the agency proposal?
Common internal costs include stakeholder time, content review, legal review, data cleanup, photography, software licenses, procurement, and staff training. List them beside agency fees so leadership sees the full investment.
Can agencies price a redesign before discovery?
An agency can estimate against stated assumptions. Complex migrations, integrations, content models, or unknown technical constraints may require a paid discovery phase before the agency can commit to a fixed implementation scope.
