~/gtm-as-code/

Your GTMbelongs in git

Name: Cargo
SKU: cargo
Availability: InStock

Your ICP, your plays and your agents, declared as code: the foundation of a self-driving GTM engine.Your coding agents write it, Cargo keeps it working, and the repo is yours.

What GTM as Code means Read the quickstart

$npx @cargo-ai/cli@latest project init my-gtm

Works signed out. Scaffolds the repo, and deploys nothing.

my-gtm

plan/

The number you are chasing this period, the moves that get you there, and the outcomes that have to become true.

plan/company-plan.md

---title:description:period:--- ## The one goal _One number, with the number it starts from andthe date it has to be true by._ ## The forecast

context/

ICP, personas, objections and proof. One claim per file, in the folders a rep would recognise.

context/icp/_template.md

---title:description:--- ## Firmographic - Industry:- Size:- Geo: ## Pains

initiatives/

One file per bounded bet, with an owner, a deadline and success criteria you can check as true or false.

initiatives/_template.md

---title:status: proposedowner:deadline:--- ## Success criteria _Checkable true or false. No adjectives._ - [ ]

cadence/

A weekly plan, a daily log, and a carryover file that keeps the dropped balls visible.

cadence/weekly/_template.md

---week:serves:--- ## Theme _One sentence. The single thing this weekis about._ ## Deals to move | Account | Stage | The move | Owner |

infra/

Models, segments, tools, agents and plays in TypeScript, deployed with one command. The only layer that needs Cargo.

infra/README.md

# Infra What runs in production. A self-contained CargoCDK project: every `.ts` file here declares aresource, and deploy reconciles the workspaceto match. | File | What it does || --- | --- || `context.ts` | Brings `../context` under CDK |

context.ts

Puts the folder above under project management, so what your agent reads and what production runs on are the same files.

infra/context.ts

import { defineContext } from "@cargo-ai/cdk"; // Brings the repo's context/ directory under// CDK management.export const context = defineContext({  path: new URL("../context", import.meta.url)    .pathname,});

evals/

Test cases that catch a prompt change making your agents worse, before it ships.

evals/promptfooconfig.yaml

# Prompt regression tests. One suite per agent# whose prompt you own.description: GTM prompt suites providers:  - id: openai:gpt-4o    config:      temperature: 0 tests:  - file://_template/cases.yaml

outputs/

An append-only archive of the work, dated and tagged with what it produced. This is what gives an agent memory.

outputs/_template/README.md

---title:outcome:date:serves:--- ## What ran - Play:- Trigger:- Context used:

AGENTS.md

The operating manual your coding agent reads first, so it works the repo by its conventions rather than guessing.

AGENTS.md

# my-gtm GTM This repository is my-gtm's GTM engine:knowledge, infrastructure, and run history forthe whole go-to-market, managed as code. The knowledge layers ship empty, not populated.Every repeating artifact has a `_template.md`beside it to copy.

cargo.state.json

What is live right now, which is how a change can be previewed as a diff and rolled back to any earlier state.

cargo.state.json

{  "stateUuid": "<your deploy state>"}

Scaffolded from a template you can read. Plain text you can edit and delete, all of it MIT licensed.

~/how-it-runs/

Run it, then talk to your agent

You are not expected to write code. Your agent handles git and the deploys, and you review its work like a campaign brief.

Run one command, then ask your agent

The repo scaffolds signed out. Your agent reads AGENTS.md and opens a branch.

~/my-gtm

$ npx @cargo-ai/cli@latest project init my-gtm✓ Scaffolded my-gtm from getcargohq/cargo-manifest✓ Initialized a git repository.✓ Created the initial commit. nothing deployed, works signed out # in Claude Code, Cursor or Codex> seed this repo for my company reading AGENTS.md asking about your ICP and plays opened agent/tighten-icp, waiting on you # when you want Cargo running infra/$ cargo-ai login

Review what it changed

Every change is a diff on a branch, waiting for you before anything ships.

agent/tighten-icp2 files changed

context/icp/mid-market-saas.md

segment: mid-market SaaS

confidence: validated

- fit_signals: uses a CRM

+ fit_signals: uses a CRM, 50+ seats, hiring RevOps

infra/context.ts

model: accounts,

- signals: [fundingRound],

+ signals: [fundingRound, headcountJump],

owner: territory(region),

Waiting on your review

~/the-idea/

What “your GTM belongs in git” means

Your GTM belongs in git is the idea that go-to-market logic is software. Your ICP, your scoring, your plays and your agents live in a repository, so every change to them gets what a change to software gets: a diff, a review, a preview of what it moves, and a way back.

01
Every change is a diff
Scoring logic that lives in CRM settings and local folders has no memory and nothing to revert to. Plain rebuilt its model five times before moving it into a repo, which took under a day.
4:42Cole D'Ambra, Plain
02
Nothing ships without a review
A broken payment system fails loudly. A broken go-to-market workflow keeps running, and an agent repeats the mistake every day. The faster agents write, the more the review is worth.
23:10Karl Rafidimanana, TRA
03
See the blast radius before the merge
A pull request that changes a threshold says how many accounts it re-tiers before anyone approves it. A human still says yes.
4:42Cole D'Ambra, Plain
04
Files first, a database when you need one
Files are versioned, readable and consumable by agents. Graduate to a warehouse when concurrent writers make pull requests the bottleneck, not before.
49:55John Kutay, Rippling
05
Learn the architecture, not the syntax
Your agents write the code. What the person who owns the system needs is data architecture: durable tables, unique keys, system design.
1:09:32Aurelien Aubert and Noah Adelstein

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

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

~/gtm-as-code/

Your GTMbelongs in git

Your ICP, your plays and your agents, declared as code: the foundation of a self-driving GTM engine.Your coding agents write it, Cargo keeps it working, and the repo is yours.

What GTM as Code means Read the quickstart

$npx @cargo-ai/cli@latest project init my-gtm

Works signed out. Scaffolds the repo, and deploys nothing.

my-gtm

plan/

The number you are chasing this period, the moves that get you there, and the outcomes that have to become true.

plan/company-plan.md

---title:description:period:--- ## The one goal _One number, with the number it starts from andthe date it has to be true by._ ## The forecast

context/

ICP, personas, objections and proof. One claim per file, in the folders a rep would recognise.

context/icp/_template.md

---title:description:--- ## Firmographic - Industry:- Size:- Geo: ## Pains

initiatives/

One file per bounded bet, with an owner, a deadline and success criteria you can check as true or false.

initiatives/_template.md

---title:status: proposedowner:deadline:--- ## Success criteria _Checkable true or false. No adjectives._ - [ ]

cadence/

A weekly plan, a daily log, and a carryover file that keeps the dropped balls visible.

cadence/weekly/_template.md

---week:serves:--- ## Theme _One sentence. The single thing this weekis about._ ## Deals to move | Account | Stage | The move | Owner |

infra/

Models, segments, tools, agents and plays in TypeScript, deployed with one command. The only layer that needs Cargo.

infra/README.md

# Infra What runs in production. A self-contained CargoCDK project: every `.ts` file here declares aresource, and deploy reconciles the workspaceto match. | File | What it does || --- | --- || `context.ts` | Brings `../context` under CDK |

context.ts

Puts the folder above under project management, so what your agent reads and what production runs on are the same files.

infra/context.ts

import { defineContext } from "@cargo-ai/cdk"; // Brings the repo's context/ directory under// CDK management.export const context = defineContext({  path: new URL("../context", import.meta.url)    .pathname,});

evals/

Test cases that catch a prompt change making your agents worse, before it ships.

evals/promptfooconfig.yaml

# Prompt regression tests. One suite per agent# whose prompt you own.description: GTM prompt suites providers:  - id: openai:gpt-4o    config:      temperature: 0 tests:  - file://_template/cases.yaml

outputs/

An append-only archive of the work, dated and tagged with what it produced. This is what gives an agent memory.

outputs/_template/README.md

---title:outcome:date:serves:--- ## What ran - Play:- Trigger:- Context used:

AGENTS.md

The operating manual your coding agent reads first, so it works the repo by its conventions rather than guessing.

AGENTS.md

# my-gtm GTM This repository is my-gtm's GTM engine:knowledge, infrastructure, and run history forthe whole go-to-market, managed as code. The knowledge layers ship empty, not populated.Every repeating artifact has a `_template.md`beside it to copy.

cargo.state.json

What is live right now, which is how a change can be previewed as a diff and rolled back to any earlier state.

cargo.state.json

{  "stateUuid": "<your deploy state>"}

Scaffolded from a template you can read. Plain text you can edit and delete, all of it MIT licensed.

~/how-it-runs/

Run it, then talk to your agent

You are not expected to write code. Your agent handles git and the deploys, and you review its work like a campaign brief.

Run one command, then ask your agent

The repo scaffolds signed out. Your agent reads AGENTS.md and opens a branch.

~/my-gtm

Review what it changed

Every change is a diff on a branch, waiting for you before anything ships.

agent/tighten-icp2 files changed

context/icp/mid-market-saas.md

segment: mid-market SaaS

confidence: validated

- fit_signals: uses a CRM

+ fit_signals: uses a CRM, 50+ seats, hiring RevOps

infra/context.ts

model: accounts,

- signals: [fundingRound],

+ signals: [fundingRound, headcountJump],

owner: territory(region),

Waiting on your review

~/the-idea/

What “your GTM belongs in git” means

01
Every change is a diff
Scoring logic that lives in CRM settings and local folders has no memory and nothing to revert to. Plain rebuilt its model five times before moving it into a repo, which took under a day.
4:42Cole D'Ambra, Plain
02
Nothing ships without a review
A broken payment system fails loudly. A broken go-to-market workflow keeps running, and an agent repeats the mistake every day. The faster agents write, the more the review is worth.
23:10Karl Rafidimanana, TRA
03
See the blast radius before the merge
A pull request that changes a threshold says how many accounts it re-tiers before anyone approves it. A human still says yes.
4:42Cole D'Ambra, Plain
04
Files first, a database when you need one
Files are versioned, readable and consumable by agents. Graduate to a warehouse when concurrent writers make pull requests the bottleneck, not before.
49:55John Kutay, Rippling
05
Learn the architecture, not the syntax
Your agents write the code. What the person who owns the system needs is data architecture: durable tables, unique keys, system design.
1:09:32Aurelien Aubert and Noah Adelstein

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

Your GTMbelongs in git

Run it, then talk to your agent

Run one command, then ask your agent

Review what it changed

What “your GTM belongs in git” means

Every change is a diff

Nothing ships without a review

See the blast radius before the merge

Files first, a database when you need one

Learn the architecture, not the syntax

Build the self-driving GTM engine

Your GTMbelongs in git

Run it, then talk to your agent

Run one command, then ask your agent

Review what it changed

What “your GTM belongs in git” means

Every change is a diff

Nothing ships without a review

See the blast radius before the merge

Files first, a database when you need one

Learn the architecture, not the syntax

Build the self-driving GTM engine