A founder texted me last month with a screenshot of his tool stack. Forty-one logos. Annual cost: $387,000. ARR: $4.2M. He asked me which tools to cut.
The honest answer was: most of them.
I have run RevOps audits on about 40 B2B companies over the last three years, ranging from pre-seed to mid-stage Series B. The pattern is the same every time. Tools get bought to solve a moment of pain. Nobody removes them when the pain passes. The stack grows. The data fractures. The CFO eventually asks what all of this is doing for pipeline, and nobody has a clean answer.
This post is about the opposite. What is the smallest possible RevOps tech stack that lets a B2B team go from cold outbound to closed-won without leaking data, attribution, or budget. I am going to name specific tools and prices. I am also going to tell you what to skip.
The default stack most teams end up with
Before I get to what works, here is what I see when I open a typical Series A RevOps stack:
- HubSpot or Salesforce as the CRM
- A separate marketing automation platform that overlaps 80% with the CRM
- Two sales engagement tools because somebody piloted both
- Three enrichment vendors with overlapping data
- A scheduling tool that costs more than the CRM seat
- A conversational intelligence tool that nobody listens back on
- An ABM platform that nobody logs into
- A data warehouse that one engineer set up and then left
- Half a dozen point automation tools
Combined cost: $200K to $500K per year. Combined value: maybe a third of that.
The problem is not that any of those tools are bad. It is that nobody designed the stack. Each one got bought to plug a hole. The integrations are duct tape. The reporting is impossible because every tool owns part of the truth.
Average waste in B2B RevOps tech budgets we audit. Two thirds of the spend goes to tools that overlap, duplicate, or sit unused.
The five jobs a RevOps stack actually has to do
Strip the marketing back and the stack has to do five things. That is all. Every tool you own should belong to one of these jobs. If it does not, cut it.
- Record the truth. One system holds accounts, contacts, deals, and revenue history. Nothing else gets to be the source.
- Find and qualify accounts. Enrichment, signals, and intent that turn a list of companies into a list of accounts worth working.
- Reach the buyer. Outbound and inbound delivery: email, calls, LinkedIn, ads, forms.
- Run the work. Workflows and automation that move data, send messages, and route leads without humans copy-pasting.
- Show the numbers. Reporting and dashboards that tell the team what to do tomorrow.
That is the whole job. Five layers. Most stacks have 12.
Layer 1: the CRM
This is the heart of the stack. Get it right and the rest is easy. Get it wrong and no amount of tooling will save you.
For B2B companies up to about 300 employees, HubSpot is almost always the right call. It is faster to set up, the UI is decent, and the workflow engine is genuinely good now. Sales Hub Professional starts at $100 per user per month. Marketing Hub adds another layer if you need it.
For companies above 300 with complex sales motions, multi-product portfolios, or heavy customization needs, Salesforce starts to make sense. Not before. Most teams that pick Salesforce at Series A regret it within 18 months. The implementation cost alone runs $150K to $400K, and you need a full-time admin.
Attio is the wild card. It is what HubSpot would be if it was rebuilt today. Flexible data model, fast UI, decent API. I have moved two clients onto it in the last six months. The reporting is still thin and the workflow engine is younger than HubSpot's. Watch this one.
What to skip in this layer:
- Any CRM that does not have a real API
- "Industry-specific" CRMs that lock you into one motion
- Anything that needs more than a week to set up for under 50 users
We wrote a full breakdown of how to pick between HubSpot and Salesforce in our CRM and RevOps work and a migration playbook if you are already stuck on the wrong one.
Layer 2: find and qualify
This is the layer most teams overspend on. They buy ZoomInfo, Apollo, Lusha, Cognism, and an intent vendor on top, then run all five in parallel. The data still has gaps.
The way to do this in 2026 is waterfall enrichment. One tool, multiple data providers, fallback logic. You pay only for what you actually pull. Clay is the leader here. About $349 per month gets you a real account. It is the single best tool I have added to a B2B stack in the last two years.
Clay does three things at once:
- Finds and verifies contact data across 50 providers
- Adds firmographic and technographic fields on demand
- Watches signals (hiring, funding, tech changes, news) and writes them back to the CRM
A startup with 200 target accounts can build a full enriched list for under $500 in credits. That same list from ZoomInfo plus an intent provider would run $40K a year.
What to skip:
- Any enrichment tool that charges per-seat instead of per-credit
- Intent data products that send you 10,000 "interested" accounts per week with no signal logic
- ABM platforms above $50K a year unless you have already proven the motion
For most teams, Clay plus a small LinkedIn Sales Navigator seat ($99 per user per month) is enough to feed the entire pipeline. We dig into the signals side in our buyer intent guide.
Layer 3: reach the buyer
This is where companies usually have too many tools. Sales engagement platforms, email warming tools, LinkedIn automators, voicemail drop, dialers.
The 2026 reality is that you need one sales engagement tool, one cold outbound infrastructure, and ads if you can afford them. That is it.
For sales engagement, the choice is HubSpot Sequences if you are on HubSpot, Outreach or Salesloft if you have a real outbound team of 5+ SDRs. For under five SDRs, HubSpot Sequences is good enough. Spending $130 per SDR per month on Outreach for a three-person team is wasted money.
For cold outbound infrastructure, you need Smartlead or Instantly plus a separate sending domain. Around $99 per month. Cold email and your main HubSpot-connected domain should never share the same DNS. If you do not separate them, one bad campaign burns your main inbox and breaks your inbound replies for a month.
What to skip:
- Two sales engagement tools in parallel
- LinkedIn automation tools that risk your sales reps' accounts
- Dialers if your reps do not actually call
If you want the deeper version on this, the cold email deliverability piece covers exactly how to set up the second domain.
A clean stack has one tool per job, not three.
Every duplicate vendor in your stack is a place where your data and reporting will eventually disagree. Pick one, kill the others, and accept that the chosen tool will not be perfect.
Layer 4: run the work
This is the layer that quietly decides whether the whole stack works. Without an automation layer, every other tool is an island and somebody is exporting CSVs at midnight.
For most teams, HubSpot Workflows handles 70% of the automation needs. The other 30% is the stuff that lives between systems: pulling enriched data from Clay back into the CRM, routing leads based on territory, sending Slack alerts when a target account hits a signal, syncing data to the warehouse.
That is where n8n comes in. It is open source, self-hosted, GDPR-safe, and runs about $20 a month on a small VPS. It connects almost anything. Zapier can do similar things, but the per-task pricing makes it expensive at scale and the data still leaves your perimeter.
The pattern I now build for clients:
- HubSpot Workflows for everything that lives entirely inside HubSpot
- n8n for cross-system orchestration, enrichment writeback, and Slack notifications
- One named owner. Always. Automation without an owner becomes shelfware in six months.
We covered the n8n side in detail in our n8n RevOps guide, and the wider workflow patterns are in the HubSpot workflows playbook. The wider AI automation work we do for clients is mostly built on top of this layer.
Layer 5: show the numbers
The mistake here is jumping to a BI tool too early. Most Series A teams do not need Looker or Tableau. They need three or four good HubSpot dashboards that the leadership team actually opens.
For under 50 employees, HubSpot dashboards are enough. Build five views: pipeline by stage, pipeline by source, deal velocity, SDR activity, win/loss by segment. That is the entire reporting layer.
For above 100 employees, when you have multiple products, partner channels, and a real finance team, you start needing a warehouse. The minimal version is Fivetran plus BigQuery plus Metabase. That stack runs around $1,500 to $3,000 per month and gives you proper attribution, cohort analysis, and revenue forecasting.
What to skip until you genuinely need it:
- BI tools at under 50 employees
- Multi-touch attribution platforms before you have 500 closed deals
- AI-powered forecasting tools that just resell your own CRM data back to you
The actual stack: what I build for a Series A team
Here is the stack I have built five times in the last year for B2B SaaS teams between $1M and $10M ARR. Total cost: about $2,800 per month for 15 users, all in.
A few notes on this.
The team has nothing for conversational intelligence. Most three to seven person sales teams do not need it. The cost of Gong is hard to justify until you have at least 10 AEs who are actually being coached on the recordings. Before that, a $30 per month transcription tool gives you 80% of the value.
There is no separate marketing automation platform. HubSpot Marketing Starter is included in the seat cost. For under 10K contacts and basic nurture sequences, that is enough. Marketo and Pardot are vestigial purchases for most companies that buy them.
There is no separate data warehouse. The reporting lives in HubSpot. We add Fivetran and BigQuery later, usually around the $5M ARR mark.
This stack will run a $1M to $15M ARR B2B team comfortably. Past that you start adding complexity: a warehouse, multi-product reporting, regional CPQ rules. But the core five layers do not change.
Where teams overspend
Three patterns come up in almost every audit I run. If your stack has any of these, you can probably cut 40% of the spend without losing capability.
The other thing I see: teams paying for AI features that are already in HubSpot or Clay. The vendors selling "AI-powered prospecting" or "AI-driven forecasting" as standalone products are mostly arbitraging the buzzword. Check what your existing tools already do before adding another logo.
How to actually rebuild your stack
If you are reading this and realising your stack is the messy version, here is the order I run a cleanup in.
First, list every tool you pay for and what job it does from the five layers. If a tool does not fit one of those jobs, it is a candidate to cut. If two tools do the same job, one of them goes.
Second, check usage. Most SaaS platforms have admin-level usage reports. Anything with under 20% of seats logged in monthly is a cut candidate. Anything with under 5% is gone.
Third, map the integrations. Where does each tool sync with the CRM? What gets pushed and what gets pulled? If a tool is not integrated with HubSpot, it is probably a data island and you are losing reporting on whatever it touches.
Fourth, rebuild from the CRM out. The CRM stays. The waterfall enrichment tool stays. The sales engagement tool stays. Everything else has to justify itself against the five-layer test.
This is what we do for clients in our GTM and RevOps engagements. A typical audit cuts 30% of the budget in the first month and rebuilds the reporting in the second. The team gets a cleaner pipeline view and the CFO gets back about $80K to $200K a year, depending on team size.
Stack feels bloated? Let us audit it.
Book a free 30-minute RevOps stack review. We will tell you which tools to cut, which to keep, and where the data is currently leaking.
Book a stack audit →FAQ
What is a RevOps tech stack?
A RevOps tech stack is the set of tools that supports your end-to-end revenue process: CRM, enrichment, sales engagement, automation, and reporting. A good stack has one tool per job, not three.
How much should a B2B company spend on RevOps tools?
For Series A teams between $1M and $10M ARR, total tooling spend should sit around $2,500 to $5,000 per month for 10 to 20 users. Past that, you are usually paying for overlap.
Do I need Salesforce if I have a small B2B team?
No. Below 300 employees, HubSpot is almost always the better choice. Salesforce makes sense when you have complex sales motions, multi-product portfolios, or compliance requirements that demand deep customization.
What is the cheapest way to enrich CRM data in 2026?
Clay is the most efficient option for most B2B teams. It does waterfall enrichment across 50 providers, charges by credits used, and writes data back to the CRM. A 200-account list typically runs under $500 in credits.
When should I add a data warehouse?
Around $5M ARR or 100 employees, whichever comes first. Before that, HubSpot dashboards handle 90% of what leadership needs. Add Fivetran, BigQuery, and Metabase when you start needing multi-product reporting or proper attribution.