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
Tray.io

Revenue logic the GTM team owns

Tray.io is an enterprise automation and integration platform. Cargo is GTM orchestration: the data model, scoring, routing and agents, declared in code you own.

Start building

Trusted by GTM teams at

  • <1 h to a repAugment Code
  • New signal in 2 daysWeights & Biases
  • Dust
  • −40% enrichment costWorkOS
  • Braintrust
  • 2x pipelineDescript
  • 3x card spend per oppAlaan
  • +30% pipelineEngine
  • Scaleway
  • Preply
  • DataDome
  • 80% CRM enrichedOneflow
backed by y combinator

Tray.io integrates the business. Cargo runs the revenue engine.

On an iPaaS, every GTM concept is assembled out of generic steps and then maintained.

Tray.io and Cargo compared
Tray.ioTray.ioCargo
Built forTray.ioTray.ioIntegration across the businessCargoThe revenue engine
Owned byTray.ioTray.ioIT or central opsCargoThe GTM team
GTM semanticsTray.ioTray.ioAssembled out of generic stepsCargoData model, waterfalls, scoring, routing and territories
GTM as codeTray.ioTray.ioWorkflows built in Tray's visual builderCargoThe workspace in TypeScript, in your git repo
Best whenTray.ioTray.ioThe mandate is integration across systemsCargoThe mandate is revenue

In short. Tray.io keeps the integration estate; Cargo owns the revenue logic that decides what to do with what those integrations deliver.

What an iPaaS leaves you to assemble

On an integration platform each of these is built from generic steps.

  • 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

  • Enrichment waterfalls

    Providers in a waterfall, with retries and rate limits handled.

    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

  • Files in a repo you own

    Models, plays, territories and agents in TypeScript.

    • plan
    • context
    • initiatives
    • cadence
    • infra
    • context.ts
    • tam-building
    • account-scoring
    • evals
    • outputs
    • AGENTS.md
    • cargo.state.json

  • 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

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

Tray.ioChoose Tray.io when…
  • The mandate is integration across the business
  • IT or central ops owns the platform
  • Many systems need general-purpose workflows
  • Enterprise governance across those systems decides it
Choose Cargo when…
  • The mandate is revenue
  • The GTM team should own its own logic
  • Data model, scoring and routing should be built in
  • Coding agents should build and change the engine

Both true. Tray.io is the better integration platform. Cargo is the better GTM engine. Tray.io keeps the integration estate, and Cargo owns the revenue logic that decides what to do with what it delivers.

Cargo vs Tray.io, in short

If the mandate is integration across the business, compare iPaaS platforms directly. If it is revenue, Cargo: the data model, enrichment waterfalls, scoring, routing and the agents that run on them are primitives, declared in code the GTM team owns instead of a ticket queue.
Tray.io is an enterprise automation and integration platform: general-purpose workflows connecting many systems, with the governance and support an enterprise expects. Cargo is a GTM orchestration layer, so the data model, enrichment waterfalls, scoring, routing and the agents that run on them already exist as primitives, and the whole engine is declared in code you own.
When the mandate is integration across the business rather than revenue specifically, and the team that owns it is IT or central ops. Tray.io is designed for exactly that shape of problem and Cargo is not.
The GTM semantics. There is no account or contact model to build on, no enrichment waterfall, no scoring or routing primitive and no territories, so each is assembled out of generic steps and then maintained. That work is the reason the GTM team often ends up back in another team's ticket queue.
Yes. Tray.io keeps the integration estate, Cargo owns the revenue logic that decides what to do with what those integrations deliver.
Hypergrowth
“Essential. Innovative. Indispensable. Cargo let you build your unique growth engine, a much-needed solution in the market today.”
Guillaume CabaneGuillaume Cabane · Co-Founder @Hypergrowth
Oneflow
“Cargo allows us to aggregate data from external sources and orchestrate it to meet our go-to-market needs across different countries.”
Alexandre BejaouiAlexandre Bejaoui · Head of Revenue Operations @Oneflow
Weights & Biases
“Cargo allows us to grease the wheels across the revenue organization, surfacing signals to AEs, customer success, and leadership at just the right moment.”
Frederic PinchonFrederic Pinchon · Director Revenue Analytics @Weights & Biases

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
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 GojiberryCargo x PhantomBusterCargo x ZapierCargo x ApolloCargo x Chili PiperCargo x Common RoomCargo x MakeCargo x Tray.io

Company

ManifestoCommunityEventsJobsPartners DirectoryPartner Program

Legal

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

$ npm install -g @cargo-ai/cli