Is CRM dead? What comes after CRM is the context graph
Updated
Is CRM dead? Yes, and the context graph has to replace it. The CRM was built on one idea: a person sits down after the call and types in what happened. That idea is over. Once software can turn every meeting, email and call into data, the customer record has to be built from the conversations themselves, linked to the people, companies and deals they involve, with a source on every fact. That record is a context graph, and it does the CRM's job at a resolution a CRM can't reach.
The software won't disappear overnight. Andreessen Horowitz found that CRM usage has risen since AI tools were adopted at scale, and Vantage Point expects the CRM to matter more over the next three years, even as far fewer people log in to it every day. Vantage Point reads the CRM as the record AI sits on top of, and a16z keeps it as one input among many. This guide argues that a record people have to type can't carry that weight. You can rip out Salesforce or HubSpot and run on the graph alone, but you don't have to. Either way the graph becomes the record and agents do the data entry. If you keep the old CRM, it becomes one more place they write to.
Three positions cover most of the published argument. Andreessen Horowitz (a16z) puts a system of intelligence above the CRM. Vantage Point keeps the CRM as the governed record and makes AI the way people reach it. Christopher O'Donnell of Day AI, in the essay at lifeaftercrm.com, argues that the record itself has to be replaced, because anything built on a record of what people typed inherits everything they left out. This guide takes the third position.
Three positions on where the CRM goes
The CRM becomes one input to a system of intelligence
In From system of record to system of intelligence (May 2026), a16z argues that the CRM keeps its place but loses its center:
"The CRM isn't going to go away... but it's turning into just an input; one of many inputs, into the systems of intelligence which we use to get work done."
Their reason is where the work happens: "In the AI era, gravity will come from orchestration." They are careful to say this is not bad news for the CRM, "But the locus of value is migrating upward, into the layer that reads and writes to the database."
The CRM stays the governed record, and AI becomes the way in
Vantage Point looks at the same shift from inside the CRM. In its three-year view (August 2026), it predicts that "three years from now, far fewer people will log into a CRM interface daily, but the CRM itself will matter more, not less." People reach the CRM through AI, and the CRM keeps the jobs that need an owner: configuration and administration, data model design, and compliance review and audit.
Standage pushes the same idea one step further. In a July 2026 post, it argues that once an agent does the work, the record becomes the audit trail of what an autonomous system did: "less system of record, more system of accountable action."
The record itself has to be replaced
O'Donnell, writing at lifeaftercrm.com (September 2026), disputes the assumption the first two share:
"The system of record is a system of amnesia. Whatever you put on top of it inherits the amnesia."
The argument is that a smarter layer on top can't recover what the record never stored, so the record has to be built from what happened, not from what someone typed about it.
| System of intelligence (a16z) | Governed record (Vantage Point) | Context graph (lifeaftercrm.com, this guide) | |
|---|---|---|---|
| Does the CRM survive? | Yes, as one input among many | Yes, and it matters more | As software, for now. As the record, no |
| Where the value goes | The layer that reads and writes the database | The AI layer people use to reach the CRM | A context graph built from the conversations, with agents on top |
| What the agents read | The CRM and the other systems of record | The governed CRM | Every meeting, email and call, with a source on each fact |
All three agree the value is moving. They split on whether the database is good enough to build on, and that split decides what a revenue team should buy next.
Where the current thinking breaks
The first two positions assume someone keeps filling the CRM in. A system of intelligence that reads the CRM, or an engagement layer that sits on it, can only be as good as what is in it, and what is in it was typed by people with other jobs to do.
The resolution ceiling
O'Donnell's essay opens with a deal: nine months of calls, a champion who carried it inside the buyer, and an objection in March that nearly killed it. When the deal closes, a rep changes one dropdown to Closed Won, and, in the essay's words, "That's all the company remembers."
O'Donnell's name for the problem is resolution. "The quality of the answer is limited by the resolution of the data it has to work with," the essay says, and the CRM's resolution is low: "You cannot reconstruct nine months of a human relationship out of Stage:Closed Lost, Price:$4,200." The ceiling is set by the way the record is filled: "a store built around human data entry fixes that limit at whatever a person would bother to type."
Ask an agent what won that deal and which open deals look like it. Reading the CRM, it can match on industry, size and stage. It can't see the March objection, how the team answered it, or who the champion was. It will answer anyway, and the answer will sound sure of itself. Teams that hit this usually blame the model, then switch to a better one, and the new model reads the same dropdown.
Why the record was built for typing
Contact management moved from business cards to a spreadsheet to a spreadsheet online, and in the essay's words each step was "a better way of organizing what a person had already captured." Underneath all of them sat the CRM's founding premise, that "the human is the source of truth": a person sits down after the fact and types in what happened. O'Donnell argues that premise was correct only while a person was the only thing that could turn a conversation into data. Like the switchboard operator, it was right until it wasn't.
Bolting an assistant onto the CRM inherits its gaps
The fastest way to try the new layer is to connect an assistant to the CRM you have. It works on day one, and it carries three problems with it.
- It inherits the amnesia. The assistant reads what the CRM holds, so its answers stop at the dropdown.
- It inherits the integration user's permissions. As Vantage Point puts it, "external assistants connected via API inherit the permissions of whatever integration user you configure." Every person who asks gets that user's view, unless someone rebuilds the CRM's sharing rules in the assistant.
- It still depends on people logging activity. If reps update the record the night before the forecast, the assistant knows what the CRM knew the night before the forecast. The typing moves only if something else writes the record from the conversations.
Teams are naming it on sales calls
O'Donnell's essay quotes a Day AI discovery call from September 15, 2026. A VP of Sales described where their own setup had stalled: "I've built my own skills in Claude, but it's taking me far too long... it's taking me 12 minutes... to write an email that doesn't work. I need this to scale and be quicker." The company's CTO described what the team needed: to "ingest these additional net new records and incrementally build on that [context] graph," in place of "building workflows and signals within Salesforce, which is building for the last generation of workflow operation."
That is the resolution ceiling described by the people hitting it. The essay goes on to estimate how many companies are at that point now and will be in the next few years. Those are O'Donnell's estimates. The pattern on the call is the evidence.
How Day AI handles it
Day AI provides the context graph and agent control plane to quickly and securely upgrade your company brain. It is the context graph that replaces the CRM as the record. Teams looking for an AI-native CRM find that it does that job, but it is built as what comes after the CRM: it keeps the customer record itself, so nobody types it, and it runs alongside Salesforce or HubSpot or in place of them.
A record built from the conversations
Day AI builds a self-updating customer record from every meeting, email and call. Each person connects their own Gmail and Google Calendar. Day AI's notetaker joins Zoom, Google Meet and Microsoft Teams calls and writes the transcript into the record when the meeting ends. Gong and Granola calls come in with their transcripts and their full history, so a new workspace can start with years of calls already in it. Slack comes in from the channels the Day AI app joins. All of it resolves into the same people, organizations and opportunities, and anyone your team emails becomes a contact automatically.
Because the conversations are kept, fields can be derived from them later. A custom property starts from a definition an agent follows, gets filled from your team's conversations, from web research or both, and is backfilled across all the history already in the graph.
This is O'Donnell's superset argument in practice. A record that keeps the conversations can produce every field a CRM holds, and a CRM can't produce the conversations. As the essay puts it, "You cannot play Elden Ring on a Game Boy."
Agents that do the typing, and the work after it
On top of the record, Day AI runs governed agents that create finished work. They prospect, prep every meeting, draft follow-ups and keep the pipeline clean. Skills run on a schedule or on events, such as a recording being ready or an email landing, and every skill keeps a history of its runs. When one misfires, you tell the agent, change the skill, and every later run uses the change.
Every value carries its receipts
"Every value carries its own receipts" is how O'Donnell describes the record the essay argues for, and it is the same thing Standage asks of a system of accountable action. In Day AI, every fact and every action traces to the source conversations. Answers cite the call clip or the message they came from. A value derived from a conversation links back to the meeting or email it came from, with the passage cited. Every value keeps its history: who changed it, a person or an agent, when, why, and what it was derived from, and your agent can read that history back when you ask what changed on a deal.
Permissions that travel with the data
O'Donnell argues that permissions belong with the data, not in a layer bolted on later. Day AI applies them as the data arrives. Each person sets sharing rules for their own mail, by domain, address or Gmail label, and Day AI decides who can see each email thread as a step in ingestion, before any person or agent can read it, and stores that decision with the message. When the same message sits in several teammates' inboxes, a private rule from any of them keeps it private, and one private message keeps its whole thread private. An agent inherits the permissions of the person it works for, not those of an integration user, so the problem Vantage Point names doesn't arise.
Replace the CRM, with or without a rip-out
A common fear, and one the essay answers in its own section, is "we have to keep our CRM." The essay's answer is that the agent control plane does all the CRM data entry, and that syncing the two is theoretically possible, but "there's just no point... You don't have to bite that off on day one."
Day AI runs as a layer on top of Salesforce or HubSpot or in place of them. You can switch the old CRM off, or keep it. Either way the record moves to the graph on day one.
- Alongside the CRM. Day AI supports connecting MCP servers, including the Salesforce and HubSpot ones. Each person connects with their own login, through an OAuth app your company registers. Agents read the CRM live, and with the server's write tools allowed they write back to it, so a skill can update deal stages, notes and fields after every call. In a chat, those calls can pause for the person to approve them first. CRM records are read live, not copied into Day AI.
- In place of the CRM. Contacts, organizations and opportunities move over as a CSV import that your agent runs in a chat: it inspects the file, works out what each row is and maps the columns. From then on the record keeps itself current from the conversations.
Either way, the CRM stops being the record and stops being the place people type.
One limit to know: email in the record comes from Google Workspace today. Outlook, Outlook Calendar and Teams are reachable live through connectors in beta.
Which future is your company in?
Answer three questions about your own team.
- Pick your biggest win last quarter. Can anyone explain why you won it without asking the rep who closed it? If the answer lives in the rep's head, the record is at its ceiling.
- When a rep asks your AI assistant about an account, does it see only what that rep may see? If it sees what the integration user sees, the assistant inherited the CRM's permissions problem along with its data.
- If you added a field today, such as "competitor mentioned", could it be filled for last year's deals without anyone typing? If not, every new question about your pipeline starts from empty.
Three yes answers: you are in Vantage Point's future, for now. The record is current and governed, and an AI layer on top can work, as long as its permissions stay as tight as the CRM's. The ceiling arrives the first time you ask a question nobody typed a field for.
One or two: you are in a16z's future. The CRM is one input, the real story is spread across inboxes, call recorders and Slack, and you need a layer that reads all of them.
None: you are at the resolution ceiling. A layer that reads only the CRM will inherit its amnesia. Start a context graph, next to the CRM you have or in place of it, and let it take over as the record.
Question 3 is the hardest to pass, because it depends on what the record stores, not on how well the team keeps it.
Read the argument in full
For the opinion behind this guide, read Christopher O'Donnell's essay at lifeaftercrm.com. To see where your own setup sits against that argument, run the company brain evaluation in your folder with npx skills add day-ai/company-brain-evaluation. It scores your build on safety, performance, capability and adoption.
For depth on the pieces this guide leaves out: Context graph vs. RAG vs. CRM compares the three ways of storing customer data, How to build a context graph walks through building one, and Build vs. buy sets out which parts are worth building yourself.