If you searched for this article, you probably already know the answer. Nobody googles “how to fire my web developer” while things are going great.
So let’s skip the part where I talk you into it and get to the two things that actually matter: confirming your gut is right, and getting out without losing your domain, your email, or your data. Because here’s what most people don’t realize until it’s too late — the decision is the easy part. The exit is where people get burned.
The signs it’s time
You’re grateful when they reply. Think about that for a second. You’re paying someone monthly, and your emotional baseline is relief when they answer an email. Response time has become the whole relationship. That’s not a service — that’s a situationship with an invoice.
You’re paying monthly and can’t name what you got last month. One client came to us paying over $1,000 a month to their SEO team. When we went through the account, we couldn’t find evidence of meaningful work in the previous six months. Not sabotage, not theft — just a provider who’d billed and skipped doing the work. If someone asked you right now what your web company did for you in July, could you answer? If the honest answer is “hosting, I think, and they renewed something?” — that’s your sign.
Every small request becomes a billable event. Update a phone number: invoice. Swap a photo: invoice. Ask a question about your own website: somehow, also an invoice. There’s a version of hourly billing that’s fair and transparent. Then there’s the version where the meter feels like the whole point.
You don’t have your own credentials. You’ve never logged into your hosting. You’re not sure where your domain is registered. Your Google Analytics belongs to… somebody. Hold that thought — this one gets its own section, because it’s the difference between a clean exit and a hostage negotiation.
Why this happens (the honest version)
Here’s the thing: unresponsiveness isn’t a solo-developer problem or an agency problem. It happens at every size. We took over a site for an institution that had been with an established web company for years — real company, real staff — and one of their core complaints was that support was slow and when they did respond they were less than helpful. Size didn’t save the relationship.
When it goes wrong, it’s usually one of two things.
The first is a provider with no system behind the person. No documentation, no defined response times, no backup coverage. Everything lives in one person’s head, and when life or growth or a bigger client comes along, you feel it immediately. This isn’t villainy. It’s just what happens when there’s no structure underneath the relationship.
The second is more common with agencies, and it’s sneakier: the bundle.
Paying $3,000 or $5,000 a month “just for SEO” sounds terrifying to a small business. But social media management, web development, SEO, content creation, and a monthly call with your account rep — all for $2,000 a month? That sounds like a deal. I’ve worked inside that model. It isn’t a deal. Spread $2,000 across five service lines and each one gets a few hundred dollars of actual attention. The “content” is one thin article. The “SEO” is a checkbox. The bundle isn’t value — it’s a way to make thin work on five fronts look like a full-service relationship.
Now, to be fair: a bundle can be the right fit. If you genuinely need light coverage across the board and you know that’s what you’re buying, fine. But understand the trade — you’re not getting the best of any of those things at a bundled price. Doing all five well costs a lot more than $2,000 a month, and the shops that can actually deliver that charge accordingly.
The fix isn’t choosing between a solo developer and an agency. It’s choosing a provider whose scope you can audit: what specifically gets done, how many hours it represents, documented somewhere you can see it. If a provider can’t answer “what did you do for me last month” with specifics, the size of their team doesn’t matter.
How to leave safely (the part nobody covers)
Here’s the rule that matters more than anything else in this article: do all of this before the breakup conversation. Not after. Not during. Before. Once you announce you’re leaving, your leverage drops and the clock starts.
1. Confirm you own your domain. Look up your domain’s registrar and confirm it’s registered in your name, in an account you control. This is the single most important asset on this list. If your developer registered the domain under their own account “to make things easy,” fixing that is job one — before any other conversation happens.
2. Have admin access to your own website. Not the hosting — the site itself. If it’s WordPress, that means an administrator-level login to your own WordPress dashboard, in your own name. Hosting is your provider’s plumbing: which servers, which company, how it’s configured — that’s what you’re paying them to worry about, the same way an office tenant doesn’t need the building’s architectural plans. But the site is yours, and admin access to it is non-negotiable. With it, you can see who else has accounts, export your content, and get a backup out with or without anyone’s help. A developer who’ll only give you an editor login on your own website — or no login at all — is keeping a door between you and your own property. That’s the red flag, and it’s worth resolving while things are still polite.
3. Take a full backup you control. Here’s the rule that simplifies everything: if you have a current backup and control of your domain, your site can move — period. Any competent provider can stand it up on new hosting without the old provider’s cooperation, permission, or even awareness. Site files and the database, exported and stored somewhere yours — a drive, your own cloud storage. Asking your developer for a backup copy is a completely normal request, and any legitimate provider hands it over without drama. The cautionary version: we’re working with a business right now whose developer went unresponsive, and without a backup in hand, the fallback for a site like theirs is reconstructing it from what’s publicly visible — every word and image recoverable, but the working machinery rebuilt from scratch. A backup you hold is the difference between an afternoon move and that.
4. Find out where your email actually lives. If your email runs on Godaddy, Gmail or Microsoft 365, it’s independent of your website hosting and it’s safe — nothing about changing developers touches it. It’s unusual these days to host email with your site, but if that is the case it needs to be part of the plan, not a surprise on cutover day.
5. Own your analytics, Search Console, and tag manager. These should be your accounts, with the developer added as a user — not the developer’s accounts with you as a guest. If it’s backwards, ask to be added as an administrator on each one now, while the relationship is still polite.
6. Inventory your plugin and theme licenses. Some licenses are yours. Some are the developer’s agency licenses, shared across their clients — and those leave when they do. Knowing which is which now prevents the fun surprise of premium plugins deactivating a month after the handoff.
The exit-fee trap
Some developers charge for every step of the way out like California collecting taxes when you move to Texas. A hundred dollars to hand over access to your own domain. A fee to export a backup of your own website. An “offboarding” invoice for the privilege of leaving.
It’s ugly. And there’s not much you can do about it after the fact — arguing over $100 with someone who controls your DNS is a bad negotiating position.
Which is exactly why the checklist above happens before the conversation. If you already hold your domain, a current backup, and your analytics, there’s nothing left to toll-booth. The exit fee only works when they’re holding something you need.
What good looks like on the other side
Whoever you hire next, set the standard on day one: everything in your name, provider added as an administrator. Your domain, your hosting, your analytics, your Search Console, your tag manager — yours. A provider who resists that arrangement is telling you something important about how the next exit will go.
That’s not paranoia. That’s just ownership. It’s your business — the accounts that run it should belong to you.
Stuck partway through this checklist? Can’t get access, or not sure who controls what? That’s exactly what a rescue assessment is for — we’ll look at your situation and tell you honestly where you stand. Get a Free Rescue Assessment
