Skip to content
Skip to main content
PLATFORM · LAYER 01 · THE SURFACE

Your website used
to have one
audience. Now
it has three.

The Surface is where humans, agents, and crawlers meet your company. If your site treats them like one audience, all three lose. We build Surfaces that expose the same company to all three, plus the structured underbelly that makes that possible.

Book the diagnostic →See Layer 03 · Kernel
90 minutes. No slides. Just the map.

All three meet your company here.

01
ARRIVES LATE
The human
Shows up already convinced or already skeptical, having spent the early part of their evaluation talking to an AI.
Late-stage. Already shortlisted. Reading for confirmation, not discovery.
02
ARRIVES FIRST
The agent
Shows up before the human. Runs the comparison. Decides whether you make the shortlist at all.
Skimming for citations. Quoting, paraphrasing, or skipping you in ~200ms.
03
ARRIVES CONSTANTLY
The crawler
Shows up over and over, feeding the next agent's next answer.
Indexing. Re-indexing. Building the training set the agents draw from.

Larger than the marketing site.

Each one is a surface. The job of the Surface layer is making sure they all expose the same company.

  1. 01
    The public website
    AEO-native architecture, schema, and citation patterns built for LLMs.
  2. 02
    Customer portals
    Logged-in users doing real work — not just downloading invoices.
  3. 03
    Conversational interfaces
    Chat-first access to the company. Not bolted-on chatbots. Backed by the kernel.
  4. 04
    Embeddable widgets
    Components that ride along into partner sites, marketplaces, and integrations.
  5. 05
    Structured data + content patterns
    What makes every word above legible to the agents reading it.

A brochure assumes a curious human. That assumption is dead.

Today's reader is an agent skimming for citations. It will quote you, paraphrase you, or skip you in about 200 milliseconds. If your site doesn't tell the agent what kind of company you are, what you sell, who you serve, and why someone should pick you, the agent makes something up. That made-up version is what the human sees.

8%
The 8% Rule names the ceiling.

AI engines cite owned websites in roughly 8% of their answers. That number can't go to 100. But for most companies it's currently sitting at zero — and getting it to "sometimes" is the unlock.

Read the 8% Rule →

Four installs. Website & CX Platform Development.

We do not just ship a site. We ship the queryable public interface of your company.

DELIVERABLE · 01
FLAGSHIP

AEO-native website rebuild

Not a redesign. A legibility rebuild.

New schema, new content architecture, new internal linking, new citation patterns.

  • Schema architecturestructured data agents can actually parse and cite
  • Citation-first contentevery page answers a question worth quoting
  • Internal linkingjoins the topical graph an LLM is trying to build
  • Legibility test suitewe measure citation lift, not just analytics
Built to be cited by AI overviews. Read fluently by agent buyers.
AEO-Native Websites →
DELIVERABLE · 02

Customer Portals

Live context layer between the company and its customers

Real-time data, agent-mediated support, self-serve workflows.

  • Live datafrom the kernel, not from yesterday's CSV export
  • Agent-mediated supportthe portal answers questions before a ticket gets opened
  • Self-serve workflowsreal work, not invoice downloads
  • Identity-aware surfaceswhat a customer sees vs. what a partner sees
Replaces ticket volume instead of generating it.
Customer Portals →
DELIVERABLE · 03

Conversational UI

Chat-first interfaces · read from the kernel

Answer like the company would. Not bolted-on chatbots — real chat-first access to the company.

  • Kernel-backed answersthe same source of truth your team trusts
  • Voice-tuned outputssounds like your brand, not a generic assistant
  • Escalation as a flowone click. Full context preserved for the human picking up
  • Audit-logged conversationsevery exchange queryable, retained per policy
When the kernel knows the answer, the conversational UI delivers it.
Conversational UI →
DELIVERABLE · 04

Migrations & Replatforming

The moment to install the Surface correctly

When you're already replatforming, install the Surface correctly instead of porting old assumptions forward.

  • From WordPress · Drupal · Webflowonto HubSpot CMS or a headless stack
  • Schema preservationagent-legibility survives the move
  • URL · redirect · canonical mapno citation loss during transition
  • Content audit + cullleave behind what shouldn't make the trip
Survives a migration without losing agent-legibility.
Migrations & Replatforming →

You'll know your Surface is doing its job when:

✓
AI engines start citing your site.
As a source. You can measure this. We do.
✓
Your conversational UI answers without escalating.
Because the kernel knows the answer.
✓
Portals replace ticket volume.
Instead of generating it.
✓
The site survives a migration.
Without losing its agent-legibility.

The Surface alone is theater.

You can have the prettiest, most schema-rich site on the internet — and it'll still hallucinate if the kernel underneath has nothing to say. Build bottom-up. Expose top-down.

LAYER · 02
The Voice
The Surface reads from here — so the agent knows how the company sounds.
→
LAYER · 03
The Kernel
The Surface reads from here — so the answer is actually true.
→
LAYER · 04
The Agents
The Surface feeds them — so they have a place to render.
→
LAYER · —
The Protocol
Build the Surface alone and you've built a stage. We expose top-down, build bottom-up. The protocol is the seam.
→
L3
→
L4

Surface upgrades compound at L3. Reach full value at L4.

Below L3, the Surface has nothing real to expose. That's why we always look at the kernel first — even if the entry point is a website conversation.

See the Maturity Model →

The diagnostic is pre-loaded.

You walk away with a map of which Surfaces are working, which are dead weight, and which need to be rebuilt before the next quarter's AI shift hits.

  • Audited your AEO posture against the legibility tests
  • Run your site through the schema and citation-pattern probes
  • Pulled the data on which AI engines are citing you — and which aren't
  • Identified the highest-leverage pages to rebuild first
  • Built a maturity-level placement with specific evidence

Things people ask before signing.

Is this just SEO with a new name?

No. SEO optimizes for human-clickable rankings. AEO optimizes for agent-citable answers. Different audience, different signals, different deliverables. We do both — but we lead with AEO because that's where the unclaimed ground is right now.

Do we have to rebuild the whole site?

Rarely. Most clients start with a citation audit, a schema retrofit on the top 20 pages, and a handful of pillar-page rebuilds.

What CMS do you build on?

HubSpot CMS for most clients. We also work in headless setups when the engineering team prefers it.

How long until we're cited?

Citation lift typically shows up 6–10 weeks after a schema retrofit ships. Larger rebuilds take a quarter to settle.

What about Google? Are we abandoning SEO?

Not at all. AEO-native architecture happens to be excellent SEO architecture — clean schema, fast pages, strong internal linking, real answers to real questions.

DIAGNOSTIC · 90 MINUTES · NO SLIDES

Map your company's intelligence in 90 minutes.

No slides. Just the map. We'll whiteboard what your company already knows, what it's forgetting, and which layer to build first.

Book the diagnostic

Yours to keep — signed or not.