Yes, you can build your own CRM with Claude. People who have done it report a first version, with companies, people, deals and a pipeline, in an afternoon to a weekend using Claude Code, Lovable or a Notion database. The tables come together fast. The harder work starts after: getting email, calendar and calls into it without typing, letting a team sign in, catching duplicates, and keeping backups. If you want something shaped to your business without owning that work, there is a middle path: a CRM your assistant reshapes for you, where the plumbing already exists.
Mostly because it got easy. A CRM used to be a weeks-long software project; with Claude Code or Lovable it is an evening. Once building is that cheap, two other things stand out: a homemade CRM fits your business exactly, and the ready-made ones cost a lot for a small team.
We make a CRM, so read this knowing that. In our experience the app is rarely what goes wrong with a homemade CRM. What goes wrong is that, a few weeks in, people stop typing things into it.
Each of these is easy to start and slow to finish.
You pay for the build once. Upkeep you pay for every month, mostly in your own hours and in interruptions on days you had planned for customers. Whoever writes the software ends up owning it.
Swap in your own numbers. Here we assumed 4 hours a month of fixes and small changes, at $100 an hour: that’s $400 a month, and it doesn’t count a bug that loses you a deal. Capable for a team with 10 active accounts is $33.90 a month, and the upkeep is our problem.
| What matters | A spreadsheet or Notion, plus ClaudeGoogle Sheets, Notion, Airtable | Build your ownClaude Code or Lovable, on a database like Supabase | The middle path: CapableA CRM your assistant shapes for you | An off-the-shelf CRMHubSpot, Salesforce, Pipedrive |
|---|---|---|---|---|
| Fits your business | Yes, any columns you like | Yes, anything you can describe | Yes. Your assistant adds objects, fields and pipelines from the chat | Within the vendor’s settings, usually by an admin |
| Time to first use | Minutes | An afternoon to a weekend for a first version | Minutes. Sign in with Google or Microsoft | Hours to weeks of setup |
| Email, calendar and calls logged automatically | No. You paste things in, or ask Claude each time | Whatever you build, for as long as it keeps working | Yes: email, calendar and a meeting recorder. LinkedIn in beta | Email and calendar sync on most plans; recording varies |
| Works from Claude and ChatGPT | Through each tool’s own connector | Through an MCP server you write and host | Yes, both, through one MCP connection | Through their MCP connectors, depending on the CRM and plan |
| A team on one record | Shared document permissions | What you build | Unlimited seats, with roles and team or own-book visibility | Roles and permissions, with each person paid for |
| Approval and history for AI changes | No | What you build | Field-by-field approval for what the assistant infers, and a full history | Varies by CRM |
| Who keeps it running | You | You | Capable | The vendor, plus your admin |
| What you pay | The subscriptions you already have | Hosting, plus your time | $29 a month per workspace plus $0.49 for each active account, unlimited users | Per seat, per month |
Each option does more than one row can say. For CRM-by-CRM detail on Claude and ChatGPT support, checked on each vendor’s own pages, see our full comparison. See the full comparison of CRMs for Claude and ChatGPT →
What people like about a homemade CRM is that it fits how they work and they can change it just by describing what they want. You can keep that. What you can hand off is the wiring: email, calendar and meetings, matching people to companies, sign-in, permissions and backups.
We built Capable to sit there. You shape it from Claude or ChatGPT, it picks up your conversations without anyone logging them, and when your assistant works something out on its own, it asks before saving.
Add an object called Placements with a status, a start date and the family it belongs to.A new object with those fields, usable from the chat and in the web app.
Make a pipeline for pilots: Intro, Demo, Security review, Pilot, Signed.A second pipeline with your stage names.
Add a Source field to deals: LinkedIn, referral or event.A dropdown field, so reports can group by source.
Set up a 10-day plan: LinkedIn invite, a comment, a message, then a call on day 10.A sequence with a due date for each step. Capable keeps track; the messages go out from you or your assistant.
Which pilots haven’t heard from us in two weeks?A list from the record. Say “save it” and it becomes a report.
New to the idea of a CRM inside your assistant? What an MCP CRM is → · The three kinds of AI CRM → · Why there are no seats →
Yes. Whether you started in a spreadsheet, a Notion database or an app you built, export it to CSV and ask your assistant to import it. Capable maps your columns and shows you a preview first. If a record already exists with different data, it won’t be overwritten.
You can also keep the tools you built on top. They can read what changed since they last checked, or receive a webhook.
of Michael Clausen’s CRM updates at FAIVE arrive through MCP, straight from Claude.
“The easy answer was ‘let’s make an Excel sheet.’ It’s also the worst possible answer. We realized it as soon as we started filling out the first cells.”
Mainly because it has become easy: with Claude Code or Lovable, a first version takes an evening. A homemade CRM also uses your own stages and fields, and it skips the per-seat prices, the higher tiers you need for standard features and the AI credits that ready-made CRMs charge for.
Yes. Describe the tables you need, usually companies, people, deals and activities, and Claude Code will write the database, a web app and an MCP server so Claude can read and update it. That part goes quickly. Getting email, calendar and calls into it, and running it safely for a team, takes longer and never quite finishes.
People who have built one report an afternoon to a weekend for a first version. After that the work comes in smaller pieces: a new data source here, a new colleague there, an API change you didn’t see coming.
Hosting can cost next to nothing. Your time costs more: bug fixes, API changes and whatever the team asks for next come out of hours you’d otherwise spend with customers. For comparison, Capable is $29 a month per workspace plus $0.49 for each active account, with unlimited users, so a team with 10 active accounts pays $33.90 a month. Contacts, prospects and seats are free.
Not really. Claude’s chats and memory aren’t a structured record your team can share, and Claude doesn’t pull in your email, calendar and meetings in the background. It needs a CRM to read from and write to, whether you build that yourself or use one like Capable.
For a short list you update by hand, yes, and plenty of people start there. It gets awkward when you want conversations captured automatically, the same person recognised across email and LinkedIn, or a colleague working the same accounts.
No. A workspace admin asks in Claude or ChatGPT, say “add a Renewal date field to accounts”, and the field appears in the chat and the web app.
Yes. Capable connects to both Claude and ChatGPT through one MCP connection, and both read the same record.
Yes. Export it to CSV and import it from the chat or the web app. You see a preview first, and existing records with different data are left alone. Capable also imports from Salesforce, HubSpot and Attio.
No. Reports export to CSV, and the change feed and webhooks let other tools follow along. If you just want to look around first, the trial is 14 days and doesn’t ask for a card.
Shape it from Claude or ChatGPT. Capable picks up the conversations and keeps the record.
No card needed. Or talk to us first.