Collaborative & personal
Team context, and yours
Your teams build the company context together. Each user adds personal context, like formats or habits, read only in their own conversations.
Context Manager
Customer data, activation memory and business rules, unified in your warehouse and read by Dan, your LLMs and your agents. Dan proposes your definitions, and you accept the ones that fit.
Context Manager · Three layers, one truth
Why it matters now
Agents take on the execution, your team keeps the direction. Before an agent acts, it needs to know your customers and your rules.
Yesterday
Context lives in your team
Today
Context lives in each prompt
Tomorrow
Context has to live in one shared place
Tomorrow, concretely
People steer
They set the goals and approve what matters.
Agents act
Each one supports someone on your team.
Retention lead
Spots customers drifting away and drafts the win-back plan.
Is Claire still active?
CRM manager
Proposes the next move for each customer.
What did she already get?
Service advisor
Briefs the advisor live, next best action included.
What is she worth?
E-commerce lead
Knows who it is talking to, hands over when it should.
What may I tell her?
Underneath, the same three questions
01 · Customer data
Who is this customer?
02 · Activation memory
What have we already done with them?
03 · Business rules
What are we allowed to do?
When each agent answers them on its own, you get as many answers as agents.
The problem
The problem
With DinMo context, the agent finds 3,380 high-value customers to win back, sends the message to Claire M. by email only, hides her phone number and waits for Camille D. to approve. Her unified profile, your definitions and your rules light up under it.
Your definitions, your consent rules and one shared truth, applied on every request.
Without context, the agent reads raw tables and answers 129,600 customers: it counted every account that logged in this year, exposed Claire M.’s phone number and sent the audience without approval.
It invents your definitions, reads fields it should never see, and answers differently from the agent next door.
What’s inside
DinMo turns your warehouse into one customer context. Each layer is kept in your cloud and read in place.
One profile per customer, with orders, events, predicted value and churn risk attached.
The audiences, journeys and syncs DinMo runs, with their results, so every reader knows what was already done.
Your definitions, consent rules and playbooks, written once in the Context Manager and read on every request.
Every change Dan prepares waits for your review before it runs. Every read by any agent stays within that agent’s scope.
Let Dan define your business
Start an analysis, and Dan studies your workspace for as long as it needs: your models, your fields, how your customers buy and subscribe. It comes back with the definitions your industry relies on, each with its formula and the evidence behind it. You review them, accept the ones that fit, and every answer, audience and prediction uses them from then on.

Approval: Promote 6 definitions to the workspace?
Nothing is shared until you accept it. Every definition keeps its versions.
Meet DanWho reads it
The same answer, on the same definitions, whoever asks.
Your marketing teammate. Asks in plain words, waits for your approval.
Claude or ChatGPT read the context through the DinMo MCP plugin, within your scope.
Your own agents call DinMo through the same MCP plugin, one scope per client.
Service, sales, editorial or product teams get the answer before the call, and your website reads it through the Personalization API. No data ticket.
How you build it
Write it as a team, keep personal notes for yourself, import the definitions you already have, or start from a first draft.
Collaborative & personal
Your teams build the company context together. Each user adds personal context, like formats or habits, read only in their own conversations.
Many types of context
Business definitions, company facts, rules, periods, channels, playbooks, and whatever else your business runs on. The knowledge that makes an agent answer like your best analyst.
Semantic layer sync
Metrics already defined in dbt, your warehouse or a spreadsheet? Connect the source: DinMo imports the definitions and keeps them in sync.
Drafted by Dan
Dan analyzes your models, segments and fields, factors in your industry, then proposes the definitions worth sharing. Your team reviews and approves.
FAQ
Is DinMo a CDP or a semantic layer?
DinMo brings both capabilities together in one platform. For marketers, it’s an agentic CDP that helps them move faster every day. For AI agents, it provides a customer context layer with unified profiles, business definitions, rules, and governed access. If you already have a semantic layer, DinMo’s open, composable architecture lets it stay in sync with your existing definitions, so you maintain a single source of truth.
Does our customer data leave our warehouse?
Your customer tables stay in your warehouse and DinMo queries them in place. Data leaves only when you activate it to a tool, or when an authorized agent reads the fields its scope allows. If you choose DinMo Hosting, you can have your warehouse hosted in either the EU or the US.
Which agents and LLMs can connect?
Dan, and through the DinMo MCP plugin your own agents and assistants such as Claude, ChatGPT, Gemini or Mistral. Your website and apps read the same context through the Personalization API. Each client gets its own scope.
How do you stop an agent from seeing what it shouldn’t?
Every client has a scope on fields, models and actions, agents act within the permissions of the person they work for, and sensitive fields are masked by policy. Every change Dan prepares waits for your review before it runs, and every read and action is logged.
Context Manager
See how DinMo turns your warehouse into governed customer context, on your own data.