Your CRM doesn't have a feature problem. It has a data-entry problem.
Notion Pilot is that idea for a CRM you actually own — data kept up to date by AI assistance, in your own Notion workspace.
Why that announcement matters more than it looks
The interface was the bottleneck
Nobody quits a CRM over a missing field. They quit over fifteen clicks between two meetings.
The process still holds
The agent inherits the CRM's permissions instead of bypassing them. No access to a record, no access for the AI.
The idea outlives the vendor
Claudeforce only works if you already pay for Salesforce. Same idea, without the estate — that is this page.
Notion is built on a database structure. It is not a CRM yet.
Every Notion table lives inside that structure — and a row in one table can relate to a row in another. A contact relates to a company. A deal relates to both. Rename that company once, and every deal, contact, and activity referencing it updates instantly — because they hold a relation, not a copy.
That single property is the entire difference between a CRM and a spreadsheet. Notion has had it all along.
What Notion doesn't give you is a schema shaped like a pipeline — and someone to keep it current. That's exactly what we bring.
One company. One row. Everywhere.
This is the thing a spreadsheet can never do, no matter how many tabs you add.
In Excel
A client renames itself and you find-and-replace across six sheets. You will miss one, and nobody will notice until the QBR.
In Notion
You edit the company row. Every deal, contact and activity pointing at it updates, because they were never copies.
| Name | Sector | Tier | People | Last activity | CRM status |
|---|---|---|---|---|---|
| Voltaris Énergie | Energy | Tier 1 | 3 contacts | 2d | Active |
| Néorégie Grid | Public Sector | Tier 2 | 1 contact | 11d | Prospect |
| Hexalis Industries | Industry | Tier 2 | 5 contacts | 34d | Prospect |
| Cerena Renouvelables | Energy | Tier 3 | 2 contacts | 6d | Active |
The same rows, seen six ways
A view is a lens, not a copy. Board for the Monday pipeline review, table for the audit, calendar for next steps, timeline for the quarter — every one of them reading the identical rows, live.
So nobody exports anything, nobody rebuilds a deck, and there is no “which version is current?”. Leadership opens the view. That is the whole reporting story, and it replaces the weekly spreadsheet ritual outright.
The deal, and the trail that proves it
Every lead carries its own activity trail, so “what happened on this deal?” is a click, not an archaeology project — and the one number every pipeline review actually turns on finally means something:
| Deal | Stage | Value | Prob. | Activities | Last activity |
|---|---|---|---|---|---|
| Voltaris — Platform licence | Proposal Sent | 120 000 € | 60 % | 7 activities | today |
| Astria — Optimisation | Negotiation | 80 000 € | 75 % | 12 activities | 3d |
| Cerena — Consulting | Qualified | 45 000 € | 40 % | 4 activities | 6d |
| Hexalis — Platform licence | Waiting for a Response | — | 10 % | 2 activities | 34d · stale |
| Kaleo — Licence | Closed Won | 52 000 € | 100 % | 9 activities | 12d |
| Activity | Type | Outcome | Next step | When |
|---|---|---|---|---|
| Demo follow-up | Follow-up Needed | Send proposal, 12 licences | logged by AI | |
| Technical demo | Demo | Positive | Loop in security | 4d |
| Discovery call | Call | Positive | Book demo | 11d |
Around that deal: companies, people, meetings
Everything hangs off the deal. A call logged this morning appears on the lead, on the contact and on the company — one row, related three ways, never three copies.
Companies
autoLeads
autoThe pipeline everything points at.
Activities
autoPeople
autoMeetings
manualauto Notion Pilot reads and writes these four. manual Meetings lives in Notion and stays yours.
But who keeps all of this up to date?
Building the schema is one good afternoon. Keeping it true is every afternoon after that. Here is the same deal record, and nobody touched it in between.
Nothing here is broken. Every formula is still correct — they were simply never fed. A CRM that runs on discipline decays at the speed of your busiest week.
- We deploy a ready-to-use CRMSix databases — Companies, People, Leads, Activities, Meetings, ICP profiles — relations wired, stages filled, and the pipeline formulas already computing.
- You reshape itA property here, a stage split there, a tier system nobody else would want. That is the whole reason to build a CRM in Notion.
- The automation followsThe assistant reads your workspace through Notion's own MCP server, so it works on the structure you grew into — not one hardcoded a year ago. Add a field on Monday, it fills it on Tuesday.
And when it gets something wrong, tell us — an awkward property, a stage the matcher misreads, a report you still rebuild by hand. Feedback from real pipelines is what shapes this roadmap.Open an issue →
Open Notion to see the pipeline. It already moved.
Notion Pilot does the typing. You keep the judgement.
Your AI assistant reads the thread, searches the CRM, and shows a preview. Nothing reaches Notion that you haven't approved.
Your AI assistant
paste · preview · goSubject: RE: optimisation platform — next steps Thanks for Tuesday's demo. The team is convinced on the solver side. We need a security review before signing, and our budget window closes 15 December. Can you send a proposal for 12 licences? — Camille Dubois, Head of Grid Analytics, Voltaris Énergie
| Database | Action | Record |
|---|---|---|
| Companies | matched | Voltaris Énergie no change |
| People | create | Camille Dubois Head of Grid Analytics · director |
| Leads | update | Voltaris — Platform licence Discovery → Proposal Sent · 50 → 60 % · close 15 Dec |
| Activities | create | Demo follow-up Email · Follow-up Needed · proposal due 20 Nov |
Where your data goes
Where your data goes. Your CRM records are stored in your Notion workspace. On the Notion Enterprise plan, Notion can host that workspace in the EU (Frankfurt); on other plans, Notion stores it in its default region (US). Region and terms are set by your agreement with Notion (details). EU hosting covers CRM data stored in Notion, not AI processing. When your assistant reads CRM records, that content is processed by your assistant's provider (e.g. Anthropic for Claude), under the provider's data processing terms; Notion's residency does not cover it. Notion states that some of its own AI processing can also happen outside the residency region. notion-pilot.com deploys the CRM structure and keeps no CRM records and no Notion access token.
Deploy the CRM, then teach your assistant to run it
Nothing to migrate, nothing to sign. Deploy writes the CRM into your Notion. Claude then reaches those same pages through Notion's official MCP — a second OAuth, same workspace — and the skills in this repo tell it how to run the pipeline.
The skills are the product
An MCP connection alone just gives an assistant hands. These are the instructions that make it useful on a CRM — search before write, dedup, a validation table, and a hard stop until you approve.
Operate the CRM — create and update leads, log activities, enrich people and companies. Always shows a validation table and waits for your go.
Fill firmographics from French open data — SIREN, NAF/APE sector, size — instead of typing them.
1 Install the skills
Claude app: Customize → Plugins → Add marketplace → ldom1/notion-pilot-powers. Claude Code: the two lines below. All three skills arrive together and update with the repo. No clone, no symlinks, no config file.
/plugin marketplace add ldom1/notion-pilot-powers /plugin install notion-pilot-powers@notion-pilot-powers
2 Connect Notion
Notion's hosted MCP, not the wizard's integration. Complete its OAuth once — it sees the pages you can see, including the CRM you just deployed. Restart the assistant and the skills trigger on their own. Notion MCP setup.
# Claude Code
claude mcp add --transport http notion https://mcp.notion.com/mcp
# then run /mcp and complete the OAuth flow
# Cursor — .cursor/mcp.json
{ "mcpServers": { "notion": { "url": "https://mcp.notion.com/mcp" } } }Questions
Do I need to code?
Not to deploy the CRM: one click and a Notion authorisation. The assistant runs in the Claude app or in Claude Code, with the free notion-pilot-powers plugin and Notion's official connector; a step-by-step guide (PDF) is there if you want to be walked through it.
Does my data stay in Europe?
Your records live in your Notion workspace. On Notion Enterprise, Notion can host the workspace in Europe (Frankfurt) — that is a Notion option, to confirm with Notion. When your assistant reads your records, its provider (for example Anthropic for Claude) processes them under its own terms.
Can the AI write anything it wants?
No. Preview is the rule: every write is proposed, you approve. Ambiguous matches are put to you.
What about companies outside France?
They are recorded as usual, but not enriched automatically: enrichment relies on French open data.
Run your next real deal through it
One channel, one database, a week of real emails. Then look at the pipeline on Monday and decide whether you believe it.