Loading tutorials…
Loading tutorials…
Monday Sales CRM is fast to spin up and easy to wire wrong. Pipeline stages drift, contact data fragments across boards, and reports stop making sense within 90 days. This walks the configuration that holds up past the first quarter.
Who this is forFounders, sales ops, and SDR leads setting up Monday Sales CRM for the first time — or anyone running a DIY CRM template who is about to add their first 5 reps. If your current setup has deals living on a generic 'project' board instead of the Sales CRM template, this tutorial is the rebuild path.
What you'll need
Step 1
Monday → My work → + Add new board → From template → CRM → Sales CRM. The template ships with Deals, Contacts, Accounts, and Leads boards pre-wired.
Open Monday → My work → + Add new board → Choose template → CRM category → "Sales CRM."
The template creates a dedicated workspace with 4 connected boards: Leads (top-of-funnel), Contacts (people), Accounts (companies), and Deals (pipeline).
Connections between boards are pre-wired: a Deal links to a Contact links to an Account. This is the key benefit of the template — building these connections manually takes 2-3 hours and is easy to get wrong.
Don't be tempted to 'simplify' by combining boards. Sales CRMs need separate objects for People, Companies, and Deals because a person can be at multiple companies over time, and an account can have multiple deals.
Rename the boards if needed (e.g., "Deals" → "Pipeline — North America") but keep the structure.
Step 2
The Status column on the Deals board is your pipeline. Lock the stages, the colors, and the definitions before any data goes in.
Open the Deals board → Status column header → Edit Labels.
Define 5-7 stages mapped to your real sales motion. Common B2B SaaS template: New Lead → Qualified → Discovery → Demo → Proposal → Negotiation → Closed Won / Closed Lost.
Assign a color to each stage. Convention: blue/grey early stages, yellow mid-funnel, green Won, red Lost.
Write a 1-sentence definition of each stage in a "Pipeline Definitions" Monday Doc. "Qualified" should mean the same thing to every rep — usually a checklist (budget confirmed, decision-maker identified, timeline known).
Add a "Closed Lost Reason" Dropdown column. Without this, you cannot answer "why are we losing deals?" — and that question is worth more than the CRM itself.
Step 3
Contacts are people, Accounts are companies. Set the columns that make reps productive on day one.
Open the Contacts board. Add columns: First Name, Last Name, Email, Phone, Job Title, LinkedIn (Link column), Owner (Person), Lifecycle Stage (Status: Lead/MQL/SQL/Customer/Churned), Last Activity Date, Account (Connect Boards → Accounts).
Open the Accounts board. Add columns: Company Name, Domain (Text), Industry (Dropdown), Employee Count (Numbers), Annual Revenue (Numbers, currency formatted), Owner (Person), Lifecycle Stage, Account Type (Dropdown: Prospect / Customer / Partner / Churned).
Set up the Connect Boards → Mirror columns: on Deals, mirror Account.Industry and Account.Employee Count so reps see context without opening the linked record. Mirror columns are read-only by design.
On Contacts, set up the Mirror to show the parent Account.Owner — useful when a contact moves companies.
Step 4
Calls, emails, meetings, and notes need a place to live. The template includes an Activities board — wire it correctly.
Open the Activities board (or create one if your template did not include it).
Columns: Activity Type (Dropdown: Call / Email / Meeting / Note / Task), Subject (Text), Date (Date), Owner (Person), Outcome (Status: Connected / No Answer / Voicemail / Booked / Cancelled), Related Deal (Connect Boards → Deals), Related Contact (Connect Boards → Contacts).
On Deals, add a Mirror column showing the count of Activities → useful for the "show me deals with no activity in 30 days" view.
Train reps to log every activity at the time it happens — not at end of week. End-of-week logging is the #1 source of unreliable CRM data and costs an average of $15-30K/yr per rep in mis-forecasted pipeline.
Step 5
Rep adoption depends on views that match how reps actually work. Build 4-5 default views before inviting the team.
On Deals board, build: (a) Kanban by Status — the daily-driver pipeline view, (b) Main Table filtered by "Owner = me" — the rep's personal pipeline, (c) Table grouped by Close Date month — for forecasting, (d) Dashboard view (built in tutorial 4) — for managers.
On Contacts board, build: (a) Main Table sorted by Last Activity Date ascending — surfaces neglected contacts, (b) Filtered by "Owner = me," (c) Filtered by "Lifecycle Stage = MQL or SQL."
On Activities, build: (a) Calendar view by Date — shows the week ahead, (b) Filtered by "Owner = me" and "Date = this week" — the rep's daily call list.
Save views at the board level (visible to all members) versus user level (your own). Be deliberate about which is which.
Step 6
CSV imports go in this order: Accounts → Contacts → Deals → Activities. Reverse order breaks Connect Boards relationships.
Export from your existing CRM (HubSpot, Pipedrive, Salesforce, spreadsheet) as CSV. Clean the CSV first — Monday will faithfully import garbage.
On the Accounts board → Import → CSV. Map columns carefully. Verify a sample of 10 rows before confirming the full import.
On Contacts board → Import → CSV. The "Account" column needs to match exactly an Account name that already exists, or the Connect Boards link will not form.
On Deals board → Import → CSV. Similarly, Account and Primary Contact columns must reference existing records.
On Activities → Import → CSV last. Related Deal and Related Contact must reference existing records.
Run a post-import audit: spot-check 20 deals for missing accounts, missing contacts, wrong owners. Fix immediately. Bad data on day one is bad data on day 365.
Step 7
Sales reps need full edit on Deals/Contacts they own, read on team data, no edit on board structure.
Account → Administration → Users → Invite users. Add reps as Members (paid seats).
Workspace permissions → Sales CRM workspace → set to Closed → invite only reps + sales manager + admin.
Board permissions on each Sales CRM board: enable "Item-level permissions" so reps can only edit deals/contacts they own. Set on the board → Board settings → Permissions → Item-level → "Owner can edit, others can view."
Sales manager should be a Member with edit on all items (no item-level restriction).
Audit access by logging in as a test rep and confirming they see what they should and cannot break what they should not.
Common mistakes
Building a "CRM" on a single generic board
What goes wrong: Deals, contacts, companies, and activities all pile onto one board with conflicting columns. Within 90 days you cannot run pipeline by account, by industry, or by source. Forecasting is guesswork — a missed quarter worth $50K-200K in lost predictability.
How to avoid: Use the Sales CRM template with separate Accounts / Contacts / Deals / Activities boards connected via Connect Boards columns.
Letting reps create their own pipeline stages
What goes wrong: Within 6 weeks you have 18 stages across 4 reps — half are synonyms, none roll up. Forecast accuracy drops below 40% and the leadership team loses trust in CRM data entirely. Average cost: a quarter of bad hiring/spending decisions worth $30-100K.
How to avoid: Define 5-7 stages centrally, lock the Status column, and document each stage in a Monday Doc. Sales manager controls stage changes via permissions if needed.
No Closed Lost Reason column
What goes wrong: You lose 30% of deals and have no idea why. Marketing keeps generating leads in the wrong segment, sales keeps repeating the same objections, and product never hears about the recurring 'missing feature' that costs $200K+/yr in lost ARR.
How to avoid: Add a Closed Lost Reason Dropdown column on Deals (Budget / Timing / Competitor / Feature gap / No decision / Other). Require it before moving a deal to Closed Lost via a Required Field automation.
Importing data without standardizing keys first
What goes wrong: CSV has 'Acme Corp,' 'Acme Corporation,' 'Acme,' and 'acme corp.' all as different account names. Deals do not roll up to a single account. Reps duplicate outreach to the same company. Estimated waste: $10-30K/yr per 5 reps from duplicate effort and confused prospects.
How to avoid: Standardize keys in the CSV (Excel/Google Sheets) before import. Use a Find-Duplicates pass. Match Connect Boards keys exactly to existing record names.
No activity-logging discipline
What goes wrong: Reps log activities at end of week from memory. Last Activity Date is wrong, follow-up cadences break, and pipeline reviews work from fiction. Mis-forecasted pipeline costs $15-30K/yr per rep in the wrong hiring/spending bets.
How to avoid: Log activities in real-time (Activity board + email sync). Use automations to require an activity log when a deal moves stages. Manager runs a weekly "no activity in 14 days" view.
Inviting marketing and CS as Members on the Sales CRM workspace
What goes wrong: Marketing edits deals 'to help,' CS updates Lifecycle Stage on contacts they touch, and your single source of truth becomes a multi-author document with no audit. ~$20K/yr in lost rep productivity reconciling 'who changed this?'
How to avoid: Sales CRM workspace = Closed. Marketing and CS get Viewer access only, or are invited as Members to specific boards they own (not the whole workspace).
Recap
Done — what's next
How to set up a Monday.com workspace without painting yourself into a corner
Read the next tutorial
Hand it off
A Monday Sales CRM holds 12-36 months of pipeline data — every setup decision compounds. A specialist will set up the template, define stages, configure Connect Boards, migrate data, and train your reps in 4-8 hours. One-shot engagements typically $300-600; ongoing CRM ops support runs $400-1,200/mo at $14-16/hr.
See specialist rates
Standard tier has the Sales CRM template and Connect Boards — enough for most teams under 10 reps. Monday Sales CRM tier ($12-15/user/mo) adds email integration, mass sending, and call logging from inside Monday. If you live in your inbox and want native email sync, Sales CRM tier is worth it. Otherwise Standard works.
HubSpot CRM is purpose-built for sales + marketing + service workflows with deeper email tooling, sequences, and reporting. Monday Sales CRM is more flexible (you can customize columns freely) but shallower (sequences and email-tracking are less mature). Pick HubSpot if you want a sales-first system. Pick Monday if your team already uses Monday for project management and you want CRM in the same tool.
Use Subitems for deal-related tasks (call back on Tuesday, send proposal by Friday, follow up with legal). Avoid subitems for line items / products on the deal — those belong on a Quotes or Line Items board connected to the deal.
Yes. Two clean patterns: (1) One Deals board with a 'Pipeline' Dropdown column (New Business / Renewal / Upsell) and use board views to filter — simpler. (2) Separate Deals boards per pipeline — more isolation but harder to report cross-pipeline. Most teams under 20 reps go with (1).
Deals board has a Connect Boards → Contacts column that supports multiple contacts per deal. Add all stakeholders (Champion, Decision Maker, Influencer, Blocker). Add a Role Dropdown on Contacts to label each. This is critical for enterprise deals where 4-6 stakeholders matter.
Monday.com
Monday.com is easy to spin up and easy to scatter. Three weeks in, most teams have 14 boards across 4 workspaces with no naming convention and no governance. This walks the setup sequence that keeps Monday useful past month three.
Monday.com
Monday automations are powerful and easy to over-wire. Most accounts past 100 active automations have 30-40% redundant or broken ones nobody notices. This walks the patterns that hold up at scale.
Monday.com
Most Monday dashboards rot within 60 days because they were built to look impressive instead of answer questions. This walks the dashboard patterns leadership actually uses every Monday morning.
HubSpot CRM
HubSpot's Smart CRM is free, fast to spin up, and easy to break in the first month. Most owners skip the account-level defaults, invite users with the wrong permission sets, and end up rebuilding 60 days in. Here is the setup sequence that holds up.