Message before decoration
The first screen names who the offer is for and what changes for them. Visual polish on top of an unclear offer just makes the confusion load faster.
All services
Business websites, designed and built to win enquiries.
A business website on Next.js, new or rebuilt: the offer clear on the first screen, rendering chosen per page type, metadata shipped with each template, and a quote path on every service page rather than one contact form buried in the nav.
Website design and development: what is included
- For a rebuild, an audit of the current site: what ranks, what earns enquiries, what can be retired
- Page structure and offer written down before any design work starts
- Rendering strategy chosen per page type rather than applied uniformly
- Responsive interface system with documented type scale, spacing, and component states
- Next.js build with canonicals, titles, and structured data committed with each template
- Accessibility and performance verified against the deployed site, then written handover
Website design and development: what gets decided first
One responsive system
Mobile, tablet, and desktop share a type scale and spacing set rather than behaving like three separate designs that happen to share content.
Every service page can convert
A visitor who lands deep from search should be able to enquire from that page, not navigate back to a single contact form to do it.
Website design and development in 5 steps
Start from the offer, or the old site
A new site starts from who it is for and what each page has to do. A rebuild starts by crawling the current site for the pages that carry search traffic and enquiries, because a rebuild that quietly drops one of them is a downgrade.
Settle the offer and the structure
What each page is for, who it is for, which claim it makes, and what it asks for at the end. Decided in writing before design, because rearranging pages after they are built is the expensive way to have this conversation.
Choose rendering per page type
Static, incremental, server-rendered, or client-fetched, decided by how the data behaves rather than applied uniformly. This decision sets the performance ceiling for the whole site.
Build with metadata attached
Each template ships with its canonical, title, and structured data in the same commit, so there is never a version of a page live without them.
Verify and hand over
Real-device checks, keyboard and screen-reader passes, a performance budget verified against the deployed site rather than a local build, then written handover notes.
Rendering is decided per page type, not once for the site.
Most performance problems in a Next.js build come from applying one rendering mode everywhere. A marketing page that server-renders on every request is slow for no reason, and a stock level that was baked in at build time is wrong. The decision is per page type, and it is made before the build.
Static
Service pages, about, contact, legal
Rendered once at build time and served from the CDN. Fastest possible response, nothing to compute per visit. The default for anything that changes less often than you deploy.
Incremental
Blog posts, case studies, catalogue pages
Static, but regenerated in the background on a schedule or when content changes. Editors see updates without a rebuild, and visitors still get a CDN response rather than waiting on a render.
Server-rendered
Stock levels, pricing, anything per-user
Rendered per request because the data is only correct at the moment it is asked for. Slower than static and worth it only where staleness would be wrong rather than merely old.
Client-fetched
Dashboards behind a login, search results
Rendered in the browser after load. Right for interactive state that search engines never need to see, wrong for anything that should appear in results.
Working out a budget? There are guides to what a small business website costs in the UK and website design costs in Dubai and the UAE, with my starting prices and what moves a quote above them.
Website design and development: questions
How much does a business website cost?
Website builds start around £750, whether it is a new site or a rebuild of a small one. Moving a site that already ranks is priced as a migration, from £3,000, because the crawl and the redirect map come on top of the build. Beyond that, the number moves on page count, how ready the content is, how many integrations have to keep working, and whether the offer itself needs rewriting before anything gets designed. A five-page service site with copy already written is a very different job from a forty-page catalogue where half the content needs restructuring first.
How long does it take to build a website?
Most business sites take three to six weeks, once scope, content, and a review rhythm are settled. The long pole is almost never the code. It is waiting on content, logo files, product data, or a decision about what the offer actually is.
Do you build new websites, or only rebuild existing ones?
Both. A new site starts from the offer: who it is for, what each page has to say, and what it asks the visitor to do. A rebuild starts one step earlier, with a crawl of the current site to find the pages that already earn search traffic and enquiries, so none of them are dropped by accident.
Do I need a rebuild, or just a redesign?
If the current stack is sound and the problem is presentation, a redesign on the existing platform is cheaper and lower risk. A rebuild is worth it when the platform itself is the constraint: plugin weight you cannot remove, a theme nobody can safely change, no way to add a page type, or performance that will not improve without changing how pages are rendered. I will tell you which one you are looking at after seeing the site.
Who writes the content?
You know the business, so the facts have to come from you. I structure it: what belongs on which page, what order it goes in, which claims need a number behind them, and what the page should ask the visitor to do at the end. Handing over a blank CMS and calling it done is how sites end up with a beautiful shell and lorem ipsum in the service pages six months later.
What CMS do you use?
Whichever suits how often you publish. Sites that change monthly are usually better with content in the repo: nothing to log into, nothing to patch, and content changes go through the same review as code. Sites where non-technical staff publish weekly need a real CMS, either headless WordPress if your team already knows wp-admin, or a hosted headless option. This is decided before the build, because it changes the architecture.
What does it cost to run afterwards?
A Next.js site of this size runs on Vercel's Pro plan or a similar host for a small monthly fee. Vercel's free Hobby plan is for non-commercial sites, so a business site should not sit on it. There is no server to patch and no plugin subscriptions. The cost that does remain is a domain, possibly a CMS, and whatever transactional email you send. That is usually well below what a maintained WordPress install costs once hosting, security plugins, and updates are counted.
What happens after launch?
You get the repo, the deployment, and written notes on how the templates fit together and where to change what. If you want ongoing work I am available for it, but the handover assumes you might not. A site that only its original developer can maintain is a liability, not an asset.
Tell me what you need built.
A couple of sentences is enough to start. I reply within one business day.