How to Run a GTM Audit: A RevOps Framework for B2B SaaS

TL;DR: Most GTM audits fail because they turn into technology reviews. A real audit covers four pillars — process, technology, data, and people — and produces a prioritized fix list, not a slide deck. Here's the framework we use at VEN Studio to diagnose B2B SaaS revenue engines in 30 days or less.

---

60% of CRM implementations fail. Most GTM motions have broken plumbing that nobody has formally mapped in 18 months. And the average B2B SaaS company is running 80+ tools, up from 8 in 2015, with almost no documentation of why each one exists.

You don't need a bigger tech stack. You need a clear picture of what's working, what's broken, and what to fix first. That's what a GTM audit is for.

I've audited 50+ B2B SaaS revenue operations as founder of VEN Studio, as VP of RevOps at Clearco, and as a seller who spent seven years watching broken processes punish quota attainment. The same four failure modes show up almost every time: undefined process, bloated tech, garbage data, and misaligned people. The audit framework below attacks all four — in that order.

---

What a GTM Audit Actually Is (and Isn't)

A GTM audit is a structured diagnostic of your revenue engine. It maps your current state, identifies gaps between how you sell and how your systems assume you sell, and produces a prioritized list of fixes with clear owners and timelines.

It is not:

• A software evaluation
• A headcount review dressed up as strategy
• A project that ends with a deck and a handshake

Sound familiar? That's what most audits become. A real audit ends with action, not analysis.

The framework covers four pillars:

1. Process — How leads move from awareness to closed-won
2. Technology — What tools exist and whether they're earning their seat
3. Data — Whether you can actually trust what's in your systems
4. People — Whether roles, incentives, and skills match your GTM motion

Audit them in that order. Process is the foundation. Technology is built on top of process. Data quality depends on both. People alignment is the last thing to assess — because misalignment is usually a symptom of the first three problems, not a cause.

---

Pillar 1: Process

This is where most audits should spend the most time and where most audits spend the least.

Your process audit maps the actual sales motion — not the one in the onboarding deck, but the one your reps are actually running. They're almost always different.

Questions to ask:

• What are your defined pipeline stages, and what are the entry/exit criteria for each?
• Can every seller on your team describe those criteria the same way?
• Where do deals stall most often, and why?
• How are leads qualified before they hit the CRM? Who owns that decision?
• What triggers a deal to advance? Rep discretion or a documented event?
• Is your ICP written down and operationalized — or is it a vague agreement nobody uses?
• What's your handoff process between SDR and AE? Between AE and CS?
• How are expansion and renewal managed, and who owns the motion?

What you're looking for: Consistency. If you interview five reps and get five different answers to "how do you qualify a deal," you don't have a process — you have individual habits wearing a process costume.

Common findings:

• Stage definitions exist in Salesforce but nobody follows them
• No documented entry/exit criteria — deals advance based on gut
• Handoffs are informal Slack messages with no accountability structure
• ICP is aspirational, not operationalized into routing or scoring logic

---

Pillar 2: Technology

This is where most audits spend too much time. Don't let it happen.

The goal of a technology audit isn't to find better tools. It's to assess whether your current tools are earning their seat and whether they're configured around how you actually sell.

Questions to ask:

• What tools are in the stack, and who owns each one?
• What is each tool supposed to do, and what is it actually doing?
• Where are there redundancies — tools doing the same job?
• What's your CRM adoption rate? Are reps logging activity or are you estimating?
• Is your CRM configured to match your sales process, or does it force reps to work around it?
• Where does data flow between tools, and are those integrations documented?
• What tools were purchased in the last 24 months and never fully implemented?
• What's the fully-loaded cost of the stack per revenue dollar?

What you're looking for: Tool sprawl with no documented rationale. We regularly find companies paying for tools that duplicate core CRM functionality they haven't turned on yet. We've seen companies buy Tableau when basic Salesforce field history and a native dashboard would've done the job.

Common findings:

• 3-5 tools doing overlapping jobs (especially in sales engagement and conversation intelligence)
• CRM fields and objects that haven't been touched in 12+ months
• No single owner for 40% of the tools in the stack
• Integrations that were built once, never tested, and now silently failing

---

Pillar 3: Data

This is the unsexy pillar. It's also the one that breaks everything else.

The most common thing I hear from revenue leadership when they look at their CRM: "I don't trust this data." That's not a data problem. That's a process and adoption problem that shows up in the data. But either way, it needs to be fixed before anything else works — including AI.

Questions to ask:

• What percentage of opportunities have complete, accurate data at each stage?
• What is your contact and account data decay rate? (B2B data decays at 30%+ annually)
• Are required fields actually required, or are there workarounds?
• What's the source of truth for revenue data? Is it one system or three?
• How are duplicate records handled? Manually? Automatically? Not at all?
• What data are you using for forecasting, and how often is that data wrong?
• Can you produce a clean list of all open opportunities with accurate close dates and amounts right now? (Just ask. The answer tells you everything.)
• Who is responsible for data quality? If the answer is "everyone," the answer is no one.

What you're looking for: Systematic gaps, not one-off errors. A few bad records is normal. A pattern of incomplete fields across 60% of your pipeline means your process is structurally broken — likely because the CRM isn't built around how reps actually work.

Common findings:

• Contact data that hasn't been validated in 18+ months
• Forecasting built on close dates that reps update arbitrarily
• No data owner — hygiene is done manually during QBR panic
• Duplicate accounts or contacts causing attribution errors

---

Pillar 4: People

Last pillar. Most sensitive. And frequently the one that explains everything you found in the first three.

People problems in GTM are almost always structural, not personal. A rep who skips CRM fields isn't lazy — they're probably working around a CRM that doesn't match their motion. A CS manager who doesn't own a revenue number isn't strategic — maybe no one ever gave them one.

Questions to ask:

• Are roles and responsibilities clearly defined across the revenue org?
• Does everyone with a revenue number understand how their quota was set?
• What percentage of your sales team hit quota last year? (Industry average is around 47%)
• Is there a compensation plan, and do reps understand it? (75% of reps think they're paid wrong)
• Are RevOps, Sales, Marketing, and CS aligned on ICP, pipeline definitions, and attribution?
• Who owns the handoff between each team? Is that accountability documented?
• What does onboarding look like for new sellers? Is there a structured ramp plan?
• Where is leadership spending time — on strategy or on firefighting?

What you're looking for: Structural misalignment. When sales blames marketing for bad leads and marketing blames sales for ignoring them, that's usually a gap in how MQL is defined and who owns the qualification decision. Fix the definition, not the relationship.

---

The Audit Scorecard

Score each pillar on a 1–5 scale across the dimensions below. This gives you a baseline and a comparison point after you implement fixes.

Pillar	Dimension	Score (1–5)	Notes
Process	Stage definitions documented
	Entry/exit criteria consistent
	Handoffs formalized
	ICP operationalized
Technology	Tool ownership defined
	CRM adoption >80%
	No functional redundancies
	Integrations documented
Data	Pipeline data completeness
	Contact data accuracy
	Single source of truth
	Data ownership assigned
People	Role clarity
	Quota attainment >60%
	Cross-functional alignment
	Comp plan clarity

Scoring guide:

• 1 — Not documented, not functioning, or unknown
• 2 — Partially in place, inconsistently applied
• 3 — Documented and mostly followed, some gaps
• 4 — Consistent and functioning, minor optimization needed
• 5 — Best-in-class, proactively maintained

Total your scores. A company with 60+ out of 80 is in reasonable shape and needs optimization. Below 40 means you're running on habits and hope — and one bad quarter away from a real crisis.

---

How to Prioritize Fixes

Not everything that scores low is equally urgent. Prioritize fixes using two dimensions: impact on revenue and implementation difficulty.

Priority	Criteria	Typical Examples
Fix now	High impact, low difficulty	Enforcing required fields, documenting stage criteria, assigning tool owners
Fix next	High impact, high difficulty	CRM restructure, comp plan redesign, data migration
Fix later	Low impact, low difficulty	Cleaning up unused reports, decommissioning a redundant tool
Deprioritize	Low impact, high difficulty	Building complex lead scoring before ICP is operationalized

One rule: do not touch technology before process is documented. We've seen this mistake more times than I can count. A company fixes its CRM fields while the underlying sales motion is still undefined. Six months later, the data is clean but the process is still wrong — and now you need to rebuild the CRM again.

Implementation difficulty increases exponentially when delayed. Fix process first. Technology second. Data third. People alignment happens continuously throughout.

---

The Audit Timeline

A proper GTM audit takes 30 days if you're moving with urgency. Here's what that looks like:

Week 1 — Discovery

• Stakeholder interviews (Sales, Marketing, CS, RevOps, leadership)
• Document collection (comp plans, playbooks, CRM setup, tool contracts)
• CRM access and initial data pull

Week 2 — Analysis

• Map current-state process across the full funnel
• Audit technology stack against documented process
• Run data quality assessment across key objects (Leads, Contacts, Accounts, Opportunities)
• Score all four pillars

Week 3 — Synthesis

• Identify root causes (not just symptoms)
• Build prioritized fix list with owners, timelines, and effort estimates
• Draft scorecard with current-state scores

Week 4 — Readout and Planning

• Present findings to leadership — findings, scores, priorities
• Align on 30/60/90-day fix plan
• Assign owners and establish accountability checkpoints

Plan for 30% buffer on all timeline estimates. Companies that move fastest through audits are the ones with documentation already in place. Most don't have it, which means Week 1 runs long.

---

Where to Start If You're Running This Yourself

If you're going to run this without outside help, start with these three questions. They'll tell you where your biggest gaps are before you run the full framework:

1. Can every seller describe your qualification criteria the same way? If no, start with process.
2. Do you trust your pipeline data enough to make a forecast you'd bet on? If no, start with data.
3. Do you know which tools in your stack have no defined owner? If no, start with technology.

Pick the pillar that answered "no" fastest. That's your bleeding edge.

---

FAQ

How often should a GTM audit happen? Annually at minimum for companies in active growth. At Series A, do it as soon as you're transitioning out of founder-led sales. After any significant GTM change — new segment, new product, new leadership — run it again. The audit is a diagnostic, not a one-time event.

What's the biggest mistake companies make during a GTM audit? Jumping straight to technology. The first question shouldn't be "is our CRM the right one?" It should be "does our sales process exist on paper?" In our experience, most companies that think they have a CRM problem actually have a process problem that the CRM is reflecting back at them.

How do you get reps to participate honestly? Make it clear the audit is not a performance review. You're auditing the system, not the people. The most useful input usually comes from your worst performers — they've found every workaround your process allows because they had to. Talk to them first.

Should RevOps run the audit or bring in outside help? Depends on the capacity and seniority of your RevOps function. If you have a senior operator who can hold a mirror up to the business without political risk, run it internally. If your RevOps team is junior, overextended, or too close to the systems to see them clearly, bring in outside help. The second pair of eyes isn't a luxury — it's often what makes the difference between findings that get acted on and findings that get filed away.

What's a realistic improvement timeline after an audit? Quick wins (required fields, stage definitions, tool owners) in 30 days. Structural fixes (CRM rebuild, comp redesign, handoff formalization) in 60–90 days. Systemic improvements (data quality programs, ICP operationalization, forecasting accuracy) over 6–12 months. Anyone promising a full GTM transformation in 90 days is selling you something.