A useful CRM answers three questions quickly: Who are you talking to? Where does the opportunity stand? What happens next?
You can build a first version in Notion with two databases and two views. Start there. Add company records, activity history, or a larger Business OS only when your sales process actually needs them.
The setup below keeps people in Contacts and opportunities in Deals. Connecting them lets you open a deal and find the relevant person without copying their details into every record.
This is different from a contact list, which stores names but may not show what to do next. It is also smaller than a Business OS, which may bring sales, client delivery, and other operations into one workspace. If you want to compare ready-made options rather than build, see our Notion sales pipeline and CRM template guide.
Before creating properties, write down the stages an opportunity actually moves through. A lean service-business pipeline might be:
New lead → Conversation → Proposal → Won or Lost
Use your own language. You may not send proposals, or you may need a distinct “Waiting for reply” stage. Add a stage only when it tells you something useful about what happens next.
For example, a web designer might create a deal called “Acme website redesign.” The deal is in Proposal, its next action is “Check in about the estimate,” and its follow-up date is next Tuesday. That is enough information to make the pipeline actionable.
Create a database called Contacts. Start with:
Name: The person’s name.
Email or preferred contact method: How you reach them.
Status: For example, Lead, Client, or Past Client.
Company: Optional plain-text field if you need it.
Keep notes on a contact’s page if you need a little context. Do not create a separate Companies database just because a CRM diagram shows one. Add it later if several contacts belong to the same organization and you need to manage that relationship.
Create a database called Deals with these properties:
Deal name: A specific opportunity, such as “Acme website redesign.”
Stage: Your pipeline stage.
Contact: A Relation property pointing to Contacts.
Next action: The next concrete step.
Follow-up date: When you will take that step.
Value: Optional, if deal size helps you prioritize.
In Notion, add a property to Deals, choose Relation, and select the Contacts database. When entering a deal, select the relevant contact. If you want to see linked deals on each contact’s page, enable the two-way relation.
A relation connects the records; it does not automatically write your follow-up or advance the deal. Those still need a process you will use.
Make a Board view of Deals grouped by Stage. Show open opportunities and hide Won and Lost deals from this working view. The board should tell you where your current conversations stand.
Make a second Deals view filtered to show open deals with a Follow-up date on or before today. Display the contact, next action, and date. This is the view to check when you start sales work.
A filtered view does not send a notification by itself. If you need a Notion notification for a particular follow-up, set a reminder on that deal’s date property and check that it behaves as expected. If you need automated emails or sequences, verify a separate tool or automation setup rather than assuming the template provides one.
The setup works only if you update it after real conversations. After a call or reply, take a moment to:
Change the deal stage if it moved.
Write one clear next action.
Set or revise the follow-up date.
Add a short note if you will need context later.
Then review the Follow-ups due view on the days you handle sales. Check the pipeline regularly for deals that are open but have no next action or follow-up date; those are easy to forget.
Once the first version is working, a few additions may earn their place:
Companies database: Useful when multiple contacts and deals belong to the same organization.
Activities database: Useful when you need a searchable history of calls, emails, and meetings. Link activity records to Contacts or Deals.
Projects database: Useful when a won deal turns into client delivery. Connect the project to its originating deal so the agreement is easy to find.
None of these connections automatically creates a project, sends an invoice, or emails a prospect. If those handoffs matter, document the manual step first; add automation only after you have verified how it will work.
A ready-made CRM can save configuration time if its included fields and views match your process. Compare its entry tier and setup instructions, then try a real deal in the preview if one is available. You can inspect the SalesHub CRM Dashboard as a focused option or browse Business & Agencies dashboards for broader systems.
If your business needs sales and delivery work in the same place, read Business OS vs Life OS in Notion before adopting a larger workspace. Solopreneurs & Startups is another place to browse systems by business workflow.
Notion may be too lightweight if you depend on high-volume email sequences, specialized sales reporting, complex permissions, or deep integrations. Write down those requirements before moving an established process into a template.
Open your CRM and try these five actions:
Add a new contact.
Add a deal and link it to that contact.
Move the deal to its current stage.
Record the next action and follow-up date.
Find that deal in your Follow-ups due view when the date arrives.
If those steps are easy, use the CRM before making it more elaborate. The best first version is the one you will still update after a busy day.
Explore curated dashboards by workflow and system scale.
© OS Dashboard HQ 2026. All rights reserved