Everything around the meeting

Name: Cargo
SKU: cargo
Availability: InStock

Chili Piper qualifies, routes and books the inbound lead in seconds. Cargo runs what happens before the form and after the meeting.

Start building

Trusted by GTM teams at

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

Chili Piper books the meeting. Cargo decides who owns the record.

Chili Piper owns the moment a hand-raiser arrives. Cargo orchestrates the engine around that moment.

Chili Piper and Cargo compared
	Chili Piper	Cargo
Built for	The moment a hand-raiser arrives: qualify, route, book	The engine before the form and after the meeting
Meetings	Concierge booking, calendars and rescheduling	Not a meeting-booking product
Routing	The inbound lead to the right rep	Territories and assignment on every record, CRM-agnostic
GTM as code	Configured in the Chili Piper app	The workspace in TypeScript, in your git repo
Best when	Inbound speed to lead is the constraint	Every record needs enrichment, scoring and an owner

In short. The common pairing: Cargo enriches and scores the record and decides who should own it; Chili Piper turns that decision into a booked meeting.

What happens around the meeting

A booked meeting is one moment. Every record needs the rest.

Enrichment waterfalls
Fill the fields a route depends on before it runs.
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
Every assignment traced
Each run leaves a log, so why a lead reached a rep has an answer.
Traces
All triggers4/4 statusesLast 7 days
3,912 traces
Record
Trigger
Spans
User
Duration
Started at
Finished at
Credits
Ada Lovelace
Route inbound leads
6 spans60
2.41s
Nov 3rd, 2026 10:14:02
Nov 3rd, 2026 10:14:04
1
Northwind
Account researcher
3 spans30
AMAlice Martin
8.62s
Nov 3rd, 2026 10:11:40
Nov 3rd, 2026 10:11:49
3
Katherine Johnson
Route inbound leads
5 spans41
1.97s
Nov 3rd, 2026 10:09:13
Nov 3rd, 2026 10:09:15
1
Contoso
Enrich new accounts
4 spans40
3.18s
Nov 3rd, 2026 09:58:21
Nov 3rd, 2026 09:58:24
2
Grace Hopper
Route inbound leads
6 spans60
2.06s
Nov 3rd, 2026 09:51:07
Nov 3rd, 2026 09:51:09
1
Globex
Account researcher
4 spans40
MDMarc Dubois
11.3s
Nov 3rd, 2026 09:44:52
Nov 3rd, 2026 09:45:03
4
Alan Turing
Route inbound leads
6 spans60
2.28s
Nov 3rd, 2026 09:39:18
Nov 3rd, 2026 09:39:20
1
Initech
Enrich new accounts
4 spans31
4.05s
Nov 3rd, 2026 09:31:46
Nov 3rd, 2026 09:31:50
2
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
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 Chili Piper when…

Inbound speed to lead is the constraint
The job is getting a qualified lead into a calendar
You want concierge booking and rescheduling
A narrow tool that does one thing well is enough

Choose Cargo when…

Every record needs enrichment, scoring and an owner
Routing should work across CRMs, not inside one
The work starts before the form and goes past the meeting
Coding agents should own territories and assignment

Both true. Chili Piper is the better meeting booker. Cargo is the better GTM engine. The common pairing: Cargo decides who should own the record, and Chili Piper turns that decision into a booked meeting.

Cargo vs Chili Piper, in short

If the job is booking inbound meetings, compare scheduling tools directly: Cargo is not one. If the problem is everything around the meeting, Cargo: it enriches and scores every record, routes it with territories and assignment in any CRM, and logs why each lead reached its rep.

Chili Piper owns the moment a hand-raiser arrives: qualifying a form submission, routing it to the right rep and booking the meeting immediately, with the handoff handled. Cargo orchestrates the engine around that moment, including everything that happens before a form is ever submitted and everything downstream of the meeting.

When inbound speed to lead is the constraint you are actually solving. Chili Piper is very good at the specific job of getting a qualified inbound lead into a calendar in seconds, and buying a narrow tool that does one thing well beats building it.

Cargo routes, with territories and assignment as first-class primitives, and it is CRM-agnostic rather than tied to one CRM. It is not a meeting-booking product: the concierge experience, the calendar mechanics and the reschedule handling are Chili Piper's job.

Yes, and this is the common pairing. Cargo enriches and scores the record and decides who should own it; Chili Piper takes that decision and turns it into a booked meeting.

“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

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

Chili Piper and Cargo compared
	Chili Piper	Cargo
Built for	The moment a hand-raiser arrives: qualify, route, book	The engine before the form and after the meeting
Meetings	Concierge booking, calendars and rescheduling	Not a meeting-booking product
Routing	The inbound lead to the right rep	Territories and assignment on every record, CRM-agnostic
GTM as code	Configured in the Chili Piper app	The workspace in TypeScript, in your git repo
Best when	Inbound speed to lead is the constraint	Every record needs enrichment, scoring and an owner

Chili Piper

Cargo

Built for

The moment a hand-raiser arrives: qualify, route, book

The engine before the form and after the meeting

Meetings

Concierge booking, calendars and rescheduling

Not a meeting-booking product

Routing

The inbound lead to the right rep

Territories and assignment on every record, CRM-agnostic

GTM as code

Configured in the Chili Piper app

The workspace in TypeScript, in your git repo

Best when

Inbound speed to lead is the constraint

Every record needs enrichment, scoring and an owner

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,

});

Everything around the meeting

Chili Piper books the meeting. Cargo decides who owns the record.

What happens around the meeting

Enrichment waterfalls

Scoring on your ICP

Routing that knows the org

Every assignment traced

One GTM data model

Built by coding agents

GTM as code, in your repo.

When to choose which

Cargo vs Chili Piper, in short

Build the self-driving GTM engine

Everything around the meeting

Chili Piper books the meeting. Cargo decides who owns the record.

What happens around the meeting

Enrichment waterfalls

Scoring on your ICP

Routing that knows the org

Every assignment traced

One GTM data model

Built by coding agents

GTM as code, in your repo.

When to choose which

Cargo vs Chili Piper, in short

Build the self-driving GTM engine