Search “web developer” and you’ll get two very different kinds of result: agencies with a team page and a client-logo wall, and individuals like me who do the whole thing themselves. Both can build you a good website. But you’re not really choosing between two suppliers — you’re choosing between two ways of working, and the difference shows up long after the site goes live.

What an agency genuinely does better

Let’s be fair to agencies, because the honest version of this matters. An agency has capacity — several people, so a big build with a hard deadline doesn’t rest on one person’s calendar. It has redundancy — if someone’s off sick or leaves, the work continues. And for a large organisation that needs a designer, a developer, a copywriter, a project manager and an SEO specialist all at once, an agency can staff that in a way one person can’t.

If your project is genuinely large, multi-stream, and time-critical, an agency is often the right call. I’d tell you that to your face.

What you pay for that, and where it goes wrong

The trade-off is layers. At an agency, the person who pitches you is rarely the person who builds the site. Your notes go to an account manager, who relays them to a developer you never speak to. Every change passes through a layer of translation, and every misunderstanding costs a round trip. You’re also paying for overhead you never see — the office, the sales team, the project-management tooling — baked into the invoice.

And the thing most businesses discover a year later: the junior who actually built your site has moved on, and nobody left at the agency really knows how it was put together.

What working with one person actually changes

With a freelancer, the person you email is the person writing the code. There’s no translation layer, no account manager, no “let me check with the developer.” When something breaks at 11pm, the person who fixes it already knows why, because they built it.

In my case there’s a second layer to that: I do the WordPress development and the brand strategy, so the copy on your checkout page matches the tone that got someone there in the first place — instead of two separate suppliers optimising two halves of the same funnel in opposite directions.

The honest test

Ask any developer, agency or freelance, the same question: “Who will I actually be speaking to, and will they still be reachable in a year?” The answer tells you more than any portfolio. An agency might answer “your account manager.” I answer “me, both times.”

If that’s the working relationship you want — direct, accountable, one person who understands the whole thing — that’s exactly what I offer. If your project genuinely needs a full team, I’ll tell you that too, and point you in the right direction.

Most WordPress maintenance plans do exactly one thing: run the updates. Plugins, themes, WordPress core — all kept current, invoice sent monthly, box ticked. That’s not nothing. But it’s a fraction of what “protecting your site” actually requires, and it’s the fraction that’s easiest to automate and sell, which is exactly why it’s what most plans are built around.

Here’s what tends to fall through the gap between “updates are running” and “the site is actually protected.”

Updates without testing are a gamble, not a safeguard

Auto-updating a plugin on a live site with no staging check is how a “maintained” site goes down on a Tuesday afternoon for no obvious reason. A plugin update conflicts with a theme function, a checkout breaks silently, and nobody notices until a customer complains — sometimes days later. A maintenance plan that runs updates without ever testing them afterward is trading one risk (an outdated plugin) for another (an untested one), and calling it protection.

Backups that have never been restored aren’t backups

Almost every hosting plan and maintenance package includes “daily backups” in the feature list. Far fewer have ever actually tested whether that backup restores cleanly. I’ve seen backup systems silently fail for months — the job runs, the file gets created, and it’s corrupted or incomplete the one time it’s actually needed. A backup nobody has restored is a belief, not a safety net.

Security monitoring is different from security patching

Patching closes known vulnerabilities after they’re published. Monitoring catches the thing patching can’t: unusual login attempts, a file that’s changed when nothing should have touched it, a spike in outbound requests that suggests something’s already gotten in. Most maintenance plans cover the first and skip the second entirely, which means the plan is built to react to problems that are already public knowledge, not to notice the ones that aren’t yet.

What a plan that actually protects the site looks like

• Staged updates, not blind ones — changes tested somewhere other than the live site before they touch it.
• Backups verified on a schedule, not just generated — an actual test restore, not an assumption.
• Uptime and file-integrity monitoring, so a problem gets caught in minutes, not whenever a customer happens to mention it.
• Someone who understands the site’s actual build, not a generic support queue reading from a script — the difference matters most exactly when something goes wrong in a way that isn’t in the manual.
• Performance kept in view, not just security — a site that’s technically safe but has slowed to a crawl is still losing you visitors and rankings. This is worth treating as part of the same job, not a separate line item.

Why this usually comes down to who’s holding the plan

A lot of this gap exists because the person running your maintenance plan didn’t build the site, and doesn’t know it well enough to notice when something’s subtly wrong rather than obviously broken. That’s not a criticism of maintenance providers generally — it’s just what happens when maintenance gets treated as a commodity add-on rather than an extension of the original build.

The version of this that actually works is closer to what I do for maintenance clients: the person keeping the site running is the same person who understands how it was built, which means an update that looks routine but touches something custom gets caught before it ships, not after a customer reports it. It’s also worth checking how your site is actually performing separately from whether it’s “maintained” — the two get bundled together in most plans, but a fast, secure site and a slow, secure site both tick the same maintenance checkbox.

If your current plan can’t tell you the last time a backup was actually restored, or whether an update was tested before it went live, it’s worth asking those two questions directly before renewing it.

“WordPress developer Hertfordshire” turns up a mix of agencies, marketplaces, and one-person operations like mine — and the range in what you actually get for your money is wider here than the search results make it look. A few direct questions before you commit will tell you more than any portfolio page.

“Who will I actually be speaking to?”

At an agency, the person who pitches you is rarely the person who builds the site. You’ll often deal with an account manager relaying your notes to a developer you never speak to directly — which means every change goes through a layer of translation, and every misunderstanding costs a round trip. With a freelancer, ask plainly whether it’s genuinely one person start to finish, or whether the work gets subcontracted out once you’ve signed. Both can produce a good result. Only one of them means the person answering your emails actually understands the code underneath your site.

“Is this a template, or is it actually built for us?”

A huge share of “custom” WordPress sites are a page-builder theme with a logo swapped in and a few colours changed. There’s nothing wrong with that for a very simple brochure site — but if your business has any real logic to it (bookings, a product catalogue, membership tiers, an integration with something else you already use), ask specifically how that gets handled. “We’ll find a plugin for that” is a different answer, and a different risk, than “I’ll build that as a proper custom feature.” Neither is automatically wrong, but you should know which one you’re paying for.

“What happens after launch?”

This is the question most businesses forget to ask, and the one that costs them most a year later. WordPress sites need ongoing attention — plugin updates, security patching, the odd thing that breaks when a third-party service changes its API. Ask what that looks like concretely: is there a maintenance plan, who’s on it, and what’s covered versus billed separately. A developer who goes quiet the day after launch is a common enough pattern locally that it’s worth asking about directly, not assuming.

“Can I see something you built that’s still live, still yours?”

Portfolios go stale. Ask for sites that are both still online and still maintained by the person you’d be hiring — not a project from three years ago that’s since been rebuilt by someone else because the original build didn’t hold up. A developer confident in their own work will point you to something recent without hesitation.

“Do you understand what my business actually does?”

This sounds obvious, but it’s the fastest way to separate a developer who listens from one who’s already decided what you need before you’ve finished explaining it. A good discovery conversation should feel like it’s about your business — your customers, your bottlenecks, what’s actually slowing enquiries down — not a features checklist read out in order. If the first meeting is entirely about templates and page counts, that’s a preview of how the whole project will go.

Why local still matters, even for a fully remote industry

None of this work requires being in the same town. But there’s a real, practical difference between a developer who’s driven past your shop, understands the local competition, and can meet face-to-face when something needs a proper conversation, versus one who’s never set foot in Hertfordshire and never will. It doesn’t replace technical competence — it’s not a substitute for the questions above — but weighed evenly between two developers who both answer well, it’s a reasonable tiebreaker.

I work as a freelance WordPress developer across Hertfordshire, with dedicated work in Watford, St Albans, and Welwyn Garden City — but wherever you end up hiring, ask the five questions above before you sign anything. They’ll tell you more in ten minutes than an hour of scrolling portfolios will.

Most businesses hire a brand strategy agency once, get burned, and either give up on the idea entirely or hire a second one to fix what the first one left behind. That second hire is usually more expensive than doing it properly the first time — and it’s almost always avoidable.

Here’s what I’ve learned from the other side of that second hire, having rebuilt more than one brand that a previous agency “did” but never actually landed.

The wrong reason to hire one

If the honest answer to “why are we doing this?” is “our logo looks dated,” you don’t need a brand strategy agency yet — you need a designer. Strategy is the layer underneath the visuals: who you’re actually for, what you’re claiming that a competitor can’t, and why someone should believe you over the business next door. A new logo on top of an unclear answer to those questions is just an expensive coat of paint.

The right reason looks more like: your positioning hasn’t kept up with what the business has become, your messaging says something different depending on who’s writing it that week, or you’re about to spend real money on marketing and don’t trust what it would actually be saying.

What “strategy” should mean in the pitch

Watch for agencies that jump straight to moodboards. A strategy engagement should produce something you could hand to a new hire on day one and have them understand the business’s position without a single visual in sight — a written point of view on the market, the audience, and the gap you’re filling. If the first deliverable mentioned in the pitch is a logo concept, the “strategy” part is decorative.

Ask directly: what do we get before any design work starts? A good answer names something concrete — positioning statement, messaging framework, competitor teardown. A vague answer (“we’ll workshop it together”) usually means the thinking happens live, on your dime, without anyone owning the outcome.

Questions worth asking before you sign anything

• Who’s actually doing the strategic thinking? Agencies often sell you the founder in the pitch and hand you a junior account manager once the contract’s signed. Ask who you’ll be working with day-to-day, by name.
• What happens to the deliverables if we don’t like the direction? A confident agency has a revision process built in from the start, not a defensive one bolted on when you push back.
• Can we see the strategy work, not just the finished design, from a past client? Most portfolios only show the pretty end result. The positioning document underneath it tells you far more about whether they can actually think, not just decorate.
• Who implements this afterward? A brand strategy with nobody responsible for carrying it into the actual website, packaging, and sales materials just becomes a PDF nobody opens again.

The handoff problem nobody mentions in the pitch

This is the part that quietly wastes the most money. A strategy agency delivers a beautiful brand book, then hands you off to whoever builds your actual website — a different company, working from a PDF, with no stake in whether the strategy survives contact with a real homepage. Something always gets lost in that handoff: the tone that worked on paper reads differently in a hero headline; a positioning nuance gets flattened because the developer never sat in the strategy sessions.

It’s worth asking, plainly, whether the same people who define the brand will be anywhere near the people who build the site it has to live on. If the answer is no, budget extra time — and money — for the inevitable gap between what was promised and what actually ships.

What good actually looks like

A brand strategy that’s working doesn’t feel like a project that finished. It shows up months later in how a salesperson describes the business unprompted, in which leads self-select before they even reach the contact form, and in whether a rebrand actually changes how people talk about you — not just how the business looks on a slide.

If you’re choosing between agencies right now, weight the pitch toward whoever can show you their thinking, not just their finished work, and toward whoever’s still in the room when the strategy has to become a real brand identity and a real website — not just a document that gets filed away once the invoice clears.

Every brand has a story whether or not anyone’s bothered to write it down — customers form one anyway, from whatever fragments they pick up: a review, a shopfront, a five-second glance at a website. The only choice is whether that story is the one you’d actually want told. Here’s how storytelling actually functions in the brand and marketing work I do, not as an abstract concept but as a practical part of the job.

Why a story lands when a feature list doesn’t

A list of services describes what a business does. A story explains why it matters to the person reading it — and that’s the part that actually gets remembered. When I worked on repositioning cyber-security messaging for News UK, the technical facts didn’t change; what changed was framing them around what was actually at stake for the people reading it, rather than listing protocols. That’s the difference storytelling makes in practice: same substance, dramatically different retention.

The story is the brand identity, not a layer on top of it

A brand identity that’s just a logo and a colour palette is only half-built. The other half is the narrative underneath it — what the business stands for, why it exists, and what it’s actually like to deal with. When I rebranded The Hollybush Bar & Restaurant, the visual identity mattered, but what actually shifted bookings was making sure someone scrolling past on their phone understood, in a few seconds, exactly what kind of evening they’d get there. That’s story doing the work visuals alone can’t.

Make the customer the subject, not the business

The brands that tell their story well almost always centre the customer’s problem, not their own achievements. A laundrette’s story isn’t “we’ve been dry cleaning for twenty years” — it’s “you get your Monday morning back.” That reframe is small on paper and enormous in practice, because it’s the difference between a business talking about itself and a business talking to the person it’s trying to reach.

How to actually build it, without overengineering it

• Start with the real problem you solve, stated plainly — not the version dressed up for a pitch deck.
• Know who you’re actually telling it to. The story for a landlord filling short-term lets isn’t the story for a family looking for their first home.
• Use real specifics, not generic claims. “Fast” and “reliable” are what everyone says. A specific detail — how a problem actually got solved for a real customer — is what sticks.
• Keep it consistent everywhere it shows up — website, social media, in person at the counter. A story that changes depending on the channel isn’t a story, it’s inconsistency with better production values.

Where it actually shows up, if it’s working

You’ll notice storytelling working less in a metrics dashboard and more in ordinary moments: a customer who describes your business accurately to a friend without needing it explained, or new enquiries that already understand roughly what they’re getting before the first conversation happens. If your marketing spend is going up but neither of those things is happening, the story either isn’t being told or isn’t the right one.

If your brand’s story hasn’t been properly worked out — or hasn’t been carried consistently from the identity through to the marketing and the website — that’s usually the highest-leverage place to start before spending more on ads to amplify a story that isn’t landing yet.

Rebranding gets treated as a coat of fresh paint — new logo, new colours, job done. Done properly, it’s closer to renegotiating what your business is allowed to claim about itself, and then making sure every touchpoint agrees with that claim. Here’s when it’s actually worth doing, and what changes when it’s done right rather than cosmetically.

The signs it’s actually time, not just overdue for a refresh

• The brand hasn’t kept pace with the business. If you’ve expanded services, moved upmarket, or started serving a different customer than the one your original branding was built for, the visual identity is describing a business that no longer exists.
• You’re indistinguishable from the competitor next door. If a customer couldn’t tell your marketing apart from a rival’s with the logo covered, the brand isn’t doing its job regardless of how polished it looks.
• A merger, acquisition, or expansion has happened. Two businesses becoming one, or one business entering a new market, creates a real need for a single identity that doesn’t quietly contradict itself across locations.
• The look is visibly dated. This is the most obvious sign and the least useful one on its own — an outdated look is worth fixing, but only alongside the reasons above, not instead of them.

What a real rebrand looked like in practice

The rebrand I did for Triage Vets in Mill Hill is a good example of what actually changes. The previous identity looked like a generic clinical practice — nothing wrong with it, but nothing that told a pet owner what made this practice different from any other vet nearby. The rebrand wasn’t about making it prettier for its own sake; it was about making the practice’s approach to care visible before a client had even walked through the door, in the signage, the website, and the materials in the waiting room.

Where the actual value shows up

The return on a rebrand rarely shows up as a single metric on a dashboard. It shows up in smaller, harder-to-fake ways: a customer describing your business accurately to a friend without prompting, staff feeling genuinely proud to represent the brand rather than apologising for it, and new enquiries that already understand roughly what they’re getting before the first conversation. If none of those shift after a rebrand, the visuals changed but the underlying identity didn’t.

The order that avoids wasting the budget

Rebrands go wrong most often when the design work starts before the thinking does. The sequence that actually holds up:

• Audit what you have. Be honest about what’s working and what isn’t before deciding what to change — not everything needs to go.
• Define the actual goal. “Attract a different customer” and “look more established” are different problems with different solutions. Naming the real one up front stops the project drifting halfway through.
• Understand who you’re actually rebranding for. Not the business owner’s taste — the customer’s expectations and the gap the brand needs to close for them.
• Let visuals follow the strategy, not the other way round. A logo concept before the positioning is settled usually has to be redone once the positioning catches up.
• Launch with a plan, not a quiet swap-out. Customers and staff both need a reason the change happened, or it reads as random rather than intentional.

A rebrand done in that order takes longer than picking a new logo off a moodboard, but it’s the difference between a business that looks different and one that’s actually repositioned. If you’re weighing whether now’s the time, it’s worth starting with an honest rebranding conversation before committing to any visual direction.

A brand identity isn’t the logo. It’s what’s left in someone’s head after they’ve closed the tab — whether they can describe your business in one sentence, and whether that’s the sentence you’d want them to say. I’ve built brand identities for businesses ranging from a laundrette to a security firm to a restaurant, and the ones that actually work share the same handful of habits. Here’s what I look for before a single pixel gets designed.

Start with what’s actually different, not what sounds good

“Quality service” and “trusted by our customers” aren’t a brand identity — they’re what every competitor’s About page says too. When I worked on Protech Motors‘ identity, the useful starting point wasn’t a mood board, it was a plain conversation about what actually set them apart from the garage down the road. A brand identity built on a real, specific difference is easy to design around. One built on generic reassurance ends up looking like everyone else’s, no matter how much time goes into the logo.

Make the visual system survive outside the mood board

A logo that looks great on a white background in a pitch deck can fall apart the moment it’s embroidered on a uniform, printed on an invoice, or shrunk to a favicon. Before I sign off on any identity, I test it in the places it’ll actually live — signage, packaging, a social profile picture, a printed menu — not just a polished presentation slide. That’s where colour palettes that seemed fine suddenly clash, and where typography that looked elegant becomes unreadable at a small size. Metro Laundrette & Dry Cleaners needed a mark that still read clearly on a shopfront sign from across the street — a very different test to how it looks on a screen.

Say what you do in the words your customers actually use

Messaging is where most brand identities quietly fall apart, because the language a business uses internally is rarely the language its customers use to describe it. If your own team needs the tagline explained to them, a customer certainly will. When I rebuilt the identity for The Hollybush Bar & Restaurant, the brief wasn’t clever wordplay — it was making sure someone scrolling past on their phone, deciding where to eat tonight, understood exactly what kind of night they’d get.

Keep every touchpoint pulling in the same direction

A brand identity isn’t one asset, it’s dozens of small decisions that all need to agree with each other — the website, the social profiles, the signage, the email signature, the invoice template. The moment one of those goes rogue — a different logo file used on the van, an old colour surviving on a business card — the whole thing starts to look unmanaged, and customers notice inconsistency even when they can’t name what’s wrong. This is usually the point where a brand identity needs someone who can see the whole system, not just design the next asset in isolation.

Judge it by what it does, not how it looks in isolation

The real test of a brand identity isn’t whether you like looking at it — it’s whether it changes how people behave. Do the right customers recognise themselves in it before they’ve read a word? Does someone describe your business accurately to a friend, unprompted? A brand identity that photographs well but doesn’t shift either of those is decoration, not identity.

If you’re building or rebuilding a brand identity, it’s worth treating it as one connected system from the start — logo, messaging, and the actual website it all has to live on — rather than commissioning the pieces separately and hoping they align later. I cover the full process on my brand identity page if you want to see how that fits together.

Every brand design brief starts the same way: a client with a clear idea of what they want, and a business that needs something more specific underneath it. This is a walk-through of how that gap actually gets closed, using a real project rather than a general framework — the rebrand I did for Metro Laundrette & Dry Cleaners.

Listening for what’s underneath the brief

The client’s opening brief was simple: the current look felt tired, and they wanted to modernise it. That’s a starting point, not a strategy. Before any design work began, the real questions were about the business itself — who actually walks through that door, what makes them choose this laundrette over the one two streets away, and what the business had become since its original branding was done. A brand design built straight off “make it look more modern” ends up as exactly that: a facelift with nothing underneath it.

Turning that into a visual identity

Once the actual positioning was clear, the visual decisions followed from it rather than preceding it:

• The logo needed to work as a full lock-up, an emblem on its own, and a simplified white version for dark backgrounds and signage — not one version stretched to fit every use case.
• The colour had to read as clean and modern without tipping into cold or clinical, which matters a great deal for a business people associate with trusting it with their belongings.
• The typography needed to hold up at shopfront scale and on a till receipt equally, which ruled out a lot of the more decorative options that looked good in a mock-up.

Where clients push back, and why that’s useful

Clients don’t always agree with the first direction, and that’s not a problem to route around — it’s information. When a colour or logo direction gets pushback, the useful response isn’t to defend the design, it’s to understand what the reaction is actually about. Often it’s not really about the colour at all — it’s a concern about whether the new look still feels like “them.” Working through that honestly, rather than just supplying more options, is what gets to a result the client will actually stand behind once it’s live.

What changed once it shipped

The result wasn’t just a new logo — it was a full identity carried through the shopfront, marketing materials, and a rebuilt website, so the same brand showed up consistently everywhere a customer might encounter it. That consistency is the part that’s easy to skip under time pressure, and it’s usually the first thing that erodes if nobody owns the whole system.

What this project says about the process generally

Cohesive brand design isn’t a single deliverable, it’s a sequence: understand the business properly first, let the visual decisions follow from that rather than lead it, expect and use pushback rather than avoid it, and make sure the result actually gets carried through every place a customer sees the brand. That sequence is the same regardless of whether the client is a laundrette, a security firm, or a restaurant — only the specifics change.

If you’re weighing up a rebrand or a fresh brand identity and want to see how this looks end to end, it’s worth looking at the finished result rather than just the brief that started it.

I’m Terence Meghani. I do brand identity, marketing, web development, and photography — mostly for businesses in Hertfordshire and London who need someone who can own the whole thing rather than handing pieces of it to three different suppliers who’ve never spoken to each other.

How I got here

I started my first business at 16. It didn’t last, but it taught me more about actually running something than any course would have — how to sell, how to follow through, and how to notice when a plan isn’t working and change it rather than defending it. I never went the traditional design-school route. Most of what I know came from doing the work, badly at first, on real projects with real budgets, and from travelling enough to see how differently businesses operate outside whatever bubble I’d have stayed in otherwise.

Before I worked for myself, I was in sales and marketing at Staples and at Three (Hutchinson UK) — jobs that taught me how to read a client’s actual problem rather than the one they think they have, and how a business decision looks from the other side of the table. At 23, I started the business that’s turned into what I do now: helping brands tell their story properly, through design, marketing, and photography, rather than treating each of those as a separate purchase.

What I actually do

Four things, and I treat them as one connected job rather than four separate services:

• Brand identity — logo, colour, typography, and the messaging underneath it, built to hold up outside a mood board.
• Marketing — campaigns built around what a business actually offers, not a generic template dressed up with the client’s logo.
• Website development — sites built to convert, not just to look good in a portfolio screenshot.
• Photography — because most brand identities fall apart the moment real photography is needed and nobody planned for it.

Who I’ve worked with

The range is wide on purpose. I’ve rebuilt the identity for a laundrette, resolved cyber-security messaging for News UK, worked on brand campaigns for Royal London, and helped the NHS communicate more clearly with the public. Locally, that’s meant projects like Protech Motors, Triage Vets, Kemp Services, and The Hollybush Bar & Restaurant — each one different, but built the same way: understand the business properly before touching the design.

What clients say

“The custom website designed by Terence transformed our business. His SEO expertise helped us rank higher and reach new audiences.” — Rishi, Xclusive Services

“Terence played a crucial role in resetting our cyber messaging. His efforts have had a lasting impact on our communication strategies.” — Mun, News UK

“Thanks to Terence’s marketing and web design skills, our sales and market presence have significantly improved.” — Kush, La Royale Banqueting Suites

How I actually work

I don’t believe small businesses need to choose between cheap and generic, or expensive and slow. Most of the value I add comes from doing the strategic thinking myself rather than farming it out, and from staying involved after launch rather than disappearing once the invoice is paid. If something breaks on a Tuesday, you’re talking to the person who built it, not a support queue reading from a script.

If you want to see what that looks like in practice, the rebranding and website maintenance pages both cover real examples in more depth. Or just get in touch — I’d rather have the actual conversation about your business than have you read a bio guessing at it.