What's the actual modern GTM stack for a lean team?
Two things: Clay and a primary CRM. Get those right and you can run a serious GTM motion off a small team. Everything else is a nice-to-have you add when you feel a specific pain, not a starting requirement. Most lean teams get this backwards, buying a shelf of tools and using a fraction of them.
They're not alone in that. Gartner has found marketers use only about a third of their martech stack's capability, down from over half a few years earlier. So the discipline here isn't which clever tool to add. It's refusing to add anything until you're actually using what you've got.
What are the two tools you can't skip?
Clay and a CRM, and they do different halves of the job. Clay is where you build and enrich: target lists, buying groups, firmographics, signals, the research layer that feeds everything. It's the engine room of a modern GTM motion, and for a lean team it replaces a lot of manual work and a lot of separate point tools.
The CRM is your source of truth: HubSpot or Salesforce, depending on how you're built. It's where the relationship lives, where deals move, where your team looks to know what's actually going on. Clay finds and enriches; the CRM remembers and reports. You need both, and honestly for a while you need only both. If you're choosing between the big two, that's its own decision, and it leans heavily on how much you'll invest in CRM automation and admin.
What's worth adding after that?
A couple of tier-two tools, once you feel the need for them. The first is Apollo. It does enrichment, but its real value for a lean team is the sales-side lifecycle engagement: it lets your GTM people run their own sequences and workflows without having to live inside a heavy marketing automation platform. That's a genuine unlock when you want the GTM team moving fast on their own without waiting on marketing ops.
The second is an outreach tool, HeyReach or Smartlead being the usual picks. These automate the mechanical touches across LinkedIn and email: see who engaged, send the connection, wait, follow up. Note the word mechanical. They handle the sequencing and the timing of touches, which frees your people to spend their attention on the messages and the replies that need a human. That's the right split, and it's the same line I draw in what to automate versus keep human.
Two tools to run the motion, two more when you feel the pain. Everything else is a solution to a problem you don't have yet.
What should you leave out?
The rest of it, until you feel the pain. The intent-data platform, the second enrichment vendor, the conversation intelligence suite, the standalone scheduling and routing tools: all can be worth it eventually, none is worth it on day one. Buy tools to fix problems you're genuinely hitting, not problems a demo convinced you that you might have one day.
The honest test before any new tool: can you name the specific pain it removes this month, and are you already using what you own to its edge? If not, you're just going to add it to the two-thirds of your stack that Gartner says nobody touches.
Where do lean teams overspend?
Two places, reliably: the CRM and Clay. On the CRM, teams buy the big professional tiers largely to get sequencing, when the Apollo credits they already own would do that job. You end up paying a premium for a feature you're duplicating. Salesforce carries a second hidden cost too: it really needs a permanent admin to run well, which is a standing salary, not just a licence. Factor that in before you commit, because plenty of lean teams don't and regret it.
On Clay, the overspend is nearly always about triggers. Teams run credit-heavy enrichment processes on a schedule, re-enriching the same universe on a timer, burning credits on data that hasn't changed. Trigger on signals instead. Enrich when something happens, a new account appears, a signal fires, a stage changes, not because it's Tuesday. Same data, a fraction of the cost. Get those two habits right and the lean stack stays lean, which was rather the point.
If you want your stack sized honestly against what you're actually doing, with no upsell to tools you don't need, book a free Growth Audit. You can also see how we build and run the motion on our GTM engineering page.
Frequently asked questions
Do I need both Clay and a CRM, or can one do both?
You need both; they do different halves. Clay builds and enriches your lists and tracks signals, the research layer. The CRM is your source of truth, where relationships live and deals move. Clay finds and enriches; the CRM remembers and reports. For a good while, those two are the whole stack a lean team needs.
HubSpot or Salesforce for a lean team?
It depends on how much you'll invest in admin. Salesforce is powerful but really needs a permanent admin to run well, which is a standing salary on top of the licence. HubSpot is friendlier for a lean team to run without dedicated ops. Factor the true running cost, not just the sticker price, into the choice.
Why not just buy the CRM's sequencing tier?
Because you're often paying a premium to duplicate something you already own. The Apollo credits many teams already have will run sequences perfectly well, so buying up to a big professional CRM tier mainly for sequencing is a common, avoidable overspend. Check what you can already do before you upgrade.
How do I stop Clay burning through credits?
Trigger on signals, not on a schedule. The usual overspend is running credit-heavy enrichment on a timer, re-processing the same universe when nothing's changed. Enrich when something actually happens: a new account appears, a signal fires, a stage changes. Same data, a fraction of the credits.
