# Rare for Teams: the CRM your agents can finish

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.

To talk about a pilot, email [contact@rarecrm.ai](mailto:contact@rarecrm.ai?subject=Rare%20for%20Teams).

## Why now: your team can build software in an afternoon, so why are you still waiting on your vendor?

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: other CRMs give you an API to work around them, we give your agents the CRM itself

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.

| A typical CRM | Rare for Teams |
| --- | --- |
| 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: ask for a new view, field or workflow, and it's built into the CRM

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. Claude Code, Codex or your own engineering team: any of them can do it.

For example, you ask for it: "Create a reconnect queue for people I haven't talked to in 90 days." It adds `views/ReconnectQueue.tsx`, `workflows/reconnect.ts` and a change to `journal/schema.life` to your CRM, and pushes it (`git push rare main`). It goes live for your team with no server and no ops: a Reconnect Queue listing, say, Ravi Menon at 94 days and Claire Dubois at 112.

## Ready on day one: Rare for Teams works on day one, change only what your business needs, and we keep all of it running

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, for example:

- **A founder's office.** Investors by stage and warmth, candidates through hiring and customers after the sale, all in one memory. Its agents build investors by stage, a warmth score, intro requests, a hiring pipeline and a monthly investor update.
- **An agency.** Clients, their people and every promise made on a call, with follow-ups that don't depend on one person remembering. Its agents build promises by client, account health, post-call follow-ups, a weekly client digest and a competitive-research skill.
- **A recruiting desk.** Candidates and hiring managers, what each one wants, and who should meet whom next. Its agents build who should meet whom, what each candidate wants, a notice-period tracker, an interview prep brief and placement check-ins.
- **A community team.** Members, introductions and commitments, shared by the people who keep the community running. Its agents build introductions this month, member interests, an event host rota, a new-member welcome and a lapsed-member check-in.

Maintained by Rare: we run every skill and workflow in production; keep what you built working as the core changes; retry, monitor and alert when something fails; keep storage, history and daily backups; sync across phones, web and agents; handle security and access for the whole team; and run the agent that files what your team says.

## Bring your skills: the skills your team already wrote run next to your CRM, and file what they find under the right companies

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. Skills written for Claude, Codex or Gemini.

For example, every Monday at 8:00: "Run competitive-research on our top 20 accounts and update each company in Rare." The run reads the 20 accounts from Rare, checks their pricing pages, changelogs and news, and files what changed with its source, such as "Northwind launched a self-serve plan at $49 a seat, aimed at teams under 20" (northwind.com/pricing, Oct 12) and "Helix Health opened a Toronto office and is hiring a head of partnerships" (helixhealth.com/careers, Oct 13).

- **A full Linux machine for every CRM.** Each Rare for Teams CRM runs on its own machine. Install the runtimes, tools and scripts your skills need.
- **The skills you already have.** Account research, competitive analysis, pipeline reviews: the skills your team built for Claude, Codex or Gemini can run here.
- **Results land in the CRM.** What a skill finds is written into your CRM as entries with sources, on the right people and companies, and shows up in History.
- **We run the infrastructure.** 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: agents can't break it, every change is checked, committed and sourced before your team sees it

Letting agents change your CRM only works if the foundation survives them. All of this is already true of Rare today.

For example, a team's History: an agent adds the Reconnect Queue view, Alice records coffee with Farida, the competitive-research skill updates two companies with sources, and Sam records a pilot call, each change checked. An agent's attempt to merge two people named Sam is refused, because a line names someone not in the journal.

- **Plain text is the source of truth.** 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.
- **Every change is a commit.** The journal is a git repository. Every edit, a person's or an agent's, is recorded, reviewable and reversible.
- **Checked before it lands.** Every change is checked against the whole journal before it is saved, and a change that would break it is refused.
- **Every fact has a source.** Each thing Rare knows links back to where it came from, so automation never blurs what was said with what was guessed.
- **Agents check their own work.** After every edit, an agent runs Rare's checks, and each mistake names the line to fix, before anything reaches your team.
- **One set of rules.** Your agents follow the same instructions Rare's own agent does, so what they write reads like what Rare writes.

## No lock-in: your CRM is plain text in a git repository, so it leaves with you whenever you do

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.

## We're opening Rare for Teams to a handful of teams already building their own agent skills

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. Email [contact@rarecrm.ai](mailto:contact@rarecrm.ai?subject=Rare%20for%20Teams).