If I Had to Hire a WordPress Agency Tomorrow
Key takeaways:
- The discovery call is the most reliable signal you have, agencies that ask about your business before your budget are worth talking to; the ones that skip straight to quoting are not.
- “Who does the actual work?” is the single most important question most buyers never ask. The answer will tell you more than any portfolio screenshot.
- Agencies that push back on your brief are showing competence, not arrogance. The ones who say yes to everything are the ones who will quietly fail you six months later.
The View from Inside the Industry
I’ve introduced clients to other agencies more times than most people would expect. Sometimes we weren’t the right fit for the budget. Sometimes the client needed a capability we didn’t have. Sometimes I just knew a competitor would serve them better than we would, and I said so.
What those conversations taught me (watching those engagements from a distance, sometimes hearing how they ended) is that most buyers have no idea what to actually look for when choosing a WordPress agency. They look at portfolios and check Google reviews and compare quotes. None of that is wrong. But it misses the signals that actually matter.
If I had to hire a competitor to build my own site tomorrow, I would not do any of those things first. I would run a very specific set of tests. Here is exactly what those tests are.
What should a good discovery call feel like?
Within the first ten minutes of a call, you can tell almost everything you need to know about how an agency operates.
A good agency will ask about your business before they ask about your website. What do you sell? Who buys it? What happens after someone visits your site, do they call, do they buy online, do they fill out a form? What has not worked before? These questions are not small talk. They are an agency doing its job, which is to understand the problem before proposing a solution.
A weak agency will ask what pages you need, what your budget is, and when you want to launch. Those questions are not wrong, they are just wrong to ask first. Agencies that open with them are not thinking about your business. They are thinking about scoping a project.
I had a client last year who came to me after spending six weeks with another agency. The first call with that agency lasted forty minutes. The client told me they spent most of it talking about the design brief. Nobody asked about conversion rates, about where their leads currently came from, or about why the existing site was underperforming. They got a beautiful new site that launched on time and changed nothing about their business results.
The discovery call is not a formality. It is the first real test of whether an agency thinks like a partner or like a vendor.
Who does the actual work?
This is the question most buyers never ask, and it is the one that matters most.
When you hire an agency, you are not necessarily hiring the people on the call. You might be hiring a project manager who coordinates with a development team in Eastern Europe, a designer in the Philippines, and a copywriter who also works with three other agencies simultaneously. None of that is automatically bad. My own team at Chillybin is distributed across six countries, and I am transparent about that with every client from the first conversation.
The problem is when agencies obscure this. When they show you a team page full of faces without being willing to tell you which of those people will touch your project. When they give vague answers about “our development team” without specifying where they sit, what their process looks like, or how quality is controlled across time zones.
Ask directly: who will manage my project day to day? Who does the development work? Is that person an employee or a contractor? If the agency hedges, changes the subject, or gets defensive, that is a signal worth taking seriously.
I have seen too many engagements fall apart not because the agency lacked skill but because the person who sold the project was never involved in delivering it, and nobody on the delivery side had any real context for what the client actually needed.
What should you actually look at in a portfolio?
Not the screenshots. Screenshots tell you almost nothing useful.
Any agency can make a site look good in a static image on a high-resolution display. What you want to know is what happened after it launched. Did the client’s conversion rate improve? Did organic traffic grow? Did they rehire the agency for the next phase of work, or did they disappear?
Ask these questions directly. A good agency will have answers, because they have stayed in contact with their clients and they track what their work produces. Some will be able to give you before-and-after numbers. A 34% increase in quote requests. A page that went from 2.1% conversion to 4.7% within three months of launch. A site that now ranks for twenty terms it previously did not appear for at all.
An agency that cannot speak to outcomes (only to deliverables) is an agency that does not think in terms of results. That is a real distinction, and it becomes a very expensive one about eight months after your site goes live.
The second thing I would look at is whether the portfolio shows range of problem, not just range of industry. Pretty sites for restaurants and lawyers and e-commerce brands do not tell me the agency can solve complex problems. I want to see evidence of an agency that has navigated something genuinely difficult: a migration from a legacy platform, a site that needed to perform in multiple languages, a project that changed scope significantly mid-build and still landed well.
Process is what separates agencies that get lucky from agencies that reliably deliver.
Why would a good agency push back on my brief?
Because your brief is probably wrong in at least two places, and a competent agency knows that.
This is the thing buyers consistently misread. You come in with a brief. You have been thinking about this for months. You know what you want. Then the agency says they are not sure the approach you have described will actually solve the problem, and you feel like they are being difficult.
They are doing their job.
Back in 2009 when I started Chillybin, I made the mistake of saying yes to everything. A client asked for a feature that made no sense for their users (I built it. A client wanted a homepage layout that would have buried their most important content below the fold) I designed it. The sites launched. The results were mediocre. And I was the one who knew, before a single line of code was written, that the approach was flawed.
An agency that says yes to everything is not being accommodating. It is being cowardly, or it does not understand the work well enough to know what to push back on.
What good pushback sounds like: “I understand why you want this, but here is what we have seen happen when sites are structured this way, and here is an alternative that addresses the same goal.” What bad pushback sounds like: “We do not do it that way.” One is expertise. The other is a rigid process masquerading as a standard.
If an agency reviews your brief and has no questions, no challenges, and no alternative suggestions, be cautious. A brief that requires no pushback is either perfect (rare) or being accepted by someone who is not thinking hard enough about it (common).
What does pricing actually tell you?
A lot more than most buyers realise.
Suspiciously cheap almost always means one of three things: the project is being scoped as a template deployment with minimal customisation, the development work is being offshored with minimal quality control, or ongoing support and maintenance are simply not included in the model and will be charged at a painful hourly rate later.
I have seen $2,000 WordPress builds that worked fine for two years. I have also seen $8,000 builds that were unmaintainable after six months because the agency used a custom theme architecture that only they could support, and then they stopped answering emails.
The number itself matters less than understanding what is actually inside it. Get a proper scope breakdown. Understand what happens after launch. Understand who you call when something breaks at 11pm on a Sunday before a product launch. If the agency does not have a clear answer to that question, you are buying a product, not a service.
Agencies that do not raise the retainer conversation during the sales process are selling you a finished object. Once they hand it over, your leverage disappears. The best agencies I have observed treat launch as the beginning of a relationship, not the delivery of a finished asset.
What are the red flags that are easy to miss?
The absence of process documentation is the one I would weight most heavily.
If you ask an agency how they manage a project and they give you a narrative rather than a framework, pay attention. “We kick off with a design phase, then go into development, then QA, then launch” is not a process. Every agency says this. It tells you nothing about how decisions get made, how scope changes are handled, how content delays are managed, or what the approval process looks like when the client and the agency disagree.
Ask for a sample timeline or a project plan from a previous engagement. Ask how they handle a situation where the client is late delivering content. Ask what their revision policy is and where it has caused friction in the past. The specificity of those answers will tell you more than the agency’s website ever will.
A process document that has clearly been built from actual experience of things going wrong is worth ten polished case studies. Experience shows up in the edge cases, not the success stories.
The other flag I would watch for: no questions about your existing site before proposing a rebuild. Any agency worth hiring will want to look at your analytics, your current traffic sources, and what is already working before they suggest tearing everything down. An agency that proposes a full rebuild before seeing a single data point is not thinking about your business. They are thinking about their pipeline.
The part buyers consistently underweight
Culture fit matters in a way that sounds soft until it is not.
You are going to disagree with your agency at some point. A decision will need to be made quickly, or a piece of feedback will be delivered bluntly, or a timeline will slip and the conversation will become uncomfortable. How an agency handles those moments is entirely a product of who they are, not what they have built before.
Ask about a project that went wrong. Every agency that has been operating for more than three years has had one. How they talk about it tells you how they operate when things are hard. Agencies that cannot describe a failure clearly are either inexperienced or defensive. Neither is what you want.
Knowing how to choose a WordPress agency is really knowing how to read the signals that most buyers skip past because they are looking at the wrong things. Screenshots. Quote comparisons. Review counts.
What I would actually look for is an agency that asks better questions than I do, tells me when my brief is wrong, knows exactly who is building my site, and has clearly been through enough difficult projects to have built a real process out of the wreckage.
That combination is rarer than it should be. But it exists. You just have to know where to look.