What Does a WordPress Consultant Actually Do? And When Do You Need One Before an Agency?

Somebody emails you a quote to rebuild your site, and it has five figures. Somebody else says it’ll take two weeks and costs a fraction of that. A third person says you don’t need a rebuild at all, you need to fix your checkout and stop paying for six plugins.

All three sound confident. None of them can be compared to each other. So who do you trust?

When this happens, you probably don’t have a hiring problem yet. You have a decision problem, and what you need is a WordPress consultant.

What a WordPress consultant actually does

A consultant’s product is a decision, not a website.

The short version: a developer is hired to build or fix a specific thing. A consultant is hired to work out what the thing should be, whether it’s worth doing, and in what order. Strategy and diagnosis on one side, execution on the other. In real life plenty of people do both, which is why the line gets blurry.

Here’s what a good engagement tends to include:

• Conversations first. What is the site supposed to do for the business? Leads, sales, members, students, donations? Who’s it for? What’s it doing instead?
• A look under the hood. Hosting, theme, plugins, forms, integrations, analytics, who has the logins, what happens when something breaks.
• Straight answers on keep, fix, replace, or rebuild. This is the big one.
• A written roadmap. Prioritized, with rough costs and risks, that you can hand to any builder.
• Sometimes, a second set of eyes on a proposal you’ve already received.

The deliverable is usually a document and a conversation. That’s it. It should be something you could take to a freelancer, Codeable, or a team like ours and say, “Quote this.”

That portability matters more than it sounds. When the plan lives in your head or in one vendor’s proposal, you’re stuck with that vendor. When it’s written down, you can get three quotes against the same page and finally compare apples to apples.

How is that different from hiring an agency?

An agency’s default move is to build. That’s not a knock. It’s the business model, and I say that as someone who runs one.

If you ask a hammer shop whether you need a hammer, you can guess how that goes. A good agency will tell you when the answer is no, and I’d like to think we do. But you’re asking someone to advise you into spending less on them, and I’d understand if you wanted a referee.

I wrote the sibling to this post, Freelancer, Codeable, or Agency? How to hire a WordPress developer, for the person who knows what they want built and needs to pick who builds it. This one’s for the step before that.

Three signs you need advice before builders

1. You can’t say what the site is for in one sentence.

If the answer is “it should look better” or “it should be more modern,” that’s a mood, not a goal. A builder will happily build to a mood. You’ll get a nicer-looking version of the same problem.

2. The quotes you’re getting don’t match, and you can’t tell why.

Mismatched quotes are usually answers to different questions. One includes content, one doesn’t. One assumes a rebuild, one assumes a repair. Someone needs to translate before you spend a dollar. A detailed scope helps here, which is why we give them away.

3. The real question is “should we?” not “how do we?”

Should we rebuild or fix? Move off the platform we’re on? Add membership or courses, and with what? Replace the developer who left? Those are decisions with years of consequences. Deciding them mid-build, with the meter running, is the expensive way to do it.

And when you don’t need a consultant

Just as important. Skip it when:

• The task is small and specific, like a checkout bug or a landing page from finished designs. Hire the builder.
• The site is on fire. If it’s down or hacked, you need hands on the keyboard today. That’s what our site rescue work is for, and advice comes after the fire.
• You already know exactly what you want, you’ve written it down, and you just need someone good to do it.

A consultant before a three-hour fix is just an extra invoice.

What to ask before you hire one

A few questions I’d put to anyone offering to advise you:

• What exactly will I have in my hands at the end? A report, a roadmap, a call?
• Will you be bidding to build what you recommend? If so, how will I know the advice isn’t shaped by that?
• Will I own the document and be free to take it elsewhere?
• What does “done” look like, and what happens if the answer is “you don’t need anything”?

That last one is my favorite. A consultant who can’t say “do nothing” isn’t advising you.

Where this leaves you

If your problem is a task, hire the person who does the task. If it’s a pile of unclear options and conflicting quotes, get the decision made first, then build.

We do this kind of work at DigiSavvy, and you can see where it fits on our WordPress expert page. The pricing page shows what ongoing support looks like once the decision is made. Or take the advice and nothing else. I won’t be offended.

Not sure yet if you’re holding a task or a decision? Start with our free SEO Snapshot. We look at how your site shows up in Google and in AI answers and tell you what we’d fix first. Take it to whoever you like after that.

So, which one are you holding right now: a task, or a decision?