SERVICE 01 / WEB DEVELOPMENT

Websites that hold up under real traffic.

Hand-built marketing sites and WordPress builds on Bricks or Gutenberg — measured against Core Web Vitals, not a template preview.

Astro / Tailwind / Bricks / Gutenberg / Laravel / Cloudflare

Fixed scope, agreed in writing before the build starts.

What this covers.

Custom design, no page-builder cruft

Layouts drawn for your content, then built with the smallest stack that carries them.

A performance budget

Page weight and layout stability are checked before launch, not after a complaint.

WordPress where WordPress fits

Bricks or Gutenberg, never Elementor — an editor your team can use without breaking the page.

Accessible by default

Keyboard paths, focus states and measured contrast on every text/ground pair.

Analytics and consent wired

Nothing loads before a visitor agrees, and the choice is remembered.

Documented handover

Code, domain, DNS and accounts transfer to you, with the deploy written down.

STACK

Four stages, always in this order.

  1. STAGE 01

    Survey

    What exists, what it must do, and who maintains it after handover.

  2. STAGE 02

    Plan

    A written scope and a fixed quote before anything is built.

  3. STAGE 03

    Build

    Slices you can click in staging, with changes priced in writing.

  4. STAGE 04

    Maintain

    Monitoring, updates, backups and support under a one-year warranty.

Questions this page always gets.

Do you work with our existing WordPress site?

Often. If the content and structure are sound, a rebuild of the theme is cheaper than a migration. If the plugin stack is the problem, we say so before quoting.

Who writes the copy?

You can supply it, or we write it from the survey. Either way the copy is agreed before design is finalised, because layouts follow content.

What happens after launch?

You own the code, domain and accounts. Ongoing maintenance, updates and support are a separate decision, not a trap.

Can you take over a site someone else built?

Yes, after a survey. Half-finished builds are quoted only once we know what the code actually does.

The rest of the sheet.

Scope it with a call, not a form war.