Notion Business Templates: CRM, Projects and Operations
The most useful Notion business templates combine three systems: a CRM to win and manage clients, a project system to deliver the work, and an operations system for the processes, meetings and routines that keep the business running. When these three share connected databases, a won deal becomes a project, the project links to the client, and the team follows documented procedures, all without re-entering information.
This guide shows how a connected CRM, projects and operations template is structured: the databases and properties it needs, how the three systems link together, which automations are worth setting up, the dashboards each role should see, and how to roll it out without overwhelming your team.
Why CRM, Projects and Operations Belong Together
Most small businesses start with separate tools: a spreadsheet or app for leads, a task manager for delivery, and shared documents for procedures. The problems appear at the handoffs:
- Details agreed during the sale do not reach the people delivering the work.
- Nobody can see the full history of a client, including deals, projects and meetings, in one place.
- Procedures exist, but they are not linked to the tasks where people need them.
- Owners assemble status updates by asking around rather than opening one view.
A connected Notion business template solves this by giving every client, deal, project and procedure a single record, then linking those records with relations. The same information appears wherever it is needed, instead of being copied.
The Data Model: How the Three Systems Connect
A solid CRM, projects and operations template usually needs seven core databases. Each database should hold one kind of thing, and relations connect them.
| Database | System | Holds | Relates to |
| Companies | CRM | Client and prospect organisations | Contacts, Deals, Projects, Meetings |
| Contacts | CRM | Individual people | Companies, Deals, Meetings |
| Deals | CRM | Sales opportunities | Companies, Contacts, Projects |
| Projects | Projects | Work being delivered | Companies, Deals, Tasks, Meetings |
| Tasks | Projects | Individual pieces of work | Projects, SOPs |
| SOPs | Operations | Documented procedures | Tasks |
| Meetings | Operations | Meeting notes, decisions and action items | Companies, Projects |
Read the chain from left to right: a Company has Deals; a won Deal becomes a Project; a Project contains Tasks; Tasks link to the SOPs that explain how to do them; and Meetings attach to the company or project they concern. Rollups then carry numbers back up the chain, such as task progress on each project or total deal value on each company.
The CRM Template
Key Properties
| Database | Essential properties |
| Companies | Name, Industry, Status (prospect, active client, past client), Account owner, Total deal value (rollup), Active projects (rollup) |
| Contacts | Name, Company (relation), Role, Email, Phone, Last contacted |
| Deals | Deal name, Company (relation), Primary contact (relation), Stage, Value, Expected close date, Owner, Next action, Next follow-up date, Project (relation) |
Pipeline Stages
Keep stages few and clearly defined, so everyone moves deals at the same point. A practical default is: Lead, Qualified, Proposal sent, Negotiation, Won and Lost. Add a Lost reason property to learn why deals do not close.
Views to Include
- Pipeline board grouped by stage, showing value and owner.
- Follow-ups due filtered to deals with a next follow-up date this week.
- My deals filtered to the person viewing.
- Won this quarter for a quick revenue check.
The Projects Template
Key Properties
| Database | Essential properties |
| Projects | Project name, Company (relation), Deal (relation), Status, Project lead, Start date, Due date, Budget or fee, Progress (rollup from Tasks), Open tasks (rollup) |
| Tasks | Task name, Project (relation), Assignee, Due date, Priority, Status, Related SOP (relation), Estimated time |
Views to Include
- Active projects board grouped by status.
- Timeline for scheduling and spotting overlaps.
- My tasks filtered to the current user and sorted by due date.
- Overdue tasks for project leads.
A Project Kickoff Template
Set up a database template in Projects that includes a kickoff checklist, scope summary, key contacts and a linked view of the project’s tasks. Set it as the default, so every new project starts the same way, whether it was created manually or from a won deal.
The Operations Template
Operations covers the recurring, behind-the-scenes work that keeps delivery consistent: procedures, meetings and routines.
| Database | Essential properties |
| SOPs | Title, Department, Owner, Status (draft, approved, needs update), Last reviewed, Related tasks (relation) |
| Meetings | Title, Date, Type (internal, client, review), Company (relation), Project (relation), Attendees, Decisions, Action items |
Two operational routines work particularly well in Notion:
- A weekly operations review created by a repeating database template in Meetings, with sections for pipeline, active projects, blockers and priorities.
- An SOP review cycle using a “Needs review” view that filters SOPs whose last review date is older than your chosen interval.
Linking tasks to SOPs is the step most templates skip. When a recurring task, such as onboarding a new client, links to its procedure, team members can follow the process without asking.
Connecting the Workflow: From Won Deal to Delivered Project
The handoff from sales to delivery is where a connected template earns its value. A typical flow looks like this:
- A deal moves to Won in the CRM.
- A new project is created, related to the deal and the company, using the kickoff template.
- The project lead and team are notified.
- Standard tasks are added and linked to the relevant SOPs.
- A kickoff meeting is logged in Meetings and related to the project.
- The company’s status changes to Active client, and its page now shows the deal, project and meetings together.
Automations Worth Setting Up
Notion database automations run when a page is added, when a property is edited, or on a recurring schedule. These are the most useful ones for this template:
| Database | Trigger | Action | Purpose |
| Deals | Stage set to Won | Add page to Projects, with the deal and company related | Starts delivery without re-typing details |
| Deals | Stage set to Won | Send notification to the project lead | Makes the handoff visible |
| Projects | Page added | Send notification to the project lead | Confirms new work has arrived (runs for projects created manually or by a button, not by another automation) |
| Tasks | Status set to Done | Edit property (for example, set a Completed date) | Keeps records accurate |
| Companies | Every week | Send notification to account owners | Prompts regular account reviews |
Automation Limits to Plan Around
- Plan requirements: database automations can be created and edited on paid plans. Free Plan users can create Slack notification automations only, and can use but not edit automations that come with a template.
- Automations cannot trigger other automations. If a Deal automation creates a Project, that new project will not trigger a Projects automation. A button clicked by a person, however, can trigger database automations.
- Restricted pages are skipped. Automations will not act on pages whose access is restricted, so check sharing settings on the databases involved.
- Guests cannot create automations, even with full access to a database.
Practical tip: if you want the new project to trigger its own automations, such as creating standard tasks, use a “Convert to project” button on the deal instead of a fully automatic handoff. Because a person clicks the button, downstream automations in the Projects database still run.
Dashboards for Each Role
A connected template lets each person start from a page built around their responsibilities, using linked views of the same databases.
| Role | What their dashboard shows |
| Owner or manager | Pipeline value by stage, active projects by status, overdue tasks, SOPs needing review, this week’s meetings |
| Sales or account manager | My deals, follow-ups due, recently won deals, my client companies |
| Project lead | My projects, overdue and upcoming tasks, recent client meetings |
| Team member | My tasks due this week, linked SOPs, upcoming meetings |
How to Roll Out the Template in Stages
Introducing all three systems at once is the most common reason business templates fail. A staged rollout gives each part time to become a habit.
| Stage | Focus | Done when |
| 1. Projects and Tasks | Move all active work into Notion | The team checks “My tasks” daily instead of other tools |
| 2. CRM | Import companies, contacts and open deals | Every open deal has a next follow-up date |
| 3. Connect | Relate deals to projects and add the handoff button or automation | New projects start from won deals |
| 4. Operations | Add SOPs for the most repeated tasks, and the weekly review | The weekly review runs from Notion |
| 5. Dashboards | Build role-based home pages | People start their day from their dashboard |
Assign one owner for the whole system. That person approves new properties, keeps naming consistent and prevents duplicate databases from appearing.
When the System Outgrows Notion
Notion handles CRM, projects and operations well for many small and mid-sized teams. Consider additional tools when you need high-volume sales automation (a dedicated CRM platform), invoicing, inventory or accounting tied to operations (an ERP solution), or reporting that combines Notion data with finance and sales data (Power BI dashboards). Notion can remain the place where work is planned and documented while those systems handle transactions and analysis.
Get a Connected Notion Business System
Pentium Solutions builds connected Notion business systems for CRM, projects and operations, along with ready-to-use templates and digital products. Where a process needs more than Notion, Pentium also develops Power BI dashboards, spreadsheets, business apps and ERP solutions.
Frequently Asked Questions
Can one Notion template handle CRM, projects and operations?
Yes, if it uses connected databases. A good template relates companies, deals, projects, tasks, SOPs and meetings, so information flows between them rather than being copied.
How do I connect my Notion CRM to my projects?
Add a relation property between your Deals and Projects databases. When a deal is won, create a project and relate it to the deal and company, either manually, with a button, or with a database automation.
Can Notion automatically create a project when a deal is won?
Yes, on paid plans. A database automation triggered when the deal stage is set to Won can add a page to your Projects database. Note that a page created by an automation will not trigger further automations; a button clicked by a person will.
What is a Notion operations template?
It is a system for the recurring work behind delivery, typically SOPs, meeting notes, decision logs and routines such as a weekly operations review.
Should I set up the CRM or the project system first?
For most teams, start with projects and tasks, because they are used daily. Add the CRM next, then connect the two and add operations.
Is a Notion CRM good enough for a small business?
For relationship-based sales with a manageable number of deals, yes. Teams that need email sequences, call tracking or advanced forecasting usually need a dedicated CRM platform.