Terminal
Terminal/Skill
Finds the people who hold budget for your product at one company, with titles, LinkedIn profiles and checks that they still work there.
By Clay
Works with
npx skills add clay-run/clay-skill-creator --skill find-decision-makers-at-companyThe insight: the obvious tool answers the wrong question. Clay's managed "Find People at Company" function returns the company's top people ranked by seniority and ignores role filters entirely — it answers "who is important here," while the buyer of your product is a FUNCTION × SENIORITY pair ("who owns the budget for this category"). A famous-CEO test passes coincidentally; for any real persona the top-N list is confidently wrong. So this skill searches role-scoped from the start, maps titles to seniority/department with deterministic rules, verifies current employment on the person's own record, and frames who's the economic buyer vs the champion — because "decision-maker" is a claim about budget authority, not fame.
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.
| Input | What the installer supplies | If it is missing |
|---|---|---|
| The company | a domain, preferably | a bare name is resolved to a domain and confirmed first — a wrong domain finds a different company's people |
| What they sell | the function they target, which is what defines the buyer | ask. This maps to target departments and a seniority floor; without it "decision maker" has no meaning |
| How many people | one economic buyer, or the committee | up to five with roles framed is defensible and must be stated |
If an answer sheet is present beside this skill, load it and ask only for what it does not cover. A partial sheet is normal; a value it is missing gets asked for on its own rather than restarting the interview. Say which values came from the sheet before using them — a sheet applied silently is a wrong field nobody catches. If there is no sheet, say nothing about sheets — the check is a file lookup, not a question, so run the interview as though the feature did not exist rather than reporting an absence. At delivery, offer to save the answers back (identifiers only — never a token or a password), private and never published — and phrase the offer so it explains itself: "want me to save your answers to a file, so the next person on your team doesn't have to answer these again?"
Run clay whoami; echo "exit_code=$?". If it fails or Clay tools are missing, run
the Clay plugin's setup skill, restart if it says to, and re-run this skill. Tell
the user which workspace you're in.
references/finding-mechanics.md §Buyer mapping): e.g. spend management →
Finance & Accounting, Director+; security → IT & Security, Director+.Run filters-mode people search with the company anchor + job_title_keywords for
the target function's title vocabulary (both list-shaped; exact mechanics and field
paths in the reference). Widen the title vocabulary before widening seniority — the
miss is usually vocabulary ("Head of", localized titles), not absence. NEVER
substitute the seniority-ranked company lister for a role question (its measured
behavior is the reference's §Why not the obvious function).
Map every returned title with the canonical rules — seniority by title-token overrides (Chief/Founder/Owner → C-level; Director/VP → Executives; Senior/Lead/ Group → Non-Exec Management; product/program/project managers are ICs, the classic misread), department by the 12-value enum. Keep candidates whose department matches the target AND seniority clears the floor. Ambiguous titles go to an LLM pass only after the deterministic rules, and its verdict must quote the title it ruled on.
domain field echoes YOUR search anchor, not the person's
employment — read the person's own latest-experience fields for employer, title,
and start date.multi-role / departed /
unconfirmed explicitly, never silently drop or keep.Per person: name · title · seniority · department · buying-committee role (economic buyer / champion candidate / influencer) · LinkedIn (canonical) · employment (current/multi-role/unconfirmed, with start date) · evidence (the record fields that earned the row). Run summary: candidates examined, kept, rejected-by-reason, and —
when fewer than asked — an honest shortfall with which vocabulary/seniority was
searched. Zero matches is a RESULT: "no identifiable [function] leadership" beats
promoting whoever ranked first. Getting their email is find-work-email's job — hand
off, don't inline.
Ask: "Who would buy our spend-management platform at brightloop.example?" Mapping: Finance & Accounting, Director+. Search: company anchor + title vocabulary (CFO, VP Finance, Controller, Head of Finance) → 3 candidates. Classification: CFO (C-level, Finance) → economic buyer; VP Finance (Executives, Finance) → champion candidate; "Finance Program Manager" → IC by the manager-override rule, dropped with reason. Employment: CFO's own record shows current role since 2025-11 (new in seat — noted as a hook); VP shows a second concurrent advisory role → multi-role, kept with flag. Delivered: 2 kept + 1 rejected-with-reason + handoff note ("emails: find-work-email"). Search quota only; zero credits spent.