A marketing website engineered from the schema layer up. Component system designed against your brand tokens, content layer your team can edit (CMS or typed MDX, depending on team shape), and the four foundations that decide whether you get found and cited (schema graph, Core Web Vitals budget, llms.txt, AI-crawler access) baked in at launch rather than bolted on at month 6. The end state is a site Pulse audits at 70+ on its own rubric the day it goes live.
Component system (10 to 25 components depending on surface count)
Design tokens layer (colour, type, spacing, motion) wired to Tailwind
Content layer: Sanity, Contentful, or typed MDX, scoped to your team
Schema graph: Organization, WebSite, WebPage, BreadcrumbList per route
Core Web Vitals budget agreed at scope and enforced at build time
llms.txt + robots.txt + AI-crawler allowlist for the 18 named crawlers
Sitemap and IndexNow integration
Prerendered HTML for all public routes (raw-HTML AI crawler readiness)
Analytics and monitoring (PageSpeed Insights, Plausible or GA4)
Foundations
Every bespoke websites engagement inherits the four UX Studio foundations.
Schema graph wired at every URL. Core Web Vitals budget agreed at scope. Crawler-access policy across 18 named AI crawlers. Schema-per-page rather than templated copies. The full foundations grid lives on the UX Studio overview.
WordPress, Webflow, and Framer all ship faster for the first version. They all become a tax later. WordPress accumulates plugin debt and PHP rendering performance ceilings; Webflow and Framer cap your structured-data control and your AI-crawler access policy. Next.js with a typed content layer trades a slightly longer week-1 setup for a site you can extend, audit, and run on Pulse-grade foundations indefinitely. The right answer depends on your roadmap: if you're publishing 5 marketing pages and never iterating, Webflow is fine; if you're building a content surface that needs to rank and get cited, Next.js is the right floor.
Existing brand identity is the default. We translate your brand tokens (colours, type, spacing, logo system) into a design system layer and the components inherit from there. If the brand identity itself needs work, that scope sits separately and runs in parallel with the engineering build, not in series.
Whichever team you want. The content layer is scoped to your team's workflow: marketers who want a CMS get Sanity or Contentful; engineering teams who already use Markdown get typed MDX in the repo. The build ships with documentation and a written editorial workflow so updates do not require us in the loop.
Work with valUX
Start where it hurts.
If your organic traffic is sliding, start with a Pulse audit. If you want a programme rather than a one-off, ask about a retainer. Either way, every enquiry is read by a senior architect, and you hear back within one working day.