Outbound Wiki

Article

"CRM Data Model Design: A 6-Step Guide (With Examples)"

resources.rework.com

Open at publisher

Quoted on this wiki

Every place a page here uses this source, in the order the words come in it.

  1. Contacts: Individual people your team interacts with “Companies (Accounts): The organizations contacts belong to” Deals (Opportunities): Active sales motions with a close date and value

    In Prospect list schema

  2. Deals (Opportunities): Active sales motions with a close date and value “Activities: Calls, emails, meetings, tasks (the interaction record)” Before you add anything else, validate that these four cover 90% of your sales motion. They usually do. The temptation to add custom objects is strong. Resist it until you've proven the standard objects can't handle the use case.

    In CRM adoption and activity capture

  3. Core picklists to define before go-live: “Lead Source: Where contacts enter the CRM. Sample values: Inbound Web, Outbound SDR, Referral, Partner, Event, Content Download, Paid Ad, Trial Signup. Keep these at the source level, not "Facebook Ad - Campaign Name - March 2026." Source-level values stay clean. Campaign-level belongs in your marketing attribution tool.” Industry: Use a consistent taxonomy. Start with 10-12 values and resist requests to add more in the first 90 days. SaaS, Financial Services, Healthcare, Manufacturing, Professional Services, Retail, Media, Education, Non-Profit, Other.

    In CRM system-of-record boundaries

  4. That third attempt started with a whiteboard, not a laptop. “Contacts vs. Leads vs. Accounts vs. Deals: the relationships between these objects determine what you can report on, what you can automate, and how your pipeline works.” This guide walks you through designing a CRM data model on paper before you configure a single field.

    In Outbound CRM data model

  5. “The second rebuild happened because they discovered, mid-Q2, that their contact model couldn't support multiple contacts per deal with different roles.” That third attempt started with a whiteboard, not a laptop.

    In Outbound CRM data model

  6. That third attempt started with a whiteboard, not a laptop. “The core lesson: every CRM implementation that falls apart does so because someone started clicking before thinking.” This guide walks you through designing a CRM data model on paper before you configure a single field.

    In Outbound CRM data model

Quotes are verbatim and belong to their publishers. Where a quote has been translated, the original wording is kept below it.