When to Fire Your Web Developer

A Difficult Decision

No one starts a web developer relationship planning for it to fail. You invested time finding someone, money paying them, and trust believing they'd take care of your digital presence. But sometimes it doesn't work out, and recognizing when to end things is as important as knowing how to start them.

I've been on both sides of this. I've been the developer clients left, and I've helped businesses transition away from developers who weren't serving them well. The situations vary, but the patterns are consistent. Here's how to recognize when it's time for a change—and how to make that change without destroying your website in the process.

Warning Signs That Matter

Not every frustration means you should end the relationship. Look for patterns, not isolated incidents.

Communication Breakdown

The most common issue—and often the most fixable if addressed early:

• Emails and messages go unanswered for days
• You're always the one initiating contact
• Questions get vague or defensive responses
• You feel out of the loop on your own project
• Updates only come when you chase them

Chronic Missed Deadlines

Occasional delays happen in web development. Patterns of missed deadlines indicate deeper problems:

• Deadlines consistently slip without advance warning
• Excuses feel rehearsed or implausible
• New timelines are also missed
• Your project always seems to be "almost done"

Quality Concerns

Work that consistently fails to meet reasonable standards:

• Bugs and errors that should have been caught
• Work that doesn't match what was discussed
• Technical debt accumulating from shortcuts
• Other developers identify significant problems

Trust Erosion

The hardest to define but most important:

• You suspect you're not getting the full story
• Invoices don't seem to match work delivered
• They're defensive when you ask questions
• Your gut says something is wrong

When to Try to Fix It

Not every problem requires ending the relationship. Some situations warrant attempting repair:

Worth Trying to Fix

• First occurrence of issues: Everyone has rough patches
• External factors: Developer dealing with illness, family issues, etc.
• Miscommunication: Expectations weren't clearly established
• Scope confusion: What's included wasn't well-defined
• Growing pains: Developer taking on too much, learning to manage

How to Attempt Repair

1. Schedule a direct conversation

   Not email—a call or meeting. Explain specifically what isn't working.

2. Document expectations

   Put communication expectations, response times, and quality standards in writing.

3. Set a trial period

   Give it 30-60 days with clear metrics for improvement.

4. Check in regularly

   Brief weekly check-ins can prevent issues from festering.

Probably Time to Move On

• Repeated patterns: Same issues despite discussions
• Dishonesty: Trust violations are hard to recover from
• Capability gaps: They simply can't do what you need
• Hostility: Defensive, argumentative, or unprofessional behavior
• Your business is suffering: The relationship is costing you customers or opportunities

Preparing for the Transition

Before ending the relationship, protect your business by ensuring you have everything you need.

Access and Credentials

Gather all access information:

• Hosting account: Login credentials, account ownership verification
• Domain registrar: Access to domain management
• CMS admin: WordPress or other system administrator access
• Email: Access to any email services they set up
• Analytics: Google Analytics, Search Console access
• Third-party services: Any tools connected to your site

Files and Assets

• Source code and design files
• Database backups
• Original images and media files
• Documentation they've created

Verify Ownership

Confirm accounts are in your name or can be transferred:

• Domain registration should list your organization
• Hosting account should be billed to you
• You should be the primary owner on all accounts

Having the Conversation

Ending the relationship professionally protects your reputation and makes the transition smoother.

Keep It Professional

• Be direct but not confrontational
• Focus on business needs, not personal grievances
• Give appropriate notice (review your contract)
• Put the termination in writing

What to Say

Simple and professional works best:

"We've decided to move in a different direction for our web development needs. We appreciate the work you've done and would like to discuss transitioning to our new arrangement. Please provide all credentials and access information so we can ensure a smooth handover."

What to Avoid

• Lengthy explanations or justifications
• Accusations or blame
• Emotional language
• Threats or ultimatums
• Ghosting without notice

Handle Pushback Gracefully

If they respond defensively or try to negotiate:

• Acknowledge their perspective briefly
• Reiterate that the decision is final
• Stay focused on the practical transition
• Don't engage in arguments

Managing the Transition

A smooth transition protects your website and business continuity.

Immediate Steps

1. Create complete backups

   Full site backup including database, files, and media before any changes.

2. Change all passwords

   Update credentials for every system the developer had access to.

3. Revoke their access

   Remove their user accounts from your CMS, hosting, and other systems.

4. Document current state

   Note any pending issues, incomplete work, or known problems.

Finding a Replacement

• Take time to find the right fit—don't rush into another problematic relationship
• Be clear about what went wrong before and what you need differently
• Start with a small project to test the new relationship
• Check references specifically related to your concerns

Onboarding New Developer

• Provide complete access and documentation
• Explain any known issues or technical debt
• Establish communication expectations upfront
• Set clear milestones and check-ins

Special Situations

Developer Won't Release Credentials

If they refuse to provide access:

• Review your contract for ownership clauses
• Contact hosting providers directly with proof of ownership
• Domain registrars have processes for ownership disputes
• Consider legal counsel for significant disputes

Mid-Project Ending

If you must end during an active project:

• Document what's been completed vs. paid for
• Get all work-in-progress files
• Understand what's needed to complete the project
• May need to negotiate final payment based on work delivered

Long-Term Relationship Ending

When ending a multi-year relationship:

• Express genuine appreciation for past work
• Allow time for knowledge transfer
• Consider whether ongoing consultation makes sense
• Maintain the relationship if possible—you never know when paths cross again

Moving Forward

Ending a developer relationship is a business decision, not a personal failure. Sometimes relationships don't work out despite everyone's best intentions. What matters is handling the transition professionally and learning from the experience.

If you're reading this and recognizing your current situation, trust your judgment. The patterns you're seeing are real. The frustration you're feeling is valid. And making a change, while difficult, is often the right choice for your business.

Your website is too important to leave in a dysfunctional relationship. A good developer is out there—one who communicates well, delivers quality work, and treats your business with the care it deserves. Sometimes you have to end what isn't working to find what will.