The sales tech market is noisy. Established players are adding AI fast, new AI native alternatives keep appearing, and today’s favorite may be old news tomorrow.
Start by understanding what you actually need. What is slowing growth? Which capability is missing? What matters now, and what can wait?
Then ask whether today’s solution will still fit tomorrow. Can you add new capabilities without rebuilding the whole system?
Start with the bottleneck. Add the right capability at the right stage. Build a connected system your team can actually run.
The names included here are examples, not rankings, endorsements, or a shopping list.
9 funnel categories. 4 ARR stages. Foundation underneath.
9
Funnel categories
3
Funnel stages
4
ARR stages covered
4
Questions to build your map
Where the gaps usually are
Find Buyers
Find the right company at the right time
Move Deals
Help opportunities progress
Close Revenue
Improve win rates and predict revenue
Foundation
CRM & Revenue OS
Automation & orchestration
Not a funnel stage, the plumbing underneath every other category. Intent data, enrichment, outreach activity, call notes: all of it has to land somewhere and move between tools without manual relay. CRM is where it lands. Automation is how it moves. This is assumed, not ranked.
Some of the names you'll run into
Clay
Artisan (Ava)
Oliv AI
Warmly
n8n
6sense
Apollo
LinkedIn Sales Nav
Gong
HubSpot
PandaDoc
RB2B
Cognism
Qualified
Clari
ZoomInfo
A few things worth knowing
Region shapes everything
Tool performance varies by geography. What works in the US might not be relevant in EMEA or APAC. Test it before you commit.
This map can't see your buyer
ARR and team structure get you most of the way, but not all of it. Selling into HR tech, where you can't see what's running inside the buyer's stack, makes intent prediction critical. Selling into martech, where KPIs shift across verticals, makes messaging and personalization the harder problem.
Can Claude replace this category?
Sometimes. If the job is mainly thinking or writing, Claude may already cover it: research, sequence drafts, call summaries, list scoring, or even a lightweight internal assistant. You can also build custom workflows with Claude Code, Cowork, or APIs instead of buying another point solution. But live data, deliverability, permissions, CRM sync, and reliability still need real infrastructure. Ask: is this a thinking task, an infrastructure problem, or something you are ready to build and maintain?
What does your stack actually need right now?
Four questions: ARR stage, biggest bottleneck, team structure, build capacity. Your team structure decides how many categories to take on at once, no point recommending five tools to a team that can't run two. Watch the map above order itself.
Question 1 / 4
Where is your ARR right now?
This sets the baseline for which categories are mature enough to matter.
Question 2 / 4
What's actually slowing you down?
Pick up to 2, most important first. This pushes the matching categories to the top.
Question 3 / 4
How is your revenue team structured?
This decides how many categories to take on at once. A lean team shouldn't juggle five tools.
Question 4 / 4
What's your team's build and integration capacity?
This changes how to fill each gap, buy a tool or build with Claude, not which gaps matter.
Your stack map
Find Buyers
Move Deals
Close Revenue
Foundation
CRM & Revenue OS
Automation & orchestration
You flagged this as disconnected. Review it before adding anything else.