Pinned Tweet
Day AI is EXACTLY this.
With multiplayer data.
Off the shelf.
With a Claude Code harness to manage entire workspace config (for admins, in addition to the UI)
day.ai
It's been really fun leveraging @bot for GTM! Have spent a few weeks iterating on some of my workflows, so I wanted to share how I use Grok Bot at SpaceXAI.
Prompts: HubSpot, Rox, Clarify, Monaco
Agents: Muse, OpenClaw, Grok Bot, Dots, Day AI
Loops: Day AI
Graphs: Day AI
Andrej Karpathy:
"Prompting is going away. Delete everything, keep Graph."
In just 124 minutes, he shows how to build graphs and why they're the only layer that survives in the end
Prompts → Agents → Loops → Graphs
a loop keeps one agent running until the job is done
a graph decides which agents exist and what each one passes to the next
anyone can build an agent, almost nobody builds the graph that runs them
watch it today, then save the full guide below ↓
These are Skills not Agents.
Same mistake HubSpot made.
GTM folks deserve full consumer-grade agents on the level of Instinct, Grok Bot, Muse, Dots, OpenClaw and Hermes.
With guard railed sandbox environments, full data privacy and complete RevOps control.
Facts.
98.7% of CRM data (k/v pairs) in @Day_ai_app is generated, not manually entered.
Now you can take your agents and measure them (anonymously) against what everyone else is doing.
A bit of a throwback, but hey, if it works, it works … introducing Agent Grader.
It's free, ten simple questions, under 5 minutes. Share it internally if you want to up your game.
Have at it y'all, and let me know what you think.
agent-grader.com/?utm_source…
People thought I was crazy about the "shape of an agent." But today we have Instinct, Muse, Grok Bot and Dots … and everyone is starting to agree on what an agent actually IS.
Heck, sometimes they even have a SOUL definition. Maybe that's a little too far, but hey, useful instructions are … useful? (Depends on the model. Looking at you, Opus 5.5.)
They're long-lived. They respond to coaching and feedback. They have ongoing conversations with you and learn about you. They have roles and responsibilities, like the job description a human would have.
I'm blown away. Two weeks ago I put out a manifesto called Life After CRM. Thousands of you typed the URL into your browser by hand, and 70% of the people who opened it read the ENTIRE thing. Thank you.
When I went to write that manifesto, I just sat down and talked. Two hours, no stopping. Rolled webcam video in case it was useful and ended up with an 8GB .mp4 nobody was supposed to see.
Then our @Day_ai_app video team found it on the shared drive and cut it. It's raw.
The behind-the-scenes source video: youtu.be/9viCOzuQ0ps
The manifesto it became: lifeaftercrm.com
The secure multiplayer version of this is @Day_ai_app
Agent Control Plane === vendor-provided governance for the skills/agents you already have defined. Wildly valuable, easy to deploy.
day.ai/
What if we said the quiet part out loud? The best revenue leaders have already stopped trusting their CRM to remember anything. They're running their own notes, their own scripts, their own shadow systems. They're quietly doing by hand what a rebuilt category should be doing automatically. That's not a workflow hack. That's a category dying in plain sight.
I don't think the answer is a smarter layer on top of the same system. I think RevOps in five years doesn't have a "CRM" at all. Instead, it has something that finds what's true about a customer from wherever it actually lives (calls, email, Slack, calendars) and acts on it without waiting for someone to write it up first.
If you run revenue and you've built your own workaround for your CRM, you already know I'm right.
fastcompany.com/91604004/wil…
