Salesforce Just Automated 85% of Support. Here’s What Founders Should Actually Be Thinking About.
This isn’t just another AI headline — it’s a shift in how we think about teams.
A few days ago, Marc Benioff dropped a number that caught everyone’s attention:
“AI now resolves 85% of our customer service.”¹
Your first thought?
Sounds efficient. Or concerning. Or maybe both.
But if you’re leading a tech team right now, the real question isn’t whether you’re for or against this kind of automation.
The question is: what does it mean for you, your team, and the kind of talent you’ll need next?
What’s Salesforce really doing here?
This isn’t just a cost-cutting play.
Salesforce is going after speed, visibility, and control.
They’re using AI (via their Agentforce platform²) to handle everything that doesn’t need a human — so their people can focus on what does.
And if they’re doing that in support, you can bet it won’t stop there.
The role of people is shifting (again)
This isn’t about replacing humans. It’s about changing the role they play.
Once the repeatable tasks are automated, why are you still hiring people?
Not for speed.
Not for task execution.
You’re hiring them for:
- Solving edge cases that don’t fit a script
- Reading context between the lines
- Making real-time judgment calls
- Connecting the technical with the human
Bottom line: less doing, more thinking.
So what now? A few uncomfortable (but necessary) questions
If you’re a founder, CTO, or scaling a tech team, now’s a good time to ask:
- Are you hiring for tasks — or for strategic thinking?
- Is your team working with AI — or around it?
- Is your structure adding clarity — or adding friction?
No easy answers here. But one thing’s clear:
this is no longer about “what’s coming.” It’s already here.
One observation, for what it’s worth
Over the past few months, we’ve noticed a pattern.
The developers who really stand out in this new landscape aren’t the ones who move fastest through a backlog.
They’re the ones who:
- ask the right questions,
- know when to break the script,
- and bring context into every line of code.
In many cases, we’ve found that in LatAm talent. Not because of location — but because of experience.
Developers who’ve grown in environments where adapting fast, thinking independently, and delivering without micromanagement wasn’t optional — it was the norm.
Final thought (no doomsday, no hype)
AI isn’t replacing your team.
But it is forcing us to rethink what teams are for.
And maybe, just maybe — that’s a good thing.
🧠 Sources:
