Product Usage Scoring & Routing
All accounts

VexElm Soft

vexelm-soft.example · Prospect229 employees · Infrastructure · Enterprise
Policy northfield_v1

Product-event timeline

  • Resolved incidentAug 9, 2026, 12:00 PM
  • Weekly actives observedAug 8, 2026, 12:00 PM
  • Viewed enterprise pricingAug 2, 2026, 12:00 PM
  • Viewed enterprise pricingJul 30, 2026, 12:00 PM
  • Invited teammatesJul 27, 2026, 12:00 PM
  • Connected serviceJul 26, 2026, 12:00 PM
  • Account createdDec 9, 2025, 12:00 PM

Scores

fitMedium
  • 229 employees falls in the 50–499 target band+20
  • infrastructure is a target B2B software/devtools/cloud industry+15
  • 52 engineering employees falls in the 20–199 target band+15
  • nl is a supported geography+10
usageMedium
  • Connected a production service to Northfield Incident Management+8 / cap 20
  • Resolved the first incident in Northfield Incident Management+15 / cap 15
  • Invited 16 teammates (exclusive band 11plus)+10 / cap 25
  • At least 3 weekly active users+10 / cap 10
intentLow
  • Viewed enterprise pricing+7.5 / cap 20
  • Viewed enterprise pricing+7.5 / cap 20

Decision

Selected play
Manual review
Owner
GTM Ops
SLA
1 business day
Strongest rejected alternative
Self-serve

All evaluated gates

  • hard_blocksNo hard blocks present
  • manual_reviewManual review: No resolved person identity
  • explicit_requestNo in-window explicit sales request
  • expansionNot a customer (expansion is customer-only); Expansion usage 43 < 45; Expansion intent 15 < 30
  • acquisition_sales_assistFit 60 < 70; Usage 43 < 50; Intent 15 < 40
  • monitorFit 60 < 70
  • self_serveProspect using the product (usage 43>=25) below the sales threshold — no sales task
  • default_no_sales_actionProspect below all activation/sales thresholds — default self-serve (no sales task, no owner change)

Decisive evidence

  • No resolved person identity

Simulate a bounded signal

One bounded, allowlisted signal. The server maps it to a bounded event, recomputes deterministically, and explains the change — nothing is persisted.

CRM state

Not synced — this evaluation did not request a CRM sync. Sync is a separate, designated action; the decision is revealed independently of any CRM write.