GTM Engineer Sympower & Automation Consultant Founder: https://teapawt.net/t.co/PRcHLWoVvW, https://teapawt.net/t.co/QRDEQ6detH Founding team: Bardeen, Hunty colombian 📍Barcelona
Book a free audit 🔻
Joined March 2019
- Tweets4.9K
- Following687
- Followers1K
- Likes2.5K
In 2026 you're either shipping an agent (outcomes, digital workers) or shipping the tools that agents need to work (headless platforms, APIs, CLIs).
Every GTM tech vendor is racing on these two edges.
Told a speaker at an event about my GTM Second Brain builder. "Oh yeah, show it to me."
So during the talk I messaged my agent on Telegram from my phone.
By the end it was built.
"Hey, it's done. Want to see it now?"
Live builds are a thing now.
Ivan Escobar | GTM Engineer retweeted
introducing @loopsterGTM - one GTM platform for a flat price, where the data is free.
we’re putting agencies back at front seat by flipping the pricing upside down.
all the data is given for free. it’s sourced by the users, and it’s given for free to the users.
here’s how it works /n
Personal AI agents for sales are still untapped.
If Instinct proved anything, it's that the concept of personal agents is just going to work. That category is still very early. And a personal AI agent for sales? Still untapped.
(I'm usually right on my predictions. We'll see.)
What's the best + most intuitive sales agent? (that is not a shitty AI SDR)
oxygen-agent.com/ (partner company of Appsaavy) is also doing incredible work in that direction - but it's mostly handy for GTM engineers - not very tech saavy.
Head about pancake.ai/ recently and seems very promising.
My GTM agency employees, on one page.
(They run on Grok Bot and work with Claude)
One Chief of Staff, the right tools and context to operate, and a team of specialists working together.
One rule sits above all of them:
Nothing goes out without my yes.
It's the smoothest agent team experience I've witnessed so far.
Here's how the rest works.
ALT Org chart of Ivan's GTM employees: Chief of Staff, outbound and content teams, on-call agents, and the two brains (GTM Second Brain and Company Brain).
My GTM employees share two brains.
The conscious one holds the foundational strategic decisions of our go-to-market, broken down into structured information:
→ ICP
→ Personas
→ Offers
→ Value props
→ Competitors
I write it. Agents read it.
I help businesses build these custom to them.
appsaavy.com/gtm-engine
The unconscious brain, agents write. Every agent grounds its work in it and files back.
I stay in the conscious one: who we sell to and why.
If you want a future proof GTM stack, let's talk about how to set it up for your business - Appsaavy.com
My networking agent has drafted 15 follow-ups this week. I've sent 2.
Looks like the more I use agents the more I turn into my own bottleneck.
Called it. In March I floated "one connection for all of LinkedIn": your agent plugged in via CLI or MCP.
Last week a friend's product, Grip, shipped exactly that. Run your LinkedIn outbound from Claude - they are going through insane traction, still on pre-launch with a waitlist.
Agents go where relationships live.
What's a next prediction on GTM?
Ardales with makers I met in Colombia in 2022.
Sebas is now at a Valencia startup building knowledge systems for AI agents. Allison and Jose David came too.
Lake, picnic, skating in Malaga.
The ones you meet building early keep showing up.
Your CRM can change its pricing.
Your sequencer can sunset a feature.
Your enrichment tool can change its API.
Your AI chatbot can switch models overnight.
Nothing wrong with any of them. That's just how software works.
But remember: none of that can happen to context you own.
That was the point of last week's Clay post. I'm not hating on Clay, just vouching that you're conscious on where your GTM foundations live:
- Personas
- Offers
- Segments
- Buying triggers
- Value propositions
- References
- Competitors
Etc.
Here's the part I left out:
owning your context is only half of it.
The other half is keeping it current.
A GTM second brain you own but never update is just a database of old assumptions.
So for me it comes down to 3 parts:
→ Own the layer
→ Update it consciously, and often
→ Build systems that allow reliable updates (without slop)
Tools come and go.
The context you keep alive stays.
Just joined Social Hub cowork in Barcelona.
Checked five or six places first. Social Hub never replied, so I followed up twice. Then they confirmed.
Persistence works, even for a desk.
First time settling after nomad life.
Ran Barcelona before sunrise.
First half marathon is done. Training for the second one before the year ends.
The city is empty at dawn. Just me and the sea.
Consistency is the whole trick. New quarter, same discipline.
