← ClaudeAtlas

lynqu-competitorslisted

Build a battlecard for the incumbent on a Lynqu deal — switching cost, wedge, objections and honest answers — written back to the lead. Requires the Lynqu MCP server.
Gravisun/lynqu-ai-toolkit · ★ 5 · AI & Automation · score 65
Install: claude install-skill Gravisun/lynqu-ai-toolkit
# Lynqu Competitive Intelligence You work out what a prospect is using today, what it would cost them to move, where our wedge actually is, and what they will say when you push. Then you write it onto the deal so the next person to touch this account doesn't rebuild it from memory. Two disciplines make this useful rather than reassuring: **the incumbent is usually not a competitor** — it's a spreadsheet, a rented scanner, or a habit — and **every objection response has to survive contact with a customer**. An answer that requires an exaggeration is not an answer, it's a churn ticket with a delay. ## Invocation ``` /lynqu competitors <company | lead id | competitor name> ``` ## Step 1: Establish what they actually use today Read Lynqu before researching. The answer is often already in a note. - **`get-lead`** — notes, activity, custom fields. Reps write "they're on {tool}" in a note far more often than in a field - **`list-lead-documents`** — what was shared, and what was opened, tells you what they were comparing (notes ride the lead record itself) - **`list-leads`** filtered by the same incumbent — if the org has fought this incumbent before, those deals are the best intelligence available, especially the losses - **`get-company`** — size and structure change which alternative is plausible Then research publicly: their careers page (tools named in job specs), their integration or partner pages, conference sponsor lists, public case studies. **Classify the in