The Architecture

Every stack answers who and what. Almost none answers why.

A modern stack resolves the visitor, then decides what to show them. Between those two steps sits the question neither answers: why is this visitor here, right now, and what is this session worth?

Identity Layer
Who is this visitor?

Resolves account, credential and consent. Works from what is already known.

Explains history.
→
Context Layer
Why are they here, right now?

InferKNOW. Reads the live session at the edge before downstream systems act. No profile required.

Explains the moment.
→
Personalization Layer
What should happen next?

Decides the response. Only as good as the signal it receives.

Explains the plan.
When identity resolves

Personalization acts on history, not today.

A known visitor may be researching, comparing, replenishing or ready to buy. The profile doesn't say which. Session context does.

When identity can't resolve

Personalization has nothing to act on.

No account, credential or consent means no signal. That describes first-time visitors, many AI-referred visitors, and every autonomous agent.

Nothing reads the moment itself. That's the gap InferKNOW closes.


The intelligence layer, in motion
WHOVisitor & identity CONTEXTThe live session INTENTWhy they're here ACTIONWhat happens next 01VisitorsWHO ARRIVES 02Existing signalsYOUR CURRENT STACK 03InferKNOWTHE MISSING LAYER 04ActionsDOWNSTREAM 05OutcomesBUSINESS IMPACT Human AI-referred Autonomous agents Edge script EVENT STREAM time Ephemeral · no storedprofile · read at the edge Identity · if known Device Channel Referral Behaviour Session context Answers who and what,not why. READSContext LIVE SESSION VECTOR INFERSIntent DELIVERS ATEdge intelligence SITUATION Exploring Ready to buy AI-referred Agent Between your identity & data systems and every downstream decision. Session Yield Pricing Offers Personalisation Recommendations Agentic systems Fraud & risk decisions A/B Testing Or passed to yourexisting stack. Conversion AOV / Revenue Experience Commerce efficiency UPLIFT +57% YIELD / SESSIONVerified against a holdout EDGE SCRIPT · SIGNAL IN AT THE EDGE · <50MS DECISION OUT · YOUR STACK LATENCY Signal Context Intent Action <50 ms end to end
Two Capabilities, One Layer

One layer. Two ways to make traffic worth more.

The same real-time read of context does two jobs: it raises the value of every human session, and it makes autonomous-agent traffic something you can sell to.

01 · Human & Contextual

More revenue from the sessions you already have.

Referral, channel, device and in-session behaviour, read continuously and acted on before the page renders. No history required.

What it does
  • Solves the cold start. The first page view already carries context, even with no usable history.
  • Reads AI-referred intent formed in ChatGPT, Gemini, Perplexity and other assistants, and acts on it as the visitor lands.
  • Adapts pricing, copy and offers to the situation, before render.
  • Uses precision timing, not blanket discounting. The lift comes from getting the moment right, not from giving margin away.
  • Turns anonymous sessions into first-party signal about intent and context.
+57% yield per session (verified holdout)
02 · Agentic

Turn agent traffic into a channel you can sell to.

Autonomous agents have no identity to resolve and no use for a page built for humans. InferKNOW detects them and responds with structured, negotiable terms.

What it does
  • Detects the agent without an account, credential or profile.
  • Offers machine-readable pricing, bundles and terms the agent can act on directly.
  • Enables direct negotiation, agent to business, instead of leaving terms to be scraped.
  • Lowers agent latency and token cost, because the agent reads structured terms rather than parsing a page.


The only layer built for a visitor that isn't human
How It Works

Three steps. Sub-50 milliseconds.

It runs at the edge, ahead of your origin server. The session is read, understood and answered before the request reaches your stack.

01

Infer

A single script reads channel, device, referral and behavioural signal at the edge, before the request reaches the origin.

Signal in · live session context
02

Decide

The signal becomes a commercial situation: exploring, ready to buy, AI-referred or autonomous agent. No stored profile involved.

Context → actionable situation
03

Respond

Pricing, copy and offers adapt before render for humans. Structured terms go directly to agents. Or the situation passes to your existing stack.

Situation → commercial action

Four situations the layer resolves

Each session resolves into one of these, and each is worth a different response.

Exploring
Reads

Signals of discovery, not purchase readiness.

Enables

An experience suited to the visitor's stage, not a hard sell.

Ready to buy
Reads

In-session behaviour showing a decision is close.

Enables

Precisely timed action without automatically giving away margin.

AI-referred
Reads

Intent carried in from an AI assistant's referral.

Enables

An experience that continues that conversation instead of starting over.

Autonomous agent
Reads

Machine traffic acting for a customer, with no identity to resolve.

Enables

Structured, negotiable terms it can act on directly.

●Single script ●~4 hrs engineering ●Live in 48 hours ●Verified against a holdout group ●No re-platforming
Scale

Start with one property. Scale across the enterprise.

One script proves the commercial impact on a single property. The same layer can sit higher in the enterprise stack, between existing Identity and downstream Marketing and Personalization. Deploy it once, and every experience that depends on that stack inherits it.

Per property

Start where the economics are visible

A single script, no re-platforming, measured against a holdout group. Prove the impact before expanding.

Enterprise level

Add the Context Layer to the stack you have

Nothing is replaced. Existing systems gain the live signal they weren't designed to generate.

Across properties

One layer feeds many experiences

Deploy at the right level and extend context across every property that shares the same enterprise stack.

It isn't a feature an incumbent can patch. It's a different layer, in a different place in the stack.

◎
Situational intelligence, not surveillance.

InferKNOW doesn't need a permanent personal profile to understand the current session. It interprets live signals in real time, whether the visitor is human, AI-referred or an agent, and can operate without identity.

No stored profiles The system doesn't depend on building a profile of each visitor.
No identity required Context can be understood even when the visitor can't be identified.
Session-level understanding The focus is what is happening now, not a record of who the visitor was.
Get Started

Read the moment. Not just the identity.

What is this session worth, and what can you do about it right now? Live in 48 hours. No re-platforming.

NO STORED PROFILES  ·  SUB-50MS EDGE