Can you switch web designers partway through a project
Separating a fixable relationship from a finished one
Three unread messages sit in a thread you started two weeks ago. The homepage still shows the same half-finished header it had the last time you checked. Nothing about the project has moved, and neither has your confidence in it.
Not every rocky project needs to end. A designer who's slow to reply during a busy stretch, or a round of revisions that felt tense, is friction. Friction like that is ordinary in a working relationship, and it usually survives a direct conversation.
What doesn't survive it is a pattern: promises that keep sliding, work that still doesn't match the brief after you've said so plainly, or a person who's gone quiet entirely. Ask yourself one plain question. If you raised the exact problem today, do you believe it would actually change? If the honest answer is no, you already have your answer about whether this is fixable.
This is one version of a wider problem covered fully in who takes care of a website after launch, which walks through what's supposed to happen when a project runs into trouble at any stage, not just this one.
What the agreement says about ending it early
Before any conversation happens, find the actual document you signed and read the section on ending the project early. Not what you remember agreeing to. What the page in front of you actually says.
Look specifically for language about notice, about what's owed if either side ends things before the work is finished, and about what happens to anything already delivered. Some agreements spell this out in detail. Others say very little on the subject, which is itself an answer worth noting.
If the contract is vague, silent, or you genuinely can't tell what a clause means, that's the moment to bring in someone qualified to read it, not to guess. A contract lawyer or a local small business legal clinic can tell you in a single sitting what the document actually commits you to.
What should be in a website design contract covers what a fair agreement addresses on this exact point, so you know what you're comparing yours against.
Money already paid against work already delivered
Line up two lists side by side: every payment you've made, and every deliverable you've actually received in exchange. A deposit against a signed contract is different from a milestone payment against a finished homepage design. Neither one guarantees the other lines up the way you assumed.
This isn't about deciding what you're owed. That's not something to work out alone, especially once trust is already gone. Get the facts straight first, before anyone brings up money at all.
Ask the designer directly, in writing, what portion of the fee was allocated to work completed so far. A specific answer to that question is worth far more than a general sense of fairness from either side. If the answer doesn't match what you've actually received, that gap is worth naming plainly before it gets resolved one way or another.
What to have in hand before you say anything
Secure access before you say anything about leaving. Ask for logins now, while the request is routine, rather than after it's attached to a conversation about ending the project.
Confirm you can personally log into the domain registrar, the hosting account, and the site's admin panel, under your own credentials, not borrowed ones. If any of those currently belong to the designer, request them now, framed as an ordinary check-in rather than a warning shot.
Ask for a copy of the site files and the content itself, in a plain format you could hand to anyone. Getting your website files back covers exactly what to ask for and how to phrase that request so it reads as routine rather than confrontational.
What you're actually entitled to take with you, separate from what's simply convenient to have, is covered in who owns your website. Read that before the conversation, not after, so you know which requests you're standing on solid ground making.
Once access and files are confirmed in your own hands, the harder conversation gets considerably safer to have. Until then, you're negotiating from a position where the other side controls everything you'd need to walk away.
Whether a half-built site is worth carrying over or starting again
A half-finished design isn't automatically worth saving just because time and money already went into it. Whether it's worth handing to someone new depends on what actually exists: clean, organized files a stranger could open and understand, or a tangle only the original designer could navigate.
A strong visual direction with weak execution underneath is worth keeping and rebuilding on top of. A confused brief with inconsistent work throughout is often faster to abandon than to untangle piece by piece.
Be honest with the next person about which one you're handing them. A designer who understands they're inheriting a rough foundation plans differently than one who assumes they're picking up something nearly finished. That mismatch in expectations causes more friction later than the actual state of the files ever does.
Briefing the next builder without poisoning the start
However badly the last relationship ended, the next one starts on its own footing, not carrying the last one's baggage into the first meeting. State what happened as fact: what was delivered, what wasn't, what state the project is actually in. Save the frustration for a friend, not the kickoff call.
A new designer needs the honest shape of where things stand, not a character assessment of the person before them. Specifics serve you better than complaints ever will: three of six pages were completed, the contract had no exit clause, the last update was two months ago. That's useful. A vague complaint about how badly things went tells a new hire almost nothing they can act on.
Once you've made the decision and gathered what you need, how to move your website away from a designer who is gone covers the practical steps of the handoff itself: migrating hosting, moving the domain, and closing out the old account for good.
Leaving a project partway through rarely feels clean in the moment. It gets considerably less painful once you're the one holding the login information, rather than waiting for someone else to hand it over.
More from the blog
- Will a professionally built website actually get you more customers
- When a booking system is worth adding to your site
- What has to be on your website before a stranger will choose you
- What to ask before a monthly retainer adds a new tool to your site
- Where your website's contact form submissions actually go