All accountsPolicy northfield_v1
BriPyr Cloud
bripyr-cloud.example · Customer179 employees · Cloud software · EnterprisePerson
- hettievale@bripyr-cloud.example
- Role
- Engineering
- Seniority
- CTO
- Email type
- Business
- Admin
- No
Product-event timeline
- Viewed SSO docsAug 12, 2026, 12:00 PM
- Viewed security docsAug 11, 2026, 12:00 PM
- Added workspaceAug 10, 2026, 12:00 PM
- Viewed enterprise pricingAug 7, 2026, 12:00 PM
- Viewed admin docsJul 31, 2026, 12:00 PM
- Account createdJan 28, 2026, 12:00 PM
Scores
fitHigh
- 179 employees falls in the 50–499 target band+20
- cloud_software is a target B2B software/devtools/cloud industry+15
- 65 engineering employees falls in the 20–199 target band+15
- cto is a Director/VP/C-level engineering role+15
- Business email on a work account+10
usageLow
- Customer added a second workspace (2 total)+15 / cap 15
intentMedium
- Viewed enterprise pricing+10 / cap 20
- Viewed SSO documentation+15 / cap 15
- Viewed security documentation+15 / cap 15
- Viewed enterprise administration+7.5 / cap 10
Decision
- Selected play
- Manual review
- Owner
- GTM Ops
- SLA
- 1 business day
- Strongest rejected alternative
- Monitor
All evaluated gates
- hard_blocksNo hard blocks present
- manual_reviewManual review: Missing geography (critical fit)
- explicit_requestNo in-window explicit sales request
- expansionExpansion usage 15 < 45
- acquisition_sales_assistNot a prospect (acquisition is prospect-only); Usage 15 < 50; No qualifying activation (no in-window production/incident/invite/active-user event)
- monitorNot a prospect (monitor is prospect-only)
- self_serveNot a prospect (self-serve is prospect-only); Usage 15 < 25; Fit and intent both at or above sales threshold
- default_no_sales_actionCustomer below the expansion threshold — monitor for future expansion (no task, existing ownership preserved)
Decisive evidence
- Missing geography (critical fit)
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.