Most RevOps teams don't have a tools problem. They have a clarity problem. You know roughly what you own. You've lost track of what it costs. You suspect some tools are underused. And there's a nagging feeling that somewhere in your stack, data is going wrong — you just can't pinpoint exactly where.
This template fixes that. It forces you to be systematic, brutal, and honest about every layer of your GTM infrastructure — from your CRM to your BI stack to the 14 browser extensions your SDRs installed when nobody was watching.
I've seen stacks with $2.4M in annual tool spend where 60% of the seats sat empty. I've seen a Fortune 500 lose $18M in pipeline because their lead routing fired on stale data. I've seen startups running 8 tools where 3 would do it better. And I've seen companies with real capability gaps they papered over with spreadsheets for two years before anyone admitted it was a problem.
This framework prevents all of that. Run it quarterly for maintenance, annually for a full teardown, and every time you're onboarding a new GTM leader or about to spend serious money on new tools.
The dirty secret of RevOps is that most technology decisions are made emotionally — a VP of Sales sees a demo, gets excited, and signs a contract. The audit happens eighteen months later when the CFO asks why the renewal is on the P&L but the tool isn't in the revenue attribution report. By then you've built process debt around something that never should have been purchased.
Before touching any section, complete a raw tool inventory dump from three sources: (1) your IT/software procurement list, (2) expense reports tagged to GTM categories, and (3) a department-by-department survey asking "what tools do you use that aren't in the company stack?". The third source always surfaces 3–7 shadow tools nobody knew about.
Each section produces a score from 0–10. Your composite RevOps Health Score is a weighted average across all sections. The weights below reflect the relative business impact of each dimension:
| Section | Max Score | Weight | Business Impact |
|---|---|---|---|
| Stack Inventory Completeness | 10 | 10% | Foundational visibility |
| Integration Health | 10 | 20% | Data flow reliability |
| Data Quality | 10 | 20% | Pipeline accuracy & trust |
| Process Alignment | 10 | 15% | GTM execution consistency |
| Cost & ROI | 10 | 15% | Financial efficiency |
| Gap & Redundancy | 10 | 10% | Capability coverage |
| Adoption & Utilisation | 10 | 10% | Investment realisation |
This is ground zero. Everything else in this audit depends on having an accurate, exhaustive list of every tool your GTM org owns, borrows, or quietly operates. Most companies get to about 70% and call it done. The remaining 30% is where the expensive surprises live.
A complete GTM technology stack operates in nine functional layers, each serving a distinct purpose in the revenue engine. Tools often span multiple layers — document them under their primary function.
Complete this table for every tool in your stack. Do not skip anything, including free tools, trial accounts, or tools "being evaluated." Every tool that touches data or process is in scope.
| Tool Name | Layer | Vendor | Contract $ | Seats | Active Users | Renewal | Owner | Status |
|---|---|---|---|---|---|---|---|---|
| Salesforce CRM | L1 | Salesforce | $___/yr | ___ | ___ | ___/___ | RevOps | Active |
| [Tool Name] | L___ | [Vendor] | $___/yr | ___ | ___ | ___/___ | [Owner] | Evaluate |
| [Tool Name] | L___ | [Vendor] | $___/yr | ___ | ___ | ___/___ | [Owner] | At Risk |
| [Add all tools] | L___ | — | — | — | — | — | — | — |
Your CRM is the single most important tool in your stack. Everything else is either feeding it, reading from it, or both. A broken CRM means nothing downstream can be trusted. Audit this layer with more rigour than any other.
Most CRM problems aren't CRM problems — they're governance problems. Wrong fields, missing definitions, no validation rules, and reps who were never taught why data quality matters. Before blaming Salesforce, audit the process that creates the data in it.
The most common sales engagement failure is too many sequences, too little governance. Companies with 200+ active sequences always have the same problem: nobody knows which ones work. Best-in-class teams have fewer than 30 active sequences — all A/B tested, all with documented reply rates.
Integrations are where stacks go to die quietly. A broken integration doesn't wave a red flag. It slowly corrupts your data, introduces lag, and eats the reliability of every report downstream — often for months before anyone connects the dots.
The integration audit is the most technically demanding section of this framework. You need someone with admin access to every tool, the patience to trace data from one system to another, and the willingness to say "this connection is broken" even when the tools appear to be talking to each other.
I've done dozens of integration audits. The most common finding isn't a broken connection — it's a connection that technically works but is syncing the wrong data in the wrong direction on a schedule that no longer matches business reality. A Marketo → Salesforce sync set up in 2019 for a $5M ARR company will look very different from what you need at $50M ARR.
Document every active integration below. For each connection, capture direction, sync frequency, what data moves, and the current health status.
| Source System | Target System | Direction | Sync Frequency | Data Objects Synced | Error Rate | Last Verified | Health |
|---|---|---|---|---|---|---|---|
| Marketing Automation | CRM | Bidirectional | Real-time / 5min | Leads, Contacts, Activity | ___% | ___/___ | Healthy |
| Sales Engagement | CRM | Bidirectional | Real-time | Activities, Tasks, Contacts | ___% | ___/___ | Degraded |
| Revenue Intelligence | CRM | One-way (to CRM) | Daily | Call records, Signals | ___% | ___/___ | Broken |
| CS Platform | CRM | Bidirectional | Daily | Health score, Renewals, NPS | ___% | ___/___ | Unknown |
| CPQ / Billing | CRM | One-way (to CRM) | Real-time (on event) | Orders, ARR, Products | ___% | ___/___ | Healthy |
| Data Enrichment | CRM | One-way (to CRM) | On record creation | Company, Contact fields | ___% | ___/___ | Degraded |
| CRM | BI / Analytics | One-way (to BI) | Nightly | All objects | ___% | ___/___ | Healthy |
| [Add all integrations] | — | — | — | — | — | — | — |
Integration appears active in both tools but data hasn't synced in days or weeks. Most commonly seen in MAP ↔ CRM connections after a tool update or field rename.
Data flows the wrong way, overwriting the authoritative source. A rep updates a field in Salesforce, MAP rewrites it with stale data on the next sync. Field-level sync ownership never set.
Integration creates new records instead of updating existing ones. Root cause: matching rules based on email when records exist with typos, aliases, or role-based emails (info@, hello@).
Bad data is the most expensive thing on your budget that never shows up on your P&L. It wrecks forecast accuracy, poisons marketing campaigns, sends reps chasing the wrong accounts, and makes your reports useless. And it compounds. Every day you ignore it, fresh bad data piles on top of old bad data — the hole gets deeper.
Run these queries directly in your CRM. This is your data health baseline — do this monthly, review quarterly, report to leadership annually.
If win/loss reason completion is below 70%, you have a systemic problem — not a data problem. Reps aren't completing it because there's no enforcement, no consequence, and no visible use being made of the data. Fix the culture first, the data will follow.
| Dimension | Score 1–3 (Poor) | Score 4–6 (Fair) | Score 7–9 (Good) | Score 10 (Excellent) | Your Score |
|---|---|---|---|---|---|
| Completeness | <60% required fields populated | 60–79% populated | 80–94% populated | >95% all required fields | ___/10 |
| Accuracy | >15% records contain known errors | 5–15% error rate | 1–5% error rate | <1% verified error rate | ___/10 |
| Duplication | >20% duplicate rate | 10–20% duplication | 3–10% duplication | <3% duplication, automated prevention | ___/10 |
| Timeliness | Data updated >90 days ago across most records | 30–90 day lag common | Updates within 7 days | Real-time updates; enrichment automatic | ___/10 |
| Consistency | Same field varies widely (30+ lead source values) | Some standardisation, many exceptions | Picklist enforced, rare free-text | Fully normalised, single picklist set enforced | ___/10 |
| Governance | No documented data policies | Some policies exist, not enforced | Policies documented and mostly followed | Automated enforcement + regular audits | ___/10 |
Technology should serve process. In most companies, it's the other way round — process has quietly bent itself to fit what the tools can do, not what the business actually needs. The result is a Frankenstein workflow where people do what automation should handle, and tools create admin instead of eliminating it.
Map every stage of your lead-to-revenue journey against the tools that support it. For each stage, document: what should happen, what tool enables it, and whether there's a gap, redundancy, or friction point.
| Stage | What Should Happen | Primary Tool | SLA | Gap / Issue | Health |
|---|---|---|---|---|---|
| Demand Generation | Campaigns drive inbound; intent data identifies active buyers | MAP + Intent Tool | Continuous | Note findings here | Assess |
| Lead Capture | Forms, chat, event scan capture contact + intent data | MAP + CRM | <5 min to CRM | Assess | |
| Lead Enrichment | Auto-append firmographic + contact data on creation | Data Enrichment | <15 min | Assess | |
| Lead Scoring | Behavioral + demographic score calculated automatically | MAP / CRM | Real-time | Assess | |
| Lead Routing | Auto-assign to correct rep based on rules (segment, territory, round-robin) | Routing Tool / CRM | <5 min from MQL | Assess | |
| SDR Outreach | Rep receives notification; follows up via sequence within SLA | SEP + CRM | <1 hour business | Assess | |
| Meeting Booked | Meeting auto-creates task/activity in CRM; SDR notified AE | SEP + Scheduler + CRM | Immediate | Assess | |
| Discovery / Demo | Call recorded; AI summary pushed to CRM; next step required | RI Tool + CRM | <24 hrs post-call | Assess | |
| Proposal / Quote | CPQ generates quote from CRM opp; approval workflow triggered | CPQ + CRM | <24 hrs from request | Assess | |
| Negotiation / Legal | Contract generated and sent; e-signature workflow active | CLM + e-Sig | Contract returned <48 hrs | Assess | |
| Closed Won | Deal marked closed; handoff to CS triggered; ARR recorded | CRM → CS Platform | Same day | Assess | |
| Onboarding | CS playbook triggered; kickoff scheduled; health score initialised | CS Platform + CRM | Kickoff <5 days | Assess | |
| Expansion / Renewal | Renewal opp auto-created; expansion plays triggered on signals | CS Platform + CRM | 90 days pre-renewal | Assess |
If your reps spend more than 20% of their time on administrative tasks that tools should be doing for them, you don't have a tech problem — you have an implementation problem. The tools usually have the capability. Someone just never configured it or didn't know it existed.
Every RevOps leader gets the call eventually: "We need to cut tool spend by 20%." If you don't have a proper cost map, you're about to make gut-feel decisions dressed up as strategy. This section gives you the framework to make that conversation honest instead of political.
Contract value is never the real cost. True TCO includes everything required to operate the tool effectively.
| Cost Component | Description | Often Missed? | Your Estimate |
|---|---|---|---|
| Contract / License | Annual contract value (ACV) from vendor invoice | No | $_______ |
| Implementation | Professional services, SI fees, internal build time | Sometimes | $_______ |
| Admin Time | FTE hours × loaded cost to administer the tool monthly | Always | $_______ |
| Training | Onboarding cost per new user, ongoing certification | Usually | $_______ |
| Integration Cost | Cost to connect to other tools (Workato, Zapier, dev time) | Always | $_______ |
| Overages | Contact limits, email volume, API call overages | Usually | $_______ |
| Opportunity Cost | What you can't build because this tool takes budget and attention | Always | $_______ |
| True Annual TCO | Sum of all above | — | $_______ |
Complete this for every tool. The "Utilisation Score" is active users ÷ total seats × 100. Cost Per Active User reveals the true unit economics.
| Tool | Layer | Annual Cost | Seats | Active Users | Utilisation % | Cost/Active User | ROI Rating |
|---|---|---|---|---|---|---|---|
| CRM (Salesforce) | L1 | $___,___ | ___ | ___ | ___% | $___ | High |
| Marketing Automation | L2 | $___,___ | ___ | ___ | ___% | $___ | Medium |
| Sales Engagement | L3 | $___,___ | ___ | ___ | ___% | $___ | Medium |
| Revenue Intelligence | L4 | $___,___ | ___ | ___ | ___% | $___ | Low |
| [All remaining tools] | — | — | — | — | — | — | — |
| TOTAL STACK | — | $___,___ | — | — | — | — | — |
For every tool in your stack, answer honestly: (1) What specific, measurable outcome does this tool drive? (2) What would happen to revenue or efficiency if we removed it tomorrow? (3) Is there a cheaper tool, a native feature, or a process change that could replace it? If you can't answer question 1 with a number, the tool is at risk.
| Tool | Measurable Outcome Enabled | Value Driver | Estimated Value | Annual Cost | ROI Multiple |
|---|---|---|---|---|---|
| Sales Engagement Tool | X pipeline created via sequences / month | Pipeline generation | $___ pipeline @ ___% WR | $___ | ___x |
| Revenue Intelligence | X% improvement in forecast accuracy; Y% reduction in ramp time | Win rate / ramp | $___ annual uplift | $___ | ___x |
| Data Enrichment | X hours/week saved on manual research; Y% better MQL conversion | Efficiency + conversion | $___ annual uplift | $___ | ___x |
| CS Platform | X% reduction in churn rate; Y% expansion motion enablement | Net Revenue Retention | $___ retained ARR | $___ | ___x |
Gaps and redundancies are two sides of the same problem: the stack doesn't match what the business actually needs. A gap means something that should be automated isn't — or simply doesn't exist. A redundancy means you're paying twice for the same thing while creating a data consistency problem as a bonus.
Rate your coverage for each GTM capability. Green = fully covered by a healthy tool. Amber = partial coverage or in a tool not actively used. Red = gap — no coverage or severe gaps in capability.
| Capability | Business Criticality | Coverage Status | Tool(s) Covering It | Gap / Note | Action |
|---|---|---|---|---|---|
| Lead capture & form management | Critical | Covered | |||
| Contact & account database | Critical | Covered | |||
| Email marketing & nurture | High | Partial | |||
| Lead scoring & qualification | High | Assess | |||
| Intent data & buyer signals | High | Gap | |||
| Account-based targeting (ABM) | High | Assess | |||
| Sales outreach automation | Critical | Covered | |||
| Meeting scheduling & routing | High | Partial | |||
| Conversation intelligence (calls) | High | Assess | |||
| Deal risk identification | High | Gap | |||
| Pipeline forecasting | Critical | Partial | |||
| Quote-to-cash / CPQ | High | Assess | |||
| Contract management & e-signature | High | Assess | |||
| Customer health scoring | Critical | Partial | |||
| Churn prediction | High | Gap | |||
| Product usage tracking | High | Assess | |||
| NPS & satisfaction tracking | Medium | Assess | |||
| Revenue analytics & attribution | Critical | Partial | |||
| GTM dashboards & reporting | Critical | Assess | |||
| Territory & quota planning | High | Gap | |||
| Compensation management (ICM) | Medium | Assess | |||
| Partner / channel management | Medium | Assess | |||
| Sales training & enablement LMS | Medium | Partial | |||
| Competitive intelligence | Medium | Gap | |||
| Data enrichment / hygiene | High | Assess |
List every capability where you have overlapping tools. For each redundancy, document the resolution path.
| Capability | Tool A | Tool B | Combined Cost | Recommended Action | Savings Potential |
|---|---|---|---|---|---|
| Prospecting data | ZoomInfo | Apollo.io | $___ | Consolidate to one; run 90-day match rate comparison | $___/yr |
| Scheduling | Calendly | Chili Piper | $___ | Standardise on one; Chili Piper if routing needed | $___/yr |
| Workflow automation | Zapier | Workato | $___ | Migrate all Zapier flows to Workato; deprecate | $___/yr |
| Email outreach | Sales Engagement Tool | Marketing MAP | $___ | Define ownership: SEP for 1:1 outbound, MAP for nurture | $0 (governance) |
| [Add your redundancies] |
Every audit needs a number. Not because numbers tell the whole story — they don't — but because a score forces honesty, creates a baseline you can benchmark against, and gives leadership a single thing to hold someone accountable to. That's what this score is for.
| Section | Your Raw Score (0–10) | Weight | Weighted Score | Benchmark |
|---|---|---|---|---|
| Stack Inventory Completeness | ___ | 10% | ___ | 7.5 |
| Integration Health | ___ | 20% | ___ | 6.2 |
| Data Quality | ___ | 20% | ___ | 5.8 |
| Process-to-Tech Alignment | ___ | 15% | ___ | 6.0 |
| Cost & ROI Clarity | ___ | 15% | ___ | 5.2 |
| Gap & Redundancy Resolution | ___ | 10% | ___ | 5.5 |
| Adoption & Utilisation | ___ | 10% | ___ | 6.8 |
| TOTAL REVOPS HEALTH SCORE | — | 100% | ___ | 6.1 |
Score what is, not what you want it to be or what it was after the last cleanup sprint. The value of this framework is in the honesty of the baseline. An inflated score leads to a false sense of security and the wrong priorities. A brutal score leads to action and results.
Dozens of audits across companies from Series A to post-IPO. The same failure patterns show up every single time. They're not unique to your company. They're not even surprising once you've seen them. But they're consistently expensive — and almost always fixable once you know what you're looking at.
Reps enter data after the deal closes, not during the process. The CRM records outcomes, not the journey. That means no activity data, no stage history, no competitive intelligence — just a grave marker for opportunities that already happened.
The hardest truth in RevOps is this: reps don't update the CRM because they don't believe the CRM helps them sell. And often they're right. If data entry doesn't save them time, surface better insights, or make their manager's coaching more precise — why would they do it? Fix the value proposition of the CRM for reps, and the data quality follows.
You're licensed for tools nobody uses. They were purchased by a previous leader, or bought for a use case that never materialised, or rolled out without proper enablement. The vendor keeps billing. Nobody notices because the contract auto-renewed and finance doesn't know what it's for.
The integration is technically active. Both tools show a green checkmark. But the data flowing between them is wrong — wrong fields, wrong direction, stale timestamps, or incomplete records. You won't find this in the tool dashboard. You find it when a rep calls a prospect who's been in a marketing sequence for three weeks and has no idea what they're talking about.
Marketing measures MQL one way, Sales measures it another. Finance uses a different ARR definition than RevOps. "Pipeline" means one thing to the CRO and something else in the board deck. You spend 20 minutes in every weekly sync arguing about whose numbers are right instead of what to do about them.
Lead scoring was built three years ago when the ICP was different, the product had fewer features, and the buyer journey looked nothing like it does today. But the model hasn't been touched. Marketing celebrates hitting MQL targets while Sales ignores 40% of the leads they receive — because they already know by experience that certain source/score combinations are junk.
There are reports. There might even be beautiful reports. But nobody refers to them when making decisions because everyone knows the underlying data is flawed. Managers pull their own spreadsheets. Leaders triangulate from three different sources. The BI investment is wasted because the data foundation was never fixed first.
SDRs found an AI outbound tool that writes their emails. A marketing manager signed up for a landing page builder on their credit card. Sales is using a WhatsApp group to coordinate account strategy. None of it is in the CRM. None of it is connected. All of it is creating customer data that's invisible to your reporting and potentially violating data compliance requirements.
An audit without a roadmap is just an expensive anxiety attack. This section converts your findings into sequenced actions with clear owners — a 90-day plan you can actually execute without burning your team to the ground in the process.
Before building the roadmap, prioritise every finding using this simple filter:
Fix This Week. Revenue is being lost or data is actively being corrupted right now. Broken integrations, duplicated lead routing, critical CRM data errors. Drop everything else.
Fix This Month. Significant friction or cost, but not actively losing deals. Poor data quality, high-value shelfware, process misalignment. Assign an owner today, start work this week.
Fix This Quarter. Optimisation opportunities. Redundancy consolidation, scoring model calibration, BI improvements. Plan and resource properly.
Plan & Evaluate. New capability gaps, strategic tool investments, advanced analytics. Requires budget approval, longer planning cycle. Document and revisit next quarter.
| Action Item | Priority | Primary Owner | Supporting Team | Target Date | Status |
|---|---|---|---|---|---|
| Complete tool inventory | P0 | RevOps Lead | IT, Finance | Day 5 | Not Started |
| Fix [broken integration] | P0 | RevOps Admin | IT | Day 7 | Not Started |
| CRM data quality baseline | P1 | CRM Admin | RevOps | Day 14 | Not Started |
| Lead scoring calibration | P1 | Marketing Ops | RevOps, Sales | Day 45 | Not Started |
| Tool redundancy consolidation | P1 | RevOps Lead | Finance, IT | Day 60 | Not Started |
| GTM Metrics Glossary | P1 | RevOps Lead | Sales, Marketing, CS, Finance | Day 45 | Not Started |
| Gap: [Add gap here] | P2 | [Owner] | [Team] | Day ___ | Not Started |
| Strategic investment: [Add] | P3 | [Owner] | [Team] | Next Quarter | Planning |
A great RevOps stack isn't the most sophisticated one. It's the one that's fully adopted, correctly integrated, and trusted by every team that depends on it. Start with trust. Trust comes from data quality. Data quality comes from governance. Governance comes from leadership commitment. That's the whole game. Everything else is implementation details.
| Metric | Below Average | Average | Best in Class | Your Score |
|---|---|---|---|---|
| MQL-to-SQL conversion rate | <20% | 25–35% | >45% | ___% |
| SQL-to-Opportunity rate | <50% | 55–65% | >70% | ___% |
| Lead response time (to MQL) | >2 hours | 15–60 minutes | <5 minutes | ___min |
| CRM field completion rate (required) | <70% | 75–85% | >92% | ___% |
| Forecast accuracy (within 10%) | <60% quarters | 65–75% quarters | >80% quarters | ___% |
| Tool utilisation (active/licensed) | <50% | 55–70% | >80% | ___% |
| Data duplicate rate (Contacts) | >20% | 10–20% | <5% | ___% |
| Win rate (from Qualified Opp) | <15% | 20–30% | >35% | ___% |
| Stack cost as % of ARR | >8% | 4–7% | <3% | ___% |
| Average deal cycle (Mid-Market) | >120 days | 60–90 days | <45 days | ___days |
| Net Revenue Retention (NRR) | <100% | 105–115% | >120% | ___% |
| Gross Revenue Retention (GRR) | <80% | 85–90% | >93% | ___% |
| Dimension | Level 1 — Ad Hoc | Level 2 — Defined | Level 3 — Managed | Level 4 — Optimised |
|---|---|---|---|---|
| Data Strategy | No formal data policy; reps decide what to enter | Basic required fields; manual hygiene sprints | Governance policies enforced; automated enrichment | Real-time data quality monitoring; predictive enrichment |
| Integration Architecture | Point-to-point integrations; mostly manual | Core integrations exist; some documented | All integrations documented; monitored; error alerts | Event-driven architecture; real-time data mesh |
| Process Design | Process is tribal knowledge; varies by rep | Key processes documented; mostly followed | Processes enforced via tools; SLAs tracked | Processes continuously optimised from performance data |
| Analytics | Spreadsheets; no agreed definitions | CRM reports; some agreed metrics | BI layer; single source of truth; certified dashboards | Predictive analytics; ML-driven insights; real-time GTM intelligence |
| Tool Governance | No approval process; shadow stack common | Basic approval; some tool owners assigned | Formal approval; utilisation tracking; regular reviews | Automated governance; spend management integrated; vendor portal |
Use this as the starting point for your agreed definitions. Every metric below should have a documented definition, a designated source of truth, and a named owner responsible for its accuracy.
| Metric | Definition | Formula | Source of Truth | Owner |
|---|---|---|---|---|
| MQL (Marketing Qualified Lead) | [Define here — be specific about score threshold, source, and disqualifying criteria] | Score ≥ ___ AND Persona = ICP | MAP / CRM | Marketing Ops |
| SQL (Sales Qualified Lead) | [Define here — what has Sales accepted and agreed to work] | MQL + SDR accepted + BANT criteria met | CRM | Sales Ops |
| Opportunity / Pipeline | [Define here — what makes an opp vs a lead] | Qualified + ACV entered + Stage ≥ Discovery | CRM | RevOps |
| ARR (Annual Recurring Revenue) | [Define here — how multi-year deals, one-time fees, and services are treated] | Monthly recurring revenue × 12 | Billing system / CRM | Finance / RevOps |
| Win Rate | [Define here — closed won / (closed won + closed lost) — include disqualified?] | CW / (CW + CL) in period | CRM | RevOps |
| Pipeline Coverage | [Define here — pipeline at start of quarter / quota] | Open pipeline / Quota target | CRM | RevOps |
| NRR (Net Revenue Retention) | [Define here — starting ARR + expansion - contraction - churn] / starting ARR | (Start ARR + Expansion - Contraction - Churn) / Start ARR | Billing / CS Platform | Finance / CS Ops |
| Time to Close | [Define here — from what date, to what date] | Closed Date - Opportunity Created Date | CRM | RevOps |
