Notion · Build Guide

How to build a Notion CRM your team will actually use

Most Notion CRMs die in week two. This is the architecture that survives: four linked databases, five views, one weekly ritual.

By Ishan Vats, Founder of IV Consulting. Certified Notion + ClickUp Consultant, Claude Partner Network, PMP®. 150+ ops transformations.

May 2026 11 min read Pillar: Scaling Without Chaos

Some links below are affiliate links. If you buy through them we may earn a commission, at no extra cost to you.

Notion 4 databases 5 views 15 min weekly ritual
Notion CRM · Live
Notion logo Hub · Notion4 linked databases
Slack logo SlackNew lead ping
Make logo MakeStale deal alert
Pipedrive logo PipedriveIf you outgrow it
7 inactive leadssurfaced, 3 reconverted
Quick answer

A Notion CRM works when it is built around how your team already works, not around what Notion can do. You need four linked databases (Contacts, Companies, Deals, Activities), a pipeline board your team opens every morning, and a 15 minute weekly review ritual. Skip any one of those three things and your CRM becomes a ghost town within a month.

01

Why 80% of Notion CRMs die in week two

You built one before. Maybe it was in Notion. Maybe it was a spreadsheet that grew too complex, or a CRM tool that cost too much and got used by nobody. You put in the work: the columns, the tags, the pipeline stages. You showed the team. Everyone nodded.

Two weeks later, half the contacts were missing their last-touch date. Four deals had been stuck in Proposal Sent for six weeks. And when you asked the team why they stopped updating it, the answer was always some version of the same thing: it takes too long, or I was not sure what to fill in.

The cause is almost never Notion itself. It is one of four structural mistakes.

Mistake 1: too many fields

The builder adds every field they can imagine: industry, company size, lead source, referral partner, deal value, close probability, next action, last contact, and a dozen others. The team opens a contact record, sees 22 empty fields, closes it, and goes back to their inbox. A usable CRM has fewer than 10 fields per database. Every field not checked weekly should be removed or moved to a secondary view.

Mistake 2: no clear update trigger

In a well-run CRM the team knows exactly when to open it: after a call, after sending a proposal, after a deal closes. With no trigger, updating the CRM becomes optional. Optional means it does not happen.

Mistake 3: built for the founder, not the team

The person who builds the CRM is usually the most organised person in the room. They design it for how they would use it, not for how a sales rep, an account manager, or a freelance contractor with three other clients would use it. The result is a system that only makes sense if you built it.

Mistake 4: no maintenance ritual

Even a perfectly built CRM degrades without a weekly review. Contacts go stale. Deals sit in the wrong stage. Without a 15 minute weekly ritual baked into someone's calendar, entropy wins every time.

Before you build Ask this first. Can your team answer these three questions without opening any CRM? Who are the five warmest leads right now? Which client has not been contacted in over 30 days? What is the total pipeline value this month? If they cannot answer those in under 60 seconds, you need a CRM. Those three answers should also be the first things your Notion CRM surfaces.
02

The four databases your Notion CRM needs

A functional Notion CRM is not one database. It is four linked databases that talk to each other. The connections are what make it intelligent.

Database What it stores Why it exists separately
ContactsIndividual people: leads, clients, prospects, partnersThe core record every other database links back to
CompaniesOrganisations those people belong toCritical for B2B: the account relationship outlives any one contact
DealsActive opportunities with stage, value, and close dateYour pipeline, built for speed of update and scanning
ActivitiesEvery logged interaction: calls, emails, meetings, proposalsThe history that stops the CRM feeling hollow after a few weeks

The reason these are four separate databases rather than one big spreadsheet is relations. When a Deal links to a Contact, and that Contact links to a Company, you can answer questions like show me all open deals where the last activity was more than 14 days ago, in one filtered view, in three seconds. You cannot do that in a spreadsheet.

Think of it this way: a spreadsheet is a flat filing cabinet where every drawer is independent. A relational database is an org chart. Every person knows who they report to, which team they are on, and which projects they own. The CRM only becomes intelligent when the connections exist.

IV Consulting take The connection map is the part most guides skip. Add a relation from Contacts to Companies, Contacts to Deals, and Deals to Activities. Then add two rollups on Companies: a count of linked Contacts and a sum of Deal Value. The moment a sales rep can open one Company record and see every contact, every open deal, the total pipeline value, and the most recent activity date on one screen, Notion stops feeling like a glorified spreadsheet. If you want this built and handed over, that is exactly what our Foundation stage does.
03

Your week-by-week build order

Do not try to build all four databases in one afternoon. Build in order, validate each layer, then add the next. The pace matches the team's readiness to adopt it.

1

Week 1: Contacts and Companies

Start with Contacts. Keep it to ten fields, no more: Full Name, Company (relation), Role, Email, Phone, Lead Status, Owner, Last Activity Date, Linked Deals, and a lightweight Notes field. Full history lives in Activities later; Notes here is just context.

For B2B teams, the Companies database is non-negotiable. When a contact leaves their company you still hold the account relationship, and when a new contact joins you can link them without rebuilding context. Add Industry, Company Size, Account Status, Account Owner, a Contacts rollup, a Total Deal Value rollup, and Website. Import your existing contacts and set up the Needs Follow-Up view immediately.

IV Consulting tip Build a Needs Follow-Up filtered view on Contacts on day one. Filter: Lead Status is Lead or Active, and Last Activity Date is more than 14 days ago. This is the first thing your team checks every Monday. If names appear in it, someone makes contact today.
2

Week 2: Deals (your pipeline)

The Deals database is the one your team looks at most, so build it for speed. Fields: Deal Name, Contact, Company, Stage, Deal Value, Expected Close Date, Deal Owner, Probability, Last Activity Date, and Close Reason.

Create a Board view grouped by Stage, filtered to hide Closed Won and Closed Lost, sorted by Expected Close Date ascending, with Deal Value, Contact, and Last Activity Date shown on each card. This is the pipeline board your team opens every morning. Add a Table view sorted by Last Activity Date ascending to surface deals that have gone quiet.

3

Week 3: Activities (the log everyone skips)

The Activities database is why most Notion CRMs feel hollow after a few weeks. Without a proper log you have a snapshot of current state and no context about how you got there. Log every meaningful touchpoint: calls, emails, meetings, proposals, check-ins. Two to three sentences is enough.

Fields: Activity Title, Type, Date, Contact, Deal, Owner, Summary, and Next Step. The Next Step field is the most important in the whole CRM. Not follow up, which means nothing, but Send revised proposal to James by Thursday. Specific, owned, dated. Build a Notion template with Summary and Next Step pre-populated so reps know exactly what to fill in.

IV Consulting tip Friction removal is the single highest-leverage thing you can do for CRM adoption. A template that opens with the right prompts removes the I was not sure what to fill in excuse entirely.
4

Week 4: Connect relations and rollups

Now wire the four databases together. Contacts links to Companies, Deals, and Activities. Companies gets a rollup counting linked Contacts and a rollup summing Deal Value. Deals links to Activities and gets a rollup for the date of the most recent Activity.

Once these exist, set up the five standard views and formalise the 15 minute Monday ritual in the team calendar. From Week 5, evaluate what is working, prune any fields nobody is filling, and only then consider adding automation.

04

The five views your team will actually use

Databases are the infrastructure. Views are the interface. Most Notion CRMs have too many views, which creates decision paralysis. These five each answer one question at one moment in the week.

1. My Deals Pipeline

Board view, filtered to Owner is Me, grouped by Stage. This is the view that opens every morning. It is the single screen a rep needs during a weekly pipeline review: what is mine, where is it, and what moves next.

2. Deals Gone Cold

Table view on Deals, filter: Last Activity Date more than 14 days ago, Stage not Closed. Opens every Monday. The deals quietly dying get pulled into the light.

3. Contacts to Follow Up

Filter on Contacts: Status is Lead or Active, Last Activity Date more than 14 days ago. Opens every Monday. A name here is a reminder, not a failure.

4. This Week's Activities

Gallery or table view on Activities, filter: Date is this week. Used during the team standup so everyone sees what actually happened, not what was promised.

5. All Active Clients

Filter on Companies: Account Status is Active Client. Used for account health checks, so no client is two years deep and still getting cold outreach from a junior rep.

05

The 15 minute weekly maintenance ritual

Building the CRM is the easy part. What makes it survive the first month is a 15 minute Monday morning ritual that becomes as non-negotiable as the team standup. Put it in the calendar, recurring, every Monday at 9am.

  • Minutes 1 to 3. Open Deals Gone Cold. For every deal idle more than 14 days, either log a planned outreach activity or move it to Closed Lost if it is genuinely dead. No deal stays active without a logged next step.
  • Minutes 4 to 6. Open Contacts to Follow Up. For every contact with no activity in 14+ days, log a planned touchpoint or change their status to Dormant. A dormant contact is an honest data point, not a failure.
  • Minutes 7 to 10. Review the pipeline board. Check expected close dates, flag anything overdue, update the stage on any deal that moved since last Monday.
  • Minutes 11 to 13. Log any activities from last week that were not entered in real time. The Monday catch-up is the safety net.
  • Minutes 14 to 15. Identify the top three priority actions for the week, note them in the standup doc, and leave the CRM.
The 15 minute rule If your Monday review takes longer than 15 minutes, the CRM has too much complexity or too little discipline. The fix is always one of two things: remove a database nobody maintains, or make the update ritual more specific. A long review is a signal, not a badge of thoroughness.

Automation: the three things worth building (later)

Once the manual ritual is stable, three automations pay immediate dividends. A new lead notification to the assigned owner via Make or Zapier, because response speed is one of the highest-impact variables in sales conversion. A deal stage change alert to the team channel when a deal moves to Closed Won, because visible wins build adoption. And a weekly stale deal reminder that filters Deals idle more than 10 days and emails the owner every Friday.

IV Consulting take Do not automate before you have manually validated the workflow for at least four weeks. Automation locks in whatever behaviour exists when you build it. If your team is still working out how they actually use the CRM, automating too early encodes the wrong habits. Build the ritual first. Automate second.
06

When Notion is not the right CRM

There are scenarios where Notion is a genuinely poor CRM choice, and it is worth being honest about them before you invest time building.

  • More than 5,000 contacts. Notion databases get sluggish at scale. Load time and filter performance will frustrate the team. Consider HubSpot Free or Pipedrive at that volume.
  • You need deep email integration. Notion does not natively log emails or sync with Gmail or Outlook. If email is the primary channel and the team expects automatic tracking, the manual input will not be sustainable.
  • A sales team larger than 8 people. Quota tracking, forecasting, and rep performance reporting go beyond what Notion's rollups handle cleanly. A dedicated CRM serves you better.
  • You need two-way calendar sync. Notion does not natively sync meetings to Google Calendar or Outlook. If automatic meeting logging matters, this gap becomes a daily frustration.
Honest verdict Notion CRM is ideal for teams of 2 to 8 people, with up to 2,000 contacts, whose sales motion is high-touch relationship management rather than high-volume outbound. For consulting firms, agencies, boutique service businesses, and early-stage startups, it is genuinely excellent. For anything with volume, velocity, or a large sales team, use a purpose-built CRM and let Notion handle your knowledge base and project delivery instead.

A real example of what this looks like when it works

One IV Consulting client, a six-person operations consulting firm, came to us with a spreadsheet three people used and three people ignored. Deals fell through the gaps. A client they had served for two years got a cold outreach email from a junior team member who did not know the relationship existed. That was the moment they knew something had to change.

We built them this exact architecture: four databases, five views, the 15 minute Monday ritual, two automations. In the first four weeks, they surfaced seven prospects inactive for over 60 days, three of whom reconverted to clients that quarter after a re-engagement sequence. The team stopped asking each other where are we with that company in Slack. And the founder went from 45 minutes preparing the Friday pipeline review to 10 minutes walking the board. The CRM did not replace human judgment. It made the judgment faster, better-informed, and more consistent.

07

Questions people ask before they build

How many databases does a Notion CRM need?
A functional Notion CRM uses four linked databases: Contacts, Companies, Deals, and Activities. They are separate rather than one big spreadsheet because relations let you answer questions like show me all open deals with no activity in 14 days in three seconds. That is the moment Notion stops feeling like a spreadsheet and starts behaving like a real CRM.
Why do most Notion CRMs get abandoned?
Most Notion CRMs die in week two for one of four structural reasons: too many fields so nobody updates them, no clear trigger for when to log an entry, a system built for the founder instead of the team, and no weekly maintenance ritual. The cause is almost never Notion itself. It is architecture and habit.
What is the weekly Notion CRM maintenance ritual?
It is a recurring 15 minute Monday review. Open the Deals Gone Cold view and either log outreach or close dead deals, review Contacts to Follow Up, scan the pipeline board for overdue close dates, log any activities missed during the week, and note the top three priority actions. If the review takes longer than 15 minutes, the CRM has too much complexity or too little discipline.
How many fields should each Notion CRM database have?
Keep each database under 10 fields. A contact record with 22 empty fields is a record nobody updates. Every field that is not checked weekly should be removed or moved to a secondary view. Fewer fields means faster updates, which means the CRM actually gets used.
When is Notion the wrong choice for a CRM?
Notion CRM is ideal for teams of 2 to 8 people with up to 2,000 contacts doing high-touch relationship sales. Choose a purpose-built CRM instead if you have more than 5,000 contacts, need deep email integration, run a sales team larger than 8 people, or require two-way calendar sync. For consulting firms, agencies, and early-stage startups, Notion is genuinely excellent.
Should I automate my Notion CRM from day one?
No. Validate the manual workflow for at least four weeks first. Automation locks in whatever behaviour exists at the time you build it, so automating too early encodes the wrong habits. Once the ritual is stable, the three automations worth building are a new lead notification, a deal stage change alert, and a weekly stale deal reminder. Book a free strategy call and we will map the highest-ROI ones for your team.

Want your Notion CRM built for you?

Book a free 30-minute strategy call. We will audit your current setup, map the three changes that make the biggest difference, and give you a build roadmap on the spot. If we are not the right team for you, we will say so and point you somewhere better.

Book a Free Strategy Call →

Free 30-minute call. Honest take, even if that means "you do not need us yet."