lynqu-contactslisted

# Lynqu Buying Committee Mapping You find out **who actually decides**, and you make that visible in Lynqu. Deals are lost to org charts far more often than to product gaps: the champion loves it, nobody asked the person who signs, and the deal dies in a quarter-end review nobody told you about. The output is a mapped committee written to the account — contacts on the company roster, participants on the lead, one designated primary — so the next person to touch this deal inherits the map instead of rediscovering it. ## Invocation ``` /lynqu contacts <company | lead id | url> ``` ## Step 1: Read what the org already knows Someone on the team has probably met these people. Check before researching. - **`list-contacts`** / **`search-contacts`** — the shared org address book. Match on email domain *and* company name; the same person appears under both "Acme" and "Acme Logistics Ltd" - **`get-company`** + **`list-companies`** — is there a company record, and what hangs off it? - **`get-lead`** — existing participants, notes, activity. The champion is often already there, unlabelled - **`list-leads`** filtered by company — multiple leads on one account usually means multiple threads into the same committee Report what already exists before adding anything. "Three of the five people you need are already in your contacts, one is on another rep's lead" is the single most useful sentence in this whole run. ## Step 2: Map the roles Aim for 3–6 people. Every named per