What actually belongs in a RevOps stack

Salesforce, HubSpot, ZoomInfo, Gong, Outreach, RingLead, ChurnZero, Chili Piper, Pendo, Power BI, Looker, Tableau, and Snowflake.

Sapwood is a revenue operations and GTM engineering shop in Denver.The audit is free. Retainer $4,000 a month, Kaypo included.
See every price

A working RevOps stack has five layers: a CRM as the system of record, enrichment and intent data, engagement tooling, conversation intelligence, and a reporting layer. Most small and mid market companies need fewer tools than they own. The most common failure is buying a category before defining the process it is meant to support.

Last updated October 12, 2026

The five layers

Bought tools nobody configured?

Stack implementation sits inside the retainer, covering configuration end to end rather than to the end of a trial.

How stacks go wrong

Buying before defining

A tool cannot decide what a qualified lead is. Purchasing one to avoid that decision produces an expensive version of the same confusion.

No owner per tool

Every product needs a named person accountable for whether it is configured and used. Without that, licenses renew for software nobody opens.

Overlapping categories

Two enrichment vendors, three reporting surfaces, and an engagement tool that duplicates the CRM. Common, and usually invisible until someone audits the spend.

Configured to the end of the trial

The single most common finding. Six figures of licensing running at a fraction of its capability.

What we work in

Stack implementation sits inside the retainer at $4,000 a month. We take no commissions from any vendor, so a recommendation to drop a tool costs us nothing.

LayerWhat it does
CRMThe system of record. Everything else attaches to it. Get this right before anything else.
Enrichment and intentFirmographics, contact data, and buying signals. Valuable only if it lands on records that are already clean.
EngagementSequences, cadences, and scheduling. Amplifies whatever process exists underneath it.
Conversation intelligenceCall recording and analysis. The best coaching tool available, and the most underused.
ReportingNative CRM reporting, a BI tool, or both. Should sit on definitions everyone has agreed.

Questions

How many tools does a small revenue team need?

Usually four or five. A CRM, one enrichment source, one engagement tool, conversation intelligence if the team is coachable, and a reporting surface.

Should we buy intent data?

Only after your CRM data is clean and routing works. Intent landing on duplicate records with no owner produces nothing.

What is the most commonly wasted spend?

Licenses for tools configured during a trial and never revisited. It is the single most frequent finding in an audit.

Do you resell any of these tools?

No. We take no partner commissions, so telling you to cancel something costs us nothing.

Can you set up a tool we already bought?

Yes. Stack implementation sits inside the retainer, covering configuration end to end rather than to the end of a trial.

Tools and stack

Related reading, all of it free.

How do we get more out of ZoomInfo than just list pulls?Should we consolidate onto one platform or keep a best of breed stack?Lead scoring tools, and why the model matters more than the toolMeeting scheduling tools, and where bookings leakSales compensation tools, and the plan underneath themCPQ tools, and whether you actually need oneB2B contact databases, and how to compare them honestlyProduct analytics for go-to-market, not for productSales enablement tools, and why content goes unusedPipeline management tools, and the hygiene problem underneathRevOps tools, and the order to buy them inCRM data quality tools, and what they cannot fixCustomer success platforms, and what health scores missABM platforms, and what has to be true before they workRevenue intelligence platforms, and what they are actually forReverse ETL, and when your warehouse should drive the CRMConversation intelligence tools, and what to do with the outputSales engagement platforms, and the thing that decides reply rateAI RevOps tools, and what each actually automatesWhere AI actually helps in RevOps, and where it does notData enrichment tools, and what each one is actually forIntent data providers, and what the signal actually tells youCRM deduplication tools, and why merging is the easy halfRevenue attribution tools, and what none of them can fixSales forecasting tools, and the input that decides whether any of them workLead routing tools, and the mechanics that decide speed to leadFractional RevOps against buying more RevOps softwareWe are paying for tools nobody uses. What now?Before you add another tool, we make the spend worth it.What a HubSpot consultant should doWhat a Salesforce consultant should doGo-to-market engineering, not another dashboard .Check your own revenue system, free →

Let us look under the hood

Read-only access to your systems, and a written report you keep either way.

Start the free audit

Let's chat

Thirty minutes. Tell us what you are working on and we will tell you on the call whether we can help.

Add your name and a work email so we know who we are talking to.

Thank you!

We will reach out to you shortly. If you have not heard from us by tomorrow, email hello@sapwood.io.

While you wait, keep reading