Two Years of AI Experiments.
One Missing Piece.
How WorkSpan's SVP of Marketing went from stalled AI rollouts to deploying Octave across every AI surface in their GTM stack.
Sam, SVP of Marketing at WorkSpan, demos how his team uses Octave as their shared GTM context layer.
Sam's team at WorkSpan spent two years trying every AI tool they could find. Clay. n8n. Claude projects. OpenAI agents. They weren't looking for a better prospecting tool or a better email writer. They were looking for the thing that makes the whole GTM org move in concert.
The problem was always the same: every tool they deployed, they had to deploy a lot of context alongside it. And that context went stale quickly, with no clean way to keep the team in sync.
"Everywhere we deployed AI, we had to deploy a lot of context and it went stale quickly."
He Looked at Octave a Year Ago and Said No
"Good pitch. I'm sorry. There's no way. I've got no one on my team. There's no way I'm going to go fill out 50 different objects and write pages and pages of text."
Fair, but then MCP happened.
We got Sam on a call and showed how easy it was to take all of the workshops from SKO, positioning and training docs, and upload those into Claude Code. In one hour, they got the library 60% built from just three days of SKO content.
MCP was the prerequisite. It turned a "no way" into a "this just works."
Easy Maintenance via Claude
Here's where it gets interesting. Sam's process to keep the whole org's context current is dead simple: he feeds Claude a transcript and asks "do we need to update Octave?"
New product release? New integration? New docs? A meeting with the product team that shifts positioning? Claude reads the transcript, understands what changed, and updates the library through the MCP. No forms. No manual entry. The whole team's context stays current because one person had a conversation with Claude.
"My process to maintain my shared org-wide context is I take transcripts, I take slide decks, and I just say — hey Claude, do we have to update Octave?"
Compounding Is the Key
Once the context layer was there, WorkSpan plugged it into everything. Email tools. Slack. n8n flows. Lovable apps. Canva. Claude sessions. Every AI surface they touch now pulls from the same shared brain.
And that creates a flywheel. The more places the context gets used, the more incentive there is to keep it sharp. Every update compounds across every tool.
Sam's words: "Every time I go and add context, it compounds."
Before, a new feature release meant hunting down 15 n8n flows, updating prompts in each one, then updating the Lovable app the team uses, then updating the Claude projects. Now it's one update in Octave, and every downstream tool is current.
His Team is Now Empowered to Adopt AI
This is the part that matters. Sam put a new sales play in Octave, dropped a message in Slack — "new play dropped" — and reps picked it up on their next account. No training session. No slide deck. No enablement hour nobody wanted to attend.
"Every seller would much rather have that and learn by doing and then Slack in or come to office hours than sit through an hour of enablement."
They took it further. WorkSpan rebuilt their onboarding using Octave + Claude Code + Lovable — a training module that pulls concepts from their library, compares them to what a new hire won't know, and generates interactive learning paths. The context layer became the enablement layer.
What This Looks Like in Practice
Contextual account plans in minutes
A rep asks Claude to build an account plan for Snowflake. Because Octave is in the tool chain, Claude pulls the right reference customers, maps relevant product use cases, and identifies current plays — including a time-sensitive AWS migration mandate. No research marathon required.
New plays deployed instantly
A new play goes into Octave. A Slack message goes out. Reps pick it up on their next account. The entire cycle from strategy decision to field execution happens in hours, not weeks.
Interactive training from the library
Claude Code pulled WorkSpan's esoteric partner ecosystem knowledge from Octave and generated a full training module in Lovable. New BDRs get up to speed on complex partnership terminology through guided learning, not a slide deck.
Update once, deploy everywhere
Octave is connected to email tools, Slack, n8n, Lovable, Canva, and Claude sessions. One context update propagates across every AI touchpoint. No more hunting down prompts across 15 different systems.