Your GTM stack doesn't need more tools.
It needs one brain that can run all of them.
That brain is Claude Code.
Here are the 15 tools I'd plug into it 👇
1. Claude Code → orchestrates the whole workflow from plain-English instructions
2. Apollo.io → B2B contact and company database for building target lists
3. Prospeo → finds and enriches emails and mobile numbers
4. PredictLeads → company signals like hiring, news events and tech changes
5. AI Ark → company and people search for sharper account lists
6. DiscoLike → finds companies that look like your best customers
7. Openmart → local and SMB business data the big databases miss
8. GetLeads → B2B contact data your AI tools can query directly
9. FullEnrich → waterfall enrichment when one data source comes up short
10. n8n → wires every tool into automated workflows
11. lemlist → multichannel sequences in one place
12. Instantly.ai → cold email campaigns at scale
13. Expandi → automates the repetitive parts of LinkedIn outreach
14. Hypertide.io → cold email infrastructure across Google and Microsoft
15. Clay → research, enrichment and repeatable GTM workflows in one table
The tools matter less than how they're connected.
Claude Code turns 15 tabs into one system.
Save this for your next build. And tell me: which tool would you add?
#GTMEngineering #ClaudeCode #Outbound #SalesAutomation
Nishkarsh Agarwal
Founder @Sparq Labs, GTME.School · 8d ago
Clay vs Instantly.ai is the wrong debate.
The best outbound stacks use both for completely different jobs.
I get this question every week now. And it's the wrong question.
Here's the thing most people miss: they were never competing for the same job.
Instantly is a sending layer.
Its entire purpose is landing your email in the inbox at volume without wrecking your sender reputation. Unlimited inboxes, a million-plus warmup network, IP rotation. That's the job it's great at.
Clay is a data and orchestration layer.
It knows who to email and what to say, enriched and personalized on fresh data. And in Sept 2026 it shipped a native Sequencer, so now it can press send too.
That overlap is why everyone's suddenly arguing.
One detail settles half the fights: Clay's Sequencer runs on Smartlead under the hood, billed in Clay credits.
So "Clay vs Instantly.ai on deliverability" is really Smartlead's engine vs Instantly.ai's. Judge Clay on data. Judge senders on sending.
The honest answer for most teams:
→ Under ~5k emails a week, where reply quality beats raw volume, Clay-native can be enough.
→ Above that, or when deliverability is the whole game, keep a dedicated sender and let Clay feed it.
Not a fight. A pipeline.
What's your outbound stack right now, all-in-one or best-of-breed?
#GTMEngineering #ColdEmail #Outbound #RevOps #Clay
Nishkarsh Agarwal
Founder @Sparq Labs, GTME.School · 3w ago
Everyone asks what to learn to become a GTM engineer.
It is five things, and the order matters more than the list.
1. Clay
The company that coined the term go-to-market engineering, and the foundational orchestration platform in the market right now.
2. Go-to-market strategy
The thinking layer underneath every tool. Skip this and you are just clicking buttons.
3. Email infrastructure and list building
4. The basics of copywriting
5. LinkedIn outbound
That is the core.
Real mastery of the popular stack beats surface-level familiarity with all of it. Get there and you can start adding value from week one.
Which of the five is your weakest?
#GTMEngineering #Clay #RevOps #SalesAutomation #B2BSales
Nishkarsh Agarwal
Founder @Sparq Labs, GTME.School · 4w ago
95% of people calling themselves GTM engineers have never touched n8n.
That gap is the easiest advantage you will ever pick up.
Most of them stop at the tools that have a nice UI.
No n8n. No Make. No webhooks.
The technical layer is the whole difference between a GTM engineer and someone who operates software.
Where to start:
→ n8n and webhooks first
→ SQL fundamentals next
→ Python after that. It does not have to be day one
Then go genuinely deep on the core sales stack instead of skimming all of it.
That depth becomes your leverage in every single conversation where you are selling yourself.
Have you touched n8n yet?
#GTMEngineering #n8n #SalesAutomation #RevOps #Outbound
Nishkarsh Agarwal
Founder @Sparq Labs, GTME.School · 3w ago
We cancelled our Clay subscription 30 days ago.
Nothing broke. Outbound got faster.
For 8 months we ran the stack every agency runs — Clay, Apollo.io, Instantly.ai, n8n, and a
Google Sheet nobody actually reviewed. $1,200/month. Around 10 hours a week
keeping it alive. Auth failures every Monday.
Then March happened.
Clay reset pricing: +28% cost, −40% credits, Pro tier deleted. And every HTTP call
became a billed "Action" — which meant our own custom API integrations started
burning credits just for existing.
We were paying Clay to run our own code.
So we rebuilt it in Claude Code. One terminal. One prompt. Prospeo.io → FullEnrich →
LeadMagic waterfall, straight into Instantly.
$400/month. Under 2 hours a week. Same reply rate. 3x the campaigns.
Three things I got wrong going in:
1. I thought we'd lose speed. We got faster — campaigns now launch in 20 minutes
instead of 2 days.
2. I thought the team would resist. First question was why we hadn't done it in January.
3. I thought clients would care which tools we use. Not one has asked. They care about
meetings booked.
Full breakdown in the carousel — the architecture, the exact prompt we run in
production, and an honest list of who should NOT do this.
If you're an agency still paying the Clay tax, this one's for you.
—
Comment "STACK" and I'll send you the prompt we actually run.
#GTM #Outbound #GTMEngineering #ClaudeCode #RevOps
Nishkarsh Agarwal
Founder @Sparq Labs, GTME.School · today
My GTM engineer is an AI agent. His name is Roz.
Roz owns every growth lead across three companies. Every outbound campaign. Client campaigns. Pipeline for the agencies.
It works because of the wiring — Prospeo, EmailBison, GoHighLevel Experts and the rest. Roz isn't drafting copy in a vacuum. It builds and ships the campaign end to end.
But here's the line that matters: as per led by the leaders of the company.
Roz doesn't set strategy. Humans still do that. Roz removes the ceiling on execution.
No single GTM hire was ever running three companies at once 👇
Nishkarsh Agarwal
Founder @Sparq Labs, GTME.School · 7d ago
You can build an entire outbound motion in eight weeks.
Most people break it permanently in the first two.
THE BUILD
→ Set up your data infrastructure
→ Test it on 100 contacts before you scale anything
→ Then the rest: automations, workflow builders, CRM, signal monitoring
→ Weeks seven and eight are pure optimization
THE FIVE MISTAKES THAT KILL IT
→ Using a single email finder, which tanks your coverage
→ Ignoring buying signals entirely
→ Over-automating personalization until it reads robotic
→ Neglecting deliverability monitoring
→ Sending without a warmup. Instant spam, and the infrastructure is gone.
Test on 100 first. Always.
Which of the five have you made?
#Outbound #ColdEmail #SalesOps #RevOps #GTMEngineering
Nishkarsh Agarwal
Founder @Sparq Labs, GTME.School · 2w ago
Your outbound isn't broken because of your tools.
It's broken because you run them in the wrong order.
Everyone's arguing about which enrichment tool to buy. Wrong fight fr.
So I put how we actually run outbound at Sparq on one sheet. One loop, eight stations. Signal, companies, people, verify, variables, send, replies, book. Then back to signal.
The line in the middle is the whole game: cheap steps before AI steps.
A few rules on there I'd tattoo on every new GTM engineer:
→ Filter on signal first. Never run tenure first.
→ Qualify the company before you pay for a single contact. Max 2 people per company.
→ Claude Code writes 2 fields per row. The email template never changes.
→ Count humans only. One audit had 131 "replies" on the dashboard. 12 were actual people 💀
→ Reply to booked call is where pipeline leaks. Not volume.
The sending math is on there too. 1 inbox × 5 a day × 26 days = 130 emails a month. Want 100k a month? That's ~770 inboxes. No magic lol.
Bottom left there's a 0–10 scorecard for the five disciplines. Screenshot it and be honest with yourself.
Comment FIELD and I'll send you the full-res sheet.
#GTMEngineering #ColdEmail #Outbound
Nishkarsh Agarwal
Founder @Sparq Labs, GTME.School · 3w ago
Apollo has never heard of your ICP.
That is a tooling problem, not an ICP problem.
Try building a list of dating app owners in the US. Or mobile app owners in one specific vertical.
That data does not exist inside Apollo.
What to use instead:
→ Ocean, for finding people in genuinely obscure pockets
→ Lookalike finders, which give you more features and more precise targeting than Ocean does on its own
→ ZoomInfo, genuinely powerful but expensive, and you are scheduling a call before you can even start
→ Clearbit, the one most people default to
Match the tool to how obscure the niche actually is. Stop blaming the list.
What is the hardest list you have had to build?
#Prospecting #LeadGeneration #ListBuilding #GTMEngineering #B2BSales
Nishkarsh Agarwal
Founder @Sparq Labs, GTME.School · 2w ago
Your orchestration platform is the most important choice in your entire stack.
Most people pick three of them and then wonder why nothing connects.
The orchestration layer is what hosts every other tool and actually runs the sequence for you. Everything else plugs into it.
Clay is my central hub. That is honestly what I use.
Make sits alongside it. I lean on it to automate everything that sits outside the core flow. Zapier does the same job if you are just starting out.
Some platforms in this category do a few more things than Clay does. They are also considerably more expensive, and you can usually close those specific gaps another way.
Pick one hub. Do not run three.
What is your central hub?
#Clay #SalesAutomation #GTMEngineering #RevOps #Automation
Nishkarsh Agarwal
Founder @Sparq Labs, GTME.School · 2w ago
One email finder will never give you full coverage.
That is the entire reason data enrichment waterfalls exist.
A waterfall is multiple providers chained together and called in sequence.
Provider one misses. Provider two catches it.
Provider two misses. Provider three catches it.
You run them to find emails, find phone numbers, and pull deeper company data. Then you verify whatever comes back.
The point is not using more tools for the sake of it. The point is refusing to bet your entire pipeline on one provider's coverage.
How many providers are in your waterfall right now?
#DataEnrichment #ColdEmail #Prospecting #Outbound #GTMEngineering
Nishkarsh Agarwal
Founder @Sparq Labs, GTME.School · 9d ago
60%+ email coverage is not a tool you buy.
It is a stack you assemble, and here is the exact one.
FOR FINDING
Prospeo, LeadMagic, FindyMail, FullEnrich and BetterContact. Enrichly is a reasonable addition.
FOR VALIDATION
ZeroBounce covers the basics. GlockApps handles deliverability testing specifically.
FOR CATCH-ALL VERIFICATION, which is the hard part
Bounceban and Enrow are the two best. This is the exact layer where most stacks quietly fall apart.
Worth knowing: most finders already validate on the way out. FindyMail validates. Prospeo validates. So you are not paying twice for the same check.
Stack it properly and your coverage lands at 60%+.
What is your coverage rate today?
#DataEnrichment #EmailValidation #ColdEmail #Deliverability #GTMEngineering
