Your WordPress Agency Is Solving the Wrong Problem

Key takeaways:

• Most WordPress agencies optimise for delivering what the client asked for, not what the client’s business actually needs, and the difference is expensive.
• The brief is a symptom. A good discovery process identifies the underlying problem. Most agencies skip discovery because it risks losing the project.
• The question that separates useful agencies from order-takers: “What does success look like in 12 months, measured in something other than how the site looks?”

When the brief is the wrong brief

I have been running a web agency since 2009. Before that, I was building sites for clients from 2003, doing the same work without the letterhead. Sixteen years of scoping, building, launching, and then watching what happens after launch has given me a specific kind of education, one that does not come from courses or conferences. It comes from patterns.

The pattern I see most often is this: a client arrives with a request, an agency takes that request at face value, builds the thing, and the thing does not move the needle the client was hoping to move. Nobody calls it a failure. The site launches, the invoice gets paid, and the client quietly wonders why nothing changed.

The wordpress agency industry is very good at executing briefs. It is much less good at questioning them.

Why do clients arrive with the wrong brief?

Clients arrive with the wrong brief because they are not briefing agencies on their business problem. They are briefing them on the solution they have already decided on. “We need a redesign.” “We need a new homepage.” “We need something that looks more modern.” These are solutions, not problems. And the agency, presented with a solution, gets to work on the solution.

This is not a conspiracy. Clients are not trying to mislead anyone. They come in having already done the internal conversation, the marketing manager has been told the site looks dated, the CEO has been to a competitor’s site and felt embarrassed, someone saw a mood board on Pinterest and forwarded it to the team. By the time they reach out to an agency, they have already formed a conclusion. The brief is that conclusion, handed over as instructions.

The problem is that the conclusion is almost always about aesthetics, and the actual problem is almost always about behaviour. Not how the site looks. What people do when they get there.

What does it mean to solve the actual business problem?

I had a client come to me a couple of years back wanting a full redesign. They had a services business, solid SEO traffic, a site that was maybe four years old and, honestly, not that bad to look at. But they were frustrated with it. They had a mood board. They had references. They wanted it to feel “more premium.”

Before any wireframes got drawn, I asked them to pull their analytics. The story those numbers told had nothing to do with how the site looked. Their homepage had a 78% bounce rate. Their contact page had a form that required seven fields and an anti-spam CAPTCHA that was breaking on mobile. About 60% of their traffic was on mobile. They had not checked the form in eight months.

The form was broken. Not metaphorically. The submissions were going to an email address that nobody monitored anymore.

A redesign would not have fixed any of that. We fixed the form, simplified it to three fields, replaced the CAPTCHA, and made sure the submissions were going somewhere useful. Bounce rate came down. Enquiries came in. The site looked exactly the same. They never did the redesign. They did not need it.

That is the gap I am describing. The brief said “redesign.” The business problem was “our contact form is broken and we are losing every lead we generate.”

Why do agencies execute the brief instead of challenging it?

The economics punish honesty. If I get on a call with a client who wants a $15,000 redesign and I tell them the redesign will not fix their problem, I risk losing the $15,000. The version where I say nothing and start on the mood board is the version that keeps the project alive.

Most agencies have made the calculation, consciously or not, that the brief is safer than the problem. The brief has a defined scope. The brief has a deliverable. You can show the client a finished product and say, “Here is what you asked for.” When you are solving a business problem, the deliverable is murkier, the scope is harder to pin down, and the results take longer to materialise.

Questioning the brief also requires a level of confidence that newer agencies and junior project managers do not always have. It feels presumptuous to tell a client they have the wrong solution. So instead, you execute what they asked for, everyone stays comfortable in the short term, and the actual problem stays unresolved.

I have done it myself, early on. I know exactly what the rationalisation sounds like from the inside: “They know their business, I know web design, let’s stay in our lanes.” The problem is that the brief lives at the intersection of both, and if nobody owns that intersection, it stays unowned.

What is discovery actually supposed to do?

Discovery is supposed to find that intersection. It is supposed to get underneath the stated request and identify what is actually happening.

A real discovery process for a website project covers a few specific things. Who is actually using the site right now, and what are they doing? Where are the drop-offs? What does the analytics data say versus what the client assumes? What has the client tried before, and what happened? What does a successful outcome look like in 12 months, measured in something concrete, something that is not “the site feels more premium”?

That last question is the one I ask in every first call now. “What does success look like in 12 months, measured in something other than how the site looks?” It is a simple question and it is genuinely clarifying. Some clients have a crisp answer immediately. “We need 40 qualified enquiries a month, we are getting 11.” That client knows what they have. That relationship will work because we are talking about the same thing.

Other clients pause and then describe aesthetics again. “We just want something that represents the brand better.” That is not a wrong answer, but it tells me the conversation about the actual problem has not happened yet, and we need to have it before anything else.

What separates an agency that builds sites from one that solves problems?

The mood board client and the problem client are genuinely different relationships. I do not mean that one client is unsophisticated and one is not. I mean that one client has thought past the deliverable and one has not, and the difference shapes everything that follows.

Mood board clients judge the project by whether the site looks like the references they brought. Problem clients judge the project by whether the problem got solved. Those are different criteria and they produce different working relationships. With a mood board client, every design decision becomes a negotiation about personal taste. With a problem client, every design decision is answerable with data: does this version convert better, does it load faster, does it reduce friction at the point where people were leaving?

The agencies that consistently build good work have shifted from the first framing to the second. They have stopped treating the brief as a spec and started treating it as a starting point. The brief tells you what the client has already decided. A good discovery process tells you what is actually true.

At Chillybin, we restructured our scoping process around this about six years ago. The discovery phase now comes before any conversation about design. Before we talk about what the site will look like, we talk about what it currently does, what the data shows, and what a solved version of this problem looks like. Some clients find this process confronting. It occasionally costs us the project. But the work that comes out of it is work we can stand behind, because the brief we are executing is the real brief, not the first brief.

The brief is a symptom, not a diagnosis

Sixteen years of scoping projects has left me fairly sure of one thing: clients do not arrive knowing exactly what they need. They arrive knowing what they think they need, which is different. The gap between those two things is where good agency work lives.

The agencies that will still be around in ten years are not the ones that get fastest at executing whatever lands in their inbox. They are the ones that have built a reputation for naming the actual problem, even when it costs them the easy version of the project.

Most clients have never worked with an agency that pushed back on the brief in a useful way. When it happens, they remember it. That is what earns the relationship, not the mood board.