Remember what you promised, and where you promised it.
Commitments, renewal terms and escalations recorded by your agents, each linked to the meeting or email where they were agreed.
Updated
Where account facts go wrong.
01
Promises get lost
A commitment made in a QBR lives in someone's notes, not on the account.
02
Terms drift
Renewal terms change across emails and calls, and the record keeps only the latest.
03
Surprises at renewal
Two people promised two different discounts, and nobody noticed until the contract.
Scenarios
Questions an account manager can answer.
How OpenCRM answers
The commitment cites the QBR notes and the exact line where it was agreed.
How OpenCRM answers
Each sponsor stays on the record with the email that introduced them.
How OpenCRM answers
An email and a call disagree, so the conflict stays open with both sources until someone confirms.
What changes.
- Commitments on the recordEvery promise links to the meeting or email where it was made.
- Terms with historyChanged terms stay on the record, marked superseded, with their sources.
- No surprises at renewalConflicting commitments are flagged when they're recorded.
- Briefs before every callAccount briefs list the observations they rely on.
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.
Can it read our support tickets?
Not directly. Your agent can save any text as an artifact and record observations from it. Built-in connectors aren't available yet.
Who writes the account briefs?
Your agent writes them with create_brief. Each brief lists the observations it cites, so a person can check it.
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.