We loved connecting with the community at Sculpt 2026 and dreaming up ways to use Clay and Octave together!
The sky's the limit, but one of our favorites is simply the ability to make sense of all the account signals you might be pulling into Clay.
Why do we do signals research in the first place?
Because it lets us infer that a business has a problem. Our product might be able to solve that problem, and we want to point that out before competitors do.
It's about connecting the dots between problems and solutions.
Octave helps connect those dots -- for your reps, for your agents, for any workflow you're hoping will make sense of all those signals you're paying for.
It can process all the signals you pull into Clay as context, then tell reps:
- Which of the signals matters most
- Why they matter -- what's the business problem, what's your solution
- Who they matter to -- one signal might matter because it implies the CMO has a problem you can solve; another signal might be indicative of a problem the CIO has
This strategic guidance (and much more!) is what Octave provides, sitting between your signals and the actual guidance you give to reps as talk tracks, emails, account briefs, etc.
Here's a demo Loom [watch below]. We imagine that we're Asana (a work management program) and we're targeting Navan (corporate travel and expense).
Let's say we find signals of recent M&A activity at Navan. Asana can help with that, in a lot of ways! And Octave shows how to explain that as you're multi-threading. For example:
- Signal 1: Navan acquired BoomPop last month. This creates technical integration work.
- COO problem: The problem for Navan's COO could be all the moving parts of cross-functional work to get this done. Asana's solution could be to make dependencies, milestones, and workstreams clear for the COO.
- CIO problem: The problem for Navan's CIO could involve governance. Reps can highlight how Asana helps manage this.
- Signal 2: Navan acquired Reed & Mackay 5 years ago but recently announced they're migrating all their customers to the Navan platform. That's a big customer operations and support project.
- CEO problem: The CEO of Reed & Mackay might want to make sure that migration goes off without a hitch, with a great experience and no churn. Asana could map out a very clear cross-company migration plan for more success.
That strategic connection-creation is happening in Octave.
In addition, Octave is assessing whether Navan is a fit for Asana in the first place. When you run the Octave integration in Clay, it can tell you:
- That Navan maps to the enterprise tech segment in Asana's (again, fake) context graph
- Which Asana use case could be most useful to Navan right now
- If Asana had multiple products and services, which ones to highlight
- The fact that Navan is a 4k+ employee, fast-growing, AI native, global company -- this creates specific coordination challenges that Asana can help with
And plenty more, of course.
Check out the video for a walkthrough and more detail, and reach out if you want to talk shop!
