Prospect data that stays yours

Name: Cargo
SKU: cargo
Availability: InStock

Apollo is prospecting and sequencing on its own contact database. Cargo runs the engine around it on providers you choose, with records in your models.

Start building

Trusted by GTM teams at

Augment Code
Weights & Biases
Dust
WorkOS
Braintrust
Descript
Alaan
Engine
Scaleway
Preply
DataDome
Oneflow

Apollo brings a database. Cargo brings the engine.

Apollo puts finding, enriching and emailing in one product. Cargo decides who to contact and when, on data that stays yours.

Apollo and Cargo compared
	Apollo	Cargo
Built for	Prospecting and sequencing on its own contact database	Orchestration for the whole revenue engine
Contact data	Apollo's own database	The providers you choose, in a waterfall
Where records live	In Apollo	In your models
Pricing	Per seat: cost scales with headcount	Usage: cost scales with what the engine does
GTM as code	Configured in the Apollo app	The workspace in TypeScript, in your git repo
Best when	A non-technical team runs outbound prospecting	Scoring and routing build on the data

In short. Use Apollo to find, enrich and email in one product at a low entry price. Use Cargo for the model, scoring and routing that decide who Apollo should contact.

What a contact database leaves out

Finding the contact is one step. Deciding who to contact is the engine.

One GTM data model
Accounts, contacts, deals and custom objects every play reads.
Companies
2 hours ago
All records
FilterSort12,480 records6/24 columns
Name+23
Domain
Employees
Country
Industry
ICP fit
Add column
Northwind
northwind.com
420
United States
Logistics
82
Contoso
contoso.com
1,200
France
Software
74
Globex
globex.com
3,400
Germany
Manufacturing
91
Initech
initech.com
260
United States
Software
68
Fabrikam
fabrikam.com
880
France
Retail
55
Umbrella
umbrella.com
2,100
United Kingdom
Healthcare
79
Stark Logistics
starklogistics.com
640
United States
Logistics
88
Wayne Freight
waynefreight.com
1,450
Spain
Logistics
71
Providers you choose
Data providers in a waterfall, so coverage and cost are yours.
Enabled
Enrich inbound leads
TriggerEditorRecordsMetrics
Search...
4/4 nodesFilter5/5 statusesAll versionsAll batchesAll dates
1,284 records
Startstart
Find emailfind_email
Enrich companyenrich_company
ICP fitscore_icp
Ada Lovelace
ada@northwind.com
Northwind, 420 employees
82/100
Grace Hopper
grace@contoso.com
Contoso, 1,200 employees
74/100
Alan Turing
No email found, 0 credits
Globex, 3,400 employees
91/100
Katherine Johnson
katherine@initech.com
Running...
Default
Scoring on your ICP
Each account gets a fit score and a readiness score from signals.
Enabled
Route inbound leads
TriggerEditorRecordsMetrics
Search...
2/2 nodesFilter5/5 statusesAll versionsAll batchesAll dates
1,284 records
Startstart
ICP fitscore_icp
Ada Lovelace
82/100
Grace Hopper
74/100
Alan Turing
91/100
Katherine Johnson
68/100
Edsger Dijkstra
55/100
Mary Jackson
77/100
Claude Shannon
86/100
Barbara Liskov
63/100
Default
Routing that knows the org
Territory, capacity, ownership and fallback, not tied to one CRM.
Back to appWorkspaceGeneralBillingUsageUsersRolesIntegrationsDomainsRevenue organizationAPIEnvironmentSystem of record
Revenue organization
New territoryNew capacity
MembersTerritoriesCapacities
A group of members that shares incoming records. Weights and a fallback decide who is next.
Territories3 territories
United StatesInbound from North America
2 membersAdded 3 days ago
FranceInbound from France
1 memberAdded 3 days ago
EMEAEverything else in Europe
1 memberAdded a week ago
United States
EditAllocations
Label*
United States
Choose a label to your territory
Color*
Choose a color to represent your territory
Description
Inbound from North America
Choose a description
Members*
AMAlice Martin
50
SOSam Okoro
50
Add member
Pick members you want to be part of your territory
Fallback Member
DCDana Cole
The member that will be used when other territory members are not available (e.g. Capacity reached).
Save
CRM-safe writes
Dedupe, protected fields and attribution on every CRM write.
Enabled
Route inbound leads
TriggerEditorRecordsMetrics
Search...
2/2 nodesFilter5/5 statusesAll versionsAll batchesAll dates
1,284 records
Startstart
Update ownerupdate_owner
Ada Lovelace
Owner updated
Grace Hopper
Owner updated
Alan Turing
Owner updated
Katherine Johnson
No Salesforce lead matches this email
Edsger Dijkstra
Mary Jackson
Owner updated
Claude Shannon
Owner updated
Barbara Liskov
Owner updated
Default
Built by coding agents
Your coding agent changes it as diffs, over the CLI or MCP.
Account researcher
TriggerEditorActivities
Deploy
Instructions
Research the account, score it against our ICP and write a two-line brief for the owner. Use our ICP definition from context, not your own.
Actions
Enrich companyenrich_company
Search the webweb_search
Get companyhubspot_get_company
The building blocks of the agent. They are the actions the agent can take. The agent will use the actions to achieve the goal.
Advanced settingsClaude Sonnet 5
Research Northwind and tell me if it fits our ICP.
Reasoned for a few seconds
Get company0
Enrich company1
Search the web2
Northwind fits: 82/100. 420 employees, logistics, and two open SDR roles, which is the growth trigger in your ICP.
It sits in the United States territory, so the owner is Alice Martin. Lead with routing: their HubSpot assigns inbound by hand today.
Ask agent...

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 requestcargo-ai project plan shows 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 covers
export 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 Apollo when…

Outbound prospecting is the whole job
A non-technical team runs it
One product should find, enrich and email
Nothing downstream builds on the data

Choose Cargo when…

Scoring and routing build on the data
Records should live in your models, not a vendor's
Coverage and cost should be yours to tune
Cost should scale with volume, not headcount

Both true. Apollo is the better all-in-one prospecting tool. Cargo is the better GTM engine. Apollo can stay the sequencer and one source in a waterfall while Cargo decides who it should contact.

Cargo vs Apollo, in short

If you want another all-in-one prospecting database, compare those directly. If the problem is that scoring, routing and the rest of the engine need to build on the data, Cargo: it composes the providers you choose into a waterfall, keeps the records in your models and decides who to contact and when.

Apollo is prospecting and sequencing on top of its own contact database: the artifact is sequences and lists inside Apollo. Cargo is the orchestration layer for the whole revenue engine, and it has no contact database of its own by design, because the data should be yours and fetched live rather than cached in a vendor's index.

When the job is outbound prospecting, the team is non-technical, and nothing downstream needs to build on the data. Apollo puts finding, enriching and emailing in one product at a low entry price, which is a genuinely good fit for that shape of team.

No. Cargo connects to the data providers you choose and composes them into a waterfall, so coverage and cost are yours to tune and the records live in your models rather than in a vendor's cache.

Apollo prices per seat, so cost scales with headcount. Cargo prices on usage, so cost scales with what the engine actually does. Which is cheaper depends entirely on the ratio of people to volume on your team.

Yes. Apollo can stay the sequencer and one of the data sources in a waterfall while Cargo owns the model, the scoring and the routing that decide who Apollo should contact and when.

“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.

Start building

//////// /////// //////// //////// /////// /// /// /// /// /// /// /// /// /// /// /// /// /// /// /// /// /// ///////// //////// /// //// /// /// /// /// /// /// /// /// /// /// /// /// /// /// /// /// /// /// /// /// //////// /// /// /// /// /////// ///////

Apollo and Cargo compared
	Apollo	Cargo
Built for	Prospecting and sequencing on its own contact database	Orchestration for the whole revenue engine
Contact data	Apollo's own database	The providers you choose, in a waterfall
Where records live	In Apollo	In your models
Pricing	Per seat: cost scales with headcount	Usage: cost scales with what the engine does
GTM as code	Configured in the Apollo app	The workspace in TypeScript, in your git repo
Best when	A non-technical team runs outbound prospecting	Scoring and routing build on the data

Apollo

Cargo

Built for

Prospecting and sequencing on its own contact database

Orchestration for the whole revenue engine

Contact data

Apollo's own database

The providers you choose, in a waterfall

Where records live

In Apollo

In your models

Pricing

Per seat: cost scales with headcount

Usage: cost scales with what the engine does

GTM as code

Configured in the Apollo app

The workspace in TypeScript, in your git repo

Best when

A non-technical team runs outbound prospecting

Scoring and routing build on the data

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 covers

export const unitedStates = defineTerritory("united-states", {

label: "United States",

members: [{ ref: alice, weight: 1 }],

fallback: dana,

});

Prospect data that stays yours

Apollo brings a database. Cargo brings the engine.

What a contact database leaves out

One GTM data model

Providers you choose

Scoring on your ICP

Routing that knows the org

CRM-safe writes

Built by coding agents

GTM as code, in your repo.

When to choose which

Cargo vs Apollo, in short

Build the self-driving GTM engine

Prospect data that stays yours

Apollo brings a database. Cargo brings the engine.

What a contact database leaves out

One GTM data model

Providers you choose

Scoring on your ICP

Routing that knows the org

CRM-safe writes

Built by coding agents

GTM as code, in your repo.

When to choose which

Cargo vs Apollo, in short

Build the self-driving GTM engine