Run what happens after the list
PhantomBuster scrapes LinkedIn into a list. Cargo builds your market, watches 35+ signals, enriches, scores and routes every account, and keeps your CRM current.
Trusted by GTM teams at
PhantomBuster gets you a list. Cargo runs your revenue engine.
Both can export a Sales Navigator search. PhantomBuster stops there. Cargo runs everything that has to happen before that list turns into pipeline.
| PhantomBuster | Cargo | |
|---|---|---|
| What you buy | A scraping tool. Each Phantom extracts data from LinkedIn or a website, or runs one action. | Go-to-market infrastructure. It runs the work from the market you target to the account on a rep's desk. |
| Scope | One step. You get a list, and everything after it is yours to build. | Every step. Cargo enriches, scores, routes and assigns each account, then alerts the rep. |
| Data | What a Phantom scrapes, kept in PhantomBuster's own storage. | One data layer: your CRM, your warehouse and 50+ enrichment providers, on your warehouse or ours. |
| Signals | Someone launches a Phantom, or it runs on a schedule you set. | 35+ signals start the work, including who follows your competitors and who connects with their sales team. |
| LinkedIn access | Your session cookie. When it expires, runs fail until you reconnect. | Searches and profiles are read without your account. Only sending uses the accounts you connect. |
| Your CRM and tools | You get a CSV or JSON file. Zapier, Make or the API moves it to the CRM. | Records are created or updated without duplicates, and the owner is set in your CRM, Slack and sequencer. |
| When a run fails | The error sits in that Phantom's log, for example a slot limit reached. | Every step is traced, and you get an alert when one fails. |
| Ready-made | A Phantom template for each single task. | Cookbooks: complete workflows, from building your market to routing accounts, installed in one command. |
In short. PhantomBuster covers one step of the job. Cargo runs every step, from the market you target to the account on a rep's desk, and shows you what happened at each one.
The whole engine, not one step
Each of these ships as a cookbook. Your coding agent installs it in one command and adapts it to your ICP.
Your whole market, in one list
Sales Navigator, Apollo, AI Ark and Exa, merged per company.
CompaniesAll recordsFilterSort12,480 records6/24 columnsName+23DomainEmployeesCountryIndustryICP fitAdd columnNorthwindnorthwind.com420United StatesLogistics82Contosocontoso.com1,200FranceSoftware74Globexglobex.com3,400GermanyManufacturing91Initechinitech.com260United StatesSoftware68Fabrikamfabrikam.com880FranceRetail55Umbrellaumbrella.com2,100United KingdomHealthcare79Stark Logisticsstarklogistics.com640United StatesLogistics88Wayne Freightwaynefreight.com1,450SpainLogistics7150+ enrichment providers
Emails, phones and company data, on Cargo credits or your own keys.
Enabled
Enrich inbound leadsSearch...4/4 nodesFilter5/5 statusesAll versionsAll batchesAll datesStartstartFind emailfind_emailEnrich companyenrich_companyICP fitscore_icpAda Lovelaceada@northwind.comNorthwind, 420 employees82/100Grace Hoppergrace@contoso.comContoso, 1,200 employees74/100Alan TuringNo email found, 0 creditsGlobex, 3,400 employees91/100Katherine Johnsonkatherine@initech.comRunning...Default35+ signals
Warm intros, competitor followers and their sales team's connections.
NorthwindSignals this week
Ada Lovelace reacted to your post2h- Ada Lovelace commented on your post3h
- Ada Lovelace viewed your profile1d
- Northwind viewed your company page1d
Scoring
A fit score against your ICP and a readiness score from signals.
EnabledRoute inbound leadsSearch...2/2 nodesFilter5/5 statusesAll versionsAll batchesAll datesStartstartICP fitscore_icpAda Lovelace82/100Grace Hopper74/100Alan Turing91/100Katherine Johnson68/100Edsger Dijkstra55/100Mary Jackson77/100Claude Shannon86/100Barbara Liskov63/100DefaultRouting and assignment
By territory or round robin, with the owner set in every tool.
Revenue organizationNew territoryNew capacityMembersTerritoriesCapacitiesA group of members that shares incoming records. Weights and a fallback decide who is next.
Territories3 territoriesUnited StatesInbound from North AmericaFranceInbound from FranceEMEAEverything else in EuropeUnited StatesLabel*United StatesChoose a label to your territory
Color*Choose a color to represent your territory
DescriptionInbound from North AmericaChoose a description
Members*AMAlice Martin
50SOSam Okoro50Add memberPick members you want to be part of your territory
Fallback MemberDCDana Cole
The member that will be used when other territory members are not available (e.g. Capacity reached).
SaveTraced and governed
Every run traced, roles for editing, approval in Slack before sending.
TracesAll triggers4/4 statusesLast 7 daysRecordTriggerSpansUserDurationStarted atFinished atCreditsAda LovelaceRoute inbound leads6 spans602.41sNov 3rd, 2026 10:14:02Nov 3rd, 2026 10:14:041NorthwindAccount researcher3 spans30AMAlice Martin8.62sNov 3rd, 2026 10:11:40Nov 3rd, 2026 10:11:493Katherine JohnsonRoute inbound leads5 spans411.97sNov 3rd, 2026 10:09:13Nov 3rd, 2026 10:09:151ContosoEnrich new accounts4 spans403.18sNov 3rd, 2026 09:58:21Nov 3rd, 2026 09:58:242Grace HopperRoute inbound leads6 spans602.06sNov 3rd, 2026 09:51:07Nov 3rd, 2026 09:51:091GlobexAccount researcher4 spans40MDMarc Dubois11.3sNov 3rd, 2026 09:44:52Nov 3rd, 2026 09:45:034Alan TuringRoute inbound leads6 spans602.28sNov 3rd, 2026 09:39:18Nov 3rd, 2026 09:39:201InitechEnrich new accounts4 spans314.05sNov 3rd, 2026 09:31:46Nov 3rd, 2026 09:31:502
GTM as code, in your repo.
Your whole Cargo workspace is TypeScript in git: every change reviewed, planned and reversible.
- In your repoThe whole workspace, declared in TypeScript.
- Planned on every pull request
cargo-ai project planshows the diff. Merging deploys it. - Undone with git revertRevert the commit and the previous version deploys.
Written by your coding agent: Claude Code, Cursor or Codex.
import { defineMember, defineTerritory } from "@cargo-ai/cdk";const alice = defineMember("alice@acme.com");const dana = defineMember("dana@acme.com");// United States accounts go to Alice, Dana coversexport const unitedStates = defineTerritory("united-states", {label: "United States",members: [{ ref: alice, weight: 1 }],fallback: dana,});
When to choose which
Both products have a real job. The decision is which job you are hiring for.
Choose PhantomBuster when…- You need a one-off export of a LinkedIn search or a web page.
- The list is the whole job: nothing goes to a CRM, a rep or a sequence afterwards.
- You want a LinkedIn campaign inbox and do not use a separate sequencer.
- One person launches a few automations by hand.
Choose Cargo when…
- The list feeds your sales team every week.
- You want a signal to start the work, not someone pressing launch.
- Each account needs a score and an owner, set in the CRM, Slack and the sequencer.
- Contacts have to arrive enriched and without duplicates in your CRM.
Both true. Both can export a Sales Navigator search. PhantomBuster stops at the list; Cargo runs what happens next. Pick on whether the list is the whole job or the start of it.
Cargo vs PhantomBuster, in short
If the list is the whole job, another scraper will do. If it feeds your sales team every week, Cargo: it builds your market, watches 35+ signals, enriches every account across 50+ providers, scores and routes it, and keeps your CRM up to date, in one system your team or its coding agent builds and runs. Cargo has been in production for about three years, and 300+ companies have built revenue engines with it.
No. Cargo extracts Sales Navigator and LinkedIn data, but that is one input. Cargo is the system around it: it decides which accounts and people to target, finds the data on each of them, scores them, assigns them to a rep, updates your CRM and hands them to the tool that sends.
More than 35. People: new decision makers, job changes, key employees leaving, people posting again after a long silence, warm intros through your team, customers or investors. Companies: job offers and reposted job offers, hiring at volume, fundraising, mergers and acquisitions, headcount growth by company or department, new tools adopted or dropped, AI adoption, companies using a competitor, new or changed Google Business listings, and public tenders. LinkedIn: new followers of your page or a competitor's page, engagement with your posts, a competitor's or an influencer's, mentions of your keywords, event attendees, and people connecting with a competitor's sales or customer success team. Predictive: companies likely to raise, be acquired, go public or grow headcount. Website visitors and buyer intent come in through connectors such as RB2B, Snitcher and G2. Most signals can watch the whole market or only the accounts you choose.
Cargo creates or updates accounts, contacts, deals and custom objects in HubSpot, Salesforce or Attio. Each record is matched on the key you choose, such as a domain or a LinkedIn URL, so nothing is duplicated. Associations, owners and lists are set in the same step, and you decide which fields Cargo is allowed to change.
Ready-made go-to-market workflows, written as code: market building, account and readiness scoring, buying signals, new-hire detection, contact sourcing, waterfall enrichment, inbound qualification and routing. Your coding agent adds one to your workspace with cargo-ai project add and adapts it to your ICP.
Yes. A cookbook counts the search, splits it under the extraction cap, merges the pieces back into as few searches as possible and loads them into Cargo, without your LinkedIn account.
Not to read. Sales Navigator searches and LinkedIn profiles are extracted without your LinkedIn account. Sending connection requests and messages uses your own account, connected with the Cargo Chrome extension.
No. Cargo feeds the sequencer you already use, such as Lemlist, HeyReach, Outreach, Salesloft, Instantly or Smartlead, and writes the outcome back to your CRM. It can also send email from Cargo mailboxes it warms up for you, and send a connection request or a LinkedIn message from your own account inside a workflow, at 0.25 credits each.
Yes, on any connector except LinkedIn. You can also run the same providers on Cargo credits, and mix both in one waterfall.
No. There are three ways: your team builds on the platform, your team builds with our help, or we build and run it for you. You own the logic, the context and the data either way.
Yes. Monaco moved its PhantomBuster workflows to Cargo, and now runs its LinkedIn prospecting, signals and enrichment there. Edflex, Foodles and Rise Up, which used PhantomBuster in their prospecting stack, run on Cargo too. Alma kicked off the migration of 160+ workflows to Cargo over a weekend, including the scraping scenarios it ran in CaptainData, another LinkedIn scraper.
Yes. Cargo's PhantomBuster integration launches a Phantom and stores its results in Cargo, so you can move one automation at a time.
“Essential. Innovative. Indispensable. Cargo let you build your unique growth engine, a much-needed solution in the market today.”
Guillaume Cabane · Co-Founder @Hypergrowth
Build the self-driving GTM engine
Your coding agents build it on Cargo.Or our team builds, operates and improves it with you.