CRM & RevOps data
Keep the system of record clean, so routing, reporting and every automation can trust it.
Roadmap: CRM, RevOps & automation
Why it matters
The CRM (usually HubSpot or Salesforce) is where GTM work becomes revenue: leads get routed, deals get tracked and leadership reads the numbers. Every enrichment, signal and sequence you build eventually writes to it. If you create duplicates, overwrite reps' notes or break routing, sales stops trusting both the CRM and you. GTM engineers who understand the data model and work well with RevOps are trusted with far more.
What it's made of
- CRM data models: leads, contacts, accounts/companies, opportunities/deals
- Lead-to-account matching and duplicate prevention
- Field ownership: which system is allowed to write each field
- Lead routing: territories, round robin, account ownership
- Lifecycle stages and their definitions
- Safe bulk updates: backups, dry runs and rollbacks
- Syncing sequencers and enrichment tools without loops
- Reports and dashboards sales leaders actually use
Know the objects and how they connect
In Salesforce, a lead is an unqualified person not yet attached to an account; on conversion it becomes a contact on an account, often with an opportunity. HubSpot uses contacts and companies linked by association, with deals on top. Either way, the account (company) is the anchor. Most GTM data problems come from people who aren't attached to the right account, or accounts that exist twice.
Decide who owns each field
Write a short field-ownership table before you connect a new tool:
- Source of truth: which system or person is allowed to set this field?
- Write rule: always overwrite, only fill when empty, or never touch.
- Freshness: when was it last updated, and by what? Store that alongside the value.
- Example: an enrichment tool may fill an empty phone field but never overwrite one a rep entered. Employee count can be refreshed monthly from a provider.
Routing that survives edge cases
A routing rule is a small program, so test it like one. Before going live, run it on real cases: a lead from an existing customer, a lead from a subsidiary, a personal email address, a country with no territory, a rep on holiday, a lead that matches two accounts. Each should have a defined outcome. Measure speed-to-lead: inbound leads contacted within minutes are far more likely to convert than those contacted the next day.
Bulk changes without fear
Before any bulk update: export a backup of the affected records and fields, run the change on 20 records and check them by hand, then run the rest in batches while watching for errors. Keep the backup until people have used the data for a week. Turn off automations that would fire on the update (such as "field changed → send email") or you may trigger thousands of unintended actions.
Mid-level looks like
Knows the main objects, imports and updates records without creating duplicates, and builds simple reports and workflows.
Senior looks like
Designs field ownership and sync rules across tools, builds routing that handles edge cases, runs safe migrations, and agrees stage definitions with sales and marketing leaders.
Common pitfalls
- Importing a list without matching to existing accounts, creating hundreds of duplicates.
- Two tools writing the same field, each overwriting the other on every sync.
- Routing rules that send leads from existing customer accounts to a new-business rep.
- Running a bulk update with no backup and no way to undo it.
Practice drills
Drill 1
Design the sync between an enrichment table, a sequencing tool and the CRM. Write the field-ownership table for ten important fields and explain how you prevent sync loops.
A strong answer: A clear source of truth per field, fill-if-empty vs overwrite rules, timestamps, and one system responsible for creating records.
Drill 2
Write and test lead routing for inbound demo requests across three regions, with existing-customer and open-deal handling.
A strong answer: Account matching before assignment, explicit edge cases, a fallback owner, and measured time from form fill to first touch.
Drill 3
A CRM has an estimated 15% duplicate companies. Plan the clean-up and the changes that stop it happening again.
A strong answer: A matching rule on normalised domain, a merge-survivor rule, manual review for uncertain matches, backups, and prevention at the point of creation.
Best resources for this skill
Repos, courses, articles and podcasts, ranked by how much they teach.
Admin Beginner Trail
A free hands-on path through Salesforce data modeling, users and basic automation, the quickest way to stop guessing when a customer's CRM is Salesforce.
HubSpot Academy Certifications
Free certifications on HubSpot's CRM, Sales Hub and data tooling that teach the object model, pipelines and reporting you will be wiring automations into.
PodcastGTM Engineer: Cliff @ Polaris
Cliff Simon, CEO & Founder of Polaris Ops, walks Andy and Noah through structuring GTM engineering across the full lead-to-cash cycle. From uncovering six months of AI Apex slop in a client's Salesforce org to crafting custom signal plays that outperform off-the-shelf data, Cliff shares what he's learned across 20+ engagements in 14 months. Topics discussed: Build versus buy decisions for GTM eng…
PodcastRevOps Meets GTM Engineering ft. Shawn Tenam
In today's episode, I chat with Shawn, GTM engineer at RevPartners, about being their first GTME hire to build an all-bound motion alongside their core RevOps/HubSpot practice - serving both early-stage companies needing email infrastructure before their first SDR hire and mature companies sitting on goldmines of unactioned CRM data. We explore his champion tracking play pulling Salesforce opport…
Salesforce Certified Platform Administrator
The standard Salesforce credential, proving you can manage objects, security, automation and reports in the CRM most enterprise sales teams run on.
Read next
Traction
Gabriel Weinberg, Justin Mares
Surveys nineteen customer acquisition channels and a process for testing them cheaply. A good map before you decide which channel to automate.
Hacking Growth
Sean Ellis, Morgan Brown
Describes the cross-functional growth team and its rapid test cadence. Useful for setting up how your experiments get proposed, prioritized and reviewed.
Lean Analytics
Alistair Croll, Benjamin Yoskovitz
Helps you pick the one metric that matters for a given business model and stage. Read it before building dashboards so you measure what drives decisions.
Trustworthy Online Controlled Experiments
Ron Kohavi, Diane Tang, Ya Xu
The rigorous reference on A/B testing pitfalls: sample ratio mismatch, novelty effects and bad metrics. Read it before claiming that a new sequence or scoring model won.