Systems
How the system works.
Architecture-first builds. AI-assisted workflow. EU-sovereign infrastructure. Performance standards. The technical reasoning behind every UK Web Marketing site, written in the register I'd use on an engineering call.
01
Architecture-first builds.
Every site is structured before it is designed. Information architecture → routes → data model → templates → visual layer. Reverse-order from typical agency workflow, where visuals lead and structure is reverse-engineered around mockups.
The build pipeline reads top-to-bottom: define the URL graph, define the render contract, define the data shape, then style. By the time anyone opens a design tool, the system already exists.
Routes-first — URL graph before any UITemplate-first — render contract before any stylingNo plugins — direct HTML, CSS, JavaScriptStatic-first — SSG with islands where dynamism is requiredAstro 6 — content-led islands architectureProgressive enhancement — works without JavaScript
02
AI-assisted workflow.
AI is used for acceleration, not decision-making. A pair-programming model: the AI handles boilerplate, scaffold, and lint-fix; the engineer makes architectural decisions. The split is deliberate and durable, because the parts of the work that fail quietly when delegated are exactly the parts that compound over months.
Used for
Scaffolding — boilerplate, file scaffolds, repetitive markupStyle sweeps — site-wide token migrations, refactor passesContent first-pass — outlines, draft copy, editing promptsQA checklists — pre-launch sweeps, accessibility audits
Not used for
Schema design — relational + content models stay with the engineerAuthentication — security primitives are not delegatedData flow — control-flow architecture stays with the engineerBrand voice — written register stays with the engineer
03
EU-sovereign infrastructure.
Hosting, mail, analytics, and CRM run on European-jurisdiction infrastructure. The stack is designed for UK regulated verticals where sub-processor disclosure and data residency are not decorative — they decide whether the site is fit for use.
Compliance frameworks the stack is aligned to:
GDPR · UK Data Protection Act 2018DSPT · NHS Data Security & Protection ToolkitKCSIE · Keeping Children Safe in EducationSRA Rule 6 · Solicitors Regulation Authority transparencyICAEW · Institute of Chartered Accountants
-
VercelHosting + edgeLondon (lhr1) -
ResendTransactional emailEU (Ireland) -
CloudflareDNS + email routingEU edge -
StripePaymentsPayments Europe (Ireland) -
PlausibleAnalytics · cookielessEU -
CapsuleCRM (Growth Engine+)Manchester, United Kingdom
Cross-link: /partners — verifiable vendor list and outbound resource directory.
04
Performance standards.
Fast load, minimal dependencies, stable architecture. The targets below are the floor on every tier, measured on a 4G throttled mobile profile — not best-case desktop numbers.
LCP < 1.0s — Largest Contentful PaintINP < 200ms — Interaction to Next PaintCLS < 0.05 — Cumulative Layout ShiftLighthouse Performance ≥ 95 — synthetic baselineZero third-party JavaScript by defaultStatic-first delivery — SSG, ISR where dynamism is requiredWCAG 2.2 AAA contrast — accessibility floor on every tier
05
Engineering philosophy.
We don't build pages. We build systems that run them. Pages are content; systems are infrastructure. Treat every build as a system, not a surface — optimised for clarity, speed, and long-term maintainability.
Systems-first design logic. Performance-led engineering execution. Structurally minimal digital architecture.