Overview

Cargo puts go-to-market workflows under version-controlled definitions rather than limiting teams to configuring routing rules in a standalone interface. That makes it a compelling option for teams already comfortable managing operational logic as code, especially when workflows span lead qualification, routing, and follow-through. Teams seeking a simple fixed-price routing tool may prefer a narrower product: Cargo consumption draws on shared credits, and workflows pause when the balance runs out.

Key features

Cargo’s building blocks include agents, context, tools, data models, plays, territories, and apps. Alongside lead qualification, territory routing, round-robin assignment, workflow automation, and webhooks, this gives teams room to coordinate more than lead assignment alone.

Workflows can start on triggers or schedules, retry failed steps, and provide a trace of each run. Those controls help teams handle recurring processes and inspect execution when a step fails. The TypeScript-based Cargo CDK can preview changes, deploy declaratively, and roll back workspace resources, making it a better fit for developer-led teams that want operational changes managed through code.

Cargo lists compatibility with Claude Code, Cursor, Codex, Gemini CLI, Devin, and Replicas, plus more than 100 integrations, including HubSpot, Salesforce, Slack, Apollo.io, OpenAI, and Anthropic. That breadth is useful when a workflow needs to connect sales systems and coding agents, though the free tier does not include all integrations.

Credits cover enrichment actions, orchestration steps, and storage inserts. Every 100 orchestration steps or 1,000 storage inserts uses one credit, so teams need to consider both workflow activity and data operations when estimating consumption. If the balance reaches zero, workflows pause until credits are added; Cargo says no data is lost. That preserves data, but an exhausted balance can still interrupt operations.

Cargo says it maintains a SOC 2 Type II report and uses encryption in transit and at rest, access controls, backups, monitoring, and vulnerability management. It also says Slack data and Customer Content are not used to train foundation models. These safeguards may matter to teams handling customer and sales data.

Pricing

Cargo uses a freemium credit model. The free 100 credits plan costs 0.00 USD per month (billed From $0/mo) and includes up to 100 enrichment credits, 10K orchestration steps, 100K storage inserts, and community support. It is a practical starting point for evaluating a small workflow, but its credit allowance and support tier make it less suited to sustained, business-critical automation.

The 1.5K credits plan costs 165.00 USD per month (billed From $165/mo), and the 2.5K credits plan costs 250.00 USD per month (billed From $250/mo). Both include all 100+ integrations and email support. The higher tier buys a larger credit pool, so teams should choose based on expected consumption rather than integration access.

The 17K credits plan costs 1190.00 USD per month (billed From $1,190/mo) and adds priority support. The 50K+ credits plan costs 3000.00 USD per month (billed From $3,000/mo) and includes dedicated support. These tiers are aimed at teams with higher workloads or stronger support needs; custom pricing is not needed for the listed tiers.

Cargo offers a free trial. Customers unhappy within the first 14 days can contact the company for a full refund. Credit exhaustion pauses existing workflows until credits are added, which makes usage oversight important across every plan.

Platforms

Cargo is available on the web and through an API. Those options suit teams integrating workflow execution into existing systems, while the TypeScript CDK provides a code-oriented way to manage workspace resources.

Who it's for

Cargo is best for technical go-to-market teams that want coding agents to execute workflows defined in Git, and that can plan around credit consumption. Its routing rules, territory routing, round-robin assignment, and CRM connectors make it relevant to lead operations, while its broader primitives and integrations support workflows beyond routing. It is a weaker fit for teams that want predictable flat-rate usage or a routing tool without a developer-led workflow model.

Pros and cons

Git-based definitions and a TypeScript CDK: preview, declarative deployment, and rollback give developer-led teams a structured way to manage workflow changes.
Execution safeguards: retries and run traces help teams recover from failed steps and inspect workflow runs.
Broad agent and integration compatibility: support for named coding agents and more than 100 integrations gives teams options for connecting tools already in their stack.
Credits can complicate budgeting: several kinds of activity consume the shared balance, and workflows pause when it is exhausted.
Support varies by tier: the free plan offers community support, while priority and dedicated support are reserved for higher-cost plans.

Alternatives

For a broader comparison of lead-routing options, see Lead Routing Software.

91Leads CRM offers a free monthly allowance of 1,000 video-call minutes, then charges ₹0.20 per minute plus GST; choose it when that call-minute model is a closer fit.
Gradient Works has a free plan with 1,000 credits, five rep users, and one Carve scenario, making it worth considering for teams focused on territory and account planning.
Mixdesk has a free tier capped at 10 conversations and 10 connected channel accounts, with no AI messages; consider it when those channel limits match the need.
boberdoo starts with a $500/month ramp-up promotion for three months and a $250 setup fee; it is an option for buyers considering a paid lead platform.
LeadExec offers a Growth plan with 10,000 leads per month, 100,000 pings per month, and overage charges; consider it when those volume-based allowances suit the workflow.
Bluebird Route has a monthly Base plan starting at $600 per month under an annual contract, with 100 seat licenses and up to 100 leads per month.
Lead Distro AI offers a Call Tracking Only plan at $147 per month, with usage billed separately; it may suit teams prioritizing call tracking.
Default offers a Growth plan billed annually at $15,000 per year, with 24,000 enrichment credits and 200,000 workflow runs per year; consider it when annual quotas and Slack support fit better.

Verdict

Choose Cargo if your team wants to manage go-to-market workflows in Git, connect coding agents and sales tools, and values retries, run traces, and a TypeScript CDK. The central trade-off is credit-based consumption: estimate usage carefully, because workflows pause when credits run out. Teams seeking simpler fixed-cost routing should look elsewhere.

	Cargo	Q-assign
Free plan	Yes	No
Free trial	Yes	No
Paid from	$165/mo	—
Open source	No	No
Platforms	api, Web	Web
Free plan	Yes	—
Paid from	165 /mo	—
Routing rules	Yes	Yes
Territory routing	Yes	Yes
Round-robin assignment	Yes	Yes
CRM connectors	5	—
Lead qualification	Yes	Yes
Workflow automation	Yes	Yes
Webhook support	Yes	—

Cargo vs Q-assign

Cargo

Q-assign