Websites that
convert, and
feel inevitable.
Marketing sites, landing systems, and CRO infrastructure built like the brand's most important piece of marketing — because they are. Editorial design, motion craft, sub-1.5s LCP, and the AI-personalization layer that lifts conversion 20–40% over launch baseline.
The web got personal, programmable, and AI-native.
Three shifts changed how marketing sites should be built in 2026: AI personalization at the edge, INP replacing FID as the interaction metric, and AI agents (ChatGPT, Perplexity) reading your site to build answers. The brands shipping for all three are pulling ahead. We build for all three.
AI personalization at the edge
Vercel Edge Middleware, Cloudflare Workers AI. Hero copy, social proof, and CTAs that adapt to the visitor — by source, by industry, by intent — without nuking Core Web Vitals.
INP < 200ms, not optional
Google replaced FID with Interaction to Next Paint in March 2024. INP is harder to hit and now a confirmed ranking signal. We build for sub-200ms INP by default — most agency sites today fail this metric.
Sites that AI agents can read
llms.txt files, semantic HTML, factual schema markup, and structured content so ChatGPT, Perplexity, and Claude cite your site cleanly when answering questions in your category.
What's actually included.
Every web engagement ships these. No "additional scope" surprises after kickoff.
Discovery & strategy
Customer interviews, sales-call review, content audit, competitor analysis. Written strategic brief — not a slide deck — that names the bets and the budget.
Editorial design system
Typography, color, spacing, motion tokens. Documented in Figma + Storybook. Built to be extended by your team after we're gone — without fracturing.
Motion & interaction craft
GSAP + Lenis where it earns its place. Motion as communication, not decoration. Every animation has a job — or it doesn't ship.
Performance budget
LCP < 1.5s. CLS < 0.05. INP < 200ms. Image optimization, font subsetting, code splitting, edge-deployed. We won't launch a site that misses these.
CMS chosen properly
Sanity, Contentful, Webflow CMS, or Payload — chosen against the editorial workflow your team actually has. Not whatever's trending on Twitter that week.
CRO infrastructure
Section-level variant system, A/B test framework, heatmap + session replay wired in, server-side conversion tracking — baked in at launch, not added later.
SEO foundation
Schema, indexable rendering, semantic HTML, 301 migration map, llms.txt for AI agents. So the site doesn't tank organic traffic at relaunch.
Three-phase launch
Soft launch → SEO migration → public launch. We launch Tuesdays. First-week monitoring built in. No Friday-night go-lives.
Documentation & handoff
Storybook + design tokens + README. Your team can maintain, extend, and add to the build for years — without paying us to come back every time.
Design. Motion.
Performance. CRO.
— Design
Design that respects the user.
Editorial typography, intentional whitespace, visual hierarchy that makes the next action obvious. We design like the customer will actually read it — because they will. Restraint, not decoration.
— Motion
Motion as communication.
Every animation has a job — guide attention, communicate state, or reward interaction. Nothing moves just because it could. No cursor effects that do nothing. No scroll hijacks. No 9-second hero animations.
— Performance
Sub-1.5s LCP, seriously.
Edge-deployed routing, AVIF + WebP with proper fallbacks, font-display:swap with metric-matched fallbacks, critical CSS inlined, JS code-split. We won't launch a site that misses the floor.
— CRO
Built to be tested.
Variant systems baked in at launch. The site keeps getting better — month over month, quarter over quarter. Most agency sites are launched and frozen. Ours are launched and iterated.
The stack we build on.
Sixteen tools we license and operate. Stack chosen per-project against the team that has to maintain it after launch.
What you actually get vs. typical agency builds.
The build details that show up two years in — or quietly don't.
How we build.
10 to 14 weeks for a typical marketing site rebuild. Discovery, design, engineering, launch — sequenced so nothing stalls.
Discovery & strategy
Customer interviews, sales-call review, content audit, written strategy doc. The brief gets earned, not assumed.
Weeks 1–2Design system
Homepage moodboard, homepage design, inner-page system, polish week. Storybook scaffolded in parallel.
Weeks 3–6Engineering & CMS
Component library buildout, page implementation, CMS integration, performance tuning, CRO infrastructure.
Weeks 5–11Soft + public launch
Soft launch on staging, SEO migration verified, public launch on Tuesday, first-week monitoring.
Weeks 12–14Pricing, transparently.
Project-based for builds, retainer for ongoing CRO. Three tiers by scope and complexity.
The Page
Single high-conversion landing page or microsite. 2–4 weeks. Built in Webflow or Next.js.
- Custom design system (page-scoped)
- Motion + interaction craft
- CRO infrastructure baked in
- Performance budget enforced
- SEO foundation
- 2 weeks of post-launch iteration
The Site
Full marketing site rebuild. 10–14 weeks. Design system + CMS + CRO + AI personalization.
- Full design system (Storybook)
- Headless CMS (Sanity / Contentful)
- AI-edge personalization
- Three-phase launch process
- SEO migration handled
- Documentation & team handoff
- 30 days post-launch support
The Iteration
Post-launch retainer. Continuous experimentation, new pages, and performance maintenance.
- 4–6 A/B tests/month
- New page production
- Performance budget maintenance
- Heatmap + replay analysis
- Quarterly experiment review
- Bug triage & small fixes
- 6-month minimum
Halden Capital's new site cut LCP from 3.6s to 1.5s — and conversion went up 38%.
Most agency sites get worse after launch. Ours get better.
Most marketing sites are built once and then punished for five years. They were designed in a hurry, built by a freelancer who left before docs were done, and shipped without anyone thinking hard about what the site was supposed to accomplish. By month six they're slower than they should be. By year two they're a redesign budget waiting to be approved.
We build differently. The design system gets documented. The performance budget gets enforced. The CRO infrastructure ships at launch, not later.
And the site keeps improving. Section-level variant testing means non-developers can A/B test headlines, hero images, and CTAs without involving us. Quarterly experimentation roadmaps mean wins compound.
Within a year of launch, the median site we ship is converting 30–60% higher than its launch baseline. That's the lift you don't get from a static redesign — and it's the reason our build engagements often roll into ongoing CRO retainers.
The practical questions.
10–14 weeks for a typical marketing site. Landing pages 2–4 weeks. Larger headless builds with custom integrations 4–6 months. We'll scope honestly after the first call.
Yes — for the right use cases. Webflow is excellent for marketing teams that want to ship without engineering. For more complex builds with custom integrations or unusual front-end requirements, we'll typically recommend Next.js instead.
AI personalization at the edge — yes, standard in 2026 builds. Custom AI agents, chatbots, or generative product features — case-by-case. We've built RAG-powered search, AI-personalized landing pages, and Claude-powered support flows.
Two paths. Either we hand off with documentation and your team takes over, or we move into a CRO retainer that covers ongoing iteration, performance maintenance, and new-page production. Either is fine.
Yes. We do a brand-system audit at the start and either adopt it as-is, evolve it for digital, or recommend specific extensions if it's not currently digital-ready. We're not precious about who designed the brand.
Yes — Shopify (custom themes or headless via Hydrogen), Stripe-powered subscription flows, and headless commerce on Next.js. Marketing-grade commerce sites, not generic plug-in builds.