How to Choose a WordPress Web Designer or Consultancy Partner (Without Wasting Money)

Most businesses only hire a web design or WordPress consultancy partner once every three to five years. That’s not enough time to build real judgement about who’s good, who’s overselling, and who’s about to hand you a site you can’t maintain. So people fall back on price, or a friend’s recommendation, or whoever answers the phone fastest. All three can work out fine. All three can also go badly wrong.

This is the practical version of that decision: what a good partner actually does for you, what separates a freelancer from an agency from a consultancy, the questions that expose a weak proposal before you’ve signed anything, and what "on track" and "on budget" really mean once the project starts.

What a web design or WordPress consultancy actually gives you that a template can’t

Anyone can drag a theme off ThemeForest and swap the logo. A proper partner does three things a template never will.

They ask what the site needs to do before they touch design. A site exists to make the phone ring, take bookings, sell something, or answer support questions before a human has to. A good consultancy starts there (what’s the site’s job, who’s it talking to, what happens after someone lands on it) and only then moves to how it looks.

They know what breaks WordPress sites in practice. Plugin conflicts, hosting that can’t handle traffic spikes, forms that silently stop delivering emails, page speed dying under a bloated builder. This is pattern-recognition you only get from having fixed dozens of sites, not from a course.

They stick around after launch. A site is a living thing: plugins update, browsers change, WordPress itself ships a new version every few weeks. A freelancer who disappears after handover leaves you exposed the first time something breaks.

None of that shows up in a portfolio screenshot. It shows up in how the conversation goes before you’ve paid anyone anything.

Freelancer, agency, or consultancy: which one do you actually need?

These aren’t interchangeable, and picking the wrong shape for your project is one of the most common ways people overspend or underspend.

A freelancer suits a small, well-defined build (a five-page brochure site, a straightforward WooCommerce shop) where you already know roughly what you want and mainly need someone to build it well. Lower cost, but capacity is one person; if they’re on holiday when your site goes down, you wait.

An agency suits a bigger or more complex build: multiple stakeholders, integrations with other systems, ongoing marketing alongside the build. You’re paying for a team and a process, which costs more but means the work doesn’t stop if one person is off sick.

A consultancy suits a business that isn’t sure what it needs yet: is the problem the website, the marketing around it, or something in how leads get followed up? A consultancy diagnoses before it prescribes, sometimes recommending a smaller build than you expected, or flagging that the real problem sits outside the website entirely.

If you already know exactly what you want built, a good freelancer or small agency is often cheaper and just as capable. If you’re not sure what "fixed" even looks like yet, that diagnosis is worth paying for before anyone starts building.

Freelancer vs agency vs consultancy, side by side

Use this as a starting filter, not a rulebook: plenty of freelancers run resilient one-person operations with backup cover, and plenty of agencies overcomplicate a job that didn’t need it.

Red flags in a sales pitch

A handful of warning signs show up again and again in proposals that go wrong:

• A price with no scope attached. "£2,000 for a website" tells you nothing. Insist on a page-by-page, feature-by-feature breakdown before comparing any two quotes.
• Guaranteed rankings or guaranteed leads. No one controls Google’s algorithm. A partner promising a specific ranking position or a specific number of leads is either naive or not being straight with you.
• Pressure to sign today. A good partner wants you to make an informed decision, not a fast one. Discounts that expire "if you don’t sign by Friday" are a sales tactic, not a real deadline.
• Vague answers about hosting and ownership. If you can’t get a straight answer to "will I own the domain and hosting account outright", treat that as a serious warning, not a detail to sort out later.
• No examples of maintained, multi-year-old work. Anyone can show you a fresh launch. The absence of anything older is often the absence of anything that’s lasted.

Six questions that expose a weak proposal fast

Ask these before you sign anything. The answers tell you more than any portfolio.

1. "What happens to the site after it launches?" A vague answer ("we’ll be around if you need us") is a red flag. You want a specific answer: a support plan, a defined response time, a named point of contact.

2. "Who owns the website once it’s built?" You should own your domain, hosting account, and WordPress admin login outright. If a partner insists on holding these themselves with no way for you to get full access, that gives them power over you later: don’t accept it.

3. "Can I see a site you built more than two years ago that’s still live and being maintained?" Anyone can show you last month’s shiny launch. A site still running well two-plus years later tells you whether their work holds up and whether they stuck around.

4. "What’s not included in this price?" Get this in writing. Hosting, ongoing plugin updates, content changes after launch, stock photography, copywriting: any of these can be extra, and you want to know before you’re mid-project.

5. "How do you handle scope changes?" Every project changes shape a little once you’re in it. You want a partner with a clear, fair process for that: not a fixed-price contract so rigid that any change becomes a fight, and not so loose that costs balloon without warning.

6. "What CMS and page builder are you using, and can I move away from you later if I need to?" If the honest answer is "you’d have to rebuild from scratch," you’re locked in. WordPress with a mainstream builder means you’re never trapped with one provider.

Keeping a build on track and on budget

Cost overruns and slipping deadlines are rarely about the developer being slow. They’re almost always about scope drifting without anyone noticing, or decisions sitting unmade while the clock runs.

Fix the scope before the build starts, in writing. Page count, features, the page builder or theme, number of revision rounds: the more of this is agreed up front, the less room there is for "well, I assumed that was included."

Decide content before design, not after. A design can’t really be finished until the actual words and images that go on it exist. Waiting until the design is "done" to start writing copy is one of the single biggest causes of projects running long: the design gets redone once real content doesn’t fit the mockup.

Set one decision-maker on your side. Projects stall when feedback comes from five people with five different opinions and no one has final say. Nominate one person to sign off each stage.

Ask for a fixed number of revision rounds, agreed up front. Unlimited revisions sound generous but usually mean the project never quite finishes: there’s always one more tweak. Two to three structured rounds, each with a clear "what needs to change" brief, moves faster and produces a better result than open-ended back-and-forth.

Build in a testing week before go-live, not the day before. Forms, checkout, mobile display, page speed: test all of it with real content, on real devices, before the site goes live. Fixing a broken contact form after launch costs you real enquiries; fixing it the week before costs nothing.

What good actually looks like once you’re working together

You’ll know within the first two weeks whether you picked well. A good partner:

• Explains why they’re recommending something, not just what: you should understand the reasoning, not just trust the invoice
• Gives you a realistic timeline and flags risks to it early, rather than only when a deadline is already missed
• Pushes back, respectfully, when you ask for something that will genuinely hurt the result (a cluttered homepage, an inaccessible colour choice) rather than just doing whatever you say
• Hands over full admin access, documentation, and a plan for support at the end: not radio silence the day the invoice is paid

If two weeks in you’re chasing them for updates, getting vague answers to direct questions, or being told things are included that quietly weren’t: that’s worth addressing immediately, not hoping it improves.

Get in touch

If you’re weighing up a new website or a redesign and aren’t sure whether you need a freelancer, an agency, or a proper diagnosis first, that conversation costs nothing. We’ll tell you straight what we think you actually need, even if it’s smaller than what you came in asking for. Get in touch and we’ll talk it through.

Frequently Asked Questions

How much should I expect to pay for a WordPress website in Edinburgh or Scotland?

It depends heavily on scope, but a straightforward brochure site typically runs from around £1,500-£3,000, while a more complex build with e-commerce or custom features can run considerably higher. Get a written breakdown of what’s included before comparing quotes on price alone: a cheaper quote missing hosting, content, and support usually costs more once those get added back in.

What’s the difference between a web designer and a web developer?

A designer focuses on how the site looks and how visitors move through it; a developer builds the underlying code that makes it work. Many small studios and freelancers do both. For anything beyond a very simple site, you want someone comfortable with both sides, or a team that covers them together.

Should I use a local Edinburgh-based partner or does it not matter?

Local isn’t a technical requirement: most of this work happens remotely regardless. But being able to meet in person, and having someone who understands the local market you’re selling into, is a genuine advantage for a local business.

How long should a typical WordPress website build take?

A straightforward brochure site usually takes four to eight weeks from signed proposal to launch, assuming content is ready on time. Bigger builds with custom functionality or e-commerce can take two to four months. The single biggest factor in how long it actually takes is how quickly you can supply final content: not how fast the developer works.

What should I do if I’m unhappy with a website partner mid-project?

Raise it directly and clearly: vague dissatisfaction is hard for anyone to act on. Ask for a written plan to address it, with dates. If it doesn’t improve, check your contract for what you own (domain, hosting, admin access) before deciding whether to walk away. You should never be locked out of your own site.