How to Audit an Inherited CRM in Your First 90 Days as a GTM Leader
Stepped into a new GTM role and the CRM is already broken? Here's the 90-day framework to audit what you inherited and build the case for a rebuild.
Your new CRM is already broken - here's what to do
The problem - you inherited someone else's mess
You've just stepped into a new GTM leadership role. You've done the listening tour. You've met
the team. And somewhere around day 30, you open the CRM and realize: nobody actually
trust it.
Sales reps aren't logging activity. Forecasting is happening in Excel. Your ops team is
apologizing for fields nobody remembers creating. The last three deals in the Closed Won stage
have been sitting there for six months.
This isn't a data problem. It's an architecture problem , and it's been accumulating since
before you walked in the door.
Why this matters - What you find in the first 90 days determines the next 12 months
The 90-day window is real. It's the only time you have political cover to ask hard questions
about existing systems without it feeling like an attack. It's when teams expect change. It's when
the noise around how we do things is lowest.
Miss the window, and the status quo calcifies. That broken Salesforce org becomes our
process. Those unmapped workflows become tribal knowledge. Six months later, you're
patching instead of building.
Most GTM leaders run a people assessment in the first 90 days. Almost none of
them run a systems assessment with the same rigor.
The CRM is a direct reflection of how revenue was built before you arrived. What you find there
tells you more about the real state of the business than any slide deck or QBR.
What you will find:
The four warning signs
These are the patterns we see repeatedly when stepping into inherited CRM environments,
Salesforce, HubSpot, or otherwise.
- Bad Data, No Baseline
Contacts without owners. Deals without close dates. Stages that don't map to any real buying motion. No one knows what's accurate.
- Over-Customized Systems
300+ custom fields. Automation workflows firing on triggers no one remembers the setting. Salesforce orgs built by five different admins over four years.
- Broken Workflows Sequences running on dead leads. Duplicate records inflating
pipeline numbers. Stage movement that triggers the wrong follow-ups.
- No RevOpsOwnership
Nobody owns the system strategically. The admin manages tickets. Nobody is connecting CRM architecture to revenue outcomes.
The framework- How to run the assessment
Don't wait until day 60 to start looking. Structure your assessment across three distinct phases.
[Days 1–30] Audit without touching
Your only job is to observe and document. Talk to sellers, ops, and finance. Don't fix anything
yet.
→Pull a pipeline report and ask sellers to walk you through every deal
→Map how leads actually flow from source to close, not how the process doc says they
do
→Count the custom fields. Flag anything without a clear owner or use case
→Identify where people are working outside the CRM (Excel, Slack, personal trackers)
→Ask: "If I needed to forecast next quarter today, what would I trust?"
[Days 31–60] Diagnose the architecture
Now you have enough context to separate symptoms from root causes. The goal is a clear
diagnosis before any rebuild begins.
→Map the existing data model, what objects exist, what connects to what, and what's
orphaned.
→Audit active automations: what fires, when, and whether anyone is monitoring outcomes
→Identify your highest-friction moments: where do deals stall, where do records break,
Where does reporting fail?
→Document what a clean, minimal CRM architecture would look like for your current GTM
motion.
→Pressure-test with your RevOps or ops lead, if you don't have one, that's part of the
diagnosis.
[Days 61–90] Build the case and the plan
Present your findings. Be direct. This is your window to get organizational alignment on the
Rebuild, not to soft-pedal the problem.
→Present the gap: Current state vs. what the business needs to scale.
→Separate quick wins (data cleanup, workflow fixes) from strategic work (architecture
rebuild)
→Define what RevOps ownership looks like, internal hire, fractional partner, or both.
→Set a 90-day post-assessment roadmap with measurable milestones.
→Get budget and executive alignment before the window closes.
The hard truth: Most CRM problems aren't technical. They're architectural. A Salesforce
org with 400 custom fields and broken pipeline hygiene doesn't need more customization, it needs a clean revenue architecture built around how your team actually sells. That's the difference between a CRM admin and a RevOps partner.
The real question - Fix, Rebuild or Replace?
After a rigorous assessment, most GTM leaders face one of three realities:
Fix: The core architecture is sound but execution has drifted. Cleanup, workflow pruning, and
better hygiene governance gets you there. Timeline: 30–60 days.
Rebuild: The platform is right but the configuration is wrong. You need a RevOps-led re-architecture on your existing tool. This is the most common scenario. Timeline: 60–90 days.
Replace: The tool no longer fits the GTM motion. Rare, but when the org has outgrown its
stack or the tool was always wrong for the motion, no amount of cleanup fixes the mismatch.
Timeline: 90–180 days with proper migration planning.
Most inherited CRMs need a rebuild, not a replacement. The instinct to rip and replace is
expensive and almost always avoidable if you design the architecture correctly the second time.
What changes after- What a clean RevOps architecture actually delivers
- The point of the assessment isn't the assessment. The point is what gets unlocked once your
- revenue systems are actually working.
- Forecast you can trust: Pipeline reflects reality. Stage movement is meaningful. You stop
- managing a spreadsheet alongside your CRM.
- Sellers adopt the system: When the CRM reflects how people actually sell, adoption follows.
- Less admin overhead, more time selling.
- Ops has strategic leverage: RevOps stops firefighting broken workflows and starts building
- systems that scale with pipeline growth.
- Leadership has visibility: One source of truth. Dashboards that reflect what the business
- Needs to know — not what someone built in 2021.
