# Notion as a CRM for a sales team: what it cannot enforce, and five checks that tell you it is time to move

https://salesbond.app/blog/notion-crm-sales-team-what-it-cannot-enforce/
Published: 2026-10-22 · Updated: 2026-10-22

Notion can work as a CRM for a handful of reps and a few dozen deals, but it cannot make a field required at a stage, keep a history of stage changes, or capture emails and calls on its own. Notion’s own help describes the CRM as something you build from a database, a Status property and a board view ( [Notion: a simple CRM](https://www.notion.com/help/guides/simple-crm-for-strengthening-client-relationships-and-managing-work)), and that is exactly where the limits sit. Two or more “no” on the checks below, and it is time to plan the move.

The five checks, in the order we would run them:

1. Can you make a field required before a deal enters a stage?
2. Is there a history of stage and close-date changes?
3. Can the manager see how the pipeline moved this week?
4. Can you limit which deals each person sees?
5. Do emails and calls land in the deal without anyone typing them in?

## Where Notion works as a CRM (a few reps, a few dozen deals)

We like Notion. A founder with twenty open deals, one database, a Status property for the stage and a board view grouped by that status has a working pipeline in an afternoon. The Notion guide proposes exactly this: a `Person` property for the owner, `Email` and `Phone` for the contact, `Select` tags for industry and lead source, a `Status` for the funnel step and a `Number` for the deal size ( [Notion: a simple CRM](https://www.notion.com/help/guides/simple-crm-for-strengthening-client-relationships-and-managing-work)). A template from Notion’s [CRM template gallery](https://www.notion.com/templates/category/crm) gets you the same board faster. It changes none of the five answers.

That setup holds while one thing is true: the person who reads the pipeline is the person who fills it. The founder knows which card is stale because she was on the call. Nobody argues about whether a deal is in Proposal or Negotiation, because nobody else moves the cards.

The trouble starts with the second rep. It gets loud with the first sales manager who isn’t selling herself, because now the pipeline is a report someone else reads, and a report is only as good as the discipline behind it.

We wrote a separate piece on [what to carry from a spreadsheet into a CRM](https://salesbond.app/blog/crm-sales-tracking-from-spreadsheet/). This one asks a different question: not which fields to move, but whether the tool you are on can hold a team to them.

![Five-row scorecard of Notion CRM checks, each with a Yes/No toggle; two or more No means plan the move](https://salesbond.app/wp-content/uploads/2026/10/notion-crm-sales-team-what-it-cannot-enforce-2.png)

## Check 1: can you make a field required at a stage?

In Notion, no. A property can be text, number, select, status, date, formula, relation, person and a dozen other types, and the help page on [database properties](https://www.notion.com/help/database-properties) describes no “required” setting for any of them. A rep can drag a card from Qualified to Proposal with the amount, the close date and the next step all blank. Nothing objects.

This goes first because it is the one control a sales manager can’t do without. A required field is how “Proposal” comes to mean “we know the budget and the decision date” instead of “I sent a PDF”. Without it, every stage is a vibe.

The usual workarounds are a formula that shows a red “Missing amount” label, or a filtered view called “Incomplete deals”. Both help. Neither is enforcement, because the card still moves. In Pipedrive an admin marks the field as required at a stage ( [required fields in Pipedrive](https://salesbond.app/blog/required-fields-pipedrive/)); in HubSpot it is a rule on the stage that asks for the property on the way in ( [stage required properties in HubSpot](https://salesbond.app/blog/hubspot-stage-required-properties/)). Either way the CRM stops the move until the field is filled.

Test it today: move any card two stages forward with every property blank. If it moves, the answer is no.

## Check 2: is there a history of stage and close-date changes?

Not by default. Notion gives you `Last edited time` and `Last edited by`, which record when the page was last edited and by whom, and update on their own ( [Notion: database properties](https://www.notion.com/help/database-properties)). That tells you something changed. It doesn’t tell you the deal sat in Negotiation for six weeks, went back to Proposal twice and has had it’s close date pushed every Friday since March.

The pushed close date is the case that matters. A rep who moves the date forward is “updating” the deal, so the timestamp looks fresh on a deal that hasn’t moved an inch. The manager sees activity; the pipeline is standing still.

You can build part of the history yourself. Database automations have a “Property edited” trigger and an “Edit property” action, so an automation can react when Status changes and write to another property ( [Notion: database automations](https://www.notion.com/help/database-automations)). They are a paid-plan feature. What you get is a home-made changelog that someone maintains, that records only what you thought to log, and that breaks quietly when somebody renames a property.

A CRM keeps this log for every deal without being asked. If your Monday review ever includes “when did this move to Negotiation?” and the honest answer is “I’d have to check with Tom”, mark it no.

## Check 3: can the manager see pipeline movement this week?

Not from Notion alone: a board view shows where each deal is now, not where it was last Monday. What a manager wants on Monday is which deals came in, which moved forward, which slipped back, which closed, and which didn’t move at all over the last seven days. That is a movement report, and it is built from exactly the stage history that check 2 found missing. Filtering on `Last edited time` for the past week doesn’t replace it, since a rep fixing a typo in a company name counts as “movement” while a deal quietly moved back on Tuesday and forward again on Thursday looks like it never left. The best you get without a changelog is a snapshot: a chart by status today next to a screenshot of the same chart from last week, compared by eye. Some teams run exactly that, and it works until there are more deals than anyone can hold in their head between two screenshots.

We think this check decides whether Notion is a pipeline or a to-do list with columns. So ask your manager to name, from Notion alone, the deals that moved back last week. If she can’t, it’s a no.

## Check 4: can you limit who sees which deals?

Partly, and it costs you. On a database page Notion offers Full access, Can edit, Can edit content, Can comment and Can view, plus Can create on the Business and Enterprise plans ( [Notion: sharing and permissions](https://www.notion.com/help/sharing-and-permissions)). These apply to the database as a whole. Give a rep Can edit content and he can edit every deal in it, including the ones that aren’t his.

Row-level rules exist, with conditions. If the database has a `Person` property, you can grant permissions to the people in it, so the owner of a deal gets access to that deal. This is set on the source database, applies across all its views, and needs the Business or Enterprise plan (same help page). Two catches. Notion respects the broadest level of access a user has, so a workspace-wide grant quietly overrides your narrower rule. And automations won’t act on pages whose access is restricted ( [Notion: database automations](https://www.notion.com/help/database-automations)), which means the home-made changelog from check 2 stops on the very deals you locked down.

For three founders none of this matters. It matters the day you hire a rep on commission who shouldn’t see the the house accounts. If your answer to “can Tom see Maria’s deals?” is “yes, and we trust him”, that is a culture answer, not a permissions answer. Write no.

## Check 5: do emails and calls land in the deal on their own?

No. The Notion CRM guide keeps an `Email` and a `Phone` property on the client record and suggests you “create a new entry every time you have a call or meeting” ( [Notion: a simple CRM](https://www.notion.com/help/guides/simple-crm-for-strengthening-client-relationships-and-managing-work)). Create. By hand. The automation that touches email is “Send mail to”, which sends from your Gmail account ( [Notion: database automations](https://www.notion.com/help/database-automations)); nothing in the help pages we read brings the reply back onto the record.

This check sets the data quality of the other four. A deal with no logged email in three weeks is a useful question for a manager. A deal with no logged email because logging is a chore tells her nothing. In Notion every call note is an act of goodwill, and goodwill runs out on a Friday afternoon. A CRM with mail and calendar sync won’t fix lazy notes, but it puts the thread and the meeting on teh deal, and the gap between them becomes visible. That gap is what you manage. Ask your reps how many of last week’s customer emails exist in Notion. If the answer involves a laugh, mark it no.

## Scored two or more “no”? Keep the move small

Count them. Past two reps it is rarely just two, and that isn’t a criticism of Notion. It is a workspace that can hold a database; a CRM is a database built around a deal.

We’d advise against rebuilding the missing pieces with automations and formula warnings. That road ends in a system only its author understands, and authors leave. Plan the move instead, and keep it small.

- Export the database to CSV (Notion exports a full-page database as a CSV file, see [Notion: export your content](https://www.notion.com/help/export-your-content) ), remove duplicates, and keep only the fields you read every week: owner, amount, stage, expected close date, next step with a date, lead source. The longer list and the first three views to build are in [tracking sales in a CRM instead of a spreadsheet](https://salesbond.app/blog/crm-sales-tracking-from-spreadsheet/).
- Write one sentence per stage before you import, then set the required fields that prove it. Nobody argues about definitions during a move.
- Leave meeting notes behind as attachments or links. What belongs in a record at all is covered in [what to store in a CRM database](https://salesbond.app/blog/crm-database-what-to-store-sales-team/).
- Expect the first month to be about habits, not features ( [CRM adoption for small teams](https://salesbond.app/blog/crm-adoption/) ).

Pipedrive, HubSpot, Salesforce and Zoho CRM each pass the five checks in their own way, and which one fits depends on your team and what else you run. A disclosure, since this is where it belongs: we build SalesBond, a sales management layer on top of the CRM a team already uses; we started with Pipedrive. It works with Pipedrive, HubSpot, Salesforce and Zoho CRM, analyses the deal data there and explains which deals need attention and why. Notion isn’t on that list, for the same five reasons. Once you’ve moved, [check your CRM with SalesBond](https://salesbond.app/).

Before any of that, run check 1 this afternoon: drag one card two stages forward with every field empty. If it lands, put the first no on the scorecard and take the other four questions to your next pipeline review, where the person who reads the pipeline can answer them.