What people mean, and what I mean
Most shops have already paid someone for “web design.” They got a homepage that looks busy on a desktop, a contact form that emails a Gmail nobody checks, and a login they do not control. The look was the deliverable. Ranking was a later conversation that never happened.
I treat design as the whole page: the words, the order, the weight of the files, whose name is on the domain. A pretty screenshot that takes six seconds to appear is a broken page. Two sites can share photos and colors and still not be the same piece of work.
Phone first is not a slogan
The person who needs you is usually not at a desk. They are in a kitchen, a parking lot, a driveway. The page has to be readable at arm’s length, tappable with a thumb, and finished loading before they bounce to whoever already showed up in the map pack.
That is why I build finished HTML instead of a page builder. The builder makes it easy to rearrange sections. It also ships a pile of unused CSS and scripts with every visit. Design that ignores that pile is decoration.
What you actually get
A set of pages — 25, 50, 75, or 100 — starting with home, about, contact, services, and service areas, then the individual jobs and towns. Static files. On-page SEO on every URL. Hosting set up so the page is the thing the server hands over, not something it has to assemble.
If the look you have is good, we keep it. I would rather put a faster engine under a site that already has links than throw the links away for a blank template that is easier to bill.
Inside a build
- Layout that holds up on a phone, not just a 1440px mockup
- Type large enough to read in a driveway
- A real contact path — phone first, a short note if they will not call
- Pages written for the work and the towns, not a single “services” dump
- Files and the domain in your name
