Cyborgs, Not Agents: The Near Future of RevOps
Here is an optimistic AI near-future for you.
You will spend more time doing what you actually enjoy — and less time clicking buttons.
I know this because I am building that future. But let me take you through why I am so convinced it arrives.
Point 1: Cyborgs vs Agents
Agents suck.
Devin. AI SDRs. Every autonomous agent that promised to replace a job role. None of them have delivered in any meaningful mainstream sense. No one has shipped an agent that can sit in a seat and do a job — reliably, without handholding, at the level a competent human operates.
Cyborgs, on the other hand, are winning.
A cyborg is a person enhanced by AI. I am one. The RevOps operators using AI natively are ones. They do more work, faster, at higher quality than they did before. They do not need an agent to replace them. They use AI as a thinking partner and execution layer, while they stay in the seat.
Full AI automation is for fools. The near future is you — enhanced. Not replaced.
Point 2: Thinking vs Executing
Your job is to build revenue systems. You spend some time strategising — figuring out the model, the flows, the rules of engagement. And then you spend twenty times longer clicking buttons in HubSpot to make any of it real.
That is the nightmare. The real work is thinking about the system. Not building it field by field, workflow by workflow, property by property.
This is not unique to RevOps. Developers live the same split: the real job is thinking about architecture, not writing boilerplate. The cursor moves, the files fill up, but none of that is where the value lives.
AI is exceptional at the execution side. Training data for execution is vast — code, configurations, sequences of actions. AI is genuinely poor at the thinking side, because every business situation is novel, contextual, and requires judgement that cannot be trained in.
The implication is obvious: offload execution to AI, keep thinking for yourself.
Point 3: The Capabilities Are Already Here
I know this is not hypothetical because I have already built it. Daeda MCP can automate execution for tasks that currently take hours. Not in theory — in practice, today.
The gap is not capability. The gap is reach.
The official HubSpot MCP is deliberately limited — read-only, constrained, not powerful enough to actually build systems through a conversation. It lets you look at your data. It does not let you act on it. That is not an AI limitation, that is a product decision.
The capabilities needed to make a plan and execute it in HubSpot already exist. The architecture is there. What is missing is the bridge that puts full execution power in the hands of the person doing the thinking.
That is exactly what I am building.
The Future This Points To
You are no longer a glorified button-pusher with a little strategic thinking bolted on the side.
Instead: you sit with a client, you work through their revenue model, you figure out what needs to change. You make a plan. Then you hand the plan to AI and hit execute. The HubSpot changes happen. The workflows update, the properties configure, the sequences trigger.
You were the thinker. AI was the executor. The outcome took minutes, not days.
For early adopters, I intend to make this a reality by August.
If you want to be one of them — join the Daeda MCP Pro waitlist.