Your GTMbelongs in git
A repo framework for a self-driving go-to-market: your ICP, your plays and your agents,declared as code. Your coding agents write it, Cargo runs it, and the repo is yours.
$npx @cargo-ai/cli@latest project init my-gtmInstall Cargo by following https://api.getcargo.io/INSTALL.md, then run npx @cargo-ai/cli@latest project init my-gtm and help me seed the repo for my company.One repository, every layer of your GTM
A repository, scaffolded from a template you can read before you run anything.Every file is plain text you can edit and delete, and all of it is MIT licensed.
- plan/
The number you are chasing this period, the moves that get you there, and the outcomes that have to become true.
- context/
ICP, personas, objections and proof. One claim per file, in the folders a rep would recognise.
- initiatives/
One file per bounded bet, with an owner, a deadline and success criteria you can check as true or false.
- cadence/
A weekly plan, a daily log, and a carryover file that keeps the dropped balls visible.
- infra/
Models, segments, tools, agents and plays in TypeScript, deployed with one command. The only layer that needs Cargo.
- context.ts
Puts the folder above under CDK management, so what your agent reads and what production runs on are the same files.
- evals/
Test cases that catch a prompt change making your agents worse, before it ships.
- outputs/
An append-only archive of the work, dated and tagged with what it produced. This is what gives an agent memory.
- AGENTS.md
The operating manual your coding agent reads first, so it works the repo by its conventions rather than guessing.
- 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.
Run it, then talk to your agent
You are not expected to write code. Your agent handles git, the conventions and the deploys,and you review its work the way you would review a campaign brief.
It scaffolds the repo, runs git init, writes the first commit and installs the Cargo skills. It works signed out, and it deploys nothing.
Claude Code, Cursor or Codex reads AGENTS.md, interviews you, and fills the layers with your company rather than the template's.
Work arrives as a diff you approve. That is the gate: nothing reaches a customer that you have not read.
Sign in with cargo-ai login when you want Cargo running infra/ for you. Everything above it works standalone until you do.
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.
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.
Cole D'Ambra, Plain, at 4:42Nothing 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.
Karl Rafidimanana, TRA, at 23:10See 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.
Cole D'Ambra, Plain, at 4:42Files 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.
John Kutay, Rippling, at 49:55Learn 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.
Aurelien Aubert and Noah Adelstein, at 1:09:32
Give your agents a runtime
Bring the agents you have.Start free, deploy in one command.