Objects, associations, and why structure decides everything
Video coming soon
No YouTube video has been added yet.
A ground-up tour of how contacts, companies, deals, and custom objects relate inside a modern CRM, and why the data model quietly determines what reporting and automation you can ever build. Paul walks through the associations that make or break a RevOps foundation.
Key ideas
Show notes
Every reporting headache and broken automation eventually traces back to the same place: the data model. In this opener for RevOps 101, Paul lays out how a CRM actually stores your revenue reality and why getting the object relationships right up front saves years of cleanup later.
Timestamps
Quotable
“Associations are where the leverage is. Get them right and you can answer questions you never planned for.”
— Paul Maxwell
Full transcript
Paul: People think a CRM is a place to store contacts. It isn't. It's a model of how your business actually makes money, and every field you add is a claim about that model.
Paul: So before you create a single custom property, ask what object it really belongs to. Is this a fact about a person, a company, or a deal? Because if you put deal-level data on a contact, your pipeline reporting will lie to you six months from now.
Paul: The associations are where the leverage is. A well-associated model lets you answer questions you didn't even plan for. A poorly associated one means you're exporting to spreadsheets forever, reconciling by hand, and never quite trusting the number.
Mentioned
Related links