Sales ops · Production

OpusClip's B2B revenue team builds call intelligence and renewal automation with Claude Code

The problem

OpusClip's B2B revenue team had minimal visibility into rep performance since the team lead could observe only a fraction of calls each week, renewal prep required manual work per account with context scattered across multiple disconnected tools, and churn-predicting patterns in the data went unquantified.

Workflow diagram · grounded in source
1
Auto-pull call transcripts
Integration
A custom Zoom MCP server built with Claude Code pulls all external call transcripts automatically.
▾ source quote
“a custom Zoom MCP server the team built with Claude Code pulls all external call transcripts automatically”
2
Parallel call summarization
Ai action
Claude Code spawns parallel subagents that distill each call into a structured summary.
▾ source quote
“Claude Code spawns parallel subagents that distill each call into a structured summary”
3
Aggregate summaries and tool data
Integration
A second session gathers those summaries along with data from HubSpot, Linear, and internal call transcripts.
▾ source quote
“A second session gathers those summaries along with data from HubSpot, Linear, and internal call transcripts”
4
Generate executive brief
Output
The session writes an eight-section executive brief with coaching briefs per rep and sections tailored for product, marketing, and GTM.
▾ source quote
“writes an eight-section executive brief with coaching briefs per rep and sections tailored for product, marketing, and GTM”
5
Map insights to Linear tickets
Integration
Feature requests surface with exact customer quotes and deal sizes attached, automatically mapped to Linear tickets.
▾ source quote
“feature requests surface with exact customer quotes and deal sizes attached, automatically mapped to Linear tickets”
6
Trigger renewal analysis skill
Trigger
When someone runs /renewal-analysis, Claude Code shows a checklist of required inputs: contract PDF, admin dashboard screenshot, and user export CSV.
▾ source quote
“When someone runs /renewal-analysis, Claude Code shows a checklist: upload the contract PDF, admin dashboard screenshot, user export CSV”
7
Generate renewal brief
Ai action
Minutes later, the team has a structured renewal brief with a health scorecard, risk assessment, pricing options, and call prep scripts.
▾ source quote
“Minutes later, the team has a structured renewal brief with a health scorecard, risk assessment, pricing options, and call prep scripts”
8
Codify skills to GitHub library
Feedback loop
Once output is validated, each workflow is turned into a Claude Code skill and uploaded to a shared GitHub repo that doubles as team onboarding.
▾ source quote
“Once the output is validated, the process is turned into a Claude Code skill and uploaded to a shared GitHub repo”
Reported outcome

The B2B revenue team now builds and maintains its own call intelligence, renewal automation, and customer dashboards.
A routing issue surfaced through transcript analysis led to a $20K plan being signed that day and more than $200K in additional pipeline. The weekly revenue report runs in about 15 minutes, an ROI calculator was produced in 60 minutes, and it unblocked five deals in the first month.

Reported metrics
Annual plan signed from routing fix discovery$20K
Additional pipeline generated after routing fixmore than $200K
Weekly revenue report run timeabout 15 minutes
ROI calculator build time60 minutes
Show all 9 reported metrics
annual plan signed from routing fix discovery$20K
additional pipeline generated after routing fixmore than $200K
weekly revenue report run timeabout 15 minutes
ROI calculator build time60 minutes
deals unblocked by ROI calculator in first monthfive deals
avoided GTM software stack costsix figures
avoided GTM software rollout timemonths to roll out
manual renewal prep effort per account (before)hours of manual work per account
tools with scattered context (before)five or six tools
Reported stack
Claude CodeZoomHubSpotLinearMixpanelClayn8nGitHub
◆ Does this fit your context?

Compare to your context

Tell us your scale, team, and constraints. We'll show what changes at your size, what fails at your scale, and whether this case is a fit, needs adaptation, or won't scale to you. Free demo, no signup.

Compare to your context →
~30 seconds · free
Source
https://www.anthropic.com/customers/opusclip
Read source ↗

Frequently asked questions

What did this team achieve with this AI workflow?

The B2B revenue team now builds and maintains its own call intelligence, renewal automation, and customer dashboards.

What tools did this team use?

Claude Code, Zoom, HubSpot, Linear, Mixpanel, Clay, n8n, GitHub.

What results were reported?

Annual plan signed from routing fix discovery: $20K; Additional pipeline generated after routing fix: more than $200K; Weekly revenue report run time: about 15 minutes; ROI calculator build time: 60 minutes (source-reported, not independently verified).

How is this sales ops AI workflow structured?

Auto-pull call transcripts → Parallel call summarization → Aggregate summaries and tool data → Generate executive brief → Map insights to Linear tickets → Trigger renewal analysis skill → Generate renewal brief → Codify skills to GitHub library.

Related sales ops cases

WHAT TO DO WITH THIS

Now compare it to your context

This case is one data point. Whether its pattern fits you depends on your volumes, your stack, and your exception load — that comparison is the step no case study can do for you.

Browse the Sales ops cases →