Rare for Teams
A CRM your team talks to: tell it what happened, and it files each detail under the right people. Then your agents change the CRM itself, its data, screens and workflows, while we keep the core underneath running.
Why now
A few years ago, even a few months ago, changing your CRM meant a feature request and a long wait. Coding agents ended that: most teams can now make those changes themselves, if the platform lets them. That changes how a business should buy software, and what it should expect of the companies it buys from.
Not an extension
Every CRM ships the vendor’s idea of your business, and your team bends to fit it. Rare for Teams lets your agents bend the CRM instead.
The vendor’s idea of a contact, a deal and a pipeline
A data model your agents shape to how your business works
An API to read and write records
The CRM itself, open to your agents: its data, screens and workflows
Plugins in a sandbox, limited to the hooks the vendor exposes
Changes made in the CRM, reviewed and versioned like code
Customization that stops where the settings page stops
If your agent can build it, your CRM can do it
Upgrades that break what you customized
A core we maintain underneath, keeping your changes working
Your data in their database, behind an export button
Plain text in a git repository that leaves with you
How it works
Whoever your team already asks to build things can change the CRM’s own code and data model. The change is reviewed and versioned like any other, and it’s live for your team without a server to run.
01Ask for it
“Create a reconnect queue for people I haven’t talked to in 90 days.”
02Your CRM, changed
Pushing…
03Live for your team
Reconnect Queue
Ravi Menon
Intro to his fund
Claire Dubois
Pilot follow-up
Ready on day one
Every team starts with the same Rare and its sensible defaults: people and orgs, conversations filed under them, follow-ups and answers with sources. When something doesn’t fit your business, ask for the change.
And nobody on your team has to maintain it for the next five years. Running what you build, in production, is our job.
Unfinished does not mean unconsidered. It means you shouldn’t need our permission.
What teams build on top




Investors by stage and warmth, candidates through hiring and customers after the sale, all in one memory.
// maintained by Rare
Bring your skills
Your team has already taught its agents to do things well. Rare for Teams gives those skills somewhere to live: a machine beside your CRM, with its memory to read and write.
Every Monday at 8:00
Scheduled“Run competitive-research on our top 20 accounts and update each company in Rare.”
› Reading 20 accounts from Rare
› Checking pricing pages, changelogs and news
› 2 changes found
Northwind launched a self-serve plan at $49 a seat, aimed at teams under 20.
Added to Northwind · from northwind.com/pricing, Oct 12
Helix Health opened a Toronto office and is hiring a head of partnerships.
Added to Helix Health · from helixhealth.com/careers, Oct 13
Each Rare for Teams CRM runs on its own machine. Install the runtimes, tools and scripts your skills need.
Account research, competitive analysis, pipeline reviews: the skills your team built for Claude, Codex or Gemini can run here.
What a skill finds is written into your CRM as entries with sources, on the right people and companies, and shows up in History.
No servers to stand up, no cron to babysit. Schedule a skill, or let your team’s agents call it when they need it.
Safe to build on
Letting agents change your CRM only works if the foundation survives them. All of this is already true of Rare today.
History
Add the Reconnect Queue view
Your agent · 9:41
Coffee with Farida at Helix
Alice · 10:02
Update 2 companies, with sources
competitive-research · 10:15
Merge two people named Sam
Your agent · 10:20
Refused: line 14 names someone not in the journal
Pilot call with Northwind
Sam · 11:30
Everything Rare knows is in readable text files. Pages, lists and search are rebuilt from them, so nothing an agent builds can corrupt what you know.
The journal is a git repository. Every edit, a person’s or an agent’s, is recorded, reviewable and reversible.
Every change is checked against the whole journal before it is saved, and a change that would break it is refused.
Each thing Rare knows links back to where it came from, so automation never blurs what was said with what was guessed.
After every edit, an agent runs Rare’s checks, and each mistake names the line to fix, before anything reaches your team.
Your agents follow the same instructions Rare’s own agent does, so what they write reads like what Rare writes.
No lock-in
A CRM your agents build on should never trap the business that built it. Clone it and you have all of it: the journal with its history, and every view, workflow and skill your agents wrote.
$ git clone rare:acme-crm
Cloning into 'acme-crm'… done.
$ ls acme-crm
journal/ views/ workflows/ skills/
$ head -3 acme-crm/journal/2026/10.life
2026-10-14 "Pilot call with Northwind"
with: Sam Patel
medium: video
If your team writes skills for Claude, Codex or Gemini today, you’d work directly with us, Rai and Roy, and shape what we build first.