Deal facts that cite the call. Not a rep's memory of it.
When your agent logs a budget, a decision maker or a close date, OpenCRM keeps the sentence the buyer said it in, and every value it replaced.
Updated
Where deal facts go wrong.
01
The forecast rests on hearsay
A close date in the CRM, with no record of who said it or when.
02
Slipped dates vanish
Each update overwrites the last, so nobody sees how often a deal has slipped.
03
Mixed signals get averaged away
The email says one thing and the call says another. One value wins without anyone noticing.
Scenarios
Questions a sales leader can answer.
How OpenCRM answers
The budget field cites the observation, and the observation cites the email and the exact sentence.
How OpenCRM answers
Every close date stays on the record, marked current, superseded or retracted, each with its source.
How OpenCRM answers
When the email and the call disagree, the conflict stays open with both attached until someone checks with the buyer.
What changes.
- A forecast you can defendEvery deal fact links to what the buyer actually said.
- Slippage you can seeSuperseded dates stay on the record with their sources.
- Mixed signals surfacedDisagreements stay open until a person settles them.
- No per-seat billOpen source under Apache 2.0, on a server you run.
Controls.
A source for each field
Observations name the field they cover and cite the artifact behind it.
Append-only event log
Entity changes are logged with their diff and never edited.
Agent attribution
Entity writes can carry the agent id, tool call id and prompt hash.
Content hashes
Each artifact is stored with a SHA-256 hash of its text.
Export
Take every record out as JSON, whenever you need it.
Self-hosted
One SQLite file on infrastructure you control.
Questions.
Does it log calls and emails for us?
Your agent does. It reads the call or email, saves it as an artifact and records the facts as observations. Connectors that pull email and calendar automatically aren't built yet.
Does it replace our current CRM?
It can sit beside it as the record your agents write to. Syncing with an existing CRM isn't built yet; Attri builds it in managed deployments.
Does it have sign-in?
Not yet. The open-source server has no sign-in or access control, so keep it on a private network. Attri adds sign-in and access control in managed deployments.
Every fact should show its source. Start with the agents you already run.
Run OpenCRM on sample data in minutes, or have Attri deploy it inside your environment with sign-in and connectors.