The One Metric Sales and Marketing Should Agree on Before Any ABM Program Launches

‍TL;DR: Before any ABM program launches, sales and marketing need explicit, written agreement on one specific metric: what counts as a genuinely engaged account, defined by a specific combination of signals, not a vague sense of "activity." Without this agreement locked in before launch, marketing will report engagement using its own definition, sales will judge account readiness using a different, unstated definition, and the two sides will disagree about whether the program is working without ever realizing they're actually measuring different things.

‍

Most ABM program launches skip a five-minute conversation that determines whether the entire program will be judged a success or a failure three months later: agreeing, explicitly and in writing, on exactly what counts as a genuinely engaged target account. Skip this conversation, and sales and marketing will each quietly apply their own definition, then argue about results that were never actually measuring the same thing.

Why "engagement" means something different to each team by default

Marketing tends to define engagement broadly: a target account's employees opening emails, visiting the website, downloading content. Sales tends to define engagement more narrowly and more skeptically: a specific person at the account expressing direct interest, agreeing to a call, or showing a clear buying signal a rep would actually act on. Both definitions are reasonable from each team's own vantage point, and they produce completely different accounts of how many target accounts are "engaged" at any given moment, which is exactly the setup for a disagreement neither side sees coming until the first program review.

What the pre-launch agreement actually needs to specify

Why a signal combination, not a single action, is the right basis for the definition

A single email open or website visit is too weak a signal to reasonably count as genuine engagement on its own, since it could reflect a passing, low-intent moment rather than real interest. Requiring a specific combination, multiple distinct people at the account engaging, or one person engaging multiple times within a defined window, produces a more defensible threshold that both teams can agree actually reflects something meaningful, rather than a threshold so low that marketing can report high account engagement numbers sales doesn't trust, or so high that genuinely promising early signals get dismissed entirely.

Why role and seniority weighting prevents a common, specific disagreement

Without an explicit agreement, marketing might count a junior employee's content download the same as a VP's direct inquiry, while sales instinctively discounts the junior signal heavily. purple path's approach to mapping the buying committee first in ABM depends on exactly this kind of role-specific understanding; building that same role-weighting logic directly into the engagement metric definition, agreed before launch, prevents the two teams from silently applying different implicit weightings to the same raw data.

Why the recency window matters more than it might initially seem

An account that engaged heavily two months ago and has gone quiet since looks identical to a currently, actively engaging account if the metric definition doesn't specify a recency requirement. This creates a specific, avoidable problem: a stale account sits in a "high engagement" bucket long after its actual momentum has faded, misleading both teams about where to focus current outreach effort. Defining a specific recency window as part of the metric, rather than treating any historical engagement as equally current, keeps the definition honest about what's actually happening right now versus what happened previously.

Why this agreement needs to happen before launch, not after the first review meeting

Reaching this agreement after the program has already launched, typically triggered by a disagreement surfacing in the first review meeting, means the conversation happens defensively, with each side already having reported numbers based on their own unstated definition and feeling some pressure to defend those numbers rather than genuinely reconsider the underlying definition. Having the conversation before launch, when no numbers have been reported yet and neither side has anything to defend, produces a more honest, less contentious negotiation over what the definition should actually be.

Why this single metric doesn't replace the need for a broader operating framework

Agreeing on this one specific engagement metric is a necessary starting point, not a complete alignment framework on its own. purple path's RevOps framework for aligning sales and marketing around ABM covers the broader shared scoring and reporting infrastructure needed to sustain alignment over time; the single-metric agreement in this article is the specific, minimum starting point that makes the rest of that broader framework possible to build on a foundation both teams have already agreed to.

How to actually run the pre-launch conversation that produces this agreement

A practical approach: before launch, bring both teams together specifically to answer three direct questions, what specific actions count toward engagement, how should different roles or seniority levels be weighted, and how current does an action need to be to still count. Write the agreed answers down explicitly, in a shared document both teams can reference, rather than treating the conversation as a verbal understanding that each side might later recall slightly differently.

What happens to programs that skip this specific pre-launch step

An ABM program that launches without this explicit agreement typically runs for several weeks or months with each team quietly tracking its own version of engagement, discovering the mismatch only when marketing reports a specific number of "engaged accounts" that sales immediately disputes based on their own, different mental model of what engagement should mean. By this point, the disagreement often gets framed as a broader trust or effort problem between the two teams, when the actual root cause was a single, specific, easily fixable definitional gap that was never explicitly closed before launch.

Why writing this definition down should feel almost unnecessarily obvious at the time

A useful signal that this conversation has gone well: if the final agreed definition feels almost too simple or obvious to have needed a dedicated discussion, that's usually a sign the conversation successfully surfaced and resolved the hidden assumptions each side was carrying, rather than a sign the conversation wasn't necessary in the first place. The value isn't in producing a complicated or sophisticated definition; it's in confirming, explicitly, that both sides are picturing the same specific thing when they use the word "engaged."

Why revisiting this same metric across multiple programs builds institutional consistency over time

A company running its first few ABM programs with this explicit pre-launch agreement discipline tends to converge, over time, on a reasonably consistent house definition of engagement that doesn't need to be renegotiated fully from scratch for every new program. Documenting the reasoning behind the definition, not just the final numbers, the first time it's agreed on makes this convergence faster, since future programs can start from an existing, well-reasoned baseline and adjust only where a specific program's circumstances genuinely warrant a different threshold.

Frequently Asked Questions

Should this engagement metric definition be identical across every ABM program a company runs?

Not necessarily; different programs targeting different segments or deal sizes may reasonably use different specific thresholds, though the discipline of explicitly agreeing on the definition before launch should apply consistently across every program, regardless of how the specific numbers within that definition are set.

Who should have final say if sales and marketing can't agree on the definition during the pre-launch conversation?

A neutral party, ideally whoever holds broader RevOps or operations authority, is well positioned to make the final call if the two teams can't reach agreement directly, since that role should have credibility with both sides without a built-in bias toward either team's preferred definition.

How often should this engagement definition be revisited once a program is running?

Reviewing it at least once per quarter, checking whether the current definition is still producing a number both teams find credible and useful, catches cases where the original definition needs adjustment as the program matures and more real data becomes available to evaluate it against.

Does this single-metric agreement apply the same way to a one-to-few ABM program as to a broader account-based program?

The same underlying principle applies regardless of program scale, though a one-to-few program with a smaller, more closely tracked account list may reasonably use a more detailed, higher-touch definition of engagement than a broader program covering many more accounts with less individual attention per account.

What's the fastest way to tell if a currently running program is suffering from this exact undefined-metric problem?

Ask a marketing team member and a sales team member separately, without letting them confer, to define what "engaged" means for the current program. If their answers differ meaningfully, that gap has very likely already been quietly causing disagreement, even if nobody has yet traced it back to this specific, fixable root cause.

‍

Having this exact conversation before your next ABM program launches, rather than after the first disputed report, is a five-minute investment that prevents months of quiet, avoidable friction. Talk to purple path about defining the right engagement metric for your next ABM program.