Office hours: Build your self-driving GTM engine·Oct 29, 9:00am PT, onlineRegister→
Cargo
  • PrimitivesData ModelsYour companies, contacts and deals, merged from every sourceContextWhat your team knows, as files every agent readsTerritoriesWho sells where, defined onceMailboxesMailboxes in your reps' names, warmed up and kept under limitsToolsThe actions your agents, plays and reps callAgentsAI that researches, decides and writes, reading your contextPlaysWorkflows that run on a trigger or a schedule, with retriesAppsInternal apps for your reps, hosted on Cargo
    Add-onsChrome ExtensionSell faster, right in your browserButtonTrigger AI agents inside your CRMFormTurn any tool into an embeddable formSlackTag Cargo in Slack. It does the GTM workGitHubPlan on every pull request, deploy on merge
    MoreProjectsDefine your entire GTM in codeCLIUse Cargo from your terminalMCPUse Cargo from Claude and ChatGPTDeveloper resourcesCargo API docs, OpenAPI spec, auth docs, webhooks, MCP serverAPI ReferenceExplore the Cargo APIDocumentationLearn how to use CargoIntegrationsConnected to your entire GTM stack
  • VeriffHow Veriff replaced MuleSoft with Cargo under NetSuite, Stripe and SalesforceAugmentHow Augment Code routes developer sign-ups to reps in under an hourWeights & BiasesHow Weights & Biases ships a new purchase signal in 2 days on CargoSee all
  • Pricing
  • Cookbooks
  • Blog
Sign in

GTM infrastructurefor coding agents

Give your coding agent the primitives to build your go-to-market. Cargo runs it.

Watch the five-minute walkthrough

Trusted by GTM teams at

  • <1 h to a repAugment Code
  • New signal in 2 daysWeights & Biases
  • Dust
  • WorkOS
  • Braintrust
  • 2x pipelineDescript
  • Alaan
  • Engine
  • Scaleway
  • Preply
  • DataDome
  • 80% CRM enrichedOneflow
  • 60% less eng. workGorgias
  • 1,000+ h savedAshby
  • 5x fewer API callsVeriff
  • Mooncard
  • Qobra
  • 80% less upkeepUpfluence
backed by y combinator
~/why-cargo/

Built in an afternoon.Still working next quarter.

AI made it easy to build GTM workflows. Keeping them working is the hard part, so Cargo runs what your coding agent builds.

Without Cargo

  • Ten tools, ten API keys, ten bills
  • It stops when the person who built it is out
  • A quota runs out and it breaks silently
  • A lead goes wrong and nobody can say why
Claude Code
mcp.json
Apollo
Firecrawl
Instantly
.env
Cursor
hubspot-cli
Exa
cron: 0 9 * * 1
Notion
Lusha
vs

On Cargo

  • One platform and one bill, data providers included
  • Keeps working when its builder is out
  • Retries and rate limits, so a quota never stops it
  • Every lead comes with its why
SuccessAda Lovelace
2.41s6 spans601Nov 3rd, 2026 at 10:14:02
WaterfallSpans
Execution
0ms603ms1.21s1.81s2.41s
Ada Lovelace
2.41s
NorthwindEnrich company
640ms
82/100Scoring
310ms
United StatesSwitch
40ms
alice@acme.comAllocate
260ms
Owner updatedSalesforce Update owner
820ms
Message sentSlack Send message
240ms
~/the-primitives/

What your agent builds with

Data models, context, tools, agents and plays, each already built to run in production. Your agent puts them together for your GTM, and your reps use the same ones in the app.

Data models

Your raw data: CRM, warehouse, product usage and enrichment merged into one set of companies, contacts and deals.

About data models

Context

What you learn from that data, written down as files in your repo: your ICP, personas, objections and rules. Every agent reads the same files.

About context

Territories

Who sells where, defined once: reps synced from your CRM, grouped into territories, each with a cap. Every play and agent that assigns a lead reads them.

About territories
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

Today

  • alice@acme.com assigned in Route inbound leads10:14 AM
  • sam@acme.com assigned in Route inbound leads9:52 AM

Yesterday

  • alice@acme.com assigned in Route inbound leads4:31 PM

Mailboxes

Mailboxes in your reps' names, on a domain you own. Cargo creates them, warms each one up and keeps it under its daily limit.

About mailboxes
Mailboxes
New folderNew mailbox
Email
Status
Type
Updated at
dana@acme.com
Active
Google
2 hours ago
alice@acme.com
Active
Google
2 hours ago
sam@acme.com
Pending
Google
5 minutes ago
dana@acme.com
Send allowance
Daily limit50
Sent (24h)18
Left32
Warm-upActive
Daily target20
Warm-up sent412
Inbox98%
Spam2%

Tools

One action, like enriching a contact or posting to Slack. Agents, plays and reps call the same tools.

About tools

Agents

AI that researches, decides and writes, reading your context and calling your tools. Every run is traced step by step.

About agents

Plays

A workflow that runs on a trigger, like a new HubSpot contact, or on a schedule. Cargo retries failed steps, stays within API limits and logs every run.

About plays

Apps

Internal apps for your reps, hosted on Cargo and wired to your data, tools and agents.

About apps

Observability

Built into every primitive: each run of a play, agent or tool is traced step by step, with what it returned and what it cost. Alerts tell you when something fails.

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
~/the-framework/

GTM as code

How it ships and stays working. Your agent writes the primitives as code in a repo you own, you review the pull request, and merging deploys it.

  1. 1. Agent writes it

    Claude Code, Cursor or Codex edits your files.

    infra/plays/inbound.ts
    export const inbound = definePlay("inbound", { model: contacts, workflow: routeLead, });

  3. 2. You review it

    The pull request lists what will change.

    $cargo-ai project plan
    + play inbound+ workflow route-lead~ model contacts2 to create, 1 to updateposted on PR #42

  5. 3. Merge deploys it

    Cargo runs the new version and logs every run.

    $cargo-ai project deploy
    deployed, 3 resourcesrun #1 Northwind scored 82 / 100 routed to Alicev12 kept to roll back

  7. 4. Agents improve it

    Agents read the run logs and open a pull request.

    Raise min score
    opened by an agentafter 1,240 runs- minScore: 70+ minScore: 75awaiting your approval

Nothing goes live until you approve it. Each approved edit goes through steps 2 and 3 again.

How projects workCookbooksIntegrations
~/where-it-fits/

Works with the stack you have

For GTM engineers, RevOps and revenue teams. Cargo reads from your tools and writes the results back where your team works.

  1. What Cargo reads

    The data you already have, wherever it lives today.

    • HubSpot: Your CRM
    • Salesforce: Your CRM
    • Snowflake: Your warehouse
    • BigQuery: Your warehouse
    • Postgres: Your warehouse or product database
    • Stripe: Billing
    • Amplitude: Product usage
    • Mixpanel: Product usage
    • Snitcher: Website visitors
    • Forms: Website forms, by webhook
    • Calendar: Meetings, from Google Calendar
    • Signals: Cargo Signals: job changes, funding and hiring
    • Apollo: Company and contact data
    • Sheets: Google Sheets and CSV files
    • 100s more

  3. The primitives, as code

    Every primitive, as a file in a repo you own.

    Your repo
    • my-gtm/
    • ├── context/
    • │ ├── icp/mid-market.mdICP
    • │ └── persona/revops.mdpersona
    • └── infra/
    • ├── models/companies.tsdata model
    • ├── territories/emea.tsterritory
    • ├── mailboxes/sdr.tsmailbox
    • ├── tools/enrich.tstool
    • ├── agents/research.tsagent
    • ├── plays/inbound.tsplay
    • └── apps/rep-desk.tsapp

  5. Where results go

    Back into the tools your team already works in.

    • HubSpot: Fields, scores and owners, back in your CRM
    • Salesforce: Fields, scores and owners, back in your CRM
    • Slack: Alerts and approvals for your team
    • Email: Sent from mailboxes in your reps' names
    • Outreach: Your sequencer
    • lemlist: Your sequencer
    • Instantly: Your sequencer
    • Claude: Your tools and agents, over MCP
    • ChatGPT: Your tools and agents, over MCP
    • Chrome: The Chrome extension, next to the page your rep is on
    • Apps: Internal apps for your reps, hosted on Cargo
    • Button: Reps run a tool from the record
    • Sheets: Rows written to Google Sheets
    • Webhooks: Results sent to any other system
    • API: Read results from your own code
~/use-cases/

What teams use Cargo for

Each of these is a cookbook: primitives already wired together for one job. Your coding agent adds it to your repo and adapts it to your team.

See all cookbooks
IQ

Inbound qualification

Every demo request is matched to its company, checked against your ICP and sent to the right rep.

VI

Visitor identification

See which companies visit your website and which pages they read.

NH

New hire detection

Get a Slack alert when a decision-maker joins a company in your ICP.

RS

Readiness scoring

Every account gets a score that rises with fresh signals and fades as they age. Accounts that cross your line are posted to Slack.

CE

CRM enrichment

Fill in the missing fields on your CRM accounts and contacts, and keep them filled in.

TB

TAM building

List every company in your market and keep the list in Cargo, ready to score and route.

~/built-on-cargo/

Teams that run their go-to-market on Cargo

descript2x

Descript doubled pipeline from free sign-ups

One play runs on every sign-up. Pipeline doubled in 6 months.

augment
gorgias
oneflow80%

Oneflow keeps its CRM 80% enriched

Four sales motions across several countries run on Cargo.

ashby
veriff
Pivot
“Most ICP models are built once and forgotten. Ours runs perpetually: every closed-won, every churn, every pattern. Cargo enriches the gaps, does the analysis, and deploys it as a skill we can call from anywhere. This is what infrastructure actually means.”
Alexis GirardAlexis Girard · Pivot
Qobra
“I've built a full BDR execution analysis in 5 minutes. Claude Code plugged straight into Cargo datasets. This is a gold mine.”
Vincent BonjeanVincent Bonjean · Qobra
Gorgias
“I built a meeting prep agent in one Claude Code session. It pulls Gong calls, Salesforce history, deal-won patterns, and sales activity, and generates a full brief before every meeting. My reps went from 30 minutes of prep to zero. The data was always there. It just needed infrastructure to act on it.”
Guillaume AubertGuillaume Aubert · Head of GTM Engineering @Gorgias
“Creating a tool: it works. Creating a play: it works. Creating an agent: it works too.”
Eliott M'Barali · GTM engineer working with Alma, building on Cargo from his coding agent
~/two-ways-in/

Build it yourself, or have our team build it

Both options run on the same Cargo account and the same repo. If our team builds it first, your team can take it over later without moving anything.

  • For GTM engineers and their coding agents

    Start building

    Your coding agent writes the workflows, and Cargo runs them in production.

    • Your GTM as code, in a repository you own
    • Data models, context and workflows, ready for your coding agent
    • Free credits to start, no card
    Start building
  • For revenue leaders and teams that want it built and run for them

    Build with us

    Our team builds, operates and continuously improves it with you.

    • Working GTM workflows, delivered as a repository you own
    • A dedicated Slack channel, onboarding and on-demand calls
    • Your engineers can take it over at any time
~/security-compliance/

Enterprise-grade infrastructure

SOC 2 Type II certified

Audited every year by independent third parties.

Audit log & evals

Every run and approval is logged. Evals gate prompt changes.

Data residency

Choose the region where your data lives.

SSO & role-based access

SAML single sign-on and role-based permissions.

Version history

Every play and agent is versioned, with diffs and rollback.

GDPR & trust center

DPA, sub-processor list and security docs for procurement.

Frequently asked questions

What Cargo is, how you build on it, and how to start.

Cargo is where your GTM workflows run: the ones that enrich, score, route and email your leads and accounts. Your coding agent (Claude Code, Cursor or Codex) writes them in TypeScript with the Cargo CDK and CLI, in a git repository you own. Cargo runs them in production and logs every step of every run.
Your tools stay: your CRM, your warehouse and your sequencer. What you stop building and maintaining is everything between them: the scripts and glue, scheduling, retries and rate limits, matching records to accounts, connector logins, and tracing a run that went wrong. Cargo is the infrastructure those workflows run on.
No. An agent connected to MCP servers calls tools live: it works out every step again each time it runs, acts before anyone can check what it will do, and leaves nothing to review. On Cargo, your agent writes the workflow as code in your repository. You review the change once, Cargo runs it the same way on every trigger, and every run is logged. Cargo also has an MCP server, so the same agent can read the results and propose the next change.
Start building if you have GTM engineers or coding agents to do the building: your agents write your go-to-market as code in a repository, and Cargo keeps it working in production. Build with us if nobody on your team will build it: our team builds, operates and continuously improves it with you, delivered as a repository you own. Both run on the same Cargo account and repo, so a team that starts with us can take it over later.
One that keeps working without somebody holding it up. AI made GTM workflows easy to build; keeping them working is the hard part. They depend on the one person who built them, they break when a quota, a schedule or an API changes, and when a lead goes to the wrong rep nobody can say why. On Cargo they start on a trigger, retry when a step fails, and leave a trace of every run, written in your repo and deployed with one command.
Run npx @cargo-ai/cli@latest project init my-gtm. It scaffolds a go-to-market repo, runs git init, writes the first commit, installs the Cargo skills, and can create the GitHub remote. Then open the folder in your coding agent and describe the workflow you want. It writes the TypeScript files, and you can also run every step yourself from the CLI.
Claude Code, Cursor, Codex, Gemini CLI and Devin. They all read the same Cargo skills, call the same MCP server, and write to the same TypeScript project. Cargo can also start Devin itself, from a play or from a failed batch.
Cargo is SOC 2 Type II certified, with SSO and role-based access, data residency, audit logs, and GDPR documentation for procurement.
Cargo
Backed byY CombinatorSOC 2 Type IICertified
LinkedinX

Product

Data ModelsContextTerritoriesMailboxesToolsAI AgentsPlaysAppsIntegrationsPricing

Add-ons

Chrome extensionButtonFormSlackGitHub

Build

DocsDeveloper resourcesCargo API docsCargo OpenAPI specCargo auth docsCargo webhooksCargo MCP serverProjectsClaude CodeCodexCursorAll coding agents

Resources

ReportsBlogCustomer storiesCookbooksEnrichmentRoutingSignalsScoringCRM hygieneAd audiencesGTM skillsGTM EngineeringGlossaryCompareCargo x ClayCargo x WorkatoCargo x n8nCargo x DeeplineCargo x DefaultCargo x LeanDataCargo x UnifyCargo x ValleyCargo x Gojiberry

Company

ManifestoCommunityEventsJobsPartners DirectoryPartner Program

Legal

SecurityTerms of servicePrivacy PolicyRefundsDPASupport
© 2026 Cargo
 ////////    ///////    ////////     ////////    ///////
///         ///   ///   ///   ///   ///         ///   ///
///         ///   ///   ///   ///   ///         ///   ///
///         /////////   ////////    ///  ////   ///   ///
///         ///   ///   /// ///     ///   ///   ///   ///
///         ///   ///   ///  ///    ///   ///   ///   ///
 ////////   ///   ///   ///   ///    ///////     ///////

$ npm install -g @cargo-ai/cli