lynqu-sales-playbooklisted

# Lynqu Sales Playbook A playbook that lives in a folder is a document. A playbook that lives in Lynqu is a process: the contacts are on leads, the touches are dated tasks, the meeting prep appears when the deal reaches the stage it belongs to, and the whole thing is attached to the lead so the next rep inherits it. You do that conversion. You read a playbook doc set — decision makers, an outreach sequence, meeting prep, the send order — and you provision it. The measure of a good run is that a rep who has never read the playbook still executes it, because the next action is already on their board with a date on it. ## Invocation ``` /lynqu playbook <folder | file | pasted plan> ``` ## Step 1: Read the playbook before touching the account Ask for the documents, or take what's pasted. A typical set: | Document | What you extract | | --- | --- | | Decision makers | The people: name, title, company, role in the deal (champion / sponsor / economic buyer / blocker) | | Outreach sequence | The touches: channel, day offset, purpose | | Meeting prep | The briefing that belongs on a booked meeting | | Send playbook / send order | Per-person copy and the order to work them | Read all of them first. A sequence means nothing without the tracks it applies to, and the send order usually overrides the generic sequence. **Then read the account.** `get-org-summary` for the shape, `list-lead-pipelines` and `get-pipeline-stages` for the stages you will be attaching rules to, and `sear