The old setup keeps people and software apart. Reps work in the UI. Integrations run on the side. The AI gets a narrow view. Everyone touches a slightly different copy of the truth.
The next version drops that split. Agents and sellers act on the same data, through whatever door they prefer.
1.One dataset, many doors
Lumenbase scopes everything to the workspace. A seller and an agent see the same contacts, deals, and history. The difference is only how they reach it:
A change made by an agent shows up for the person, instantly, because there's one source.
- Sellers use the web UI or chat
- Agents use the REST API, the Openclaw Agent API, or MCP
- Lumo, the built-in AI, reaches the whole workspace too
2.Why shared logic matters
Lumenbase keeps its CRM rules in one shared layer. The adapters for REST, Agent API, and MCP are protocol-only. So an agent writing through the API follows the same rules a person follows in the UI.
That's what makes humans and agents safe to mix. They can't drift into two different versions of "valid."
3.What this looks like day to day
A practical mix:
People and agents hand work back and forth on one timeline.
- An agent updates deal stages overnight through the API.
- Lumo builds the morning Today list from that fresh data.
- The rep opens the app and works the ranked list.
- The rep's notes feed back into the same record the agent reads next.
4.Built for it now, not someday
This isn't a roadmap promise. Lumenbase already exposes web, chat, Claude over MCP, Openclaw, and a REST API against the same workspace. The agent channels exist today.
5.Who this is for
Revenue operators at $2M to $30M ARR companies. The ones who adopt early and want their CRM ready for agents before their competitors think about it.
6.Frequently asked questions
6.1.Can AI agents and people use the same CRM data?
Yeah. Lumenbase scopes data to the workspace, so sellers and agents act on one shared dataset.
6.2.How do agents connect?
Through the REST API, the Openclaw Agent API, or remote MCP at `https://lumenbase.io/api/mcp`.
6.3.Do agents follow the same rules as people?
Yes. CRM logic lives in one shared layer, and the API adapters are protocol-only.
6.4.Is this available now or planned?
Now. The web, chat, MCP, Openclaw, and REST channels all run against the same workspace today.