When we think about an intelligent assistant, we usually picture something that talks to us. But the real work is rarely just talking. Behind every fluent conversation, deep cognitive work has to happen: understanding intent, extracting details, and turning a vague request into a clear action. We believe these two jobs are two different layers of intelligence β and separating them, not blending them, is the key to building something that genuinely works.
Two layers, two responsibilities
The first layer is conversational intelligence: the interface that faces the human, understands natural language, guides the interaction, and asks for clarification when something is ambiguous. This layer must be fluent and patient. It deliberately avoids the complex logic of the domain; its sole job is to clarify intent and gather enough context.
The second layer is background intelligence: the specialised services that handle the heavy cognitive work. This layer never talks to the human. Its job is deep processing β structuring the request, inferring priority, and executing domain logic. This is where the actual expertise lives.
Why separation matters
The easy temptation is to pour everything into a single layer: an all-in-one agent that both talks and executes the heavy work. But these two jobs have fundamentally different operating requirements. Conversation must be fast and fluent; deep cognitive work is often slow and computationally expensive. If you blend the two, either the conversation blocks waiting for execution, or the cognitive work is kept deliberately shallow to maintain response times. Separating the layers lets each be the best version of itself.
A simple example
Imagine an end-user sends a message: βMy order hasnβt arrived and nobody is answering.β The conversation layer intercepts this, recognises it as a complaint about a delay, and prompts for an order number if one is missing. It then hands the payload to the background layer, which structures the request, determines the issue type, assigns priority, and defines the next action. Finally, the conversation layer provides the user with a clear, natural reply. The user experiences a simple conversation, but behind it, two distinct layers of intelligence work in concert.
This isnβt a chatbot plus an API
To be precise: this is not merely a chatbot calling a backend service. The critical difference is that both layers are intelligent. The conversation layer is not a static interface; it understands intent and guides the conversation itself. The background layer is not a fixed function; it reasons and decides itself. This is cognitive layering: a conversational presence alongside specialised depth, neither of which is sufficient alone.
Putting it together
We believe the future of intelligent assistants isnβt one do-everything agent, but layers of intelligence that each do their own job excellently and work in concert. The conversation layer stays with the human; the background layer brings the depth. And itβs precisely this division of labour that lets a simple message become the right action β without sacrificing either the fluency of the conversation or the depth of the expertise.