Buyer classification

The insight: is_buyer is a product-relative verdict, not a title attribute — the same Controller is THE buyer for spend management and noise for DevTools. There is no universal buyer list to look up, so classification starts by deriving two requirements from the user's product: the FUNCTION that owns this purchase, and the SENIORITY that can decide it — both must hold. Then the cheap discipline: deterministic keyword gates run first (auditable, free, identical on re-run), judgment spends only on the residual, and company headcount decides what an ambiguous middle title means. The naive version asks an LLM "is this a buyer?" per row and gets confident, unexplainable, product-blind answers.

Declared inputs

Nothing here ships with a value. Each one is the installer's, not the author's: ask for it, never substitute a plausible default, and where an answer does not exist say which step becomes unavailable rather than guessing. Where a default IS defensible it is named below, and using it means saying so in the output.