Maxence Devil retweeted
Never ship “Hi {first_name}” to 5,000 people again
Introducing Cargo github integration: getcargo.ai/github
How it works:
1. An agent opens a pull request
2. Cargo comments what it will change, send and spend
3. Merge stops being the scariest button in GTM
Maxence Devil retweeted
a lead asked why we don't keep our icp in a database. made a diagram to explain, think it was worth sharing
A few months ago, “talking to AI all day” was a figure of speech.
Then I installed @WisprFlow.
Now my keyboard is decorative, and my neighbors know our ICP
🤖 Made with AI
2
3
80
Maxence Devil retweeted
Interesting POV from a customer this morning who previously used Clay:
“Clay is Webflow. Cargo is Next.js.”
Hard to say it better
Automation already works while you sleep.
The next frontier is a GTM system that can improve while you sleep.
We’ve been running Cargo’s own GTM around this architecture for the past two months.
The big shift: the GTM system itself lives in Git.
Context and strategy live as files. Execution logic and infrastructure live as code. Every change is versioned, reviewable, and reversible.
Then the loop:
Sense → Decide → Act → Steer.
Outcomes become evidence.
Evidence becomes proposed changes.
Accepted changes become the system's next version.
Here’s the reference architecture for a self-improving GTM engine ↓
2
76
2016: "Fuck, 6 more hours on this plane."
2026: "Fuck, only 6 more hours on this plane."
@Starlink + coding agents have turned long-haul flights into the ultimate deep work sessions.
2
4
68
Highlights from "Your GTM belongs in git": @Kaarolus, @Cole_Dambra, @JohnKutay and Johnathon Kidd on why go-to-market is becoming software.
You don’t need to pick Anthropic or OpenAI.
You should have both inside the same terminal workflow, with access to the same repo. No fixed roles. Sometimes Claude leads. Sometimes Codex does.
Sometimes one executes and the other challenges.
Here’s the exact setup ↓
1
1
121
That gives me two layers:
Inside Claude Code:
Low-friction access to both models in the same workflow.
Separate Codex terminal:
Independent framing when the decision actually matters.
Same repo. Different reasoning systems. Human arbitration.
2
1
35






