By clicking “Accept All Cookies”, you agree to the storing of cookies on your device to enhance site navigation, analyze site usage, and assist in our marketing efforts. View our Privacy Policy for more information.
Revenue Operations

Unblock Your Data Model, Unlock Your Revenue: How to Break the CRM Data Bottleneck

swirled squiggle accent

In almost every revenue organization, CRM data breaks down long before anyone notices. Required fields go stale, workflows stop serving a real purpose, reporting becomes manual detective work, and no one trusts the dashboards that leadership depends on to make decisions. In this webinar, RevOps Co-op + Eventful founder Matthew Volm brings together a powerhouse panel to unpack why CRM data breaks at the foundation level and what RevOps can do to restructure their systems around a true customer centric data model. The conversation includes Rob Moseley, CEO and Co-founder of GTM Engine, Courtney Sylvester, RevOps consultant, and Jared Barol, former VP of RevOps at Copy.ai and  ex-Salesforce operator.

This session dives deeply into why CRMs fail, how unstructured data creates both chaos and opportunity, the real reason leads should be eliminated, and why RevOps is uniquely positioned to rebuild the entire GTM architecture around accurate, automated customer truth.

Why CRM Data Sucks

CRM failure is not an edge case. It is the default outcome of most implementations. The day to day experience of most operators is defined by fragmented systems, missing information, manual data entry, poor hygiene, and competing definitions of what is actually happening in the revenue engine.

Rob kicked off the content by grounding the conversation in his own experience. After working across eight startups on the technical and RevOps side, he repeatedly encountered the same systemic problems: messy data models, constant firefighting, requests for fields no one fills out, and pipelines built on subjective narratives rather than objective truth.

Courtney added the perspective of someone who is often hired specifically to fix the mess. She shared that most organizations bring her in at moments of extreme operational dysfunction. Some teams are scaling quickly and want to build automation correctly, while others sit on years of bad data and broken workflows without the time or expertise to repair them.

Jared, who has held nearly every GTM role from SDR to RVP to sales engineering leader and finally RevOps, has been on both sides of the CRM pain equation. Reps feel systems make their job harder. Ops teams feel reps ignore the process. Leaders feel they cannot trust any number they see.

The webinar quickly surfaces the core diagnosis: CRM data is broken at the foundation because humans are being asked to operate as data pipelines. And no amount of tooling, enrichment, AI or dashboards will fix the system until that root issue is addressed.

Key Takeaways

Reps Cannot Be the Data Engine Behind Your CRM

One of the strongest themes throughout the webinar is that sales reps cannot be responsible for data entry. Not because they are incapable, but because their compensation, goals, and psychological incentives all push them toward selling, not data stewardship.

As Jared put it, reps are coin operated. They will do the activities that directly help them close deals and nothing that does not.

This manifests in several predictable patterns:

  • Required fields are filled with guessed values, NA, or outdated information because reps want to move to the next stage quickly.
  • Pipeline reviews become performance rituals rather than honest assessment. Reps spin stories, speak in hypotheticals, or communicate overly optimistic narratives because no one wants to walk into a QBR with a weak pipeline.
  • Teams create new fields to answer board questions or leadership requests, but no one actually fills them out. They remain empty or inaccurate, compounding confusion.

Courtney highlighted the gap between what happens on sales calls and what ends up in the CRM. It is extremely common for a rep to walk out of a meeting convinced a deal is closing within days, even when the actual conversation shows much weaker signals. Without transcripts or objective call data, the CRM captures only the rep’s interpretation, not the truth.

Rob summarized the fundamental flaw clearly: as long as humans are manually entering data, the foundation of your CRM will always be unstable.

For more on to think of your CRM as a revenue operator, check out RevOps Co-op Blog: It’s Time To Stop Thinking of a CRM as a Selling Tool.

CRM Problems Are Not Caused by Sales, They Are Caused by the Data Model

The discussion then shifts toward the deeper structural issues causing this chaos. Operational leaders often assume the CRM is the problem or that sales is the problem. But Rob makes the argument that the real culprit is the underlying data model.

CRMs are relational databases, which means they are only as strong as their object relationships. But in most organizations:

  • Contacts are not tied to accounts.
  • Leads sit unassociated, never converting into the lifecycle.
  • Opportunities lack correct contact roles.
  • Fields proliferate without governance.

The result is a relational database with broken relationships. This destroys reporting, forecasting, and GTM visibility.

Jared adds that even the most basic question can become unanswerable in a broken data model. At a previous company, he was asked how many customers the business had. After weeks of digging, he found that most of the information lived in PDFs, not in the CRM.

This kind of scenario is routine: purchase history spread across contracts, product usage stored in back end systems, customer attributes scattered across spreadsheets, and enrichment tools.

RevOps ends up stitching together fragmented truth instead of operating from a shared source of customer reality.

For more on data + AI, check out RevOpsAF Podcast Episode 50: Thinking of AI? Think Data First.

Why Leads Must Die and the Contact Should Become the Primary Object

One of the boldest recommendations in the webinar is Rob's argument that the industry should retire the concept of leads entirely.

The traditional Salesforce model assumes a linear process where leads convert into accounts, contacts, and opportunities. But this model does not work in modern GTM systems because:

  • Leads do not maintain relational context.
  • Leads duplicate existing contacts.
  • Leads make account level reporting nearly impossible.
  • Leads break attribution and lifecycle visibility.
  • Leads are often auto created for product signups, making it impossible to know which users belong to which account.

Rob’s replacement is straightforward: maintain a single object for people, the contact, and use relationships to determine lifecycle status.

This creates a far more accurate and scalable model:

  • A contact without opportunities is a lead.
  • A contact associated with an open opportunity is a prospect.
  • A contact associated with closed won deals is a customer.

This relational approach eliminates duplication, preserves context, and enables far better reporting, segmentation, and automation.

Courtney notes that every company using leads uses them in a different and often dysfunctional way, making cross org consistency impossible.

A single contact centric model solves this by enforcing structure and eliminating guesswork.

For more on the Common Customer Data Model, check out The Common Customer Data Model as the GTM Brain.

The Customer Is the Only Scalable Source of Truth Across GTM Functions

The conversation then expands into why the customer must be the central entity in a shared GTM data model.

Marketing wants to know which ICP personas resonate with which messages.

Sales wants to know which champions are driving the deal.

CS wants to know what was promised during sales and what use cases to prioritize.

Product wants to know which features are being requested and by whom.

All of these insights originate from the customer, yet the signals are scattered across:

  • Sales calls
  • Emails
  • Tickets
  • Website activity
  • Slack messages
  • Implementation notes

Rob argues that the customer is already generating a rich stream of unstructured truth, but most companies have no system to convert that truth into something structured, reportable, and actionable.

When structured correctly:

  • Marketing receives instant updates when an ICP expresses enthusiasm about a specific use case.
  • CS receives alerts about adoption risks months before renewal.
  • Product sees feature requests tied to real revenue impact.
  • Sales leadership sees objective buyer signals rather than optimistic rep interpretations.

This is how the GTM engine becomes synchronized rather than siloed.

For more on this topic, check out this article: The Living Customer Record: RevOps’ Next Evolution.

Why AI Will Not Fix CRM Data Unless Structure Comes First

At several points in the discussion, the panel reinforced a critical but often misunderstood point: AI cannot fix broken CRM data models.

Large language models excel at summarizing or interpreting unstructured data, but they cannot replace structured fields for reporting, forecasting, or governance.

Rob shared that even in legal AI applications, simple counting tasks often fail because LLMs are not optimized for deterministic answers. That means they cannot reliably replace structured picklists, numeric fields, or date fields that reporting depends on.

AI becomes powerful only after RevOps creates a unified model that can ingest unstructured data, extract key insights, and convert them into validated, structured fields.

AI is not the house.

AI is the electricity.

The data model is the wiring.

For more on this topic as it relates to cold outbound, check out RevOpsAF Podcast Episode 27: How AI Killed Cold Prospecting.

Why RevOps Must Own the Customer Centric Data Model

Throughout the webinar, the panel makes one message clear: no other function can or will own this transformation.

  • Sales teams are focused on quota.
  • Marketing teams optimize campaigns, not CRM governance.
  • CS teams focus on renewals and adoption.
  • Product teams prioritize roadmap and engineering velocity.

RevOps alone sits at the intersection, touching every workflow and every system. RevOps is the natural owner of:

  • Data governance
  • Lifecycle architecture
  • Automation
  • Integrations
  • Attribution
  • Forecasting
  • Process consistency
  • Cross functional alignment

As Matthew emphasizes near the close, RevOps cannot hide behind tools or data. Influence in the organization comes from storytelling, trust building, system ownership, and showing each team the growing value of shared customer truth.

For more on this topic, check out this article: The Hidden Cost of CRM Dysfunction in Sales Data.

How to Begin: A Practical Roadmap for Operators

Rob closed the webinar by outlining a crawl, walk, run maturity model for teams that want to fix their CRM foundation without years of disruption.

Crawl

Build structural integrity.

  • Stop allowing humans to manually create or shape records.
  • Auto create accounts and contacts.
  • Enrich records on creation.
  • Enforce object relationships.
  • Kill the lead object or migrate away from it.

Walk

Convert existing unstructured signals into structured insights.

  • Start with sales calls, emails and notes.
  • Use transcription to extract objective buyer signals.
  • Normalize use cases, personas, champions and objections into fields.
  • Build internal alerts for marketing, CS and product.

Run

Operationalize customer truth across the GTM engine.

  • Push case study candidates to marketing in real time.
  • Alert CS about adoption blockers and expected value drivers.
  • Notify product when high value customers request features.
  • Forecast pipeline using objective buyer signals instead of rep narratives.
  • Build cross functional workflows rooted in reliable customer insights.

When executed well, this model transforms RevOps from a reactive firefighting team into a strategic, insight generating, cross functional system owner.

For more on being a strategic revenue operator, check out RevOpsAF Podcast Episode 19: How to be a Strategic Revenue Operator.

Want more content link this?

Need deeper guidance on redesigning your CRM foundation, improving your data model or building AI driven workflows that actually work? Explore more articles and webinar recordings or join our global community of 18,000 revenue operators for courses, discussions and hands on help.

Want to give your sales team 40% of their time back? Learn how GTM Engine can help or check out their interactive demo here. Check out their blog and newsletter for more resources on AI and sales.

Related posts

Join the Co-op!

Or