How long does a website take?

A focused marketing site usually runs six to ten weeks from kick-off to launch. Larger content platforms run twelve to sixteen. In our experience the variable is content and sign-off, not code.

Can you work with the site we already have?

Often, yes. We can rebuild the front end on top of existing content, or repair a site that works but is slow and awkward to edit. On the first call we will tell you plainly whether a rebuild is cheaper than a repair.

Do we own the code and the accounts?

Yes. Code, domain, hosting, analytics and Search Console stay in your name. We work inside your accounts rather than holding them.

We quote a fixed price per project after scoping, and the scope, timeline and price are agreed in writing before work starts. We do not publish a rate card because the honest number depends on how many page types you need, not on how many pages.

Is it mobile-friendly?

Every build is designed at mobile width first and tested on real devices. Most of your visitors will be on a phone, and the decisions that follow from that — reading order, tap targets, form length — are made at the start rather than squeezed in at the end.

Pillar 01 · Web design & development

Websites built to be used, not just launched.

A website is the one piece of marketing you fully control. It has to load quickly on a phone, make the next step obvious, and let your team change a paragraph without opening a support ticket. That is the standard we build to.

Request a proposal How the work runs

6–10 weeks for a marketing site
WCAG 2.2 AA baseline
Fixed project price

6–10 weeks

Typical build for a marketing site

WCAG 2.2 AA

Accessibility baseline on every page

Fixed price

Agreed before any design starts

In practice

Six signs the website is holding the business back.

Any two of these and the site is costing more than it returns. We check for all six in the first week, before quoting anything.

Every enquiry arrives by phone

If nobody fills in a form, the site is not doing any qualifying for you. That is usually a page problem, not a traffic problem.

You cannot change a sentence

Content that waits three days for a text edit stops being written at all. Sites like this go stale within a year.

The homepage is the only page that ranks

One page trying to cover four services ranks properly for none of them, and your best service page never gets seen.

It takes four seconds on a phone

Visitors leave before the hero finishes loading and you never see them in a report — they just never became a row.

Each new page looks slightly different

Without a component library, every new landing page restarts the design conversation and the site drifts.

You avoid sending the link

The fastest diagnostic there is: if you would not put the URL in a proposal, neither would a client.

The work

How the work runs.

Every stage below is part of the scope, in this order.

What we actually build

Marketing sites, brochure sites for professional services, multi-language builds and larger content platforms. We work in modern frameworks and ship onto infrastructure in your name. Every build includes a component library, so new pages reuse patterns that have already been designed and tested rather than drifting into a slightly different look.

Marketing and brochure sites
Content-managed platforms
Multi-language builds
Design systems and component libraries

Performance is a design decision, not a fix

Speed is decided long before anyone runs a test. It is the image sizes, the fonts, the third-party scripts and the eighteen plugins nobody audited. We set a performance budget at the start — page weight, Largest Contentful Paint, interaction delay — and we test on a throttled mobile connection, not a studio laptop. If a feature breaks the budget, it gets a different design, not an exception.

Accessibility and the unglamorous details

Keyboard navigation, contrast ratios, labelled form fields, visible focus states, a heading order that still makes sense with the styling switched off. WCAG 2.2 AA is the baseline. Alongside it sit the things that quietly break sites a year after launch: redirect maps, useful 404 pages, XML sitemaps, canonical tags, backups and a route back if a deploy goes wrong.

You can change it without us

Every build ships with an admin area shaped around how your team actually works: pages, services, articles, images and the enquiries coming in. If changing a sentence needs a developer, we have designed the wrong thing. We hand over the accounts, the documentation and a walkthrough, then you decide whether you need us for the next change.

Deliverables

Everything a build ships with.

Audit of your current site and analytics
Sitemap and page-by-page content plan
Wireframes and full page design
Responsive front-end build
Content management and editor training
Analytics and Search Console configuration
Redirect mapping and launch support

Before we start

Four things we need from you.

None of them is a design decision. They are the things that decide whether a build lands on time, and they are almost always the reason a project stalls.

Content you already have

Existing copy, price lists, photography, product details. We will rewrite what needs rewriting, but we start from what is true rather than blank pages.

One decision maker

One person who can sign off design and copy. Approval by committee is the most common reason a six-week build takes six months.

Access to analytics and Search Console

Read access is enough. It tells us what the current site is doing well enough to keep, before we remove it.

A named owner after launch

Someone on your side responsible for keeping the site current. We train them, document the admin, and stay available.

Selected work

Projects in this pillar.

All case studies

Titan Trade Services

A trade services website rebuilt around one job: turning local searches into real quote requests.

Doxa Relief Foundation

A charitable foundation's site, built to make the work legible to donors, volunteers and partners.

Majek College

A college website built around admissions: courses, entry requirements and the next step, in the order a prospective student looks for them.

Straight answers

The questions that come up before a rebuild.

Before you brief us, read this

All insights

20 October 2026 · 6 min

What we check before quoting a website rebuild

A redesign is often the second-best answer. These are the five things we check before quoting one — and the cheaper fixes they usually reveal.

Proposal

Send us the current site and the problem.

A link, what is not working, and roughly when you need it live. We reply with questions first, then a scope, a timeline and a fixed cost.

No sales call before we understand the problem. If we are not the right studio for the job, we will say so and, where we can, point you somewhere better.

01 — About you

Name *

Email *

Phone

Company

Current website

How did you find us?

02 — The project

Service

Kind of project

Who is this for?

The people you need it to win over.

Tell us about the project *

Where you are now, what is not working, and anything already tried.

03 — Outcomes and scope

What would a win look like?

Numbers help if you have them — enquiries, sign-ups, search visibility, launch date.

Pages, features or deliverables in mind

Rough is fine. We will shape it into a scope.

04 — Budget and timing

Budget range

A range is enough — we scope to it rather than past it.

Ideal start

Your details are used only to reply to this enquiry. See our privacy policy.

The other pillars

Websites built to be used, not just launched.