Office hours: Build your self-driving GTM engine·Oct 29, 9:00am PT, onlineRegister→
Cargo
  • ProductAgentsReduce manual effort and close more deals with AIPlaysAutomate every stage of lead management so you can move fasterToolsAutomate repetitive tasks so your team can focus on what drives impactData ModelsUnify, organize, and activate your revenue dataAppsCustom interfaces for your team, wired to your live GTMTerritoriesModel your team, territories, and capacity in one placeContextOne shared knowledge base for your team and agents
    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
Blog

Full-Cycle AEs vs SDR Teams: Which Model Wins in 2026?

9 Nov8min read
MaxMax

The traditional SDR model is under siege. For decades, the playbook was simple: hire junior reps, train them on BANT qualification, give them lists and dialers, and watch the pipeline flow.

That model is breaking. Not because SDRs can’t work, but because for many B2B companies, there’s now a better alternative: Full-Cycle AEs supported by GTM Engineering.

One GTM engineer can automate what 10 SDRs used to do manually. AI handles research that took 20 minutes in under a minute. Waterfall enrichment delivers 80%+ coverage automatically. Signal-based routing ensures AEs work the hottest accounts at the perfect time.

The question isn’t “How do I build an SDR team?” anymore. It’s “Should I even build one at all?”

This guide helps you answer that question.

The Traditional SDR Model #

For context, here’s what the traditional model looks like:

The Assembly Line

  • SDRs prospect and qualify → Hand off to AEs → AEs close → Hand off to CS

The Economics

  • SDR: $70K OTE + $30K tools/overhead = $100K fully loaded
  • Output: 12-15 meetings/month → 6-8 opportunities/month → 1-2 closed deals/month
  • 6-9 month ramp before full productivity
  • 18-24 month tenure before promotion or churn

The Management Overhead

  • 1 SDR manager per 6-8 reps
  • Weekly coaching, call reviews, enablement
  • Playbook development and maintenance
  • Recruiting pipeline (30-40% annual turnover)

When it works: High-volume, lower ACV (< $30K), strong inbound flow, large mature sales org with proven career paths.

When it struggles: Mid-to-high ACV, complex sales, limited management bandwidth, signal-rich environments where timing matters more than volume.

The Full-Cycle AE + GTM Engineering Model #

The alternative model flips the script:

The Structure

  • GTM Engineer builds automation infrastructure (data enrichment, signal aggregation, routing, AI research, automated sequences)
  • Full-Cycle AEs own pipeline end-to-end (prospecting + closing, focus on Tier 1/2 accounts)
  • AI agents handle what SDRs used to do (research, list building, Tier 3 outreach, CRM hygiene)

The Economics

  • GTM Engineer: $150K + $50K tools = $200K fully loaded
  • Full-Cycle AE: $120K base + $120K variable = $240K OTE
  • Output per AE: Same or better than SDR→AE handoff model
  • Comparison: 1 GTM Engineer + 3 Full-Cycle AEs ($920K) vs 6 SDRs + 3 AEs ($1.3M)

The Automation

  • Auto-populating CRM: Lookalike accounts, champion tracking, website visitors, alumni networks
  • Intelligent routing: Signal + fit + tier-based assignment
  • AI research briefs: Company analysis, persona insights, custom talking points in < 1min
  • Waterfall enrichment: 80%+ coverage via multi-provider fallback
  • Automated sequences: Tier 2/3 accounts get multi-channel outreach without manual work

When it works: Mid-to-high ACV ($30K+), complex sales, signal-rich markets, resource-constrained teams.

Real Examples: Full-Cycle in Action #

Qobra: 1 GTM Engineer Replaced Entire BDR Team

The Setup

  • Selling compensation management software (mid-market ACV)
  • Previously: 4 BDRs + 3 AEs
  • Challenge: BDRs spending 80% of time on tasks that could be automated

The Change

  • Hired 1 GTM engineer
  • Built: Auto-enrichment pipelines, parallel dialer integration (Nooks), intent signal routing, AI research briefs
  • Moved to Full-Cycle AE model

The Results

  • Productivity up massively (specific metrics confidential)
  • Faster speed-to-lead (minutes vs hours)
  • AEs own relationships from first touch
  • Lower cost per opportunity

Descript: 2x Pipeline via Automation

The Setup

  • Video editing software with PLG motion
  • Challenge: Thousands of signups, limited BDR capacity to follow up

The Change

  • Built automated classification system (PQL scoring)
  • Implemented waterfall enrichment (Clearbit → Apollo → Clay)
  • Created tiered routing (high-intent → hot queue, others → automated sequences)

The Results

  • 80% enrichment coverage (up from 30%)
  • 2x pipeline from PLG signups
  • Doubled rep-initiated pipeline in 15 days
  • BDRs focus only on hottest leads, automation handles the rest

Gorgias: $950K from Job Change Automation

The Setup

  • Customer service platform (expansion-focused)
  • Challenge: Champions changing jobs = expansion risk + new opportunity

The Change

  • Built champion tracking automation (alerts on job changes)
  • Auto-enrichment of new companies
  • Routing to appropriate AE/CSM

The Results

  • $950K expansion pipeline last quarter from job-hop signals alone
  • Proactive outreach (AEs contacted within 24hrs of job change)
  • What used to require manual LinkedIn stalking now runs automatically

Decision Framework: Which Model is Right for You? #

Choose Full-Cycle AE + GTM Engineering If:

1. You’re selling mid-to-high ACV ($30K-$500K+)

  • Economics justify AEs prospecting their own deals
  • Expertise from first touch increases win rates (no handoff = better context)
  • Complex sales require senior involvement early

2. You have (or can hire) a GTM engineer

  • One GTM engineer can automate 70% of SDR activities
  • Investment: $150-200K/year replaces $600K+ in SDR headcount
  • Engineering multiplier effect (builds once, scales infinitely)

3. Your market is signal-rich

  • Strong intent signals (product-led signups, high-intent website visitors)
  • Clear buying triggers (funding rounds, executive hiring, tech stack changes)
  • Automated lead capture eliminates manual list building

4. You’re resource-constrained

  • Can’t afford 6-9 month SDR ramp + ongoing enablement overhead
  • Limited management bandwidth for coaching (1:6-8 ratio required for SDRs)
  • Small TAM where relationships matter more than volume

5. You value speed and context

  • No handoff = no context loss (AE owns relationship from first touch)
  • Faster response times (automation + alerts vs manual checking)
  • Better customer experience (single point of contact)

Choose SDR Model If:

1. High-volume, lower ACV (< $30K)

  • Need specialized prospectors to feed AE pipelines
  • Economics favor SDR specialization (cheaper labor for prospecting)
  • Clear separation between prospecting and closing work

2. Strong inbound flow

  • BDRs qualify and route hand-raisers efficiently
  • Speed matters more than deep discovery (24hr SLA on responses)
  • Volume justifies dedicated inbound qualification role

3. Large, mature sales org

  • Proven SDR→AE career path for talent development
  • Established enablement and coaching infrastructure already exists
  • Specialization benefits outweigh handoff costs at scale

4. Simple, transactional sales

  • Product doesn’t require deep expertise to prospect
  • Qualification is straightforward (BANT-style)
  • Prospects comfortable with two-stage process

Hybrid Approach: Best of Both Worlds

Many companies run a hybrid model:

Tier 1/2 accounts (enterprise, strategic)

  • Full-Cycle AE with GTM engineering support
  • White-glove treatment from first touch
  • Relationship-driven, high-touch motion

Tier 3/4 accounts (SMB, volume plays)

  • SDR qualification + automated sequences
  • Scale through specialization
  • Volume-driven, efficient motion

Inbound high-intent (demo requests, PQLs)

  • BDRs for speed (24hr SLA)
  • Quick qualification and routing
  • Strike while iron is hot

Complex enterprise (strategic, multi-stakeholder)

  • AE-led from first touch
  • Senior-level relationships required early
  • Long sales cycle justifies AE investment

The Economics: Let’s Do the Math #

Traditional SDR Model (10-person team)

Costs:

  • 6 SDRs × $100K fully loaded = $600K
  • 3 AEs × $240K OTE = $720K
  • 1 SDR Manager × $120K = $120K
  • Total: $1.44M/year

Output:

  • 6 SDRs × 12 meetings/month = 72 meetings/month
  • 50% meeting→opp conversion = 36 opps/month
  • 25% close rate × $50K ACV = $4.5M ARR

Cost per opportunity: $40K Cost per closed deal: $160K

Full-Cycle AE + GTM Engineering Model

Costs:

  • 1 GTM Engineer × $200K fully loaded = $200K
  • 5 Full-Cycle AEs × $240K OTE = $1.2M
  • Total: $1.4M/year (comparable)

Output:

  • 5 AEs × 15 meetings/month = 75 meetings/month (automation handles Tier 2/3)
  • 55% meeting→opp conversion = 41 opps/month (better context, no handoff)
  • 28% close rate × $50K ACV = $5.75M ARR (higher win rate)

Cost per opportunity: $34K (15% better) Cost per closed deal: $122K (24% better)

The difference: Same headcount cost, 28% more ARR, better unit economics.

The GTM Engineering Investment #

“But I don’t have a GTM engineer, what do I do?”

Option 1: Hire One

  • Profile: Technical CSM, RevOps background, or junior engineer who loves GTM
  • Salary: $120-180K (less than 2 SDRs)
  • ROI timeline: 3-6 months to full productivity

Option 2: Upskill RevOps

  • Modern RevOps = GTM Engineering
  • Tools: No-code (Clay, Zapier) → Low-code (n8n, Retool) → Full-code
  • Training: 3-6 months to build meaningful automation

Option 3: Fractional/Consultant

  • Hire GTM engineering expertise part-time
  • Build core infrastructure in 3-4 months
  • Transition to internal maintenance

What they’ll build (first 6 months):

  1. Month 1-2: Waterfall enrichment, data quality, CRM hygiene automation
  2. Month 3-4: Signal aggregation, intelligent routing, account scoring
  3. Month 5-6: AI research briefs, automated sequences, champion tracking

Tools they’ll use:

  • Data orchestration: Clay, Cargo, Hightouch
  • Enrichment: Clearbit, Apollo, ZoomInfo (waterfall)
  • AI: OpenAI API, Anthropic, custom prompts
  • CRM: Salesforce/HubSpot automation (workflows, Apex, APIs)
  • Signals: Intent data, technographics, hiring, funding

Making the Transition #

If You’re Starting from Scratch

Path 1: Full-Cycle from Day 1

  1. Hire 1-2 Full-Cycle AEs (look for technical sales backgrounds)
  2. Hire or upskill GTM engineer (even part-time to start)
  3. Build core automation (enrichment, routing, research)
  4. Scale AE headcount as automation matures

Path 2: Lean SDR Start → Transition

  1. Hire 1-2 SDRs to prove messaging and ICP
  2. Document what they do manually
  3. Automate 70% of their work via GTM engineering
  4. Transition to Full-Cycle AE model at renewal

If You Have an Existing SDR Team

Don’t fire everyone immediately. Instead:

Phase 1: Add Automation (Months 1-3)

  • Hire GTM engineer
  • Build automation alongside existing SDR team
  • SDRs focus on high-value activities (Tier 1 accounts, complex research)

Phase 2: Test Hybrid (Months 4-6)

  • Move 1-2 AEs to Full-Cycle model with automation support
  • Compare output and economics vs SDR-fed AEs
  • Refine automation based on learnings

Phase 3: Decide (Months 7-12)

  • If Full-Cycle outperforms: Transition SDRs to AE roles or other teams
  • If Hybrid wins: Keep SDRs for specific segments/use cases
  • Use data to inform decision, not dogma

Respect your people: Top SDRs often make great Full-Cycle AEs. Offer training and promotion paths.

Common Objections Addressed #

”But AEs don’t want to prospect!”

Reality check: AEs who “don’t want to prospect” actually don’t want to:

  • Build lists from scratch (automation does this)
  • Research accounts for 20 minutes each (AI does this in < 1min)
  • Manage sequences manually (automation handles this)

What Full-Cycle AEs DO:

  • Review AI research briefs (2 min)
  • Personalize automated outreach (5 min)
  • Take warm meetings with qualified prospects
  • Own deals end-to-end (better win rates)

The key: Remove the grunt work via automation. AEs love prospecting when it’s strategic and supported.

”SDRs cost less than AEs, isn’t specialization cheaper?”

Only if you ignore:

  • SDR ramp time (6-9 months to full productivity)
  • SDR management overhead (1 manager per 6-8 reps)
  • SDR turnover (30-40% annual, recruiting costs)
  • Handoff friction (context loss, qualification mismatches)
  • Lower win rates (AE doesn’t own from first touch)

Full-Cycle math:

  • 1 Full-Cycle AE ($240K) generates same pipeline as 2 SDRs ($200K) + 1 AE ($240K) = $440K
  • Better win rates (no handoff, better context)
  • Lower management overhead
  • Unit economics favor Full-Cycle at mid-high ACV

”We tried Full-Cycle before, it didn’t work”

What was different:

  • 2018: AEs built lists manually in LinkedIn/ZoomInfo → Painful, low ROI
  • 2026: AI + automation builds lists, enriches data, drafts outreach → AEs focus on high-value work

Why it works now:

  • AI research (GPT-4, Claude) wasn’t available
  • Waterfall enrichment didn’t exist (all-or-nothing data)
  • Signal aggregation required manual work
  • No-code automation was primitive

Try again with modern stack. It’s a completely different ballgame.

”What about SDR career paths? We use it to develop AEs”

Valid concern, but alternatives exist:

Option 1: Direct-to-AE hiring

  • Hire AEs with 1-2 years experience from other companies
  • Faster ramp (already have core skills)
  • Better talent pool (experienced reps prefer AE roles)

Option 2: Rotational programs

  • AEs rotate through roles (prospecting sprint, closing sprint)
  • Develop full-cycle skills without permanent SDR role
  • Keeps skills sharp across entire funnel

Option 3: Internal transfers

  • CS → AE (already know product, customers)
  • Marketing → AE (understand messaging, ICP)
  • RevOps → AE (analytical, process-oriented)

The evolution: SDR as “pay your dues” role is outdated. Modern sales careers skip straight to impact.

Key Takeaways #

  • The traditional SDR model is being disrupted by Full-Cycle AE + GTM Engineering: One GTM engineer can automate 70% of SDR activities (research, enrichment, routing, sequencing). Real examples: Qobra (1 GTM engineer replaced entire BDR team), Descript (2x pipeline via automation), Gorgias ($950K from job-change signals alone). Full-Cycle model delivers better unit economics at mid-to-high ACV ($30K+).

  • Choose Full-Cycle if you’re selling mid-high ACV in signal-rich markets: $30K-$500K+ ACV justifies AE-led prospecting. One GTM engineer ($150-200K) replaces $600K in SDR headcount. Signal-rich environments (PLG, intent data, buying triggers) enable automation to handle list building. Resource-constrained teams benefit (no 6-9mo SDR ramp, less management overhead).

  • Choose SDRs for high-volume/low ACV or strong inbound flow: Sub-$30K ACV economics favor SDR specialization. Strong inbound flow needs BDR speed (24hr SLA qualification). Large mature orgs with proven SDR→AE career paths and existing enablement infrastructure. Simple transactional sales where qualification is straightforward.

  • Hybrid approach combines the best of both models: Tier 1/2 accounts → Full-Cycle AE (white-glove, relationship-driven). Tier 3/4 accounts → SDR + automation (volume-driven, efficient). Inbound high-intent → BDR for speed. Complex enterprise → AE-led from first touch. Don’t default to all-or-nothing.

  • The math favors Full-Cycle for most B2B SaaS in 2026: Same headcount cost ($1.4M), 28% more ARR (better conversion, higher win rates), 24% better cost per closed deal. Key: Automation removes grunt work (list building, research, sequences), AEs focus on strategic prospecting and closing. The question isn’t “Should I try Full-Cycle?” but “Why haven’t I already?”

Frequently Asked Questions #

Week 1-2: Build core data infrastructure (waterfall enrichment pipelines using Clearbit → Apollo → Clay, CRM hygiene automation, data quality monitoring).

Week 3-4: Signal aggregation (intent data, website visitors, job changes, funding, tech stack), routing logic (fit scoring + signal scoring + tier assignment), alert systems (hot accounts to AEs in real-time).

Month 2-3: AI research automation (custom GPT prompts for account briefs, persona analysis, talking point generation), sequence builders (automated multi-channel outreach for Tier 2/3), response handling (classify replies, route to AEs, remove from sequences).

Month 4+: Advanced features (champion tracking, lookalike modeling, predictive scoring), optimization (A/B tests on prompts, enrichment quality checks), maintenance (API updates, new data sources, scaling infrastructure).

Tools they use: Clay/Cargo (orchestration), Python/TypeScript (custom scripts), Salesforce/HubSpot APIs, OpenAI/Anthropic APIs, data providers (Clearbit, Apollo, ZoomInfo), workflow automation (Zapier, n8n, Temporal).

Profile: Technical background + GTM curiosity. Could be: ex-SDR/BDR who learned to code, junior engineer who loves GTM, RevOps who went deep on APIs, technical CS background.

Phase 1: Foundation (Months 1-3)

  • Hire GTM engineer (or upskill RevOps)
  • Build core automation: waterfall enrichment (80%+ coverage), intelligent routing (fit + signal scoring), AI research briefs (< 1min per account)
  • Pilot with 1-2 Full-Cycle AEs alongside existing SDR team
  • Result: Proof of concept, automation handles 40-50% of SDR work

Phase 2: Expansion (Months 4-6)

  • Scale automation: automated sequences for Tier 2/3, champion tracking, CRM hygiene
  • Transition 3-4 AEs to Full-Cycle model with automation support
  • SDR team shrinks via attrition or transitions to AE roles
  • Result: Hybrid model running, 70%+ of SDR work automated

Phase 3: Full Transition (Months 7-12)

  • All AEs Full-Cycle with automation support
  • GTM engineer optimizing and building advanced features
  • Former SDRs promoted to AE or moved to other teams
  • Result: Full-Cycle model at scale, lower cost per opp, higher win rates

Key: Don’t fire SDRs day 1. Transition gradually, promote top performers to AE roles, let natural attrition happen. Respect your people while evolving the model.

Faster path (if starting from scratch): 3-4 months to Full-Cycle-ready (hire GTM engineer + 2 AEs, build core automation, launch).

Option 1: Fractional/Consultant ($5-10K/month, 3-4mo engagement)

  • Hire GTM engineering expertise part-time to build foundation
  • They build: enrichment pipelines, routing logic, AI research automation
  • Transition to internal RevOps for maintenance
  • ROI: $30-40K investment replaces $200K+ in SDR costs

Option 2: Upskill Existing RevOps (3-6mo timeline)

  • Modern RevOps IS GTM engineering
  • Start no-code: Clay, Zapier, HubSpot workflows (week 1-4)
  • Add low-code: n8n, Retool, Make (month 2-3)
  • Learn APIs: Python basics, API calls, data pipelines (month 4-6)
  • Resources: Clay University, API docs, YouTube tutorials, AI coding assistants (Cursor, GitHub Copilot)

Option 3: Start with Off-the-Shelf Tools (immediate)

  • Use Cargo for signal aggregation + routing (no engineering required)
  • Clay for enrichment workflows (templates available)
  • Apollo/Smartlead for automated sequences
  • Get 60-70% of the value without custom engineering
  • Hire engineer later to customize and optimize

Option 4: Contractor Marketplace (project-based, $3-8K/project)

  • Upwork, Toptal, Contra for specific automation projects
  • “Build me a waterfall enrichment pipeline in Clay”
  • “Set up intent-based routing in Salesforce”
  • Piece together infrastructure over 3-6 months

Reality check: If you can’t afford $150K for a GTM engineer, you probably can’t afford $600K for 6 SDRs either. Start lean with Full-Cycle AEs + off-the-shelf tools.

Problem: AEs will always prioritize closing over prospecting (natural incentive mismatch).

Solution 1: Automation removes friction

  • AI builds target lists (AE doesn’t manually prospect in LinkedIn for 2hrs)
  • Research briefs auto-generated (< 1min review vs 20min research)
  • Sequences run automatically (AE personalizes, doesn’t manually send each email)
  • Result: Prospecting becomes 15-20min/day vs 2-3hrs/day

Solution 2: Activity minimums in comp plan

  • X new accounts contacted per week (automated tracking)
  • X outbound meetings per month (separate from inbound)
  • Quota split: 60% closing, 40% prospecting output
  • Result: Incentives aligned with both prospecting and closing

Solution 3: Separate capacity planning

  • AEs have closing capacity + prospecting capacity
  • If closing pipeline is full, prospecting slows (expected)
  • If pipeline is thin, prospecting ramps up (natural behavior)
  • Result: Self-balancing system, no micromanagement needed

Solution 4: Tiered account assignment

  • Tier 1 accounts: AE fully owns (prospecting + closing)
  • Tier 2/3: Automation handles outreach, AE takes meetings when booked
  • Result: AE focuses on high-value prospecting, automation handles volume

Key insight: Don’t ask AEs to do manual SDR work. Give them automation that makes prospecting effortless, and they’ll do it.

The bottom line: The SDR model isn’t dead, but for most mid-market B2B SaaS companies selling $30K+ ACV, Full-Cycle AE + GTM Engineering delivers better economics, faster speed-to-lead, and higher win rates.

The question for 2026 isn’t “Should we innovate?” It’s “Can we afford not to?”

Decided SDRs are right for your model? Check out our companion guide: Building a Modern Sales Development Team.

MaxMaxNov 9, 2025
On this page
  • The Traditional SDR Model
  • The Full-Cycle AE + GTM Engineering Model
  • Real Examples: Full-Cycle in Action
  • Decision Framework: Which Model is Right for You?
  • The Economics: Let's Do the Math
  • The GTM Engineering Investment
  • Making the Transition
  • Common Objections Addressed
  • Key Takeaways
  • Frequently Asked Questions

Stay Informed with our
weekly Newsletter

Related articlesSee all articles
GTM Strategy
Your Agents Can Build Your GTM. Should You Run the Infrastructure Too?

AI made GTM workflows cheap to build, so teams build more of them, and every one becomes something to run. The four hidden costs of owning GTM infrastructure, when building it yourself is the right call, and what to own instead.

MaxMax·Oct 21, 2026
GTM Strategy
How to Version-Control Your Go-to-Market Stack in Git (GTM as Code)

To version-control your go-to-market stack in git, declare it in TypeScript as a Cargo project: cargo-ai project init scaffolds the repo, cargo-ai project plan prints the change as a diff your team reviews in a pull request, and cargo-ai project deploy ships it. GTM as Code, defined, with the primitives and how to start.

MaxMax·Oct 16, 2026
GTM Strategy
Building GTM Is Starting to Look a Lot Like Building Software

Revenue logic is leaving tool settings and becoming code that agents write and humans review. The four shifts behind it: code over configuration, versioned governance, new build-vs-buy economics, and a GTM system that improves instead of being rebuilt.

MaxMax·Oct 9, 2026

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

AI AgentsPlaysToolsData ModelsAppsTerritoriesContextEnrichmentRoutingIntegrationsPricing

Add-ons

Chrome extensionButtonFormSlackGitHub

Build

DocsDeveloper resourcesCargo API docsCargo OpenAPI specCargo auth docsCargo webhooksCargo MCP serverProjectsClaude Code

Resources

ReportsBlogCustomer storiesCookbooksGTM 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