A walk through a real custom build: enquiry forms, a testimonials carousel, an image-led blog and a clean domain migration.
Most write-ups of a website build are a list of features. This one is closer to what actually happened, including the parts that took longer than expected.
A West London driving school with a real problem: enquiries were coming in by phone, and anyone who found them outside working hours had no way to get in touch that felt like being dealt with. The old presence also sat across more than one address, which split whatever search value they had.
What they needed was straightforward to describe and less straightforward to build. Somewhere for a nervous first-time learner to understand what lessons involve, see that other people had good experiences, and get in touch without picking up the phone.
The site is thirteen pages, and they share a single header and footer. That sounds like a technical detail and it is really a maintenance decision.
When the school changes its phone number, that is one edit, not thirteen. When a new page is added to the navigation, it appears everywhere at once. Sites built page by page drift: one page has last year's phone number, another has a link that goes nowhere, and nobody notices until a customer does.
Shared parts mean the site cannot disagree with itself.
A form is the easiest thing on a site to get almost right and the easiest to get quietly wrong.
It needed to be short, because a nervous learner will not fill in twelve fields. It needed to say clearly what happens next. And it needed to actually arrive, which sounds obvious until you meet the number of sites where the form has been silently failing for months and nobody knew.
So it sends through a proper mail service rather than the default, it logs every submission as a backup, and if sending ever fails the visitor is told to email directly rather than being thanked for a message that went nowhere.
Alongside it, a package selector: the learner picks what they are interested in, and that comes through with the enquiry. The school knows what the conversation is about before they pick up the phone.
The testimonials carousel uses photos of actual students who passed, with permission. That is a small thing that matters more than it should.
Stock photography on a local service business is worse than no photography. Everyone can tell, and it quietly suggests that if the pictures are borrowed, the reviews might be too. Real students holding real pass certificates do a job no amount of copy can.
Driving schools compete on questions: what happens in a first lesson, manual or automatic, how many lessons will I need. Those are searched constantly and answered badly.
The blog is built so the school can publish without calling us. It carries the same shared header and footer, so a new post inherits the design automatically, and it is image-led because a guide about roundabouts is far more use with a diagram than without one.
The site was moving and so was the address, which is the harder version of a rebuild.
Every existing page was listed before anything was built. Each one got a destination on the new site. Permanent redirects went in so anyone arriving from an old link or an old search result lands in the right place rather than an error page. A sitemap was submitted and Search Console set up to watch what happened.
The result is one canonical address instead of value split across several, which is a better position than they started from.
None of that is interesting work. All of it is the difference between a rebuild that keeps its rankings and one that quietly loses them. There is more on this in when to move off a site builder.
Two things, honestly.
We would gather the photography earlier. Content is almost always what holds a build up, and waiting on images while everything else is finished is a frustrating way to spend a fortnight.
And we would agree the blog structure at the start rather than adding it once the main site was done. Retrofitting a section is always more work than planning for it, even when the retrofit goes smoothly.
A thirteen-page custom site, written from scratch, that answers the questions learners actually ask, takes enquiries reliably around the clock, and sits on a single address the school owns.
You can see it in our work, and if you want something similar, tell us what you are after.