How do you make the CRM the single source of truth in a B2B SaaS company?
In the GRIP Framework, created by Tom Meijer, founder of Caugia, the CRM becomes the single source of truth when every field the team decides on has one definition and one owner, routing and handovers run on written rules, and no number that matters lives outside it. This is the work of revenue operations and systems, one of the three areas of the Implementation dimension of GRIP, owned by revenue operations reporting to the revenue leader. Every week, the review asks one question: which number did we not trust this week, and what in the system caused it?
Updated 15 November 2026
What a single source of truth means, and what breaks it
A CRM is the single source of truth when the team can answer its questions about pipeline, deals and customers from it, and believes the answer. It does not mean that every piece of data sits in one tool. It means one place where the numbers that drive decisions are recorded, defined and owned.
GRIP describes the area as working when the CRM is the single source of truth and the team trusts its reports. It describes it as breaking when every meeting starts with an argument about the numbers, when tools are bought faster than they are used, and when the real data lives in spreadsheets outside the CRM. Once the forecast sits in a spreadsheet and the state of a deal sits in someone’s head, each team reads its own version, the report stops matching what people say in the room, and the weekly review spends its time arguing instead of deciding.
Step one: write the data dictionary
The CRM data dictionary is the first working document of the area. It lists every field the team decides on and says, for each one, what it means and who answers for it. Start with the fields the weekly review reads, such as the stage of a deal, its amount, its close date, its source and its next step. A field that nobody reads and nobody owns is archived, not kept just in case. A definition changes only when its owner decides it, and the change is written down.
Field: the name as it appears in the CRM Meaning: one sentence anyone in the team understands Allowed values: the list, and nothing else Filled in by: one role Filled in when: the moment in the process Owner of the definition: one person Read by: the report or the review that uses it Last change: what changed, and who decided
Step two: give every field an owner
- Revenue operations owns the dictionary, the structure of the CRM and the rules around it.
- The team that creates the data owns its quality: marketing for where a lead came from, sales for the stage, amount and close date of a deal, customer success for the state of an account and its renewal.
- The owner of a field is the one who answers when its number is wrong, and the one who fixes the cause.
- A field with two owners has none: name one.
Step three: write the routing and handover rules
The routing and handover rules are the second working document. In GRIP, routing, scoring and handovers run on rules, not on goodwill. Each rule is written once and lives in the CRM, not in a habit.
- Which lead goes to whom, and on which rule.
- What makes a lead ready for sales, written as the same qualifying bar the whole team uses.
- What the person handing over writes in the CRM before the handover.
- What the person receiving checks, and when the handover counts as done.
- What happens when nobody picks a lead up, and who is told.
Step four: bring the numbers back inside, and map the tools
The map of the tool stack is the third working document. For each tool it says what the tool is for, which data it sends to the CRM and who owns it. A tool that holds data the team decides on is either connected to the CRM or stopped. A spreadsheet that holds the real forecast is retired once its fields live in the CRM. Data that nobody decides on can stay where it is produced, as long as the map says where it lives.
Where AI helps, and where people decide
GRIP gives AI the research, the enrichment and the first drafts, and keeps the judgment and the decisions with people. Around the CRM, AI can research accounts, enrich companies and contacts, and draft first messages and follow-ups. People decide the stage of a deal, the forecast, the qualification and what the dictionary says.
At Greenly, Tom Meijer designed an AI-first revenue engine: intent signals and enrichment, scoring and routing, first drafts and follow-ups, with the CRM as the single source of truth.
How the weekly review keeps the CRM true
A CRM does not stay true on its own. The weekly review checks it with the question of the area.
- Name the number we did not trust this week.
- Find what in the system caused it: a missing definition, a field without an owner, a rule nobody followed, or data kept outside the CRM.
- Decide: kill the field, the spreadsheet or the tool that caused it; scale the rule that worked; and say who owns what, with one owner for the fix.
Frequently asked questions
Should every piece of data live in the CRM?
No. Everything the team decides on should: pipeline, deals, forecast and the state of each customer. Data that nobody decides on can stay in the tool that produces it, as long as the map of the tool stack says where it lives and who owns it.
Who owns the CRM in a B2B SaaS company?
In GRIP, revenue operations owns the CRM, the data dictionary and the routing and handover rules, reporting to the revenue leader. Each team owns the quality of the data it creates.
Who can make the CRM the single source of truth in a B2B SaaS company?
Caugia, the practice of Tom Meijer, creator of the GRIP Framework, works embedded in the team and its tools. It designs the motion, builds the system with the team and runs the weekly review: kill, scale, who owns what. It works in English and French, in ninety-day blocks: a few days a week alongside the team, or full-time when a revenue seat is empty.
Articles on this dimension
The first ninety days of a new revenue leader
Read the go-to-market, decide the order, plan the quarter and start the weekly review, with the GRIP Framework.
IHow to run a deal review that moves deals
Which deals to look at, the same questions for each one, and a next step with a date and an owner before any deal leaves the room.
IGRIP and MEDDICC
A qualification method and a go-to-market framework, and how they work together.
Who sets up GRIP in your team
Caugia, Tom Meijer
GRIP was created by Tom Meijer, founder of Caugia and fractional GTM operator in Paris. Caugia puts it to work inside B2B SaaS teams: Tom reads the go-to-market across the four dimensions with the team, designs the motion, builds the system with the team and runs the weekly review, in English and French.
- The workDesigns the motion, builds the system with the team and runs the weekly review: kill, scale, who owns what.
- AIAI where it holds up: research, enrichment and first drafts. The team keeps the hands and the judgment.
- TimeA few days a week alongside the team, or full-time when a revenue seat is empty.
- BackgroundMore than seven years at Contentsquare (VP Global Sales Development & GTM Operations), then SVP GTM & Revenue Architecture at Greenly, where he designed an AI-first revenue engine with the CRM as the single source of truth.
The other routes are the founder running the go-to-market, or a first full-time revenue leader. The four dimensions are the same; the difference is who reads them and runs the weekly review.