How to hire for a website redesign or rebuild

1. Redesign vs. rebuild vs. refresh

These three words get used interchangeably, and that's the first place hiring goes wrong — because the roles and budget for each are completely different. Before you write a job description or brief an agency, figure out which one you're actually doing.

A refresh is cosmetic. Same platform, same content, same site structure — you're updating colors, fonts, imagery, and maybe a handful of page layouts to match a new brand look. A refresh takes days to two weeks and usually needs one web designer, sometimes with light frontend help to implement the changes on your existing template.

A redesign keeps your current platform and most of your content but rethinks the visual design, the user flows, and often the information architecture. Pages get restructured, navigation gets simplified, and the design system gets rebuilt from scratch even though the underlying CMS stays the same. A redesign typically takes six to ten weeks and needs a UI/UX designer plus a frontend engineer, with a CMS specialist brought in if the theme or template layer needs real surgery.

A rebuild starts over: new platform, new codebase, sometimes a new CMS entirely. Content gets migrated rather than reused as-is, URLs often change, and the technical foundation is different from what you had before. A rebuild runs three to five months and needs the full team — designer, frontend engineer, backend or CMS developer, and ideally someone doing QA before launch.

The quick test: if your current platform genuinely cannot do what you need, it's too slow no matter what you optimize, it can't support the features on your roadmap, or every content change requires a developer — you're looking at a rebuild. If the platform is fine but the site looks outdated and doesn't convert, that's a redesign. If the brand needs an update but the content and structure are working, that's a refresh. Get this wrong and you'll either overpay for a rebuild you didn't need or underhire for a rebuild you did.

2. Signs you need a redesign, not just a facelift

Most companies wait too long to redesign because the site "still works." Working and performing are not the same thing. Here are the signals worth acting on:

• Conversion is quietly bleeding. If your homepage bounce rate sits above 60 to 70%, or your contact form or demo request converts under 1 to 2% of visitors, the design is losing you people who were already interested enough to show up.
• Mobile is an afterthought. If mobile makes up more than half your traffic (which it does for most B2C and a growing share of B2B sites) and your site was built desktop-first with mobile bolted on, you're serving your majority audience a worse experience than your minority one.
• Core Web Vitals are failing. A Largest Contentful Paint over 2.5 seconds, a Cumulative Layout Shift above 0.1, or an Interaction to Next Paint that lags on mobile devices — these are Google ranking signals as well as user-experience problems. Run your homepage and top landing pages through PageSpeed Insights; if you're in the red on any metric, that's a concrete, measurable reason to redesign.
• The brand has moved on and the site hasn't. If your product, positioning, or visual identity has changed in the last two to three years and your website still shows the old version, you're actively working against your own marketing every time someone lands on it.
• Every content change is a ticket to IT. If your marketing team can't update a headline, swap an image, or publish a landing page without filing a request and waiting a week, the CMS or template layer is the bottleneck — and that's a redesign or rebuild problem, not a content problem.

One or two of these on their own might just need a targeted fix. Three or more, and you're past the point where patching helps — the underlying design and structure need to change.

3. The roles a website redesign actually needs

This is where most redesigns get mis-staffed. A single "designer" hire, expected to do research, UX, visual design, and code the result, is realistic for a five-page brochure site and unrealistic for almost anything bigger. Here's what each role actually covers:

How many of these you need scales with the project. A simple refresh: one web designer. A mid-size redesign on an existing platform: a UI/UX designer plus a frontend or platform developer. A full rebuild: all four roles, often with the designer and frontend engineer overlapping for two to three weeks during handoff so nothing gets lost in translation.

4. How to scope the project before you hire anyone

Hiring before you've scoped the work is how redesigns balloon from six weeks to six months. Nail these four things first, and you'll be able to brief any designer or developer accurately on day one.

Goals. Pick one or two primary metrics the redesign needs to move — more demo requests, higher e-commerce conversion, lower support ticket volume from confused users, faster page load. Every design decision should trace back to one of these. Without a stated goal, "make it look better" becomes the brief, and that's impossible to hire against or measure afterward.

Sitemap. Audit every page your current site has. Which ones get real traffic, which ones are dead weight, and which ones are missing entirely? Most redesigns are a good moment to cut 20 to 40% of low-value pages and consolidate overlapping ones — fewer, stronger pages beat a large pile of thin ones almost every time.

Content. Inventory what you have and decide, page by page, what carries over as-is, what gets rewritten, and what's brand new. Content is consistently the most underestimated part of a redesign timeline — decide now whether your team is writing it or the agency/freelancers are, because "we'll figure out copy later" is the single most common cause of a redesign stalling in week 8.

Design system. Decide whether you need a full component library, reusable buttons, cards, forms, and page templates documented for future use, or just a set of one-off page designs. A design system costs more upfront but pays off the moment you need a new landing page six months later and don't have to brief a designer from scratch — for a site with fewer than 15 pages that won't grow much, skip it; past that, it's usually worth the extra week.

Once these four are answered, you'll know your rough page count, your content workload, and whether you need one specialist or four. That's the brief you hand to whoever you hire.

5. Choosing your platform: WordPress, Webflow, headless, or custom

Platform choice determines who you hire in the CMS/backend role, and it's worth deciding before you post a job description, not after.

Most businesses land on WordPress or Webflow, and for good reason: both let your marketing team publish without waiting on a developer, both have mature ecosystems, and both keep ongoing costs predictable. WordPress wins if you publish frequently and want the flexibility of thousands of plugins and themes — though a redesign is a good moment to strip out the 30-plus plugins most WordPress sites accumulate over the years, since plugin bloat is a common cause of slow load times. Webflow wins if design polish and page speed matter more than deep content publishing workflows, and you'd rather avoid server maintenance entirely.

Headless architectures earn their complexity when you need something a standard CMS can't give you — real personalization, application-like interactions, or performance at a scale where every 100 milliseconds of load time affects revenue. A fully custom build is rarely the right call for a marketing or content site; save it for genuine product or application work.

6. The process, start to finish

A well-run redesign follows a predictable sequence. Skipping a phase, or compressing it to save a week, is usually where the delays you were trying to avoid end up coming from anyway.

Two feedback rounds during design is normal; five is a sign the brief wasn't tight enough going in. Build phase length depends entirely on scope — a 20-page WordPress site with an existing design system builds in three to four weeks, while a 60-page site with custom interactions and integrations can run six to eight. Budget the migrate phase seriously: rushing redirects and URL mapping in the final two days before launch is the single most common cause of a redesign that tanks organic traffic.

7. What a website redesign actually costs

Through a managed India-based staffing partner, monthly rates by role look like this — all-inclusive, no separate recruitment, compliance, or equipment costs on your end:

Rates include HR, compliance, equipment, and delivery management. No employer taxes or benefits costs on your side.

Translated into project-level numbers: a mid-size marketing site redesign (20 to 60 pages, existing platform, a design system, a mid-level designer plus a mid-level frontend or WordPress developer working roughly 8 to 10 weeks) lands around $9,000 to $18,000 total. A full rebuild on a new platform, with a UI/UX designer, a frontend engineer, and a backend developer working 12 to 16 weeks, runs $18,000 to $45,000 depending on complexity.

Compare that to a US or UK agency: the same mid-size redesign commonly runs $25,000 to $60,000, and a comparable rebuild runs $60,000 to $150,000 or more once you factor in agency overhead and account management fees layered on top of the actual production work. A blended team of five through a managed India partner runs around $11,000 a month against roughly $45,000 a month for an equivalent local hire — about a 75% saving you can put toward more scope, more iterations, or simply a lower total bill.

8. How to hire and vet a redesign team

A portfolio full of pretty screenshots tells you almost nothing about whether someone can run your redesign well. Here's what actually predicts a good outcome:

1. Ask for work in your industry or a similar one. A designer who's only done consumer e-commerce may struggle with a B2B SaaS site's information density, and vice versa. Filter the portfolio review to relevant work before you evaluate taste.
2. Run a small paid trial task. A homepage wireframe, or a single component built to spec, tells you more in three days than an hour of interview questions. Pay for it — free "test work" filters out the candidates you actually want.
3. Evaluate process, not just output. Ask how they'd approach your specific redesign: what they'd want to know first, how they'd structure the discovery phase, what questions they'd ask about your goals. A good designer or engineer has a repeatable process; someone who jumps straight to "I'd make it look like X" is optimizing for aesthetics over outcomes.
4. Confirm ownership terms before you start. You should own the design files, the source code, and full CMS access at handoff — not just a live site you can't edit without the original team. Get this in writing before work begins, not after the invoice.
5. Decide between staff augmentation and a dedicated team. If you already have someone internally directing the project, augmenting your team with one or two specialists works well. If you'd rather hand over the whole redesign and get a finished site back, a dedicated team that coordinates itself is the better fit.

If you're building the team from scratch rather than hiring a single freelancer, building your team in India through a managed partner solves the coordination problem directly — the designer, frontend engineer, and platform developer are matched to work together from day one instead of being three separate hires you have to introduce to each other.

9. Mistakes that wreck a redesign

10. Why a managed India team works for this

A redesign is a short, multidisciplinary project — you need a designer, a frontend engineer, and often a platform specialist, working together for two to four months, not a permanent hire. That's exactly the shape of project where a managed India team has the clearest advantage, and it isn't only about the rate.

The cost math is real. A US senior designer or engineer runs $140,000 to $185,000 a year; the equivalent India hire through a managed partner runs from $3,200 a month, or roughly $38,400 a year. For a project-based engagement rather than a full-time hire, that gap is the difference between a redesign that fits comfortably in a quarterly budget and one that needs board sign-off.

The talent pool is deep enough to match specialists to your platform. India has 4.3 to 5.8 million software developers and a fast-growing design workforce alongside it — roughly one in eight developers worldwide, with the population growing about 11% a year, more than double the US rate. That depth means a WordPress specialist, a Webflow developer, and a frontend engineer who's actually shipped Next.js sites are all findable within days, not the weeks it takes to source and screen three separate specialists locally.

The overlap works. On a shifted schedule, an India-based team gives you roughly 2.5 hours of live daily overlap with US-East and about 4.5 hours with the UK, enough for a design review call or a standup — the rest of the day becomes a genuine advantage, since feedback you send at the end of your day is turned into revised mockups or shipped code by the time you're back online the next morning.

Quality isn't a gamble. The same talent pool builds and runs production systems for 174 Fortune 500 companies across more than 390 Global Capability Centers in India — Microsoft, JPMorgan, Walmart, and Google among them. That's not a coincidence; India holds the world's highest concentration of CMMI Level 5 and ISO 27001 certified IT organizations. The quality difference between a good and a mediocre redesign team comes down to hiring bar and project management, both of which a managed partner controls directly.

Your IP stays yours. Standard agreements include work-for-hire and IP-assignment clauses that vest every design file and every line of code in you, backed by India's Digital Personal Data Protection Act 2023 — there's no ambiguity about ownership once the project wraps.

11. Frequently asked questions