Start with one sales process and a clear finish
Choose a journey the team can explain: an enquiry is qualified, linked to the right customer records and given an owner and next action. Agree what each stage means before building rules. For example, “Qualified” might require a relevant need and an agreed next conversation; “Won” should represent your actual acceptance rule, not merely a sent proposal. These are CompanyConnect design recommendations, not default monday CRM settings.
Confirm the product before copying a board design
monday CRM and a general work-management workspace are not interchangeable feature lists. Check which product and plan your team has, who administers it and which permissions or recipes are available. Start with the existing CRM structure instead of deleting core boards or creating duplicate customer databases. The official getting-started guide below explains the product layout; exact controls can change.
Give each record a distinct job
Use Leads for incoming prospects, Contacts for people, Accounts for organisations and Deals for opportunities. Connect the relevant records so a deal can be understood alongside its customer relationships. Two people at the same organisation should not become one contact simply because their company name matches. Decide which identifier your team trusts and document when a person must review an uncertain match. The record map below illustrates the distinction without using real customer data.
Choose fields that make the next action visible
For the first workflow, identify the source, responsible person, current stage and next-action date. Add the contact/account relationship and information genuinely needed for qualification or reporting. Define who can change a stage, how missing ownership is surfaced and what closes an exception. Do not assume a field is technically mandatory on every plan: verify the controls in your account and use a documented review step where enforcement is unavailable.
Prepare a recovery copy and test the import
Before changing existing records, export an appropriate recovery copy and agree how mistakes will be reconciled. Standardise email, phone, identifiers and stage values, then use a small representative sample rather than the entire customer file. Map columns deliberately. The CRM importer distinguishes adding everything, skipping matching rows and updating matches using a selected matching column. Updating a match can replace existing information; choosing a matching field is not proof that every duplicate has been resolved.
Inspect what happened after the import
Review existing Leads-board automations before importing: a rule can change the status of an imported record. Reconcile the resulting record count, owner, stage, relationships and any overwritten fields against the sample. Keep ambiguous records in an owned exception list. Do not repeatedly import the file to see whether an unexpected result fixes itself; determine which records changed and choose the recovery action first. The sample tests below describe acceptance expectations, not automatic product behaviour.
Connect and verify one complete customer journey
Take one fictional lead through your qualification rule, establish its contact/account relationship and record the associated opportunity. Check the actual saved records: correct owner, correct customer, intended stage and visible next action. A button click or a rule marked active does not prove that the handoff finished correctly. Repeat with a duplicate enquiry and an incomplete record before using the process with authorised live information.
Automate one bounded handoff, then check its limits
Start with a rule such as notifying an internal owner when an agreed follow-up date arrives. Treat this as a recipe concept: confirm the trigger, conditions, recipient and supported actions in your account. Test missing owners, repeated triggers and rules that could trigger each other. Keep customer emails and other consequential actions outside the pilot unless separately approved. An automation can consume more than one action, and allowances depend on the plan; inspect actual usage rather than estimating from the number of rules.
Hand over an operating system, not just a set of boards
Document the record map, stage meanings, matching rule, automation owner and recovery procedure. Useful acceptance checks include no unintended overwrites, valid customer links, visible exceptions and no unapproved outbound messages. Then compare a consistent sample of missed follow-ups, unowned opportunities and correction effort with the previous process. A cleaner board alone is not evidence of more revenue. Expand only after the team can explain both a normal result and a failed handoff.