Your AI doesn’t know your company.Gatlas gives it the context.
Gatlas keeps your companies’ data and what it means in one place, called a context layer. Your people read it, and so do your AI agents, such as Claude or ChatGPT. It works for a group of companies or for one.
Where company knowledge sits
A company’s tools hold its records. How to read those records is in its people’s heads.
Across a group, every company has its own tools and its own way of counting. Explaining the same things again takes time every month.
An AI agent is only as useful as what it knows about your company.
Records, in tools
Ledgers, CRMs, inboxes and drives hold what happened: every invoice, deal and message.
Know-how, in people
Most of it was never written down.
An AI agent, with the tools only
Without what your people know, it guesses.
Tools
- e-conomic
- HubSpot
- Shopify
- Google Drive
- Stripe
People
- Which number is current
- How margin is defined
- Which customers are exceptions
Reads every record
Cannot read what people know
A column of tools on the left, an AI agent in the middle and a column of people on the right. Solid lines run from every tool to the agent. Dashed lines from the agent toward the people stop short.
Three layers of a company
Of a company’s three layers, two run on software and the third is carried by people.
AI agents can only read software, so what a company knows has to be written down in software too.
No existing tool can hold it, because each tool sees only its own part of the company.
- CustomersWebsite, shop and support
- OperationsAccounting, sales and projects
- ContextWhat the company knows: its data and what the data means
- Runs on software
- Carried by people
- CustomersWebsite, shop and supportRuns on software
- OperationsAccounting, sales and projectsRuns on software
- ContextWhat the company knows: its data and what the data meansCarried by people
Three stacked layers. Customers and Operations are drawn solid. Context, underneath them, is a dashed outline with people standing on it.
What Gatlas is
Gatlas is the context layer for a company or a group of companies.
It connects the tools each company already runs and keeps a current copy of their data. Your people say what the data means, and an agent writes it down.
No tool is replaced. People, agents, dashboards and documents all read from that one place.
Your tools
- e-conomic
- Shopify
- HubSpot
- Google Drive
- Xero
- Stripe
- Attio
- QuickBooks
Gatlas
Approved corrections come back as notes
Where it is used
Your own agents
- Claude
- ChatGPT
- Cursor
Run by Gatlas
- Gatlas agentIn Slack
- Automations
Built in Gatlas
- Dashboards
- Documents
- WorkflowsPlanned
Lines run from a column of tools into Gatlas, drawn as three stacked parts: Data, Engine and Action. From Action, lines run out to agents, dashboards and documents, with a dashed line to workflows. One line returns to Engine.
Data, engine, action
One part connects the data, one holds what it means, and one puts it to use.
- Accounting and banking
- CRM and calls
- Files and documents
- Datasets
- Descriptions
- Notes
- Agents
- Dashboards
- Documents
- Automations
Three stacked plates: Data at the bottom, Engine in the middle and Action on top. Each plate carries pins that name what it holds.
Data
Connects the tools each company runs.
Gatlas reads each tool on a schedule and keeps a current copy of its data. The tool keeps its data, and no company changes how it works.
Engine
Holds what the data means.
A dataset is a table built from your data, such as a monthly P&L, with a written description. Corrections your team approves are saved as notes. Every agent that reads a company reads both.
Action
Puts it to work for people and agents.
Your own agent answers from it. Dashboards, documents and decks are built on it. Alerts and scheduled posts run on it.
Who writes the definitions
Today your own agent writes the definitions with you. Gatlas drafting them for your approval is planned.
| Level | Who writes | Who approves | Status |
|---|---|---|---|
| Your agent | Your own agent, as you work with it | You, in the conversation | Today |
| Co-pilot | Gatlas, from a survey of your data | Your people, before anything is saved | Planned |
| Autonomous | Gatlas, on its own | You set the limits and read what changed | Planned |
How a correction is saved
A correction is made once and kept.
Ask
A finance lead asks an agent for gross margin by company.
Correct
The answer is wrong for one company, which books freight under overhead. The finance lead tells the agent.
Approve
The agent offers to save the correction as a note. The finance lead says yes.
Reuse
The note reaches every agent that reads that company.
Answered once
Count the work in your company that only moves information: finding a number, explaining it again, forwarding the file. With Gatlas each answer is written down once, and every person and agent reads it from there.
- Exports
- Figures re-keyed into a report
- The same question answered again
- Status updates
- Handovers
- Forwarded threads
Today and planned
What each part does today, and what is planned.
| Part | Today | Planned |
|---|---|---|
| Data |
| Planned Files no tool holds, such as brand files. |
| Engine |
| Planned Gatlas drafts the definitions for you to approve, including where one company counts a figure its own way. |
| Action |
| Planned Agents and workflows you set up in Gatlas. |
Guarantees
What holds for every answer, in every company.
- Sources
- Every number traces back to its sources
- Freshness
- Each dataset says when its data was last refreshed
- Access
- Each person and each agent sees only the companies you grant
- Log
- Every request an agent makes is logged
- Storage
- Each company’s data syncs into its own set of tables in Gatlas
Build your context layer
Start with one company and its tools. Add the rest when you are ready.