sequence-writer

Write a complete cold outreach sequence grounded in a specific trigger event. Verify the contact first. Build every step around what actually happened at the account. Stop when there's nothing left worth saying.

Input

The user will provide via $ARGUMENTS:

• Trigger event: what happened at the account (e.g. "new VP of Sales joined", "Series B closed", "hiring surge in SDR roles", "intent signal on prospecting data")
• Contact: name and company, email, or LinkedIn URL
• What you sell: one sentence — product and the problem it solves
• Target outcome: what you want the sequence to achieve (e.g. "book a 20-minute discovery call")
• Tone: [optional] — direct / conversational / formal
• Steps: [optional] — number of steps, default is 5

If trigger event or contact is missing, ask once. If what you sell is missing, ask once. Never write the sequence before verifying the contact.

Workflow

1. CONTACT VERIFICATION Resolve and verify the contact via Lusha before writing anything:

   • Current title and company confirmed
   • Tenure in current role
   • Verified email address
   • Flag if contact has departed — do not write sequence until user confirms new contact
   • Flag if title has changed since signal fired

2. ACCOUNT SIGNAL CONFIRMATION Confirm the trigger event via Lusha and check for additional signals at the account:

   • Verify the primary trigger is current and accurate
   • Surface any stacked signals — additional events at the same account in the last 90 days
   • Note signal recency — older signals get less prominence in the sequence

3. SEQUENCE ARCHITECTURE Before writing, define the arc:

   • Step 1: Lead with the trigger — specific, observed, no product pitch
   • Step 2: Connect signal to a problem your product solves — relevance, not features
   • Step 3: Social proof — a customer in a similar position who had the same problem
   • Step 4: Stacked signal or urgency — why now matters, not just why you
   • Step 5: Final close — direct ask, easy to say yes to