There’s something I’ve never understood.
As a developer, I believe it is morally — and yes, legally — wrong to withhold access to a client’s website, hosting, or digital services. Yet I see it happen far too often.
Some developers let frustration, ego, or resentment dictate their behavior. They get upset. They feel under appreciated. They feel replaced. And instead of staying professional, they weaponize access.
I get it. Clients can be difficult. They can be demanding, indecisive, slow to pay, or quick to criticize.
But none of that justifies abandoning professionalism.
Be Professional. At All Times.
Here’s the hard truth: sometimes clients move on.
It can feel personal.
It can feel unfair.
It can feel like you’re being dumped.
But professionalism is not conditional. It’s not something you turn off when your feelings get hurt. No client can take that away from you — only you can.
If you run a business, attitude matters just as much as skill. Maybe more.
Anyone can build a website. Not everyone can run a business with integrity.
And if you’re offering services to clients, you have a responsibility to deliver them correctly — including when the relationship ends.
What Do You Owe Your Clients?
You owe them everything.
And I mean that literally.
Clients should have access to every account connected to their business:
-
Hosting accounts
-
Domain registrations
-
SSL certificates
-
CDN services
-
Email platforms
-
Cloud services
-
CMS logins
-
Payment gateways
-
Analytics tools
Everything.
All account names. All URLs. All usernames. All passwords.
If you created it, configured it, or manage it for them — they should have access.
This isn’t optional. It’s basic ethics. And in many cases, it’s the law.
Yet I regularly see developers who, through either spite or laziness, fail to provide this critical information. I’ve personally had to help clients track down and reset account after account because their previous developer disappeared or refused to cooperate.
That should never happen.
Clients: Here’s What You Should Insist On
If you hire a developer, you should receive:
-
Full access to every account tied to your business
-
All usernames and passwords
-
Clear documentation of where things are hosted
-
Confirmation that accounts are registered using your email address
Hosting, domains, SSL certificates, CDN services — they should all be set up under your ownership.
When you part ways with a developer, you must be able to:
-
Access every service immediately
-
Change every password immediately
This protects you.
And believe it or not — it protects the developer too.
When relationships end, emotions can run high. Sometimes people retaliate. Removing access eliminates risk on both sides.
Clean break. No gray area. No liability.
Developers: Protect Yourself, Too
Here’s the part no one talks about.
Clients can be unstable too.
They can break things. They can ignore instructions. They can make changes they don’t understand — and then blame you.
When a client leaves, make it a clean and documented separation. Transfer everything. Confirm access. Remove yourself properly.
Don’t leave yourself exposed to accusations later.
Professionalism isn’t just about being nice.
It’s about being smart.
Things Happen. Be Prepared.
Life doesn’t pause for business.
Developers get sick. People move. Companies shut down. Emergencies happen.
If you’re a client and your developer suddenly becomes unavailable, will you be able to access your own website?
If the answer is no, that’s a problem.
Redundancy and transparency aren’t luxuries. They’re safeguards.
The Bottom Line
If you’re a client:
Set expectations from day one. Tell your developer you expect full access and ownership. Make it clear you will retain master control over all services.
And store your credentials somewhere extremely secure.
If you’re a developer:
Pass everything on. Not just because it’s right — but because it builds trust.
Clients who feel safe don’t feel trapped. Clients who feel informed feel empowered. Clients who feel empowered refer business.
No one wants to feel held hostage.
Goodwill compounds. So does reputation.
It’s Not Them. It’s You.
I’m not saying all developers behave badly. But enough do that this conversation needs to happen.
As a client, protect yourself so you can move forward without your current developer.
As a developer, build your systems so your clients can move forward without you.
You may not like it.
But that’s part of being a professional.
And at the end of the day, your integrity is worth more than any single project.
0 comments