Pinned Tweet
The most dangerous thing in RevOps?
An outdated definition
That no one questions anymore.
2
9
345
Simon Jasmin retweeted
No browser required. Our API is the UI. 🔓 Salesforce Headless 360 just exposed our entire platform — apps, workflows, metadata, Agentforce & Slack — as unified APIs, MCP tools & CLI. Build on any surface. Give Agentforce deep, trusted context. Stop just using Salesforce. Start building with it. 🚀
cio.com/article/4159536/sale…
Anyone else struggling with Salesforce Agentforce in sandbox?
Web Content Crawler randomly breaks.
Bot doesn’t respond or just stalls.
In prod? Smooth.
In sandbox? A mess.
Is this a known issue? Or just us?
Curious if others hit the same wall. 👇
#Salesforce #Agentforce #RevOps
1
1
53
Most companies aren’t underperforming.
They’re under-integrated.
Fix the flow, the growth will follow.
I’ve sat in rooms where everyone nodded at the forecast.
But no one could explain the assumptions.
That’s not strategy, that’s theater.
4
52
Before you blame the tool
Ask if your team even agreed on the workflow.
Misalignment hides in the obvious.
If “lead status” means five different things internally
That’s not miscommunication.
That’s a system problem.
3
94
Don’t build workflows around how you wish people worked.
Build around how they actually do.
That’s operational empathy.
3
67
Process clarity is not optional.
It’s the foundation of repeatable revenue.
RevOps makes it visible, and enforceable.
4
133
SaaS doesn’t scale without infrastructure.
That means more than code.
It means systems, workflows, and shared accountability.
1
5
128
The first step in RevOps is not automation.
It’s alignment.
Across roles, definitions, and objectives.
1
3
99
Process is not bureaucracy.
It’s performance, made repeatable.
Good systems create confident execution.
1
32
Automation is only powerful
When built on clearly defined logic.
Otherwise, it just amplifies chaos.
Sales and marketing don’t need more meetings.
They need shared definitions, shared metrics,
and shared accountability.
1
5
139

