How to Evaluate a WordPress Agency Before You Sign the Contract (And Avoid a Costly Mistake)

Why Most Agency Evaluations Fail Before They Start

I’ve been on both sides of agency evaluations — pitching our work and watching prospects describe the nightmare they inherited from a previous partner. The pattern is almost always the same: the company chose an agency based on a polished pitch deck and a competitive price, then discovered six months later that the team couldn’t deliver.

The root problem is that most evaluation processes focus on outputs — portfolio screenshots, case study metrics, testimonials — instead of capabilities. A beautiful portfolio tells you an agency did good work once. It tells you nothing about whether they can do good work for you, on your timeline, with your constraints.

In my experience, a rigorous evaluation takes about two weeks and saves you months of pain. The framework I’m sharing here is what I’d honestly want a prospect to use when evaluating us, because it surfaces the things that actually predict project success.

Test Their Technical Credibility With Specific Questions

Don’t just ask an agency if they “know WordPress.” That’s like asking a surgeon if they know anatomy. Instead, ask pointed questions that reveal depth. Here are a few I’d recommend: How do you handle deployments to production? What’s your approach to custom Gutenberg blocks versus ACF? How do you manage WordPress updates on sites with heavy customization?

You’re not looking for a specific “right” answer. You’re looking for specificity and conviction. A competent agency will have strong opinions backed by experience. They’ll say things like, “We use a Git-based deployment pipeline with staging environments because we’ve seen too many direct-to-production pushes break sites.” Vague answers like “we follow best practices” are a red flag.

I’d also ask them to walk you through a recent project’s architecture decisions. Why did they choose that hosting provider? Why that page builder — or no page builder at all? The ability to articulate trade-offs is what separates a senior team from one that’s winging it.

Evaluate Their Process, Not Just Their Portfolio

A portfolio shows finished products. What it hides is the chaos — or the discipline — that produced them. I’ve seen agencies with stunning portfolios that are an absolute nightmare to work with: missed deadlines, scope creep without communication, radio silence for days at a time.

Ask these questions before you sign anything: What does a typical week of communication look like during an active project? Who is my day-to-day contact, and are they also doing the work? How do you handle scope changes — is there a formal change order process? A mature agency will have documented answers to all of these. They’ll show you their project management tools, introduce you to your actual project manager, and explain their escalation path when things go sideways.

My view is that communication cadence is the single best predictor of project success. If an agency can’t articulate how they’ll keep you informed, they won’t. It’s that simple. During the evaluation phase, pay attention to how quickly they respond to your emails. That responsiveness rarely improves after you’ve signed the contract.

Talk to Their Clients — Especially the Unhappy Ones

Every agency will hand you two or three glowing references. That’s theater. What you actually want is to talk to a client whose project hit a rough patch. Ask the agency directly: Can you connect me with a client where the project didn’t go as planned, and tell me how you handled it?

An agency that’s willing to share a difficult reference is telling you something powerful: they’re confident in how they recover from problems. And problems will happen. Integrations break, timelines slip, requirements change. What matters is whether the agency communicates proactively, takes ownership, and adjusts without blaming the client.

When you do speak with references, ask specific questions: Was the final invoice within 15% of the original estimate? Did the agency push back on bad ideas, or just say yes to everything? Would you hire them again? That last question is the only one that truly matters, and the hesitation — or enthusiasm — in their answer will tell you everything.

Red Flags in the Contract You Shouldn’t Ignore

I’ve reviewed competitor contracts that made my jaw drop — and not in a good way. Here are the specific clauses I’d scrutinize before signing: IP ownership (you should own your code and design assets outright upon payment), hosting lock-in (some agencies require you to host with them and make it painful to leave), and source code access (you should have full repository access from day one, not just when the project ends).

Watch out for vague deliverables language. “We’ll build a modern WordPress website” means nothing. The contract should specify the number of page templates, custom post types, integrations, and revision rounds. If it’s not in the contract, it doesn’t exist — no matter what was discussed in the sales call.

I’d also be cautious of agencies that require 100% payment upfront or refuse milestone-based billing. A standard structure is 30-40% upfront, with the remainder tied to specific deliverables. This protects both parties and keeps incentives aligned throughout the engagement.

Start With a Paid Discovery Phase to Reduce Risk

If you’re still uncertain after evaluating an agency’s technical chops, process, references, and contract terms, there’s one more move I always recommend: start with a paid discovery engagement before committing to a full build. This is typically a 2-4 week phase where the agency audits your current site, documents requirements, and delivers a detailed project plan with architecture recommendations.

This approach does two critical things. First, it gives you a low-risk way to experience the agency’s actual working style — their communication, their thinking, their attention to detail. Second, it produces a deliverable (the project plan) that you own and can take to another agency if the fit isn’t right. It’s the closest thing to a test drive that exists in this industry.

I’ve seen discovery phases save companies from six-figure mistakes. The plan that comes out of discovery often reveals that the project is more complex — or simpler — than anyone assumed. Either way, you make the big commitment with your eyes open, and that’s the entire point of a proper evaluation.