Web Design & Development
Web Design & Development
Websites built from scratch — fast, readable on a phone, and simple enough that you can update them yourself.
Websites built for your business, not for a template gallery
Most sites fail for the same reason: the content is squeezed into a layout that was designed before anyone knew what the page had to say. We work the other way around. We start with what the site has to do — sell, explain, collect enquiries, publish — and design outward from there.
That means the page plan is agreed with you before any visual work starts. You see the structure, the order of the sections and what each one is for, while changing it still costs a conversation instead of a rebuild.
What is included
- Structure and page plan agreed with you before design work begins.
- Responsive layouts. The phone version is designed, not shrunk — narrow screens get their own layout decisions.
- An admin panel where you edit text, pages, images and menus yourself, without calling us.
- Search engine basics done properly: clean URLs, unique titles and descriptions, an XML sitemap, canonical tags and structured data.
- Accessibility and reduced-motion support built in from the start, not bolted on after a complaint.
- Two languages where you need them, with correct
hreflangtags and translated URLs rather than a machine-translation widget.
How the project runs
- Scope. We go through what the site must do and who it is for. You get the page plan in writing.
- Design. Layouts for the pages that matter, reviewed at full width and on a phone.
- Build. The site is built on a staging address you can open and click through at any point.
- Content. Your text and images go in. If you are migrating, existing content is carried across rather than retyped.
- Launch. DNS is switched after the site is verified on the temporary address, so the public URL never points at a half-finished copy.
The standards we build against
Google evaluates page experience through three field measurements, collectively called Core Web Vitals. A page is considered good when Largest Contentful Paint (LCP) stays under 2.5 seconds, Interaction to Next Paint (INP) stays under 200 milliseconds and Cumulative Layout Shift (CLS) stays under 0.1. These are assessed at the 75th percentile of real visits, which means three quarters of your visitors have to get that experience — not your test machine on a good connection.
Those thresholds are not our promise; they are the bar the work is measured against. We report where the site lands before handover, and the layout decisions that affect them — image sizing, font loading, reserved space for anything that loads late — are made during the build, where they are cheap, instead of afterwards, where they are not.
The same applies to content structure. Headings follow a real hierarchy, structured data describes what the page actually is, and the markup stays clean enough that both search engines and language models can extract meaning from it without guessing.
Custom build or a website platform
A hosted website builder is genuinely the right answer for some businesses, and we will say so. The trade-off is worth understanding before you choose.
| Website builder | Custom build | |
|---|---|---|
| Time to first version | Days | Weeks |
| Layout freedom | Within the template | Whatever the content needs |
| Page weight | Ships the whole framework | Only what the page uses |
| Moving elsewhere later | Export is usually partial | Files and database are yours |
| Monthly cost | Per-seat subscription | Hosting only |
The decision usually comes down to how long the site has to last and how specific its content is. A three-page brochure that will be replaced next year does not need a custom build. A site that carries your catalog, your services and your search traffic for the next five years probably does.
When we are not the right fit
- You need a working site this week. A custom build does not compress that far.
- You want a marketplace, a social platform or a product with user accounts and billing. That is software development, and it should be scoped as such.
- You want the site built and then handed to whoever is cheapest to host it. We can do that, but the argument for working with us is that the people who built it keep it online.
What happens after launch
Because we also run hosting and manage servers, the site is not handed to a third party the day it goes live. Certificates, backups, updates and DNS stay with the people who know how the site is put together. If something breaks at 9am, the person looking at it has seen the code before.
What we need from you
A website project moves at the speed of its content. The build is predictable; waiting for text is not. Knowing this up front shortens most projects by weeks.
- Who the site is for, in one or two sentences. Not a demographic — a description of the person who lands on the page and what they came to find out.
- The text, or the decision that we should write it. Either answer works; leaving it open is what stalls projects.
- Your logo in a vector format if one exists, plus any brand colors you are committed to.
- Access to the domain, or the name of whoever holds it. This is the single most common delay at launch: nobody can find the registrar login.
- One decision-maker. Feedback from four people with different opinions is how a design ends up satisfying none of them.
Anything you do not have, say so early. There is a version of the project that starts without final text and a version that waits for it, and they are priced and scheduled differently.
What we hand over
At the end of the project you get the site, the credentials and the ability to leave. Concretely, that means the domain registered in your name, admin access to the site, the database and the files, and a walkthrough of the panel delivered in person or recorded.
The reason this list gets spelled out is that "we built your site" and "you own your site" are not the same sentence, and the difference only becomes visible on the day you want to move.
Frequently asked questions
Who owns the website and the domain when the project is finished?
You do. The domain is registered in your name, the code and the database are yours, and you get the credentials. This is worth asking every agency you speak to: under copyright law the person who writes the code holds the rights unless they are transferred, and a domain registered in an agency's own account stays in that account. We transfer both as a matter of course.
Can I edit the site myself afterwards?
Yes — that is what the admin panel is for. Text, pages, images, menus, services and SEO fields are all editable without touching code. We walk you through it before handover.
How long does a website take?
It depends on how many pages there are and how ready your content is. Content is the usual bottleneck, not the build: a site with text and images waiting moves several weeks faster than one where the copy is still being written.
Do you redesign existing sites, or only build new ones?
Both. For a redesign we keep the URLs that already earn traffic and redirect the ones that change, so the rankings you have built up survive the move. Dropping that step is the most common way a redesign loses traffic.
Will the site be fast on a phone?
That is a design decision before it is a technical one. Mobile layouts are designed separately rather than scaled down, images are sized for the screen that requests them, and we measure against Google's Core Web Vitals thresholds before handover rather than hoping.
Do you write the content as well?
We structure it and we will tell you plainly when a page is not saying enough, but the words about your business are best written by people who run it. If you want copy written for you, say so at the scoping stage and we will price it in.