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
~/context/

One shared contextfor your team and your agents

Your ICP, personas, positioning, and playbooks as files that every workflow and agent reads.

Start building

Trusted by GTM teams at

  • Augment Code
  • Weights & Biases
  • Dust
  • WorkOS
  • Braintrust
  • Descript
  • Alaan
  • Engine
  • Scaleway
  • Preply
  • DataDome
  • Oneflow
backed by y combinator

From a folder of markdown to every agent

Write what your team knows as files, deploy, and every agent reads the same version.

1. Files you write

Markdown in a context folder, next to your code.

context/
icp.md
positioning.md
personas/
head-of-growth.md
vp-sales.md
playbooks/
outbound.md

2. Synced on deploy

One defineContext call, shipped with the rest of the project.

export const context =
defineContext({
path: "context",
});
$ cargo-ai project deploy

3. Read by

Every agent, play, coding agent, and teammate.

  • Agentscapabilities: ["context"]
  • Plays and toolsthrough their agent steps
  • Coding agentscargo-ai context graph get
  • Your teamthe workspace context repo
~/knowledge-graph/

Your files, linked into a graph

Cargo derives a knowledge graph from your context that agents can traverse.

ICPPersonasPositioningPlaybooksSignalsIicp.mdIfirmographics.mdPhead-of-growth.…Prevops-leader.mdPchampion.mdOpositioning.mdOmessaging.mdOcompetitors.mdBoutbound.mdBexpansion.mdSintent.mdSproduct-usage.md

Put what you know to work

One set of files behind every agent, play, and teammate.

Ground your agents in your ICP

A qualify agent reads the same file your reps do.

context/icp.md
---title: Ideal customer profile---## Who we sell to- B2B software, 200 to 2,000 employees- A RevOps or GTM engineering owner- Salesforce or HubSpot as the CRM## Who we skip- Agencies and resellers## Who we talk to- personas/vp-sales.md- personas/head-of-growth.md## When to reach out- Hiring a RevOps or GTM engineer- Moving to a new CRM

Review changes like code

Context lives in your repository, so a change is a pull request.

context/personas/vp-sales.md
- budget is set in Q4+ budget is set in Q1

One version for everyone

Edit a file, deploy, and every reader gets the change.

Terminal
$ git commit -m "Budget moves to Q1"$ cargo-ai project deploy

Have an agent write your context, or write it yourself

Both write the same code into your repo. Pick who types it.

Set up Claude Code with Cargo
Claude Code~/my-gtm

Write our ICP and the three objections we hear most into context, so every agent reads the same thing.

  • Editedcontext/icp.md+2
  • Rancargo-ai project plan
    + create context:workspace1 to create, 0 to update, 14 unchanged.
  • Rancargo-ai project deploy
    context:workspace created1 created, 0 updated, 14 unchanged.
Worked through 3 steps

Deployed. Every agent now reads the same ICP and objections from context/.

1import { defineContext } from "@cargo-ai/cdk";
2
3// Sync a local folder of .md/.mdx as your
4// workspace knowledge base
5export const context = defineContext({
6path: "context",
7files: { "generated/icp.md": buildIcp() },
8});
$ cargo-ai project plan
+ create context:workspace
1 to create, 0 to update, 14 unchanged.
$ cargo-ai project deploy
✓ context:workspace created
✓ 1 created, 0 updated, 14 unchanged.

Cookbooks built on context

Agents that read your context, and the ones that keep it current.

AS

Account scoring

Score every account against your ICP on a schedule.

CC

Call capture

Turn your recorded calls into a go-to-market knowledge base.

IQ

Inbound qualification

Qualify and route inbound demo requests from your website form.

LC

LinkedIn content

Draft LinkedIn posts every week from your own proof points.

WC

Web capture

Keep your company context current from your website and competitors' pages.

WL

Win loss review

Run a monthly win-loss review of your CRM's closed deals.

See all cookbooks
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 Gojiberry

Company

ManifestoCommunityEventsJobsPartners DirectoryPartner Program

Legal

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

$ npm install -g @cargo-ai/cli