Product Usage Scoring & Routing
All accounts

BriIv Soft

briiv-soft.example · Prospect44 employees · Consulting · Starter
Policy northfield_v1

Person

Email
kira.gale@briiv-soft.example
Role
Engineering
Seniority
Manager
Email type
Business
Admin
Yes

Product-event timeline

  • Invited teammatesAug 12, 2026, 12:00 PM
  • Viewed pricingAug 11, 2026, 12:00 PM
  • Weekly actives observedAug 9, 2026, 12:00 PM
  • Connected serviceAug 6, 2026, 12:00 PM
  • Resolved incidentAug 5, 2026, 12:00 PM
  • Viewed pricingAug 1, 2026, 12:00 PM
  • Account createdNov 17, 2025, 12:00 PM

Scores

fitLow
  • manager is a Manager/lead engineering role+10
  • us is a supported geography+10
  • Business email on a work account+10
  • Compatible technical environment for Northfield Incident Management+15
  • Personal-use workspace is a poor-fit signal-20
usageMedium
  • Resolved the first incident in Northfield Incident Management+11.25 / cap 15
  • Additional resolved incident (5 points each, cap 15)+3.75 / cap 15
  • Additional resolved incident (5 points each, cap 15)+3.75 / cap 15
  • Invited 20 teammates (exclusive band 11plus)+25 / cap 25
  • At least 3 weekly active users+10 / cap 10
intentLow
  • Admin active on 6 distinct days in the last 14 days+10 / cap 10

Decision

Selected play
Self-serve
Owner
SLA
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); Expansion intent 10 < 30
  • acquisition_sales_assistFit 25 < 70; Intent 10 < 40
  • monitorFit 25 < 70
  • self_serveProspect using the product (usage 54>=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

  • Prospect below sales threshold; self-serve without a sales task

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.