How do you switch your web design agency mid-project?
You switch web design agencies mid-project in four moves: secure your accounts, check your contract, collect the handover, then start the new team on a small, defined piece of work. The order matters. If you give notice before you control your domain, hosting and files, you lose your best chance at a cooperative handover.
This is a rescue playbook for founders whose project has stalled or gone wrong. If you're still choosing an agency, the questions to ask a web design agency will help you avoid ending up here next time.
When should you fire your web agency?
Fire your web agency when the problem is structural, not a single bad week. Missed deadlines with no new plan, work that ignores agreed scope, or a team that has stopped responding are structural. One weak design round is not.
- Deadlines slip with no explanation or new date. A late project with a credible plan can recover; one without a plan rarely does.
- The people changed. The team you hired was replaced without notice.
- Quality is below what they showed you. Compare delivered work with the live sites in their portfolio.
- Every change becomes a dispute. Scope fights on small items usually mean the scope was never defined.
- You've raised the issue and nothing changed. Give one clear, written chance to fix it first.
Many of these trace back to warning signs that were visible before signing. Our list of web design agency red flags shows how to spot them early, and why website projects fail explains the root causes.
What should you secure before you tell the agency?
Before you give notice, make sure you can log in to every account your website depends on, with owner or admin rights. Transfers are easy while the relationship is friendly and slow once it isn't.
Asset | What you need | Why |
|---|---|---|
Domain registrar | Owner login and DNS control | Without it you can't point the domain anywhere |
Hosting or builder workspace | Owner or admin role on Webflow, Framer, Vercel or similar | So the site can't be taken down or locked |
Code repository | Admin access to the repo | Code history and the latest version |
Design files | Figma files in your workspace, not shared links | Shared links can be revoked |
Analytics and Search Console | Admin access | Your traffic history and SEO data |
Forms, CRM and email tools | Owner login | Leads keep arriving during the switch |
How do you handle the contract and final payment?
Read the termination clause before anything else, because it sets your notice period, what you owe for work done and when ownership of the work transfers. Many contracts transfer ownership only on full payment for delivered work, so settle that cleanly.
- Find the termination and notice clauses, and any minimum term.
- List what has been delivered and accepted versus what is in progress.
- Propose payment for completed and accepted work, in writing.
- Confirm that ownership of files, code and assets transfers on that payment.
- Agree a handover date and what will be delivered on it.
Keep the tone factual. The goal is a complete handover, not a win. If the contract is unclear on ownership, take the specific clause to a lawyer, because ownership terms differ by contract and jurisdiction.
What should a website handover checklist include?
A website handover should give the new team everything needed to continue without calling the old one: access, files, the current state of the work and the reasons behind key decisions.
Access
Owner logins for domain, hosting or builder, repository, CMS, analytics, Search Console, forms and any paid plugins or fonts.
Design files
All Figma files moved into your workspace, including components, styles, unused explorations and exported assets.
Code and content
The latest code pushed to your repository, a content export from the CMS and any copy documents.
State of work
A written list of what's done, what's in progress and known bugs, with links to each.
Decisions
Why key choices were made: platform, CMS structure, integrations, URL changes and anything agreed with you verbally.
Third parties
A list of every service the site depends on, who pays for it and when it renews.
What if the old agency won't cooperate?
If the agency stops responding, focus on what you can control. If you own the domain and hosting accounts, you can usually recover the live site, its content and its code from those accounts even without help.
If key assets are in the agency's name, send a short written request listing each asset and a reasonable deadline. Keep records of payments made. If that fails, take the contract to a lawyer. Meanwhile, the new team can often rebuild from the live site and your content faster than a stalled dispute resolves.
How do you de-risk the switch with a one-week trial?
De-risk the switch by giving the new team one week of real, paid work before you commit to the full project. A trial shows how they communicate, how fast they understand inherited work and what they ship, which no sales call can tell you.
A good first week has a written scope and a decision at the end. Typical trial goals: audit the inherited files and code, fix the most visible problems on the live site, and produce a plan and fixed quote for the remaining work. Published guides to paid trials for marketing and virtual-assistant work describe the same shape: one to two weeks, a written scope and a clear decision point.
- Designify trial week: one week of design and development
- $1,000
- Monthly retainer if you continue
- $6,000/mo
- Website package: up to 6 pages, +$500 per extra page
- $8,000
For what a single week can realistically produce, see can you build a website in one week.
How do you choose the next agency so it doesn't happen again?
Choose the next agency on the risks that failed last time. If copy stalled the project, hire a team that writes. If handoff between designer and developer failed, hire one team that does both. If you lost control of assets, insist on building in your accounts from day one.
- Re-read your last proposal and mark the lines that caused problems. Ask every new agency about those lines first.
- Send the same brief to two or three teams. Our web design brief template helps.
- Use questions to ask a Webflow or Framer developer if you're staying on a builder platform.
- Compare structures, not just agencies: in-house team vs studio and SEO agency vs web design agency cover the other options.
