Revenue logic you can review
Make builds scenarios on a visual canvas. Cargo declares the revenue engine in TypeScript, planned as a diff, with accounts and routing built in.
Trusted by GTM teams at
Make draws the workflow. Cargo declares it.
A scenario is a picture. A Cargo project is text a person reviews and a coding agent can change.
 Make | Cargo | |
|---|---|---|
| Built for | General-purpose automation | The revenue engine |
| GTM as code | A scenario on a visual canvas | TypeScript in your git repo, planned as a diff |
| GTM semantics | None: built from generic modules | Accounts, contacts, enrichment and routing as primitives |
| AI agents | No text for an agent to read or write | Code a coding agent reads and changes |
| Best when | Nobody on the team will read a diff | The work is a revenue engine |
In short. A common split: Cargo owns the revenue engine, and Make handles internal automation that has nothing to do with go-to-market.
What a canvas leaves you to build
Make has no GTM semantics. In Cargo these ship with the platform.
One GTM data model
Accounts, contacts, deals and custom objects every play reads.
CompaniesAll recordsFilterSort12,480 records6/24 columnsName+23DomainEmployeesCountryIndustryICP fitAdd columnNorthwindnorthwind.com420United StatesLogistics82Contosocontoso.com1,200FranceSoftware74Globexglobex.com3,400GermanyManufacturing91Initechinitech.com260United StatesSoftware68Fabrikamfabrikam.com880FranceRetail55Umbrellaumbrella.com2,100United KingdomHealthcare79Stark Logisticsstarklogistics.com640United StatesLogistics88Wayne Freightwaynefreight.com1,450SpainLogistics71Enrichment waterfalls
Providers in a waterfall, with retries and rate limits handled.
Enabled
Enrich inbound leadsSearch...4/4 nodesFilter5/5 statusesAll versionsAll batchesAll datesStartstartFind emailfind_emailEnrich companyenrich_companyICP fitscore_icpAda Lovelaceada@northwind.comNorthwind, 420 employees82/100Grace Hoppergrace@contoso.comContoso, 1,200 employees74/100Alan TuringNo email found, 0 creditsGlobex, 3,400 employees91/100Katherine Johnsonkatherine@initech.comRunning...DefaultFiles 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
Planned as a diff
Every change is previewed as a plan and reviewed before it deploys.
cargocommented on pull request #312$ cargo-ai project plan~ tool.score-signals update= 41 resources unchangedPlan: 1 to update. Merging deploys it.Scoring and territories
Fit, readiness and ownership as primitives, not generic modules.
Revenue organizationNew territoryNew capacityMembersTerritoriesCapacitiesA group of members that shares incoming records. Weights and a fallback decide who is next.
Territories3 territoriesUnited StatesInbound from North AmericaFranceInbound from FranceEMEAEverything else in EuropeUnited StatesLabel*United StatesChoose a label to your territory
Color*Choose a color to represent your territory
DescriptionInbound from North AmericaChoose a description
Members*AMAlice Martin
50SOSam Okoro50Add memberPick members you want to be part of your territory
Fallback MemberDCDana Cole
The member that will be used when other territory members are not available (e.g. Capacity reached).
SaveBuilt by coding agents
Your coding agent changes it as diffs, over the CLI or MCP.
Account researcherDeployInstructionsResearch 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.ActionsEnrich companyenrich_company
Search the webweb_searchGet companyhubspot_get_companyThe building blocks of the agent. They are the actions the agent can take. The agent will use the actions to achieve the goal.
Advanced settings
Claude Sonnet 5Research Northwind and tell me if it fits our ICP.Reasoned for a few secondsGet company0Enrich company1Search the web2Northwind 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 request
cargo-ai project planshows 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 coversexport 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.
Choose Make when…- You want to build visually
- The work is general-purpose automation
- Nobody on the team will read a diff
- Nobody should have to open a terminal
- The work is a revenue engine
- Every change should be reviewed as a diff
- Accounts, enrichment and routing should be built in
- Coding agents should read and change the logic
Both true. Make is the better visual builder. Cargo is the better GTM engine. A common split: Cargo owns the revenue engine, and Make handles automation that has nothing to do with go-to-market.
Cargo vs Make, in short
“Essential. Innovative. Indispensable. Cargo let you build your unique growth engine, a much-needed solution in the market today.”
Guillaume Cabane · Co-Founder @Hypergrowth
Build the self-driving GTM engine
Your coding agents build it on Cargo.Or our team builds, operates and improves it with you.