Skip to content

Services

Seven lines of work, named plainly.

We design and build the site, then leave you with the repository. Agentic Sites is the one you run by chatting. Personalization, when you want the page to change per visit, is the sister company.

Agentic sites

A small-business website you run by talking to it. New pages, copy, photos, prices, menus, and plain questions. You approve before anything goes live.

  • Plain language. You do not need to know domains, DNS, or a framework.
  • The bot drafts. A person here sets it up, trains it, and stays on as backup.
  • You own the site and the content. Nothing publishes without your approval.
See Agentic Sites

Marketing sites

A site that explains an offer, carries a reader to one next step, and stays fast when the campaign traffic shows up.

  • Page map tied to the questions a buyer actually asks
  • Type, layout, and a component set you can extend
  • Forms that name their fields and fail in plain language

Product sites

A public face for a product: the promise, the proof you actually have, and a path into docs, a demo, or a trial.

  • Information architecture for more than one audience
  • UI that can sit beside a product, not just a brochure
  • Room for a later app without throwing out the system

Design systems

Tokens, type, and components documented well enough that the next page does not invent a new button.

  • Color and type that meet contrast on both themes
  • Components with states, not only the happy path
  • A short written guide for whoever edits the site next

Front-end engineering

Next.js and TypeScript, deployed on Vercel unless the project has a reason to live somewhere else.

  • Server-rendered pages, small client islands
  • Semantic HTML before decorative motion
  • A repository you own when the engagement ends

Performance and accessibility

A budget set before decoration: Core Web Vitals thresholds, WCAG 2.2 AA, and keyboard access that is tested.

  • Public targets: LCP 2.5s, INP 200ms, CLS 0.1
  • WCAG 2.2 AA, checked with a keyboard
  • Third-party tags are chosen, not piled on

Measurement and personalization

The site and the measurement are designed together, with personalization from Black Box Personalization when the page should change per visit.

  • Event names agreed before launch, not reconstructed later
  • Consent treated as a product decision
  • Integration with Black Box Personalization when you want the page to change

We design toward Google’s Core Web Vitals: LCP 2.5s, INP 200ms, and CLS 0.1, and toward WCAG 2.2 AA. A required embed is called out in the scope.