Your Web DeveloperBuilt properly.
Then kept that way.

Your Web Developer does the building. New pages and new sections, the things that have quietly broken, speed, and the technical work that stops a site ageing badly. Most months this is a few hours; in a build month it is most of them.

Web Developer Builds it, fixes it, and keeps it fast and standing up.
Briefed by your Marketing Manager, who decides each month whether this role is needed and for how many hours.
Part of your hours · up or down, month to month
Why this role

What this person does for you

They build the thing

New pages, new sections, forms that work, and the integrations that make two systems cooperate.

They fix what broke quietly

Sites decay. Plugins conflict, forms stop sending, images bloat. Somebody has to be looking.

They keep it quick

Speed is engineering work, not a plugin. Page weight, queries and images are where it is won.

Problems and solutions

What people come to us with

These are the sentences business owners actually say on the first call, and what a Web Developer does about each one. If one of them is yours, the audit will tell you how many hours it takes to fix.

My website is slow and nobody can tell me why

Speed is diagnosed, not guessed at: page weight, image sizes, database queries and what blocks the first paint. Most small-business sites are slow for two or three specific reasons and they are usually fixable in hours rather than weeks.

The contact form stopped sending and we only found out from a customer

Forms get checked as part of the monthly hours rather than when somebody complains. When one breaks it is fixed and then tested end to end, including where the message actually lands.

I need changes made and the agency that built it has gone

We take over sites we did not build. The first job is usually working out what is actually running under it, and you get told plainly if it would be cheaper to rebuild than to keep patching.

Something broke after an update and now I am afraid to touch it

Updates are applied and then checked, on a schedule, by somebody whose job that is. If an update does break something it gets rolled back and fixed rather than left.

It looks fine on my laptop and wrong on a phone

Everything is built and checked at phone width, because that is where most of your visitors are. A layout that falls apart on a phone was never finished.

I want to sell online and my site cannot do it

WooCommerce and Shopify work both sit on the bench. Whether that is worth doing, and what it would cost in hours, is one of the things the audit answers.

Skills and remit

What they are good at

Disciplines rather than software. The bench changes tools as the work changes; what does not change is what the role is accountable for.

  • Building pages and sections to a design rather than approximating one
  • WordPress theme, block and template work
  • WooCommerce and Shopify storefront work
  • Forms, feeds and the plumbing between two systems that were not built to talk
  • Diagnosing why a site is slow: page weight, images, queries, render path
  • Finding what has broken quietly — plugin conflicts, forms that stopped sending
  • Keeping a platform and its dependencies current without breaking the site
  • Making it work at phone width, not just look like it does
And what it is not

Outside this role

Every agency page reads as though one person does everything, which is how you end up disappointed by work nobody agreed to. These sit outside this role, and where something is simply somebody else’s job we have said whose.

Design decisions

A layout that needs rethinking goes to the Designer first.

The words on the page

That is the Content Writer.

Hosting, DNS and backups

Security & Hosting own the platform underneath.

Bespoke software

This is website work. A full application is a separate conversation and a separate quote.

A month in the work

What the hours actually go on

Hours are recorded against your account and reported back to you every month, so you can see exactly where the time went rather than taking it on trust.

Nobody is on a retainer here. In a quiet month you buy fewer hours of this role, and in a heavy one you buy more.

  • Ships the changes agreed in the plan
  • Fixes what has broken since last month
  • Keeps the platform and its dependencies current
  • Watches load times and page weight
  • Handles the technical half of anything the content needs
How it runs

How they work on your business

You never brief this role directly, and you never chase it. There is one route in and one route back, and it is the same every month.

  1. You raise it

    One conversation with your Marketing Manager. You describe the problem, not the solution — working out which discipline it belongs to is their job.

  2. It goes in the plan

    With hours against it, agreed with you before anything starts. If it does not fit this month, you are told that rather than discovering it later.

  3. The work happens

    The build or the fix is done, tested at phone width, and shown to you before it is live.

  4. You get it back

    Reviewed by your Marketing Manager before it reaches you, reported with the hours it actually took, and kept on the rolling view for next quarter.

How you would know it is working

Things you report as broken stop coming back, and the site gets faster between audits rather than slower.

The first thirty days

Where they would start

Fixes whatever the audit found that is actually broken, before anything new is built on top of it.

Your audit works out whether you need a Web Developer at all, and for how many hours. We would rather tell you that you do not.

Book your audit