Opus 5.5 just got a pair of hands
One AI employee can now run your entire GTM: builds the prospect list, writes the emails, chases the follow ups, and delivers the Monday report
Here’s how to run it in 8 steps: https://x.com/i/article/2113559224739409920
How to run an AI GTM team [full roadmap]
Opus 5.5 can plan your whole GTM motion in ten minutes. Then somebody still has to do it.
- That somebody is usually you. Building the list, writing forty emails, chasing replies, pulling the Monday numbers. The strategy was never the hard part. The hours were.
So I did what every AI builder does. I built an agent myself.
One weekend, Claude Code, a scraper, a Google Sheet and a prompt that wrote cold emails. On Sunday night it found 30 sponsors and drafted 30 emails. I felt like a genius.
By Wednesday it was broken. A site changed its layout, the sheet got out of sync, and the emails started congratulating companies on launches from last year.
I wasn’t running outbound anymore. I was running a babysitting service for my own agent.
This is the full roadmap I used to run GTM with two pieces: Opus 5.5 as the brain, and Viktor, an AI employee in Slack, as the hands. Eight steps, the exact prompts, and what happened when our team ran it.
Why Opus 5.5 plus Viktor
The proof that capacity is the real bottleneck already exists. Nico Torres, founder of Authority Makers, handed outbound and lead gen to Viktor.
- His agency added $133,752 in new annual recurring revenue in the first thirty days. No new hires.
Opus 5.5 is the right brain for this kind of work. Zapier's CEO Wade Foster says it is the best model for operations they have benchmarked, and the clearest upgrade is knowing when it needs more information before acting.
Zapier ran Opus 5.5 through 657 real business workflows:
But a model in a chat window can't touch your CRM. Viktor can. He lives in Slack, connects to 9,800+ tools, and posts finished work back where the team already is.
So the split is simple: Opus 5.5 thinks, Viktor does the work, and our team approves.
Step 1. Hire Viktor into Slack
Go to viktor.com and pick Continue with Slack. It takes a few minutes and you start with $100 in credits.
Create one channel for this whole roadmap: #gtm. Invite Viktor there. Everything he builds lands in that channel, so the whole team sees the work and nobody starts from zero.
Then ask him one question: "What kind of work happens in this workspace?" His answer tells you what context he already picked up.
Step 2. Put Opus 5.5 behind the work
Viktor isn't locked to one model. In Settings, open the Model tab and set Claude Opus 5.5 as the default. A workspace admin makes this call for the whole team.
Why bother? GTM work is judgment work. Which company actually fits. Which trigger is real. Which sentence sounds like a person. That is where the strongest model earns its cost.
For high volume, low judgment runs later, you can switch a single scheduled task to a cheaper model.
Step 3. Connect only the GTM stack
Connect the tools this roadmap touches and nothing else:
- Google Sheets for the prospect list
- Gmail for drafts
- Your CRM (HubSpot, Pipedrive, Attio or Salesforce)
Most connect in one click over OAuth. Start narrow. You can add tools any time, and a small surface makes the first week easier to review.
Quick test before moving on:
Step 4. Let Opus 5.5 write the plan
Every GTM team that stalls skips this step. Before any list or email, write down who you sell to and why they should care.
Paste this into Viktor in #gtm:
Step 5. Build and enrich the list
This is the work that never had an owner. Give Viktor the whole job, not one step of it.
That last line matters. A list you can't verify is worse than no list.
Aaliya, who works in content and social, ran the same pattern: prospects, research, the sheet and outbound prep in one handoff instead of moving each step between tools.
Step 6. Write the emails, send nothing yet
Now Opus 5.5 does what it is best at: writing like a person who did the homework.
The rule for the whole roadmap: Viktor proposes, the team approves. Every customer facing action waits for a human OK. Viktor has approvals built in, and "do not send" in the prompt makes it explicit.
It costs one review a day. It saves you from the email you would never have sent yourself.
Step 7. Put the boring part on a schedule
Most pipelines don't die at the first email. They die at the follow up nobody sent and the report nobody pulled. Make both run on their own.
Follow ups:
The Monday report:
After week one you stop opening five tabs on Monday. The numbers are already in the channel when the team logs in.
Step 8. Run Viktor straight from Claude Code
This is the step most GTM guides skip. If you already plan with Opus 5.5 in Claude Code, you don't need to switch to Slack to hand off the work.
Viktor ships a hosted MCP server. Any MCP agent can delegate a task to him and get the result back in one call, with the same memory, integrations and guardrails your team set up in Slack.
In Viktor, open Settings, then API Keys, and create a key with threads:create, runs:create and runs:read. API keys need a paid plan.
1. Add the server to Claude Code:
2. Check it with the whoami tool, then hand off work in plain English:
Now Opus 5.5 plans in your terminal and Viktor executes across your stack. One system, not two tabs.
Here’s Antoni from the Viktor team showing it from a coding agent:
What happened when we ran it:
The take:
- The model was never the bottleneck. Opus 5.5 + Viktor can plan a GTM motion better than most teams can staff one. What was missing was the hands: access to the tools, memory of the work, and a channel where the team sees it happen.
Most AI tells you what to do. Viktor does it. If your GTM plan lives in a doc nobody executes, that's not a strategy problem.
Try free at @viktor_com. $100 in credits. Full link in my first reply.
Use code MORLEX100 when you sign up for $100 in free credits.
In partnership with Viktor.