What a business website is actually for
A website has one job: turn a stranger who is already interested into someone who contacts you. Almost every design argument becomes easy once that is agreed, because the question stops being what looks impressive and becomes what removes hesitation.
Most visitors arrive on a phone, having clicked from a search result or an ad, giving you a minute or two of divided attention. In that time they need to understand what you do, believe you can do it, and find an obvious way to get in touch. A site that achieves those three things while looking plain will outperform a beautiful one that does not.
This is also why we resist the single long scrolling page that tries to cover everything. It reads as vague to a visitor and reads as unfocused to a search engine, which then does not know which query the page deserves to answer.
Structure comes before design
The first deliverable is not a visual. It is a map: which pages exist, what each is for, what question it answers, and how someone moves between them. Getting this right is most of the work, and changing it later is expensive.
As a rule, every distinct thing you sell earns its own page. Nine services means nine service pages, each able to rank for its own searches and each able to receive traffic from an ad about that specific thing. The same applies to the industries or markets you serve when their needs genuinely differ.
Above that sits a small number of pages doing different work: a homepage that orients and routes, an about page that builds trust, proof in the form of case studies and testimonials, a blog for questions buyers ask before deciding, and contact.
Design, mobile, and accessibility
We design mobile first, not as a slogan but because that is where most of your traffic is. A layout that works at arm length on a phone almost always works on a desktop; the reverse is frequently false.
The practical rules are unglamorous: readable type at a real size, sufficient contrast, tap targets that a thumb can hit, forms short enough to finish standing up, and contact options reachable without hunting. Animation is used where it aids comprehension and avoided where it merely demonstrates that we can.
Accessibility is treated as part of the job rather than an add-on. Semantic headings, alternative text, keyboard navigation, and contrast ratios help people who need them and are increasingly a legal expectation in the UK, EU, and US markets.
Technical foundations and speed
Speed is a conversion issue before it is a ranking issue. Visitors abandon slow pages, and on a mobile connection the difference between two seconds and six is the difference between an enquiry and a bounce.
We handle the fundamentals during the build rather than bolting on a plugin afterwards: compressed and correctly sized images in modern formats, lazy loading below the fold, minimal blocking scripts, sensible caching, and a theme that does not load a page builder framework to render a paragraph.
Alongside that sits the search infrastructure. Schema markup so search engines understand what the business and each page represent, a clean sitemap, canonical tags, proper heading hierarchy, and analytics configured to record enquiries rather than page views.
Words do more work than pictures
The most common reason a redesign fails to change anything is that the new site says the same vague things as the old one in a nicer font. Design cannot rescue copy that does not tell a visitor what you do, who for, and why you.
We write or rewrite the core pages as part of the build. That means specifics instead of adjectives: what is included, what it costs or how pricing works, how long it takes, who it suits, and who it does not. Naming who you are not for is one of the most effective trust signals available and almost nobody uses it.
If you have existing copy that works, we keep it. The goal is a site that sounds like your business rather than like an agency template.
Enquiries, forms, and integrations
A form that asks for eleven fields will lose most of the people who intended to fill it. We ask for the minimum needed to have a useful first conversation and let the rest emerge in that conversation.
Every enquiry route is tested before launch and after: the form arrives in the right inbox, the WhatsApp link opens with a sensible pre-filled message, click-to-call works on mobile, and nothing silently fails into a spam folder. Email deliverability is configured properly, because a contact form that quietly stops working is a remarkably expensive fault to leave undetected.
Where it helps, enquiries feed straight into a CRM, a shared inbox, or an automated acknowledgement so nobody waits until Tuesday for a reply to a Saturday enquiry.
Launch, handover, and what happens after
Launch is a checklist, not an event: redirects from old URLs so existing rankings survive, forms tested, analytics firing, speed verified, search console submitted, and a full backup taken before and after.
Then we hand over properly. You get a walkthrough of how to edit text, images, blogs, and service details, plus written notes for whoever inherits it after you. Everything stays in your name, and if you part ways with us you take the whole site with you.
After launch, most sites need attention rather than maintenance: watching which pages produce enquiries, adding the content that questions reveal is missing, and keeping the platform updated and backed up.
Rebuild or improve what you have
A full rebuild is not always the right answer, and we will tell you when it is not. If the structure is sound and the platform is healthy, fixing speed, rewriting the core pages, and adding proper service pages often produces most of the benefit at a fraction of the cost.
A rebuild genuinely earns its cost when the structure cannot support what the business now sells, when the platform is insecure or unmaintainable, when the site cannot be edited without a developer, or when it fails badly on mobile. We assess that honestly at the audit stage rather than defaulting to the larger project.