Signal in. Action out.
Watch the routing brain work.
This is the decision layer I build between 6sense, Demandbase, Marketo, and Salesforce — the same rules published in the public routing-rules repo, running client-side in your browser. Pick an account-level signal, send it, and see which person-level actions fire, which gates stop it, and how the plays change once an account is already a customer.
1 · Account-level signal
2 · Account
Stages mean decisions
Target, Awareness, Consideration, Decision, Purchase — each 6sense stage maps to a concrete play, agreed with sales in writing before anything is configured.
Stage mapping rules →Account ≠ person
Account-level intent never writes directly into person-level scores here. That single rule keeps surge noise from corrupting the scoring model sales already trusts.
Intent handling rules →The unit is the buying group
At enterprise scale, account-level signal is noise — a nine-division account is always in-market for something. Signals here resolve to account × business unit × service line before anything fires, and unresolvable signal routes to map-building instead of campaigns.
How I wire this in production →Gates before actions
Suppression, open-opp conflicts, persona coverage, signal freshness. The blocked paths in this demo are the ones that quietly kill trust when they're missing.
The routing matrix →Most teams run 20–40% of what they bought.
The gap is rarely configuration. It's the decisions the vendor can't make for you — which accounts are in the program, who works which stage, how a surge becomes a meeting. That decision layer is what I build and operate. This page is a small, honest sample of it.
Demo accounts are fictional. The rule logic mirrors the public repo; client engagements adapt the matrix to your tiers, personas, and coverage model. The delivery-team field note is the one signal here money can’t buy — most organizations already own it and have never captured it.