TL;DR
- Six layers, not one tool: A complete RevOps stack covers CRM, marketing automation, sales engagement, data and analytics, customer success, and finance integration. Most teams have gaps in at least two layers.
- Tool sprawl is expensive: Companies waste an average of $18M per year in redundant SaaS spend (Zylo, 2024). The average organization uses only 49% of its provisioned licenses.
- Data fragmentation is the real cost: Disconnected tools mean no single source of truth for pipeline, churn, or margin — every decision requires manual reconciliation across systems.
- The operating intelligence layer is missing from most stacks: Most RevOps teams can see what revenue came in. Few can see whether that revenue was profitable, or where margin is leaking.
- Audit before you add: Run through this checklist before purchasing anything new. Consolidation almost always delivers more ROI than net-new tools.
The average mid-sized company runs more than 100 SaaS applications. Revenue operations teams sit at the center of that sprawl — managing or depending on tools across marketing, sales, customer success, finance, and data infrastructure. The result, in most cases, is not a coherent stack. It is a collection of point solutions that were bought by different teams at different times, integrated partially, and never rationalized.
This checklist is designed to give RevOps leaders, COOs, and operators a clear inventory framework — organized by the six functional layers that every mature revenue stack needs to cover. Use it to audit what you have, identify gaps, and build a consolidation plan before your next renewal cycle.
For context on how this stack connects to operating performance, see How to Build a RevOps Team and The 10 Best AI Tools for Revenue Operations in 2026.
Why RevOps Tech Stacks Break Down
Most RevOps stacks were not designed — they accumulated. Marketing bought a marketing automation platform before sales ops existed. Sales ops added a CRM before anyone thought about data warehouse architecture. Customer success added a health scoring tool that does not integrate cleanly with the CRM. Finance runs on a separate system that nobody in RevOps can access in real time.
According to Zylo's 2024 SaaS Management Index, companies leave an average of $18 million per year on the table in wasted SaaS spend. Gartner estimates that approximately 30% of global SaaS spend — roughly $90 billion — goes to unused licenses, underutilized features, and redundant applications. The average organization uses only 49% of its provisioned software licenses.
For RevOps, the cost of a broken stack is not just financial. It is operational. When each tool holds a partial view of the customer — the CRM has deal history, the marketing automation platform has engagement data, the billing system has actual revenue — there is no single source of truth. Every business review requires hours of manual reconciliation across exports, and every decision is made with incomplete information.
The checklist below does not tell you which tools to buy. It tells you which problems need to be solved and what category of tooling solves them — so you can evaluate what you have against what you need.
The RevOps Tech Stack Checklist
Layer 1: CRM (Customer Relationship Management)
The CRM is the system of record for every customer-facing interaction. It is the foundation every other layer depends on. A CRM that is poorly configured, inconsistently used, or understaffed will degrade every AI and analytics tool built on top of it.
CRM Layer Checklist
- Single CRM instance as the authoritative system of record for all accounts and contacts
- Defined pipeline stages with clear entry/exit criteria documented and enforced
- Mandatory fields enforced at each stage (next step, close date, contact, deal value)
- Activity logging policy — calls, emails, and meetings captured (manual or via auto-capture tool)
- Deduplication process in place — contacts, accounts, and deals reviewed on a regular cadence
- CRM admin or RevOps owner responsible for data quality and configuration changes
- User adoption rate tracked — percentage of reps logging activity within SLA
- Integration with marketing automation for lead-to-opportunity flow
Common tools: Salesforce Sales Cloud, HubSpot CRM, Pipedrive, Attio, Microsoft Dynamics
Layer 2: Marketing Automation
Marketing automation handles lead capture, nurture sequences, campaign execution, and the handoff of marketing-qualified leads to the sales team. It is the highest-volume data system in most RevOps stacks — and the most likely to become siloed from the CRM if integration is not maintained carefully.
Marketing Automation Checklist
- Two-way sync with CRM — lead status, lifecycle stage, and contact data flowing in both directions
- MQL definition documented and aligned between marketing and sales — no ambiguity on what triggers handoff
- Lead scoring model in place — behavioral and firmographic signals weighted and reviewed quarterly
- Nurture sequences mapped to lifecycle stage — not every lead should go to the same sequence
- UTM tagging and source attribution consistent across all campaigns and channels
- Suppression lists maintained — unsubscribes, bounces, and active customers excluded from prospecting campaigns
- Email deliverability monitored — domain reputation, bounce rate, and spam complaint rate tracked monthly
- Campaign performance reporting connected to pipeline influenced, not just email metrics
Common tools: HubSpot Marketing Hub, Marketo (Adobe), Pardot (Salesforce), ActiveCampaign, Klaviyo (e-commerce), Brevo
Note on cost: Marketo for a mid-market company with 10,000 contacts commonly exceeds $200,000 in year-one total cost of ownership once implementation is included. A comparable HubSpot deployment runs $30,000–60,000 per year. The right choice depends on CRM architecture, team technical capacity, and integration requirements — not feature lists alone.
Layer 3: Sales Engagement
Sales engagement platforms manage outbound sequencing, call workflows, and rep activity across the prospecting and early-stage pipeline. They sit between the CRM (system of record) and the rep (point of execution), automating the workflow so reps spend less time on scheduling and sequencing and more time in conversations.
Sales Engagement Checklist
- Outbound sequences defined by ICP segment, persona, and deal stage — not a one-size-fits-all cadence
- CRM activity sync — all calls, emails, and meetings logged to the correct record automatically
- Sequence performance tracked — reply rate, meeting booked rate, and opt-out rate reviewed by sequence
- Call recording in place — whether via the engagement platform or a standalone conversation intelligence tool
- Meeting booking integrated — calendar link or scheduling tool connected to reduce friction on inbound responses
- Rep activity reporting — dials, emails sent, connects, and meetings booked reported per rep per week
- A/B testing cadence — subject lines and messaging variants rotated to improve sequence performance over time
- Governance process for sequence creation — new sequences reviewed before deployment to avoid conflicting outreach
Common tools: Salesloft, Outreach, Apollo.io, Reply.io, Groove (Salesforce), HubSpot Sequences
Layer 4: Data and Analytics
The data and analytics layer is where pipeline data, marketing data, product data, and financial data converge into the reports and dashboards that drive operating decisions. It is the layer most likely to be underfunded relative to the value it produces — and the layer whose absence is most often felt when the CRO asks a question nobody can answer in less than 48 hours.
Data and Analytics Checklist
- Data warehouse or data lake in place — all source systems writing to a central store (Snowflake, BigQuery, Redshift, or DuckDB for smaller teams)
- ETL or reverse ETL pipeline configured — source-to-warehouse and warehouse-to-CRM data flows defined and monitored
- Core revenue metrics defined in code — ARR, NRR, CAC, LTV, churn rate calculated consistently from a single source
- BI tool with shared dashboards accessible to RevOps, Sales, Marketing, Finance, and CS — no team living exclusively in exports
- Pipeline health dashboard updated daily — stage distribution, velocity by segment, stalled deals, and win rate by source
- Forecast model in place — AI-assisted or manual, reviewed weekly against actuals
- Data dictionary maintained — every metric defined, owner assigned, and calculation documented
- Alert system for anomalies — significant pipeline drops, conversion rate changes, or cost spikes trigger notification before the weekly review
Common tools: Snowflake, BigQuery, Redshift (warehouse); Fivetran, Airbyte (ETL); Looker, Tableau, Metabase, Power BI (BI); Clari, Gong Forecast (pipeline forecasting)
This is the layer where operating intelligence adds the most leverage. Most RevOps data stacks answer questions about revenue: what closed, what is in pipeline, where is the forecast. Platforms like Fairview sit above the analytics stack to connect that revenue data with cost and margin data from the finance system — so operators can see not just whether they are hitting the number, but whether the number is worth hitting.
Layer 5: Customer Success
Customer success tooling manages retention, expansion, and health scoring for existing customers. In subscription businesses, CS is where the majority of revenue is at risk — the cost to replace a churned customer is three to five times higher than the cost to retain them. Yet CS is frequently the most underinvested layer in the RevOps stack.
Customer Success Checklist
- Customer health score defined — product usage, support ticket volume, NPS or CSAT, billing status, and stakeholder engagement combined into a single score
- Health score updated automatically — not manually entered by CSMs once a quarter
- Renewal pipeline tracked in the CRM — renewal date, ARR at risk, and ownership assigned for every account
- Churn risk playbooks documented — specific triggers that initiate a rescue sequence (health score drop, usage decline, executive departure)
- QBR (quarterly business review) process in place for strategic accounts — template, frequency, and ownership defined
- Expansion pipeline tracked separately from new business — upsell and cross-sell opportunities managed as distinct pipeline stage
- Product usage data piped into CS platform — CS team can see in-app behavior without asking the product team for a report
- NPS or CSAT program running — survey cadence, response rate, and trend tracked over time
Common tools: Gainsight, ChurnZero, Totango, Vitally, HubSpot Service Hub, Zendesk
Layer 6: Finance Integration
The finance integration layer connects billing, revenue recognition, and accounting data to the RevOps stack. Without it, RevOps teams cannot answer questions about actual revenue versus contracted revenue, gross margin by customer segment, or the cost structure behind a deal. Most RevOps stacks treat finance as a separate function — finance runs their own reports, RevOps runs theirs, and reconciliation happens once a month at best.
Finance Integration Checklist
- Billing system integrated with CRM — subscription status, MRR/ARR, and payment events visible on account records
- Revenue recognition process defined — contracted ARR versus recognized revenue versus billed revenue tracked separately
- COGS (cost of goods sold) attributed at the customer or segment level — not just as a company-wide line item
- CAC calculated correctly — sales and marketing spend divided by new customers acquired in the same period, not blended with expansion
- LTV:CAC ratio tracked by cohort and segment — not just as a company average
- Gross margin by product line or customer segment visible to RevOps — not just to the CFO
- Finance data in the data warehouse — accounting exports in the same store as CRM and marketing data
- Monthly close process aligned between RevOps and Finance — no more than 5 business days from month-end to closed books
Common tools: NetSuite, QuickBooks, Xero (accounting); Stripe, Chargebee, Zuora (billing); Ramp, Brex (spend management); Fairview (operating intelligence connecting finance and revenue data)
The Layer Most RevOps Stacks Are Missing
Most RevOps stacks are reasonably complete at the individual layer level. Teams have a CRM. They have some form of marketing automation. They have a BI tool producing dashboards. The problem is that these layers operate in parallel, not in concert. Pipeline data lives in the CRM. Campaign performance lives in the marketing automation platform. Gross margin lives in the finance system. Customer health lives in the CS platform. No single tool connects them.
The result is that RevOps teams can answer individual questions — "what is in pipeline," "what did marketing spend last quarter," "which customers are at churn risk" — but cannot answer the compound question that actually drives operating decisions: "which segments are growing profitably, which are not, and what should we do differently next quarter."
This is the problem operating intelligence is designed to solve. Fairview sits above the RevOps stack — ingesting data from the CRM, the marketing platform, the billing system, the data warehouse, and the finance layer — and producing a unified view of revenue, cost, and margin across every function. Not as a replacement for any individual tool, but as the synthesis layer that connects them.
For a deeper look at how this layer works in practice, see What Is Operating Intelligence? and CFO Dashboard: The Financial Metrics That Matter.
How to Run a RevOps Stack Audit in 30 Days
Most RevOps teams approach stack audits reactively — triggered by a budget review, a contract renewal, or a data quality problem that finally became impossible to ignore. A proactive audit process, run annually, prevents the accumulation of redundant tools and keeps data fragmentation from compounding.
Week 1 — Inventory. List every tool currently active across the six layers. Include tools owned by marketing, sales, CS, finance, and product that have a revenue operations dependency. For each tool, document: vendor, annual cost, primary owner, integration points, and estimated license utilization rate. Zylo research shows average license utilization across SaaS stacks is 49% — most teams will find immediate savings before ever evaluating new tools.
Week 2 — Gap analysis. Map your inventory against the six-layer checklist above. Identify where you have gaps (no tool covering the function), redundancy (two tools solving the same problem), or broken integrations (tool exists but data does not flow to the rest of the stack).
Week 3 — Integration audit. For every tool pair that should be syncing data, verify the sync is working and the data quality is acceptable. CRM-to-marketing automation sync, billing-to-CRM sync, and CRM-to-data warehouse sync are the highest-risk failure points. Broken integrations are common — tools get upgraded, field mappings break, and nobody notices until a sales rep cannot see a customer's billing status.
Week 4 — Consolidation plan. Identify the top three to five tools that are either redundant, underutilized, or generating more data fragmentation than value. Build a consolidation case for each: estimated annual savings, migration effort, and replacement timeline. Present to the CFO and CRO before the next renewal cycle.