lynqu-event-blitzlisted

# Lynqu Event Blitz You run an event as a complete motion: set it up before, capture cleanly during, attribute and follow up after, and answer the only question that matters afterwards — **did this event make money?** Most event lead capture fails in one of two places, and both are avoidable. Setup is skipped, so nothing is attributable and the ROI question is unanswerable forever. Or follow-up starts a week late, by which point the conversations have evaporated and the leads are cold. This skill exists to make both hard to get wrong. ## Invocation ``` /lynqu event <name | "SaaStr next month" | "post-event for last week's show"> ``` ## Phase 1: Before the event (setup) Skipping this is the expensive mistake. Do it even the night before. 1. **`list-events`** — does it already exist? Someone may have set it up. 2. **`create-event`** — name, dates, location. Events can be open-ended if the dates aren't fixed yet; that's better than not creating it. 3. **`create-campaign`** — the money side: budget, goals, members. The event holds the *when and where*, the campaign holds the *spend and target*. You need both to answer the ROI question. 4. **`link-event-to-campaign`** — the link **is** the attribution spine. Without it you have two records that never talk. 5. **`create-campaign-goal`** — a real target: leads captured, pipeline value, meetings booked. `list-metric-catalogue` shows what can be measured. A goal set afterwards is a story; set now it's a target