How to Scope a Website Redesign Before Requesting Quotes
How to Scope a Website Redesign Before Requesting Quotes
Answer up front: the best way to scope a website redesign project is to start with explicit business outcomes, map scope across consistent dimensions, assign each dimension a clear level of complexity (Minimal / Standard / Advanced), and fund a short paid discovery that produces a fixed-scope MVP build plan vendors can quote against. That approach turns subjective wish lists into comparable proposals and clarifies tradeoffs between time, cost, and risk.
Why scoping well saves time and money
Vendors don’t just estimate effort — they estimate risk. When your brief is vague, proposals include contingency buffers and assumptions that make apples-to-apples comparison impossible. A crisp scope yields:
- Comparable proposals with clear deliverables and acceptance criteria.
- A prioritized roadmap so you can launch the highest-value items first.
- Lower friction during build, testing, and launch because requirements were validated early.
Decision framework: four steps to a vendor-ready scope (use this first)
- Define 1–2 primary business outcomes. Write one sentence that states the business result you need (for example: “Reduce lead response time to 24 hours” or “Replace legacy portal with a client intake portal”).
- Assign measurable KPIs. Pair each outcome with 1–3 measurable metrics and a target timeframe (months or quarters).
- Map scope across six dimensions. Convert vague requests into decisions using the checklist below: Content & IA, Design & UX, Integrations & Data, Custom Development, Security & Operations, SEO & Performance.
- Run a short paid discovery. A 1–2 week discovery crystallizes assumptions, produces a prioritized MVP, and yields a fixed build scope that reduces vendor risk and improves proposal accuracy.
Scope checklist: six dimensions, three levels
For each dimension choose Minimal (MVP), Standard, or Advanced. Write that choice into your one-page brief so vendors price the same things.
1. Content & Information Architecture
- Minimal: Rework existing pages, copy edits, and minor navigation changes.
- Standard: New page templates, full content migration from one CMS, SEO content review.
- Advanced: Content strategy, new content creation, migration from multiple systems and custom content models.
2. Design & UX
- Minimal: Template refresh using existing brand assets.
- Standard: Custom templates for 3–5 page types, a small design system, and basic prototyping.
- Advanced: Full visual system, custom interactions, accessibility audit and remediation, extensive prototypes.
3. Integrations & Data
- Minimal: Forms to email or simple CRM webhooks.
- Standard: CRM integration, analytics, marketing automation, payment gateway configuration.
- Advanced: Custom APIs, bi-directional data syncs, SSO, and large-data imports/exports.
4. Custom Development
- Minimal: Theme changes and lightweight plugins.
- Standard: Custom CMS blocks/components and small custom plugins.
- Advanced: Client portals, workflow systems, HIPAA-aware apps, or heavy single-page applications.
5. Security, Compliance & Operations
- Minimal: HTTPS, backups, and basic malware scanning.
- Standard: Managed hosting, WAF, scheduled backups, monitoring, and incident response playbook.
- Advanced: Dedicated logging, audit trails, encryption-at-rest, and regulatory controls tailored to HIPAA, SOC-like needs, or industry requirements.
6. SEO, Performance & Conversion
- Minimal: Preserve URLs where possible, basic meta tags, and analytics setup.
- Standard: Redirect plan, on-page SEO, performance tuning, and A/B test setup for key pages.
- Advanced: Full technical SEO migration, continuous CRO program, and progressive feature rollouts tied to KPIs.
Quick decision table: complexity, timeline, and risk
| Scope Level | Typical Timeline | Primary Risk |
|---|---|---|
| Minimal (MVP) | 4–8 weeks | Limited polish and fewer UX tests; good for fast validation |
| Standard | 8–16 weeks | Integration and migration complexity; requires stronger QA |
| Advanced | 12+ weeks (phased) | Custom development and compliance increase cost and maintenance needs |
One-page vendor brief (template)
Give vendors this structure so proposals are comparable:
- Project name & primary outcome — one sentence.
- Success metrics — 2–4 KPIs and target dates.
- User types & scenarios — who uses the site and what they must accomplish.
- Scope by dimension — Minimal/Standard/Advanced for each of the six dimensions above.
- Integrations & constraints — existing CRM, payment providers, privacy/compliance notes.
- Deliverables & acceptance criteria — list what counts as done for launch.
- Timeline & phases — desired start and launch windows and suggested phases (MVP, Phase 2, Phase 3).
- Budget approach — preferred procurement: fixed-price, time-and-materials, or hybrid.
How to use first-party Search Console data to prioritize scope
Your Search Console report is a short list of what searchers expect from your site. Use these signals to prioritize pages and outcomes during discovery:
- Pages with impressions but low clicks: improve meta titles/descriptions and page experience.
- Pages with clicks and falling positions: preserve URLs, validate redirects, and run an on-page SEO audit.
- High-impression branded queries: ensure your primary business info and conversion paths are clear and visible.
Prioritize pages that drive discovery and conversions in your MVP, then include technical SEO migration tasks in the build acceptance criteria. For a complete technical checklist, see our website redesign SEO migration checklist.
See the SEO migration checklist for common pitfalls and pre-launch tests.
Vendor evaluation: nine questions (and a simple scoring rubric)
Ask these questions of every agency and use a 1–5 score for each to make comparisons objective:
- Can you show examples of similar projects and explain your role and outcomes?
- How do you price projects: fixed scope, time-and-materials, or hybrid phased?
- What does your discovery include and how do you handle change control?
- Who will be on our team and how many hours of each role are budgeted?
- What are your acceptance criteria for launch and what post-launch support is included?
- How do you handle integrations, API work, and data migrations?
- What security and compliance practices do you follow?
- How do you measure and report progress and results?
- What ongoing costs should we budget for (hosting, maintenance, security, SEO)?
Score each vendor 1–5 on fit, recent relevant experience, team clarity, and proposal transparency. Add up scores to help select the best match beyond just headline price.
How to compare quotes apples-to-apples
Require the same three outputs from every vendor so proposals are directly comparable:
- A fixed list of deliverables tied to acceptance criteria.
- A timeline broken into milestones with demo points and sign-off gates.
- Clear out-of-scope items and an explicit change-request pricing model.
Bonus: ask for a small paid discovery (1–2 weeks). That discovery delivers a fixed-scope build brief and often reduces the final build cost because assumptions and risks are clarified early.
Illustrative budget ranges (use as conversation starters)
Below are illustrative ranges for common small-to-medium business projects using WordPress. Use them only as starting points; actual quotes depend on integrations, compliance, and migration risk.
| Project Type | Typical Range (USD) | When this applies |
|---|---|---|
| Simple refresh (MVP) | $8k–$18k | Template refresh, limited page migration, simple forms, no custom apps |
| Standard redesign | $18k–$45k | Custom templates, CRM integrations, performance tuning, moderate content work |
| Custom / integrated build | $45k–$120k+ | Portals, large data imports, custom APIs, or strong compliance requirements |
Pre-launch acceptance checklist (compact)
Include this checklist in the RFP and require vendors to affirm each item:
- All agreed pages migrated or recreated and verified against an approved content inventory.
- Integrations tested with test data and logs (CRM, email flows, payments).
- Redirect map applied and canonical tags verified.
- Analytics, Search Console, and tag management verified for staging and production.
- Performance targets met for key user flows (agree on metrics or Lighthouse thresholds in discovery).
- Security basics applied: HTTPS, backups, host protections, and a vulnerability scan passed.
- Editor training completed and handoff documentation delivered.
Typical timeline and roles
- Discovery & brief: 2–4 weeks — outcomes, inventory, success metrics, prioritized backlog.
- Design & prototyping: 3–6 weeks — wireframes, visual design, stakeholder reviews.
- Build & integrations: 4–12+ weeks — templating, CMS setup, API work, QA.
- Content migration & training: 1–4 weeks — migration verification and editor training.
- Launch & post-launch support: 1–4 weeks — monitoring, quick fixes, and SEO validation.
Common roles: Project Manager, UX/UI Designer, Front-end Developer, Back-end Developer, QA Engineer, SEO Specialist, and Technical Lead.
Procurement paths: pick the one that matches your risk appetite
- Do-it-with-help: You lead; hire specialists for scoped work and keep ownership of content and product decisions.
- Full-service agency: Agency owns discovery, content, design, build, and launch — single point of responsibility.
- Phased build: Discovery + MVP fixed price, then a prioritized roadmap for later phases to reduce initial risk.
When Grover Web Design is a fit
We often work with organizations that need custom development, integrated systems, or SEO-preserving migrations. If you expect portals, custom APIs, HIPAA-aware workflows, or an SEO-conscious redesign, our services align with those needs — see our Custom Web Development, SEO services, and overall Services pages for examples of how we structure projects and post-launch support.
Related reading
- How to compare agency proposals
- Preparing a project brief
- Website redesign SEO & migration checklist
FAQ
How do I estimate a budget without getting quotes?
Start by selecting Minimal/Standard/Advanced for each dimension above. Translate those choices into relative buckets (design, build, integrations, content, ops) and use the illustrative ranges as conversation starters. If possible, run a 1–2 week paid discovery to get a reliable fixed-scope build estimate.
Should I require a discovery phase?
Yes. A short discovery reduces ambiguity, produces acceptance criteria, and usually lowers downstream cost by identifying integration risks early.
When is custom development justified?
Custom development is justified when off-the-shelf tools cannot meet required workflows, integrations, or compliance controls — for example, client portals, HIPAA-aware intake forms, or unique product configurators. Keep custom work modular and documented so editorial tasks stay simple.
What post-launch costs should I expect?
Budget for hosting, backups, security monitoring, small fixes, and periodic SEO/performance work. Vendors should provide a recommended maintenance plan and clarify what’s included in the initial 30–90 day support window.
Next steps — an actionable three-step checklist
- Draft the one-page brief with your primary outcomes and the scope levels you selected.
- Run a 1–2 week paid discovery with one preferred vendor to produce a fixed-scope build plan and prioritized backlog.
- Compare proposals using the three-outputs rule (deliverables, timeline, out-of-scope) and select the partner with clear acceptance criteria and named leads.
We can’t solve your problem if you don’t tell us about it!
