Questions I’d Ask Before Hiring a WordPress Agency

Key takeaways:

• Most WordPress agencies are reselling outsourced labour, and the discovery call is where you find out if you’re talking to the team that will actually build your site.
• Ownership of files, hosting, and code is the single most overlooked clause in any agency agreement, and getting it wrong costs clients thousands to fix later.
• An agency that cannot clearly explain its post-launch support model, its version update policy, and what it does not do is not ready to be your long-term partner.

What Agencies Reveal Before the Project Starts

I have been on both sides of hundreds of discovery calls. Running Chillybin since 2009, I have sat across from clients trying to figure out whether to trust us. Before that, I was a freelancer watching agencies oversell and underdeliver. And before that, I was building sites in 1998 when the entire concept of a “web agency” barely existed.

What I know from all of that is this: the questions a client asks before signing tell me more about how the project will go than the brief itself. And the answers an agency gives reveal almost everything about whether they are actually equipped to do the work.

If I were hiring a WordPress agency that wasn’t me, these are the exact questions I would ask.

Who does the actual work?

The person presenting on the discovery call is rarely the person who will build your website. That is not inherently a problem, but you need to know the answer before you sign anything.

Ask directly: is the work done in-house or outsourced? If they say in-house, ask how many developers are on staff and where they are based. If they say they work with partners, ask who those partners are and whether you will have a direct line to them.

The offshore outsourcing model is common. An agency in Sydney or Singapore quotes the project, a team in the Philippines or Eastern Europe builds it, and the local agency acts as account management. That can work. I have seen it work. I have also seen it go badly wrong when the local agency does not have the technical depth to review what they are receiving, and the client is too far removed from the actual build to catch problems early.

What you are looking for is clarity, not a specific answer. An agency that gets evasive about where the work is done is telling you something important.

Can I see your discovery process?

If an agency sends you a quote within 48 hours of an initial call, they have not done discovery. They have done a sales call.

Real discovery takes time. It involves understanding your business model, your audience, your existing traffic, your content situation, your integrations, and your definition of success. At Chillybin we typically spend two to three weeks in discovery before a proposal goes out, because the proposal is only as good as what we understand going in.

Ask the agency to walk you through their discovery process step by step. What do they need from you? What questions will they ask? How do they document requirements? If they shrug and say “we’ll just sort out the details once we get started,” that is not flexibility. That is a sign the scope will expand and the budget will follow.

What happens after launch?

The launch is not the end. For most businesses, it is the beginning of the actual work. A WordPress site needs updates, security patches, performance monitoring, backups, and occasional fixes. The question is whether your agency is set up to do that, or whether they walk away once the final invoice is paid.

I have had clients come to us after working with agencies that simply did not pick up the phone post-launch. One retailer in Singapore came to us in 2024 after their original agency had quietly shut down, taking with them the login credentials, the staging environment, and the only person who knew how the custom checkout was built. We spent six weeks reconstructing what should have taken six hours.

Ask the agency what their maintenance retainer looks like. What is included? What is the response time SLA for a broken site? Is there a separate charge for urgent fixes? A good agency will have this documented. A bad one will make it up on the spot.

How do you handle content?

Content is where most projects stall, and most agencies do not tell you that upfront.

The usual model is that the agency builds the site and the client provides the copy, images, and any other content. That sounds reasonable until the client realises they have no copywriter, no brand photography, and no clear idea of what they want to say. The project then sits in a holding pattern for weeks or months while the agency waits and the retainer ticks over.

Ask specifically: does the agency offer copywriting? Do they have a photographer or work with one? Do they provide placeholder content during the build? What is their process when the content handover is late? The answer will tell you whether they have been through this situation before (they all have) and whether they have an actual plan.

What’s your process when something breaks post-launch?

Everything breaks eventually. A plugin update conflicts with the theme. A third-party integration changes its API. A server migration goes sideways. The question is not whether it will happen. It is whether the agency has a documented process for when it does.

Ask them to walk you through a real example. What was the problem? Who noticed it? How long did it take to fix? What was the client communication like during that window?

An agency that can answer this with specifics has been through it and learned from it. An agency that gives you a vague answer about “our team will handle it” probably does not have a formal incident process, which means the next broken site might be yours.

Who owns the files, the hosting, the code?

This is the question most clients forget to ask and most agencies are quietly relieved they didn’t.

The answer should be simple: you own everything. The domain, the hosting account, the theme files, the plugins, the codebase, the database. All of it. If an agency holds any of those on your behalf, you should have written confirmation that ownership transfers to you on final payment and that they will hand everything over without conditions if you choose to leave.

I have seen agencies hold sites hostage. Not overtly, but practically. The client’s site is hosted on the agency’s account. The DNS is managed by the agency. The WordPress admin login uses the agency’s email. The client wants to leave and suddenly discovers they cannot access anything without the agency’s cooperation.

Ask for the ownership clause in writing before you sign. If they resist or say “that’s not how we do it,” walk away.

Can I speak to a current retainer client?

References from completed projects are easy to curate. References from clients currently on a retainer are much harder to fake.

A retainer client is someone who has been through the honeymoon phase and is still paying. They have seen how the agency behaves under pressure, how they handle requests, and how their communication holds up over time.

If the agency cannot produce a single current retainer client willing to take a call, that tells you something. Maybe the retainer clients all churned. Maybe there are no retainer clients. Either way, it is worth knowing before you sign a 12-month contract.

What is your WordPress version update policy?

WordPress core, themes, and plugins update constantly. Some updates are minor. Some are breaking changes. Some are critical security patches that need to go out within 24 hours.

Ask the agency what their policy is. Do they update automatically? Do they test on a staging environment first? Do they notify you before an update goes live? Do they roll back if something breaks?

The right answer involves a staging environment, a testing protocol, and client notification. If an agency is pushing updates directly to production without testing, they are playing Russian roulette with your live site. I have seen clean WordPress installs get taken offline by a bad plugin update that a five-minute staging test would have caught.

How do you handle scope creep?

Scope creep is not a design problem. It is a process problem. And every project has some version of it.

Ask the agency how they define scope, how they document change requests, and what happens when you ask for something that was not in the original brief. A good agency will have a change order process: the request is logged, assessed, quoted separately, and approved before work begins.

A bad one will say yes to everything in the moment, absorb the extra work silently, then either cut corners elsewhere or come back with a surprise invoice at the end.

I have seen both. The silent yes is actually worse, because you do not find out there is a problem until the project is in trouble.

What do you not do?

This is the question most clients never ask, and it is one of the most useful.

Every agency has a lane. Some are strong on design and weak on SEO. Some build excellent WordPress sites but do not touch WooCommerce. Some have a content team but no paid media capability. Knowing what is outside their scope tells you what you will need to source elsewhere, and it tells you whether the agency is honest enough to say so.

An agency that claims to do everything well is either lying or has not thought hard about it. The good ones will say “we do not do ongoing content creation” or “we hand off to your developer for custom integrations” without embarrassment. That clarity is a feature, not a weakness.

At Chillybin (chillybin.co) we have always been clear that we are a WordPress-focused agency. That focus is a deliberate choice. It means we are not the right agency for every project, and we say so when that is the case.

The agencies that will not tell you what they do not do are the ones most likely to overcommit and underdeliver.

Hiring a WordPress agency is not like buying software. You are buying access to a team’s judgment, process, and accountability over time. The questions above are not gotchas. They are the baseline. Any agency worth hiring should answer all of them without hesitation, with specifics, and without making you feel awkward for asking. If they do not, you have your answer before the project has even started.