These are the 15 tools we come across most in the sales systems we review, and the ones we build ours with. It isn't a ranking — it's the stack we work with, and why we use each piece.
The tool that fits your CRM and your process beats the one that scores better in a comparison. Migrating almost always costs more than it saves.
How long before it gives you something usable. If it takes a quarter to implement before it shows anything, it has to make up for it in depth.
The licence plus the time of the person who maintains it. A cheap tool that needs someone watching it every week isn't cheap.
The system of record. It's where the sales process lives, and what everything else is measured against.
A CRM with marketing, sales and service on the same database. It's the most common starting point among the B2B companies we work with: quick to get running, with an object model that covers almost everything.
How we use it. We set up the pipeline, the required properties per stage and the conversion reports. Most of our Diagnostics end up here.
The go-to CRM when the process is complex or there are several business units. Customisable down to the last detail, at the cost of needing someone to maintain it.
How we use it. We work inside your existing instance, cleaning up objects, legacy automations and fields nobody fills in.
A modern CRM built on a flexible data model. A good fit for small teams that want a CRM that looks like their process, not the other way round.
How we use it. The default option when there is no existing CRM and the sales team has fewer than ten people.
Where the accounts, the contacts and the fields used to segment and prioritise come from.
An enrichment orchestrator: it runs dozens of providers in a waterfall and adds AI research on every account. It replaces half a dozen standalone subscriptions.
How we use it. It's where we build the lists and where each account's fit is calculated before it enters any sequence.
A B2B contact database with sequences included. Good coverage for the price when you're starting out, though patchy outside the US.
How we use it. A contact source and a cross-check; we run the serious sequences elsewhere.
Enterprise-grade company and contact data, with intent signals on the same database. It's the expensive option and the one that gives most depth on large accounts.
How we use it. When the ICP is large accounts and the cost of a bad data point is higher than the cost of the licence.
Signals that an account is in market before it raises its hand.
An ABM and intent platform: it estimates which accounts are in market and at what buying stage, so sales can focus its effort on them.
How we use it. It prioritises the list: it sets the order the team works in, rather than opening a new channel.
The sending layer: domains, warm-up, sequences and replies.
Cold email sequences with personalisation and deliverability controls. Moderate volume, carefully crafted messages.
How we use it. Campaigns with few accounts and a lot of context, where every send is genuinely personalised.
Cold email at scale: mailbox rotation, warm-up and secondary-domain management built into the product.
How we use it. Sending infrastructure when the volume no longer fits in the team's mailboxes.
What is said on calls, turned into data that flows back into the CRM.
An AI notepad for meetings: it transcribes in the background and expands your own notes instead of replacing them. No bot joining the call.
How we use it. For discovery calls and diagnostic sessions, where a recording bot gets in the way more than it helps.
Conversation intelligence: it records and analyses the team's calls, and surfaces patterns from what happens in real opportunities.
How we use it. It's where we look when you need to know why deals drop off at a specific stage.
The glue between tools. This is almost always where the team's time is won back.
No-code integrations between thousands of applications. The fastest way to connect two tools the team already uses.
How we use it. Short, low-risk automations, and prototypes before moving them to n8n.
Workflow automation with code when you need it, and the option to self-host. More control over the data and over the cost per execution.
How we use it. The flows that touch customer data or run thousands of times a month live here.
Models that classify, draft and summarise inside the flows, not in a separate tab.
Anthropic's models. We use them for how they handle long instructions and Spanish-language text.
How we use it. Account classification, call summaries and first drafts of copy inside the flows.
GPT models via API. A broad ecosystem and the default option when the destination tool already comes with a native integration.
How we use it. Prompt-based enrichment inside Clay and structured extraction tasks.
Tools only give back what the process asks of them. The RevOps & GTM Diagnostic reviews demand, process and visibility, and ends with a prioritised plan.
30 minutes, no sales pressure.