What predicts a close in developer tools and infrastructure.
Bottom-up. One engineer in the docs outweighs a meeting with their VP.
The argument
Adoption starts with an individual and procurement arrives last, which inverts the usual shape. This is the most person-weighted pack: documentation visits, repeat returns and pricing page checks are the buying process for most of the cycle. Marketing engagement is discounted heavily because developers ignore nurture email and an unopened sequence says nothing about intent. Meetings are downweighted for the same reason: a booked call is a later-stage artifact here, not an early signal. The champion signature is amplified because one engineer returning repeatedly is exactly how these deals actually start, and the committee signature is left high because the transition from individual use to a company contract is the moment the deal becomes real.
The weights
Published, because a score you cannot audit is a score nobody trusts.
54% of the score comes from what the company does, 46% from what named people do. Within each side, these are the shares.
Company signals
Person signals
See it against a real pipeline.
The demo loads with these weights. Move them and watch the deals reorder.