Structure
What the firm is claiming, in what order, and which claims have to be provable. Architecture before layout.
Website
design.
The surface is the instrument a firm gets judged by before anyone speaks to it. Zyrn builds it the way it builds an operating model — structured first, measured continuously, and handed over so the team can extend it without calling us.
01 — STRUCTURE
000%
Architecture before layout. Blocks are placed by what the page has to prove, in the order it has to prove it.
What it covers
Six modules. Structure is settled before a pixel is drawn.
Design system
Tokens, type scale, spacing, motion law. Written down, so the surface can be extended without a redesign.
Build
Static where static is correct, dynamic where it earns it. No framework the firm cannot maintain itself.
Performance
Frame time and payload are acceptance criteria, not a pass at the end. A budget, not a hope.
Accessibility
Contrast, motion preference, and keyboard paths are part of the build. Not an audit afterwards.
Handover
The team ships a new page without asking how. That is the exit condition, and it is written into the engagement.
How it runs
Three phases, the same three every line runs. Measured at each one.
P.01
Diagnose
Four to six weeks. Surface audit, structure audit, and the distance between what the site claims and what it can show.
P.02
Build
One to two quarters. System documented, surface built, performance and accessibility held to budget.
P.03
Calibrate
Ongoing. The surface is versioned like software, because that is what it is.
What changes
Signals the diagnostic watches, and the direction they are expected to move.
- QUALIFICATION Inbound arrives already understanding the terms.
- FRAME BUDGET Held under target on the hardware the audience actually uses.
- MAINTENANCE Changes ship from inside the firm, not from an agency queue.
- DRIFT Claim and evidence stop separating between quarters.
The surface,
as instrument.
The engagement closes when the firm can extend its own system without asking how.