Octave

Your GTM team is only as good as the context they're working from. Right now, that context is scattered, stale, and inconsistent. → New reps onboard off static docs that are already out of date → Marketers recycle positioning that's been copy-pasted into oblivion → Agents qualify leads without any real understanding of what converts Octave fixes the foundation. Every team member, tool, and agent works from the same living GTM context, and when something updates, everything connected to it updates with it. → New reps onboard from a living system, not static docs they'll never revisit → Marketers build from positioning that's always current, not recycled copy → Agents qualify with real ICP context, not guesswork When everyone works from the same source of truth, the whole team gets sharper together. That's what Octave is built for.

Why are we even thinking in terms of how many humans we can replace? If we're just replicating predictable revenue workflows with AI, we're gonna miss what's actually possible. The best teams aren't trying to optimize little steps and eke out efficiency from dusty old workflows. They're going clean slate and asking what their ideal go-to-market motion actually looks like with all these new capabilities, and then 3D printing it. Watch the full conversation with Zach (Octave), Jared & Matteo (GTM Engineer School) here: https://lnkd.in/gzHvezp5

A single place to store your market intelligence, update it, and have everyone access it like an API. That's how one customer described Octave in a recent G2 review: "It lets me have a single place to store things, update them, and then have others access that knowledge like an API." For product marketers and positioning pros especially, that's the unlock. No more hunting through docs, no more stale messaging living in 6 different places. See what others are saying on our G2 page → ordnl.link/DfxntZO

Most GTM teams are running 5 different motions off one generic playbook. Net-new isn't upsell. Competitive displacement isn't cross-sell. Each one has its own strategy, its own messaging, its own rules, and when you collapse them into the same model, everything gets watered down. These motions are the foundation your GTM is built on. And this level of intelligence is native to Octave. Define every unique motion your business runs, model your ICP at full resolution, and capture your social proof so it's activated across every play where it actually matters. Your agents, tools, and reps all run on the same living model. When the market shifts, it updates with it. This is what it looks like to make your GTM your moat. Learn more here: ordnl.link/46ltXvx

There's a reason nobody builds their own GitHub. It's core infrastructure, with primitives and APIs and a shared repository everyone works from. Right now teams are rebuilding their GTM context from scratch for every single agent. The CSM agent has its own repo, the outbound agent has its own, the web chat has its own. Shared context needs to live in one place. You iterate once, and everything gets the update immediately. That's what we're building at Octave. Watch the full conversation with Zach (Octave), Jared & Matteo (GTM Engineer School) here: https://lnkd.in/gzHvezp5

Your GTM can't wait for a planning cycle. A competitor repositions, a new segment emerges, a feature ships... and the natural response is to schedule a meeting, align the teams, and start rebuilding the playbooks. By the time that process plays out, the moment has already passed. Octave lets you spin up new motions grounded in your full ICP model without starting from scratch every time something changes. The context that underpins your strategy is always live, so execution never lags behind it. Plan your GTM around how fast your market actually moves → octavehq.com

Context engineering is about codifying all the unwritten assumptions your team already operates on but never documented. Every org has institutional knowledge locked up in people's heads. "We don't sell to higher education." "A DevOps engineer at Ford looks nothing like one at Stripe." Stuff that's just known. Your AI can't act on what you never articulated. Watch the full conversation with Zach (Octave), Jared & Matteo (GTM Engineer School) here: https://lnkd.in/gzHvezp5

Excited to be back for Cohort 4 of GTM Engineer School with Jared Waxman and Matteo Tittarelli! I've now met hundreds of students through this program, and it gets more fun every time. Every cohort, people show up ready to build, learn, and push each other. New ideas to explore. New workflows surface. New ways of structuring systems get tested. The questions are the real ones, not the polished ones, and the knowledge sharing is what moves everyone forward. We love sharing Octave with people for the first time and showing them what's possible when you have a context layer at the foundation of your stack. And we love getting into the hard context-engineering questions. It's not about the flavor-of-the-month growth hack, we get deep. How do I set up a system that scales when my ICP keeps changing? How do I enable a competitive POV my team will actually use? What does a "strong fit" actually look like beyond firmographics and technographics? And so much more. I'll run the context-engineering module live myself, same as C3. But this time we're going much deeper on Octave via MCP. The new things becoming possible now that you can natively connect into Claude, Cursor, and any MCP-aware client are pretty wild. You get a purpose-built GTM context brain — tuned at the core for B2B workflows — that every agent can read and write from. And of course it learns on its own from every action your team takes. Context is the lens you put between your company and the markets you operate in. The model is a commodity. Everyone has it. The lens is your alpha. Can't wait to meet the next group. We're going to have some fun!! And you can use OCTAVE15 for 15% off 😊

"Using AI isn't a differentiator anymore." That's what Zach Vidibor told me on the pod last week. Zach is the co-founder and CEO of Octave. He's been inside LinkedIn, DocuSign, and Dropbox. He watched strategy leak and compress on its way from the exec team to the frontline. He and Julian Tempelsman built Octave as the fix. Here's why we're bringing Octave back for GTM Engineer School Cohort 4. The moat isn't AI. It's the context you codify on top — your ICP, your competitive opinions, your institutional knowledge, the customers you know you don't serve and why. That's the exact thing we want graduates to walk out knowing how to build. Three reasons Octave keeps earning its spot in our program: → Octave's three pillars (Library, Playbooks, Agents) give operators and a structured, dynamic home for context. Not a doc. Not a Notion page. Not a repo. A prism of knowledge where every workflow, every agent, and every teammate reads from. → Zach teaches like an operator. He works back from real problems in the first and have students building alongside him by minute 10 of his sessions. → Their MCP makes Octave ICP context, messaging playbooks, competitive intel, and agents can now be accessed directly through Claude, Cowork, and Code to update messaging, playbooks, campaigns, and agents in plain English. Plus, it's the partner that consistently surprises most of our students. If you're late to the AI GTM party and want to build solid, concrete, hands-on 101 GTM Engineering skills from scratch, this program is for you. Cohort 4 starts May 25. Enroll: https://lnkd.in/dEctSm5T

Jacob Brown, Head of Sales Development at Rilla, doesn't use Octave to find customers. He uses it to hire the people who do. Jacob built a BDR hiring test around Octave. Candidates research a list of prospects and populate data fields manually, it's a practical skills assessment that tells him who can do the job before they're on the floor. The problem was that grading submissions by hand was eating 15 minutes a day, adding up to 65 hours a year. So he built a Google Sheets integration that pulls candidate input in real time, scores accuracy against Octave's data library, and automatically returns a pass or fail verdict before he even opens the dashboard Rilla is an AI coaching platform for field sales teams, and when your entire business depends on reps talking to customers face to face, the quality of the BDRs you hire matters a lot. The work of evaluating them shouldn't consume a week and a half of leadership time every year. Most teams use Octave for account research, outbound sequencing, lead scoring, and call prep. But the common thread is always the same. There's a gap between the data you have and the motion you need to run, and that's what Octave closes. Read Jacob's full story here → ordnl.link/H62fwuD