Most Deal-Intelligence Tools Score One Call. Jeff Ignacio's Framework Says That's Level 1 of 5.

RevOps practitioner Jeff Ignacio built a nightly agent that reads sales call transcripts and updates deal notes automatically, and in describing it he lays out a five-level maturity framework that reframes what most conversation-intelligence tools are actually doing. Level 0 is the status quo — deal context lives entirely in a rep’s head. Level 1 is call recording plus basic summarization, which is where tools like Gong and Clari mostly operate today: useful, but scored per call in isolation. Level 2 is cumulative deal-state tracking across an entire deal’s history. Level 3 adds rep-pattern coaching across multiple deals. Level 4 is proactive call preparation built from that accumulated context.

The isolation problem at Level 1 is concrete, not theoretical: a system scoring call five of a deal in isolation might flag the champion as unconfirmed, missing a confirmation that actually happened on call two. MEDDICC elements — metrics, economic buyer, decision criteria, and the rest — routinely surface piecemeal across a deal’s whole conversation history, and a tool that only looks at the most recent call will misread the deal’s real state. Ignacio’s system architecture splits the problem into three roles — a context builder, a generator, and an evaluator — and he stresses that evaluation rubrics have to be defined before model selection, warning explicitly against letting errors silently accumulate in the memory layer over time as a deal progresses.

That last warning is exactly the gap Aviso’s “RevOps Agent Owner” framework was written to address. Aviso argues that as agents like Ignacio’s move from pilot to production, organizations accumulate a governance vacuum — nobody formally accountable when an agent acts on stale or wrong context, such as an SDR agent drafting outreach about a champion who’s already left the company. Aviso’s proposed fix is a dual-ownership model: a Business Owner (typically RevOps or Sales leadership) accountable for commercial outcomes, and a Technical Owner (typically SalesOps or IT) accountable for infrastructure and compliance, connected by what it calls a Context Handshake Protocol for agent-to-agent or agent-to-human handoffs.

Put the two together and the sequencing question for any RevOps team evaluating deal-intelligence tooling is the same one Ignacio’s framework surfaces on its own: a Level 2+ system that quietly accumulates errors with nobody accountable for catching them is worse than a Level 1 tool everyone knows is limited.