Security buyers research for months before they talk to a vendor, much of it on GitHub. DemandCompass reads the signals they leave, scores whether each account knows you and whether it is moving, and lets both expire.
The person creating the signal is rarely the person signing the deal. A detection engineer forks your repo, a CISO approves the budget. DemandCompass rolls every person's signals up to the account, so the buying team shows up as one.
Across B2B, the buying journey averages 272 days, and 81% of it happens before sales sees a name (Demandbase and Dreamdata, 2026). Awareness is scored at the account level, so the quiet months count.
Security teams hire all year. A job post alone tops out at In-Market. An account needs timely evidence from a second, independent source before it crosses into Sales-Ready.
Readiness says the account is moving. Awareness says it knows you. Sales-Ready needs both, from more than one source, inside the window.
Security engineers try before they ask. They star the repo, fork it to test it against their own environment, watch the releases and open an issue when something breaks. None of that fills in a form. DemandCompass rolls each one up to the engineer's company, and with a second signal it is the earliest buying window you will see.
Detection engineering, cloud security, identity or AppSec roles say which problem the team is staffing for, and when.
A new CISO or head of security reviews the stack in the first months. The score dates it and lets it fade.
For public companies, the annual filing says where security spend is going. It can lift an account to the line, never across it alone.
A security tool added or dropped is a change window, for you or for the tool next to yours.
The install base you can displace, account by account.
The engineer who used your product last year just joined a new account. Warmest door in security.
Docs, integrations and pricing pages read by people at the same company.
The Decay Rule ages each signal on its own curve. Readiness fades fast, awareness slower. A breach headline from last spring stops counting.
A new security deployment starts from weights already learned in comparable deployments in its category, where the sample is large enough to trust.
Each week the system checks which signals preceded a real conversation and proposes a change. A person approves it. Nothing changes on its own.
829 signals captured, 150 surfaced to a person, 82% filtered out on purpose.
One deployment, one quarter.