Skip to content
RAY BEHARRY

Agent 53 of 71 · Analytics & Learning

Sales Momentum Analyst

Connect enablement and narrative to pipeline movement. Show whether deals exposed to a narrative, talk track or ESOT block progress faster and resolve objections more often than comparable deals that were not, with confounders such as AE tenure and deal size declared.

Agent contract

Use to measure whether marketing changes speed deals up: stage conversion, velocity days, objection resolution %, security-review cycle time, and talk-track adoption versus win-rate delta. The mid Impact Chain link.

When it runs

  • A talk track, battlecard or ESOT block has been live for 30 days.
  • Pipeline velocity or stage conversion moves outside its normal range.
  • Monthly enablement impact review is due.

What it needs

InputRequiredFrom
Opportunity history with stage dates and amountsYesSalesforce (integration)
Call analysis with talk-track and objection tagsOptionalGong (integration)
Enablement blocks and their publish datesYesEnablement Source of Truth (ESOT)
Tagged deal observationsYesPerformance Observations

How it works

  1. Import opportunity and call exports; record systems and windows.
  2. Run `python3 scripts/sns.py metrics sales-momentum` for stage conversion, velocity days, objection resolution % and security-review cycle time.
  3. Build two cohorts: deals where the talk track or ESOT block was used (per call tags) and comparable deals where it was not.
  4. Match or stratify cohorts on AE tenure, segment and deal size band; declare any confounder that cannot be controlled.
  5. Report talk-track adoption rate and the win-rate and velocity deltas between cohorts as ranges with n.
  6. Run `python3 scripts/sns.py metrics enablement-latency` and note whether slow updates coincide with unresolved objections.
  7. End by listing each enablement asset as keep, fix or retire, tied to its ESOT block ID and seller-facing owner.

What it delivers

Momentum readout: stage conversion and velocity table, objection resolution by objection, security-review cycle time, adoption vs win-rate cohort comparison with confounders, enablement latency, keep/fix/retire list.

Output contract: metric-readout

Quality bar

  • Cohorts are comparable on segment and deal size, or the gap is declared.
  • Deltas are ranges with sample sizes; cohorts under 15 deals are low confidence.
  • Correlation is never described as causation without a counterfactual.

Hands off

When a person steps in

  • Escalate when results could be read as rating individual sellers; report at team level only unless a human owner asks otherwise.
  • If stage definitions changed mid-window, stop and request a human-confirmed mapping.

Example

Request

“Did the new security-objection ESOT block help deals move?”

Result

Salesforce + Gong, 90 days. Block used in 41 of 112 mid-market deals. Objection resolution 68% vs 44%. Security-review cycle 12 vs 19 days (median). Win-rate delta +6 to +14 pts; AE tenure balanced, deal size skews +8% in the used cohort (declared). Enablement latency 4 days. Keep and extend to enterprise.

Illustrative example from the package documentation, not a client result.