How Indeavor put an intelligence engine behind their stack

Indeavor — workforce management software for complex operations ~120 employees · ~15 on the GTM team · Started with Octave via an agency partner; direct ownership six months later

‍

Two hundred government meeting transcripts a day. That's what Clay was pulling into Indeavor's system. Far more than any human could triage, let alone personalize outreach off.

The AE who was supposed to own the follow-up was already stretched thin. He covered government accounts as a CSM, an AE, and a product manager. Outbound was piled on top of that. It wasn't happening. The work fell off the bottom of every week.

For a RevOps lead, this is the familiar shape of the job: a strategy exists, a team exists, tooling exists, and none of it connects. The work still doesn't get done. And the person holding the pieces together is you.

For Severin Studer, Indeavor's Revenue Operations Lead, that person was him.

No engine underneath

Indeavor adopted Clay and Octave at the same time, through a third-party agency called CMM. Clay could stitch systems together and move data between them. That was the easy part. The harder part was what Clay couldn't do.

"There's no engine behind it. We have Clay that can now connect different systems, but what do we have to qualify a company, to create the content, to look if it's really a fit for us, what's the ICP?" — Severin Studer, Revenue Operations Lead, Indeavor

Clay couldn't hold a position on who Indeavor was selling to, what the products did, or what a good-fit account looked like. That layer had to come from somewhere.

Without it, Severin was building every campaign by hand. AI-assisted, technically. Drafting email one, pasting it into Outreach. Writing email two, pasting it in. And on. Generic copy, unanchored to any shared context. Roughly ten hours of his week, every week.

Meanwhile Salesforce filled up with leads nobody should have been contacting. HubSpot's scoring was somewhat useful, somewhat not, in his words. "Garbage in, garbage out," Severin says. Manageable at one AE. Not manageable at six AEs running twenty campaigns each.

This is rebuild debt in its early form: not catastrophic yet, but compounding.

The moment it clicked

For over a year, Indeavor used Octave through an agency partner. The agency did the builds. Severin saw outputs and trusted them, but he didn't own the machine underneath, or know what it could do beyond what had already been set up.

When he took direct ownership and connected Octave through MCP, something shifted.

"The moment it clicked was when I realized we can build agents specifically for our products and our solution. A sequence agent, a qualification agent, whatever we want — use them across our network, pull them into our different systems. And so we always have that engine." — Severin Studer

Octave didn't just automate faster, it held Indeavor's context (its products, its ICP, its messaging logic) in one place, and let every downstream tool read from it. Clay pulled from it. Claude pulled from it. The same agent that qualified a company could draft the outreach that followed.

One source of truth. Many surfaces.

What the engine runs on now

Severin started with the government-AE problem. It was the lowest-risk place to try, because nobody was doing the work anyway.

Govly pipes 200 meeting transcripts a day into Clay. Octave reads each one, scores the company, scores the lead, and decides whether Indeavor should even be in the conversation. If yes, the sequence agent drafts a fully personalized sequence dynamically built specifically for that individual against Indeavor's full product context and pushes them into Outreach. If no, the lead doesn't get written into Salesforce at all.

That last part matters more than it sounds. Indeavor uses Octave as a filter on top of Salesforce: nothing below a score of seven gets in. The garbage-in problem is gone.

The quality surprised him. "I ran a hundred leads through the sequence agent, and the messaging was very, very much applicable to that lead. Something I was like — yeah, I would have probably written that myself. Four hundred leads in five seconds."

For Severin personally, campaign build time went from roughly ten hours a week to one.

The engine behind the stack

Ask Severin how he'd describe Octave to a peer in another RevOps seat, and he doesn't call it a "platform" or a "tool."

"It's the engine, or brain even, behind your outreach — and your sales and marketing data. I can run Octave and say, hey, score these 2,000 leads for me, and anything under a five, delete from Salesforce. So I know the data I use, I can trust. And based on that, I can make better decisions, I can make better outreach, I can personalize more." — Severin Studer

Engine. Brain. Context held once, used everywhere. That's the Context Gap closing. It's the difference between a RevOps team that just maintains the stack and one that builds something compounding on top of it.

Next up: pushing Octave further into the sales team's hands. Direct access via Slack and Claude, so AEs can pull qualification and messaging in the flow of work instead of waiting for a batch from Severin. Marketing nurture streams are on the list too. The LinkedIn post somebody wrote last week, stitched into a message that lands because of it.

Other tools pull one signal at a time. "Octave is connecting all the different data points in one tool, versus using five different tools," he says.

When one person goes from being the bottleneck to being the architect, you can see it in the work.

‍