CRM for agents

The first agent-native CRM.

The CRM your AI agent runs for you. Rethought from the ground up for AI agents. Powered through MCP. Built to know the context of every client relationship, and equip your agent with the skills to guide every deal to close.

Get early-bird access. We use your address for one e-mail, the day your access opens, and nothing else. Our privacy notice explains how, and how to come off the list.

Follow the build:Follow on XFollow on Instagram
Claude

Planned the update from your call⌄

I'll update Northwind in backcrm.

⌃Steps
backcrm · deal.set_stageSet stage · Northwind → Negotiation⌄
backcrm · deal.set_close_dateSet close date · Northwind → Fri⌄
backcrm · activity.log_callLog call with Northwind, summary attached⌄
backcrm · memory.recordRemember · Northwind wants pricing in writing before the next call.⌄
backcrm · task.createCreate task · send Northwind pricing, due Fri, Sam R.⌄

Done. Northwind is in Negotiation, the call is on the record, and you have a task for Friday.

Reading the at-risk view in backcrm.

⌃Step
backcrm · crm.view.at_risk_dealsRead the at-risk deals view⌄

One deal has gone quiet:

DealStageLast touch
BetaCorpQualifiedsince last week
01Agent-native

Why an agent-native CRM?

Most CRMs have an MCP now. But those CRMs were built for a user interface, and their MCP just translates clicks into MCP calls. An agent-native CRM is built the other way round: in natural language.

Natural language MCP

One call instead of four. Fewer tokens, faster, fewer mistakes.

A UI-first MCP hands Claude the form's steps: find the record, set this field, set that one, save. Four calls, four chances to get it wrong, four times the tokens. backcrm hands Claude a verb: "move Northwind to negotiation". One call, done. The CRM is designed around what an agent says, not around what a person clicks.

Fewer callsFewer tokensFewer errors
UI-first MCP
1find_record("Northwind")
2set_field(stage)
3set_field(next_step)
4save()
backcrm
1deal.set_stage("Northwind", "negotiation")
4 MCP calls
1 MCP call
same result: Northwind → Negotiation

A memory on every record.

Every conversation adds context. backcrm keeps it and brings it back.

A traditional CRM keeps a record. backcrm keeps what Claude learned about it, apart from what merely happened: why the deal stalled, who really decides, what they asked for last time. That is the client context.

The recordWhat backcrm remembers
companyNorthwind120 people · Lyon
Procurement decides, not the sponsor. Security review comes first.
contactMaria C.procurement lead · Northwind
Answers on Thursdays. Wants everything in writing before a call.
Ask anything about Northwind. The right column answers.

Your playbook, as a skill.

Turn your sales rules into a custom skill. Claude follows it, for every rep.

How you qualify. What a proposal must contain. How you follow up. Write it once in plain language, save it as a skill in backcrm, and every rep's Claude sells your way — without re-explaining it in every prompt.

Skill · Discoveryin force
  1. 1Always confirm who signs before anything is sent.
  2. 2Every proposal carries pricing and a dated next step.
  3. 3Follow-ups end with a dated next step, never "let me know".
Written once. Followed by every rep.

A schema that changes when you talk.

A traditional CRM freezes your data model until the next release. Tell backcrm "we track workshops, not just deals" and the object exists two lines later, fields included.

we track workshops, not just deals
CompanyContactDealTaskWorkshop
dateownerstatusnotesfile
02Workflows

Your workflows, programmed by Claude.

Say what should happen. Claude writes the workflow, connects the tools, and reads it back before it runs.

Every source you connect will give Claude verbs: read a mailbox, watch a calendar, pull meeting notes, post to Slack. A workflow is those verbs in order, with a trigger. You describe it in plain language; Claude builds it, shows you exactly what it will do and how many records it would touch today, and hands it to you switched off. You arm it. Every run is on the record.

How it will work when the connectors ship.

You say
SR
After every meeting, find the deal, draft a follow-up from the notes on the channel we last used with the contact, and post a summary in the sales channel.
Claude builds it
GranolaMeeting endsGranola
Find the dealfrom the notes
Last channel?
GmailDraft follow-upfrom the notes
WhatsAppDraft messagefrom the notes
SlackPost a summarySlack #sales
Connectors we're building
FathomFathom
GranolaGranola
Microsoft 365Microsoft 365
backcrm
GmailGmail
OutlookOutlook
SlackSlack
WhatsApp BusinessWhatsApp Business
Everything is a workflow. Every connector will add its verbs.
03Questions

Questions, answered.

What is an agent-native CRM?

A CRM built for what an agent needs instead of for a person clicking through screens. In backcrm every business act is one verb your agent calls — move a deal, log a call, record what it learned — so there is no interface to drive.

What is MCP?

The Model Context Protocol: the way Claude talks to software directly, without a user interface in between. backcrm is reached through MCP, so your agent works it in natural language.

What is early-bird access?

You get in a month before public release. When your access opens we send you a code, and you sign up with it.

What happens to my e-mail?

We use your address for one e-mail, the day your access opens, and nothing else. Our privacy notice explains how, and how to come off the list.

Early-bird access

Be first into the agent-native CRM.

Follow the build and get early-bird access.

Work e-mail, nothing else. You get in a month before public release. When your access opens, your agent writes your team's method into your workspace with you — in the first conversation.

We use your address for one e-mail, the day your access opens, and nothing else. Our privacy notice explains how, and how to come off the list.

Or follow the build:Follow on XFollow on Instagram
Early-bird means
  • You get in before everyone else.
  • Your CRM sets itself up in your first conversation with Claude.
  • Your playbook, saved as skills Claude applies for the whole team.