Product Usage Scoring & Routing
All accounts

Arcwell

arcwell.example · Prospect · Highlighted fixture320 employees · SaaS · Business
Policy northfield_v1

Person

Email
maya.okafor@arcwell.example
Role
Engineering
Seniority
Director
Email type
Business
Admin
Yes

Product-event timeline

  • Connected serviceAug 12, 2026, 12:00 PM
  • Viewed enterprise pricingAug 12, 2026, 12:00 PM
  • Viewed SSO docsAug 12, 2026, 12:00 PM
  • Viewed security docsAug 12, 2026, 12:00 PM
  • Resolved incidentAug 11, 2026, 12:00 PM
  • Viewed enterprise pricingAug 11, 2026, 12:00 PM
  • Invited teammatesAug 10, 2026, 12:00 PM
  • Weekly actives observedAug 10, 2026, 12:00 PM
  • Account createdApr 15, 2026, 12:00 PM

Scores

fitHigh
  • 320 employees falls in the 50–499 target band+20
  • saas is a target B2B software/devtools/cloud industry+15
  • 120 engineering employees falls in the 20–199 target band+15
  • director is a Director/VP/C-level engineering role+15
  • us is a supported geography+10
  • Business email on a work account+10
  • Compatible technical environment for Northfield Incident Management+15
usageHigh
  • Connected a production service to Northfield Incident Management+20 / cap 20
  • Resolved the first incident in Northfield Incident Management+15 / cap 15
  • Additional resolved incident (5 points each, cap 15)+5 / cap 15
  • Invited 8 teammates (exclusive band 6to10)+20 / cap 20
  • At least 3 weekly active users+10 / cap 10
intentMedium
  • Viewed enterprise pricing+10 / cap 20
  • Viewed enterprise pricing+10 / cap 20
  • Viewed SSO documentation+15 / cap 15
  • Viewed security documentation+15 / cap 15
  • Admin active on 3 distinct days in the last 14 days+10 / cap 10

Decision

Selected play
Sales assist
Owner
Enterprise AE
SLA
4 business hours
Strongest rejected alternative
Monitor

All evaluated gates

  • hard_blocksNo hard blocks present
  • manual_reviewIdentity and critical fit present
  • explicit_requestNo in-window explicit sales request
  • expansionNot a customer (expansion is customer-only)
  • acquisition_sales_assistProspect fit 100>=70, usage 70>=50, intent 60>=40, activated, no hard block
  • monitorHigh-fit prospect (fit 100>=70) below sales-assist threshold — monitor without a task
  • self_serveFit and intent both at or above sales threshold
  • default_no_sales_actionProspect below all activation/sales thresholds — default self-serve (no sales task, no owner change)

Decisive evidence

  • Prospect fit 100>=70, usage 70>=50, intent 60>=40
  • Connected a production service
  • Resolved 2 incident(s)
  • Invited 8 teammate(s)
  • 5 weekly active user(s)

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

The server persists the run and executes a deterministic fictional company, contact, association, and follow-up task through its configured HubSpot adapter (deterministic fake locally and in the preview without credentials; the real test account when credentials are configured) — no outreach is ever sent, and no HubSpot external ids are exposed. This panel polls the public run status until the sync finishes; no reload needed.

Loading verification status…