Playbooks

Competitor engagement sequence

Start from the words they used on the thread. Qualify the company before either channel sends.

Last updated 23 October 2026. Public competitor facts are dated on the page.

When to run this play

Run this when a person at a company you can serve commented on a competitor, an alternative, or a category expert, and the comment says something about the job to be done. A bare like stays in a low-priority pile.

SDR teams and SaaS startups use this as the default first play. Lead gen agencies use it per client niche, with the client’s competitors, not the agency’s.

Qualify before anyone writes

  • The comment or post text is stored with the URL.
  • The person resolves to a company that fits. If the company is unknown, the row waits.
  • They are not a competitor’s employee, a student, or someone already in sequence.
  • The point you will make is about their words, not a feature dump.

Sample sequence

Example TWL Reach sequence for planning. It is not a customer result, a script to paste, or permission to contact someone you have no business contacting.

  1. Day 0 · LinkedIn. Two sentences: what they wrote, and a question. No attachment. No “I noticed you liked a post”.
  2. Day 2 · Email. Subject is their topic. Body paraphrases in one line and names the team you help. One question.
  3. Day 6 · Email. A single additional observation you can defend. If you have none, this step is deleted, not filled with a bump.
  4. Day 10 · Stop. A last line that closes the loop without a new claim. Then the workflow ends the sequence.

Keep the agent controllable

Block phrases that attack the competitor or claim a win rate. The agent drafts from the stored comment. A manager approves the pattern, then reviews exceptions.

This is a controllable AI SDR: the research runs, the copy waits, the send obeys the rule. See the AI SDR glossary entry.

Questions people ask

What if they engaged with our post, not a competitor’s?

That is a warmer version of the same play. Say it was your post. Do not pretend it was a coincidence.

How do we avoid duplicate touches?

Dedupe the person across sources before day 0. The lead deduplication guide covers the workflow shape.

Is LinkedIn automation required?

No. TWL Reach can prepare the step for a person to send. If you automate, stay inside the network’s rules. This playbook does not raise limits.

Which comparison is relevant?

HeyReach and Expandi if the question is LinkedIn sending infrastructure. Valley if the question is a packaged AI sender. TWL if the signal and the sequence should share a stack.

Put the next workflow on the stack.

Start with the tool you need. Connect signals, TWL Reach and the rest of the system when the job is real.

Get TWL