Brand, web, commerce and intelligent systems built as one connected digital infrastructure.
Scroll
The half you cannot see decides whether the half you can survives contact with a real business.
01Where most companies are
Each of these was bought from someone competent, and each works on its own terms. The cost is not in any one of them — it is in the gaps between them, and no supplier owns a gap.
01Nobody can say which enquiry came from which spend.
02The site cannot be edited without a developer, so it goes stale.
03Design and production disagree, and neither is authoritative.
04Consent was added as a banner, so the analytics cannot be defended.
05Enquiries are answered by whoever is free, and some are not answered.
06Three dashboards report three different numbers for the same month.
We build the joins, and take responsibility for them.
02The system
Everything a customer does with a company passes along this line. Above it is what they encounter. Below it is what has to be engineered for the half above to hold.
A result, an answer, an ad
Crawlability, structured data, entity definition
SearchWithout it: Without it the company is only found by people who already know its name.
The page, and the argument it makes
Content model, design system, performance budget
ExperienceWithout it: Without it the page is redesigned every time it is edited.
The product, the proof, the price
Catalogue, stock, pricing and tax rules
CommerceWithout it: Without it the store and the system of record disagree in public.
The form, the message, the call
Server validation, consent state, attribution
AnalyticsWithout it: Without it an enquiry arrives with no idea where it came from.
The reply, and what it proposes
Routing, records, and a human approval gate
AnalyticsWithout it: Without it replies depend on whoever happens to be looking.
One report the whole company accepts
Event taxonomy, pipeline, revenue attribution
AnalyticsWithout it: Without it three dashboards report three different truths.
Every engagement starts by finding which stage is failing. It is rarely the one being complained about.
03System preview
One build, seen from the operating side: how it is found, how an enquiry moves, the stack beneath it and how it is measured. Each row names a state a finished system holds — not a number from anyone’s dashboard.
States
RunningBuilt and holdingEvery page is a defined entity with a canonical address, so search engines and answer engines read the company the way it describes itself.
canonical · hreflangStructuredschema.orgMappedinternal linksConnectedsitemap · llms.txtReadystatus · redirectsMonitoredOwned bySearch
The layers a customer sees sit on the layers they never will. The line between them is where most projects stop being anyone’s responsibility.
Visible
tokensStructuredcomponentsReadyInvisible
typed buildVerifiedbudgetsMonitoredone taxonomyConsent-gatedapproval gateActiveOwned byDevelopment
The path from a landing page to a reply is one designed flow: validated on the server, qualified before it is routed, answered by a person.
/lpLandingOne promise per pageReadycontact_form_startFormDetails asked only when neededTrackedserver checkQualificationValidated before it goes anywhereVerifiedhandoffHandoffTo an owner, with its sourceRoutedreplyResponseA person, not an autoresponderOwnedOwned byExperience
Sources converge on one event taxonomy. A lead counts once, when the server accepts it, and carries its first touch into the report.
utm · referrerTrackedpage_viewObservablecta_clickStructuredgenerate_leadVerifiedfirst touchMappedone reportCoordinatedOwned byAnalytics
04Capabilities
Strategy, design, engineering and growth are not separate suppliers here. They are four stages of the same build, with the same owners and the same source of truth.
StrategyBrandExperienceDevelopmentCommerceSearchAnalytics
05Selected systems
A short index of systems we designed and engineered. Each one is described by what it does, not by what it promises.
06Proof
This site is the reference implementation of how we build. Every claim below is a property of the code that serves this page, not a promise about a future project.
States, not scores. Nothing here is a live metric, because a number on a marketing page is not a measurement of anything a visitor can verify.
No client name or logo appears on this site yet, because no written permission has been given for one. When it is, it will appear here with the work it belongs to.
01Performance
Pages render on the server. Client-side JavaScript is added only where the browser is genuinely needed, and route budgets are agreed before the build rather than measured after it.
02Search
Every route carries a canonical, the full alternates set and structured data generated from the same content the page renders. Nothing is marked up that a reader cannot see.
03Measurement
One typed event taxonomy, declared in a single module. Conversions fire after the server accepts an enquiry, never on a click, so a report and an invoice can be reconciled.
04Accessibility
Contrast, focus order, target size and reduced motion are design inputs, not a remediation pass. Every ink step is verified against the darkest surface it can sit on.
05Privacy
Denial is the default and the stored decision is what gates execution. No vendor script exists in the document until the matching category has been granted.
06Systems
Content is typed once and read everywhere; colour and space are tokens no component may bypass. Adding a language or inverting the whole surface is a data change.
We do not hand over a picture of a system. We hand over the system, and the way to run it.
07Insights
Written while the work is happening, not after. Specific, arguable, and free of the usual vocabulary.
Design16 September 2026
Speed is not a thing engineering does after the design is signed off. Nearly every decision that makes a page slow is a design decision, taken weeks earlier by someone who was not thinking about speed.
Systems18 August 2026
The category is new enough that most descriptions of it are marketing. Here is the working definition, and where the line sits against an agency or a product studio.
Design2 July 2026
Most design systems fail in the gap between the file and the build. The fix is structural: two token layers, one source, and components that cannot read a raw value.
08Start
Tell us what the business needs to do. We will tell you what it takes to build it, and what it takes to keep it running.
We use a small set of cookies to keep the site working and — only if you allow it — analytics and marketing cookies that tell us how the site is used. Nothing non-essential runs before you decide. Cookie policy