Can I use Claude as my CRM?
Yes. If you sell alone, it works today. If you have a team, it works too. You have to build the part a CRM comes with: one place where all your customer stuff is kept, and kept right.
Yes. If you sell alone, connect your mail and your calendar, and Claude can tell you where things stand with anybody. If you have a team, each person's Claude reads only their own mail. So you need one place where all the customer stuff is kept, and kept right, that everybody's Claude can read. You can keep it in a shared project or in your own database. Either way, somebody on your team has to keep it right and fix it when it breaks. A CRM like Day.ai or Attio does that part for you.
Why is everybody asking this?
Because nobody likes typing into a CRM. You have the call. Then you type up what you remember. Most people skip it.
Salesforce asked 7,775 sales people how their week goes. They spend 28 percent of it selling.
So if something can read your inbox and answer a question, people ask if they still need the CRM.
What does Claude do well as a CRM?
Connect your Gmail and your Google Calendar. Then ask it things.
- Where are we with Acme?
- Who have I not written back to this week?
- What did I promise Dana, and when?
It reads your mail and it answers. Anthropic's help page lists what it can do once connected: search and read your mail, write and send replies, see and change your calendar. By default it asks before it does anything for you.
If you sell alone and most of your selling is in email, this is enough. Nobody typed a thing.
Where does it stop working?
Four places.
It does not keep a list.
If you ask on Monday, it reads your mail and tells you. If you ask on Friday, it reads your mail again. There is no list you can sort or count.
It does not hear your calls.
Claude reads mail and calendar. If you sell on calls, it knows the call was on your calendar. It does not know what was said.
Writing things down is slow.
Reading is fast. Saving is not. The picture below is one man's stopwatch.
Each person's Claude reads only their own mail.
This is true on the Team and Enterprise plans too. An owner turns the mail connection on. Then each person signs in to their own account. Your new hire's Claude reads their mail. It does not read yours.
If both desks read the same place, both get the same answer. Somebody has to keep it right.
What decides if it will work for me?
Five things. Answer each one.
How many people sell?
- If one person sells
- Then Claude is enough.
- If two or more people sell
- Then You need one place where the customer stuff is kept, and kept right.
Where do you talk to customers?
- If it is mostly email
- Then Claude already reads it.
- If it is mostly calls
- Then Add a call recorder and connect it.
How long is your list?
- If it is short
- Then A file in a shared project works.
- If it is long
- Then Use a database. Claude searches a long file. It does not read all of it.
Does anybody need totals?
- If nobody does
- Then A file is fine.
- If your boss or your bank does
- Then Use a database or a CRM.
Does anybody on the team like fixing software?
- If somebody does
- Then You can build it.
- If nobody does
- Then Buy a CRM.
If you got the first answer every time, you can stop reading. Claude is enough for you.
If you got the second answer even once, keep going. The next two questions are what it takes.
What do I have to connect?
Six parts. A CRM comes with all six. If you build it with Claude, one comes with Claude and you bring the other five.
- Comes with Claude
Mail and calendar
Each person connects their own account.
- You add it
Calls
Add a recorder like Fathom and connect it. Claude can read the notes and what was said. It cannot change them.
- You make it
One place to keep it all
Where all your customer stuff is kept, and kept right. A file in a shared project, or a database.
- You do it
A way to get things onto the list
Somebody types it in. Or somebody tells Claude to. Or you build something that does it for you.
- You set them
Rules for who sees what
A shared project has two levels. A database has what you build.
- One of you
A person who keeps it working
Pick this person before you start.
Parts 3 and 4 are most of the work. There are two ways to do them. I call the thing you keep "the list" from here on.
Keep the list in a shared project
If you are on a Team or Enterprise plan, you can share a project. Everybody in it gets the same files and the same instructions. Anthropic's page on projects explains it.
- The file is a copy. The live Google Drive link is switched off in shared projects. If nobody uploads a new file, the team is reading last week's.
- Chats do not update it. If your teammate learns something in a chat, it stays in that chat. The team gets it only if somebody adds it to the project.
- There are two levels. A person can view, or a person can edit. That is all.
- Claude does not read all of a long file. If the files get big, it searches them for the parts that look related. That is fine for one customer. I would not add up a pipeline from it.
Keep the list in your own database
A table in Supabase, or something like it, with Claude connected. An owner adds the connection once. Then each person signs in. The database does the adding, so the totals are right.
- You fix it. Somebody picks the columns, backs it up and fixes it if it breaks. I built one for my own shop. It works, and I am the one who fixes it. If that person leaves, nobody else knows how it works.
- It was made for developers. Supabase's own guide says its Claude connection runs with a developer's access. It says the connection is meant for developers to use inside the company.
- Strangers write to you. If Claude reads your mail and can change your database, it is reading words from people you have never met. The same guide warns that those words can carry instructions. It says its own guard "is not foolproof." Their advice is to let Claude read and not write, or to approve each change by hand. That is safe. It is also slow.
- It does not fill itself in. Nothing gets into the table until somebody tells Claude to put it there. If you want it to happen without anybody asking, you have to build that too.
Both ways work for a few people who talk every day. Both ways, the work a CRM does is now your work.
What do I give up next to Day.ai or Attio?
A CRM like Day.ai or Attio comes with all six parts. Here is the difference, line by line.
What you give up if you build it
- The team's mail and meetings in one place. If you build it, each person's mail stays in their own Claude. Day.ai reads your team's email, calendar, meetings and Slack. Attio reads each person's mail and calendar and makes the people and the companies for you. The team sees who emailed who, and when. Each person chooses if the team can read the full email.
- Calls next to the customer. If you build it, calls sit in a separate tool. Attio records calls on its higher plans. It puts the notes on the person and on the company.
- Somebody else to fix it. If your build breaks, you fix it. If Day.ai or Attio breaks, they fix it.
What you keep if you build it
- You start today. There is nothing to set up first and nothing to move.
- Nothing new to buy or learn. If your team already uses Claude, they keep using Claude.
- It works your way. If you want it changed, you change it.
What a CRM still asks of you
- A bill. Every month.
- A setup. Somebody has to set it up and get every person to connect their mail. That is the job I do.
- Some work by hand. It is not all automatic. In Attio, a call goes on the person and the company by itself. You link it to the deal yourself.
So what should I do?
If you sell alone, use Claude. Connect the mail and the calendar. Keep one list of who you are working. Ask it every Monday what you dropped. I wrote out the four steps and the three things to paste in.
If two to five of you sell and you talk every day, start with a shared project. Put one person in charge of the list. Pick a day to update it. If two of you ever argue about whose copy is right, it is time for a database or a CRM.
If somebody on your team likes building, use a database. Know that you now run software. I wrote down what that takes in a year.
If selling is the whole job, get a CRM and connect it to Claude. HubSpot, Attio and Day.ai all connect. You still ask Claude. The CRM is where the customer stuff is kept. It fills itself in from the mail and the calls. Here is how the four I would look at differ.
If you tried Claude as your CRM and it stopped working when you hired somebody, you did not do it wrong. You needed one place for the customer stuff.
Will a team that builds it end up on a CRM anyway?
I think most will. Here is why, from what is on this page.
- Claude brings one part of six. You bring the other five, and you keep them working.
- Every limit shows up when you grow. You hire a second seller. The list gets long. The person who built it leaves.
- The people who built one say so. Chris Scott built his, used it, and is rebuilding the slow parts. I built mine, and it works because I fix it.
So if you build it, know what the breaking point looks like.
- If two people ask the same question and get two answers, you are there.
- If nobody has updated the list in two weeks, you are there.
- If the person who built it takes a week off and things stop, you are there.
If you see one of those, move to a CRM then. Do not wait six months.
I could be wrong. Every limit on this page is how Claude works in November 2026. Claude changes every few months.
- If a shared project can read a live file, the old copy problem goes away.
- If one connection can read a whole team's mail, both desks get the same answer.
- If Claude can save to a list fast, the stopwatch stops mattering.
If those three get fixed, building it gets close to buying it. More teams will stay on what they built, and I will have been wrong.
Claude has memory now. Does that close the gap? Not yet. Claude makes its memory from your chats. It remembers your job, your projects and how you like to work. It is made to know you. It is not a list of your team's customers. The help page does not say a team shares one.
Can you copy what a CRM calls memory? You can copy the idea. The work is the hard part. I read Day.ai's own guides to check.
- The idea is not new. Day.ai calls its version a context graph. Their guide says it is close to older ideas, not a new kind of thing.
- They say one person can build a start. Their build or buy guide says it lasts a few weeks. It says a team's own build never gets finished. They sell a CRM, so weigh that.
- They name four parts to buy. Getting everybody's mail and calls in. Keeping private mail private. Knowing two names are one person. Running it for people who do not write code.
- A smarter Claude does not fix those four. Their case is about where the stuff is kept. It is not about which model reads it.
That fits what I found building mine. Do not take their word or mine. Ask both the same five questions about one customer, and compare.
One part does not get fixed by software. Somebody has to care that the customer stuff is right. If nobody on your team does, it will be wrong in Claude and it will be wrong in a CRM.
The same thing, seven more ways
Can Claude replace a CRM?
If you sell alone, mostly yes. If you have a team, only if you add one place where the customer stuff is kept, and somebody keeps it right.
Does a Claude Team or Enterprise plan make it a team CRM?
Not by itself. It lets you share a project and turn connections on for everybody. Each person still signs in to their own mail. A chat in a shared project does not update the shared files.
Does Claude know what was said on my calls?
No. It reads your mail and your calendar. If you want calls, add a recorder like Fathom and connect it. Claude can read those notes. It cannot change them.
Can I use Supabase as the database behind Claude?
Yes. The database does the adding, so the totals are right. You have to fix it yourself, and Supabase's own guide says its Claude connection is meant for developers.
What do I give up next to Day.ai or Attio?
Three things. The whole team's mail and meetings in one place, a list that fills itself in, and somebody else to fix it. You keep a fast start and nothing new to buy.
Will a team that builds its own end up on a CRM anyway?
I think most will, once they hire a second seller or the person who built it leaves. I could be wrong if Claude fixes the limits on this page.
Does the same thing work with ChatGPT or Gemini?
Yes, and it stops in the same place. If it reads one person's inbox, it knows what one person knows.
- Salesforce, State of Sales, fifth edition. Surveyed in 2022.
- Anthropic, "Use Google Workspace connectors", Claude Help Center.
- Chris Scott, "I Used Claude to Build a Personalized CRM (Then I Tried Using It)", The Paperless Agent, August 28, 2026.
- Anthropic, "How can I create and manage projects?", Claude Help Center.
- Anthropic, "Retrieval augmented generation (RAG) for projects", Claude Help Center.
- Anthropic, on connectors for team plans, Claude Help Center.
- Supabase Docs, on connecting AI tools to a database, security section.
- Fathom, on claude.com. What Claude can read from a call recorder.
- Attio, "Email and calendar syncing", Attio help center.
- Attio, "View and manage call recordings", Attio help center.
- Day.ai, home page.
- Anthropic, on how Claude's memory works, Claude Help Center.
- Day.ai, guide on context graphs, RAG and CRM.
- Day.ai, guide on building or buying customer context.
Not sure which one fits you?
Thirty minutes. Tell me how many people sell and where you talk to customers. If Claude is enough, I will tell you.