Web Strategy

How to Choose a WordPress Developer (and What a Good Maintenance Plan Includes)

How to Choose a WordPress Developer (and What a Good Maintenance Plan Includes)

A lot of my work starts with a phone call that goes something like this. “Our developer has disappeared. We don’t have the login details for the hosting. The site was hacked last week and we don’t know who to call.”

It’s a stressful situation, and almost always avoidable. The business didn’t do anything wrong except trust the wrong person, or never think about what would happen if that person stopped responding. The site was built without documentation, accounts were registered in the developer’s name, and there was no maintenance plan in place.

Choosing a WordPress developer is one of the most important decisions you’ll make for your website. This guide explains how I’d choose one if I were on the other side of the table, and what a good ongoing maintenance arrangement should include.

Know what kind of help you need

“WordPress developer” covers a huge range of skills. Before you start looking, think about what you actually need:

  • Site building and design, setting up themes, layouts and content.
  • Custom development, building plugins, custom themes, integrations and complex features.
  • WooCommerce expertise, for online stores with specific requirements.
  • Performance and security, speeding up slow sites, hardening, cleaning up hacks.
  • Server administration, managing hosting environments, servers and deployments.
  • SEO and content, structuring the site for search and creating content.
  • Ongoing maintenance, updates, backups, monitoring and support.

Some developers cover many of these well. Others specialise. A brilliant designer may not be the right person to fix a database performance problem, and a server specialist may not produce the most beautiful layouts. Match the person to the problem.

Freelancer or agency?

Both can be excellent. The right choice depends on your project and how you like to work.

Freelancers often offer direct communication with the person doing the work, flexibility and lower overhead costs. The risk is availability: if they’re ill, on holiday or overloaded, things can stall. Ask how they handle emergencies and absences.

Agencies usually offer more capacity, a range of specialists and continuity when individual staff change. They often cost more, and you may deal with account managers rather than the people building your site.

For many small and medium businesses, an experienced freelancer with a clear process and a backup plan for emergencies is an excellent fit. For large, complex projects with tight deadlines, an agency’s capacity can matter more.

What to look for

A relevant portfolio

Look at sites they’ve built or worked on, ideally similar to what you need. Visit them yourself. Are they fast? Do they work well on your phone? Do forms work? A portfolio of beautiful screenshots means less than live sites that perform well.

Technical depth

Ask how they approach things like performance, security, updates and backups. A good developer will explain their approach clearly, without hiding behind jargon. Signs of real expertise include talking about staging environments, version control, caching layers, security hardening and testing, without you having to prompt them.

Clear communication

Pay attention to how they communicate during the first conversations. Do they listen and ask questions about your business? Do they explain things in a way you understand? Do they reply within a reasonable time? Communication during the sales stage rarely gets better after you’ve signed.

Honest advice

A good developer will sometimes tell you something you don’t want to hear. Maybe the feature you want would slow the site down, or a cheaper approach would serve you better, or a plugin you like is poorly maintained. Be wary of anyone who agrees with everything and promises the moon.

References

Ask to speak with a couple of past clients, especially long-term ones. Ask them about reliability, communication, how problems were handled and whether they’d hire the developer again.

Questions worth asking

Here are questions I’d ask any developer before hiring them:

  1. Who will own the website, domain, hosting and code when the project is finished?
  2. Which accounts will be registered in my business’s name?
  3. How do you handle updates, and do you test them before applying?
  4. Do you use staging sites and version control?
  5. How are backups handled, where are they stored and how often do you test restores?
  6. What happens if the site is hacked or goes down?
  7. How do you handle security?
  8. Will I receive documentation and login details for everything?
  9. What’s included in the price, and what counts as extra work?
  10. What happens if we stop working together?

The answers to the first and last questions are especially revealing. A professional will happily confirm that you own everything and that they’ll hand over all access if you part ways.

Red flags

Some warning signs I’ve seen repeatedly in projects that went wrong:

  • Accounts registered in the developer’s name. Your domain, hosting and key services should belong to your business. The developer can have access, but you should be the owner.
  • Refusing to share login details. You should always have administrator access to your own site and hosting.
  • Nulled or pirated themes and plugins. These are a major source of malware. A professional uses properly licensed software.
  • No mention of backups or security. If they don’t bring these up, they probably don’t prioritise them.
  • Unrealistically low prices with fast timelines. Quality work takes time. Extremely cheap quotes often mean shortcuts.
  • Vague quotes. “Website: $X” with no breakdown of what’s included leads to disagreements later.
  • Editing live sites directly. Ask how they make changes. If the answer is straight onto the live site, expect occasional outages.

Understanding quotes and contracts

A good proposal clearly describes:

  • What will be delivered, page by page or feature by feature.
  • Timeline and milestones.
  • What you need to provide, such as content and images, and by when.
  • Payment terms.
  • How changes to the scope are handled and priced.
  • Who owns the finished work.
  • What support is included after launch.

Make sure you understand how extra requests are handled. Most project disputes come from scope creep, where small additions pile up without anyone agreeing on cost.

Why ongoing maintenance matters

A WordPress site isn’t finished at launch. WordPress core, plugins and themes release updates regularly, including security fixes. Hosting environments change, PHP versions reach end of life and new vulnerabilities are discovered all the time.

A site left without maintenance gradually becomes slower, less compatible and more vulnerable. Many of the hacked sites I clean up were fine at launch but hadn’t been updated in a year or more.

You can maintain the site yourself if you have the time and knowledge. Many businesses prefer a maintenance plan with their developer, so they can focus on running their business.

What a good maintenance plan includes

Maintenance plans vary widely, so compare what’s actually included rather than just the price.

Updates

Regular updates to WordPress core, plugins and themes, ideally tested on staging first for important sites. Ask how often updates are applied and what happens if an update breaks something.

Backups

Automatic backups stored off-site, with enough history to recover from problems discovered late. The plan should include periodic restore tests, not just backup creation.

Security monitoring

Malware scanning, file change monitoring, firewall management and login protection. Ask whether hack cleanup is included or charged separately, and how quickly they respond to a security incident.

Uptime monitoring

Monitoring that alerts the developer when the site goes down, often before you notice.

Performance checks

Regular checks on page speed and Core Web Vitals, with fixes when performance declines.

Support time

Many plans include a set amount of time each month for small changes, content updates or questions. Clarify what counts toward this time and what happens to unused hours.

Reporting

A short monthly report showing updates applied, backups completed, security events and any issues fixed. It gives you visibility and proves the work is being done.

Response times

Clear expectations for how quickly urgent issues, like a site being down or hacked, will be addressed, compared to routine requests.

Keep your own records

Whoever you work with, keep a secure record of:

  • Domain registrar login and renewal date.
  • Hosting account login.
  • WordPress administrator login.
  • DNS provider access.
  • Licences for premium plugins and themes.
  • Email and other connected services.

Store these in a password manager owned by your business. If your relationship with a developer ends, for any reason, you’ll be able to continue without panic.

Frequently asked questions

How much should I pay a WordPress developer?

Rates vary widely depending on location, experience and the complexity of the work. Rather than looking for the cheapest option, look for the best value: clear scope, solid processes, good communication and a track record of reliable work. Fixing a poorly built site often costs more than building it properly the first time.

Should I sign a long-term maintenance contract?

Monthly agreements with reasonable notice periods give you flexibility. Some developers offer discounts for annual commitments. Either is fine as long as you understand what’s included and how to cancel.

What if my current developer won’t hand over access?

Start by asking clearly and in writing. If the domain and hosting are in your business’s name, you can usually regain access through the providers directly with proof of ownership. If they’re in the developer’s name, it can be more complicated. That’s exactly why ownership should be settled from day one.

Can I switch developers easily?

Yes, if you own your accounts and the site is well documented. A good new developer will start with an audit to understand how the site is built, then take over maintenance from there.

Final thoughts

The best developer relationships are long-term partnerships built on trust, clear communication and shared understanding of what the business needs. Choose someone with relevant experience and solid processes, make sure you own every account and line of code, and put a proper maintenance plan in place after launch. Do that, and your website becomes a reliable asset rather than a source of stress.