Optimize your cold sequence for your ICP in ChatGPT

Example outputs in this play are illustrative — they reflect the structure, fields, and format of real Lusha connector output, but were not pulled from a live session. Run the prompt with your own sequence and ICP to see live results.

Cold sequences usually fail not because the writing is bad but because the message could have been sent to anyone. A VP of Sales at a Series B SaaS company that just hired eight SDRs needs a different sequence than a VP of Sales at a 2,000-person enterprise that hasn’t moved headcount in two years. This prompt takes your existing sequence, pulls your ICP’s verified firmographic profile and live buying signals using Lusha in the ChatGPT Marketplace, and rewrites every step around the specific context that makes your outreach relevant to the accounts you’re actually targeting.

How to start

1

Open Lusha in ChatGPT

Go to the ChatGPT Marketplace, search for Lusha, and click “Start chat.” Every conversation started this way is automatically Lusha-enabled.

2

Or invoke Lusha in any existing conversation

Type @Lusha in the prompt bar and select Lusha from the dropdown. Unlike Claude, Lusha does not activate automatically in every ChatGPT conversation — you must invoke it every time.

3

Paste your existing sequence and fill in the brackets

Copy the prompt below, paste your current sequence where indicated, fill in your ICP details, and send. Lusha pulls live context and rewrites every step.

The prompt

Start from the ChatGPT Marketplace or type @Lusha before sending.

@Lusha I want you to optimize my cold sequence for my ICP
using verified data and live buying signals from Lusha.

MY CURRENT SEQUENCE:
[Paste your existing sequence here — subject lines,
body copy, and CTAs for each step]

MY ICP:
- Industry: [e.g. B2B SaaS, Revenue Intelligence]
- Company size: [e.g. 100–500 employees]
- Funding stage: [e.g. Series A or Series B]
- Target buyer: [e.g. VP of Sales, Head of RevOps]
- Geography: [e.g. North America, UK, DACH]

MY PRODUCT:
[One sentence — what you sell and the problem it solves]

Using Lusha, do the following:

1. ICP SIGNAL PULL
   Pull the most common buying signals currently
   firing across accounts that match my ICP:
   - What signals are most active right now
     (funding events, executive moves, hiring surges,
     intent spikes)?
   - What does the typical ICP account look like
     today — employee count range, funding stage,
     tech stack?

2. SEQUENCE AUDIT
   Review each step of my current sequence and flag:
   - Any step that could have been sent to anyone
   - Any opening that doesn't reference a specific
     signal or verified context
   - Any CTA that is too generic or low-friction
   - Any step that repeats the same angle as
     a previous step

3. REWRITE
   Rewrite the full sequence using the ICP signal
   data Lusha returned. For each step:
   - Open with the most relevant signal for that
     step — not the same signal every time
   - Connect the signal to the specific problem
     your product solves for this ICP
   - Write a CTA that is specific and tied to
     the signal, not generic
   - Keep each email under 120 words
   - Keep subject lines under 8 words

4. EXPLAIN
   For each rewritten step, note in one line
   what signal or data point you used and why
   it makes that step more relevant than the
   original.
Built by: Unknown
Tools: ChatGPT, Lusha
Type: Template

What to do next

A rewritten sequence where every step is grounded in verified ICP context and live Lusha signals. Here’s what the output looks like for a VP of Sales sequence targeting Series B SaaS companies:

Optimized sequence — Lusha ICP signals applied

StepSignal usedSubject line
Step 1 — Day 0Hiring surge — 8 SDR roles postedScaling the SDR team at [Company]
Step 2 — Day 4Funding event — Series B closedWhat the best Series B teams do differently
Step 3 — Day 8Social proof — similar ICP customerHow [similar company] did it
Step 4 — Day 14Intent signal — score 74 on categorySaw you’re researching this
Step 5 — Day 21Final close — timing urgencyLast one from me

Example outputs in this play are illustrative — they reflect the structure, fields, and format of real Lusha connector output, but were not pulled from a live session. Run the prompt with your own sequence and ICP to see live results.

Why use Lusha in ChatGPT to optimize your sequence

 

Most sequence optimization tools look backward — they analyze open rates, reply rates, and click-through data to tell you what worked before. That’s useful, but it misses the real reason sequences underperform: the message isn’t grounded in what’s happening at the accounts you’re targeting right now.

Lusha’s signal layer changes the optimization frame entirely. Instead of asking “which subject line had the best open rate,” this prompt asks “what is actually happening at Series B SaaS companies with 100 to 500 employees right now — and does my sequence reflect any of it?” The answer almost always reveals that step one could have been sent to any VP of Sales anywhere, step two repeats the same angle as step one, and none of the steps reference a named event that creates a specific reason to reply today.

Lusha processes 1.2B+ data points daily and tracks 24 live signal types across the B2B market. Running the optimization inside ChatGPT with @Lusha means the rewrite is grounded in what’s verified and current — not in what a copywriter imagined your ICP cares about six months ago when the sequence was first written.

Lusha data is sourced and used in accordance with Lusha’s Privacy Policy and Terms of Use. Lusha is GDPR compliant and covers accounts across North America, EMEA, and APAC.

FAQ

  • How is this different from A/B testing my sequence in my sequencing tool?

    A/B testing tells you which version of your sequence performed better with the audience you already had. This prompt tells you whether your sequence is relevant to the audience you want to reach — before you send it. A/B testing is a feedback loop on past sends. This is a relevance audit on future ones. The two are complementary — use this prompt to ground the sequence in verified ICP context first, then use A/B testing to optimize the copy once the signal-based framework is in place.

  • What if I don't have an existing sequence — can I build one from scratch?

    Yes — remove the “MY CURRENT SEQUENCE” section from the prompt and replace it with “I don’t have a sequence yet — build one from scratch based on my ICP and the signals Lusha finds.” The prompt will skip the audit step and go straight to building a signal-grounded sequence from the ICP data Lusha returns. For a more structured approach to building a new sequence from a specific trigger event, the Sequence Writer Skill on Campus is built specifically for that motion.

  • How often should I rerun this optimization?

    Every quarter at minimum — and any time your ICP shifts significantly. Buying signals change. The signals that were most active at Series B SaaS companies three months ago are not necessarily the same ones firing today. A sequence built on stale signal assumptions produces the same generic result as a sequence built on no signals at all. Running this prompt quarterly keeps the sequence grounded in what’s actually happening in your market right now, not what was happening when it was first written.

  • Can I optimize different sequences for different ICPs in the same conversation?

    Yes — run the prompt once for each ICP segment in the same Lusha-enabled conversation. A sequence targeting VP of Sales at Series B SaaS companies will look different from one targeting Head of RevOps at PE-backed services firms, even if the product is the same. The signal profiles Lusha returns for each segment will be different, and the rewritten sequences will reflect that. Keep each ICP optimization as a separate prompt run so the signal context doesn’t bleed between segments.

  • Does this work for sequences targeting contacts in Europe?

    Yes — and the GDPR angle is worth building into the sequence explicitly for European contacts. Lusha is fully GDPR compliant, certified by ePrivacyseal GmbH, and validated by TrustArc. When optimizing a sequence for EMEA contacts, add “Geography: UK / DACH / Benelux / Nordics” to the ICP section and note any compliance-sensitive messaging considerations. Lusha’s European coverage is particularly strong across the UK, Germany, France, the Netherlands, and the Nordics — so the signal data returned for EMEA accounts is as reliable as it is for North American ones.

Related Plays

Ready to run this?

Connect once, run anywhere. Works in Claude, ChatGPT, n8n, Clay, or any agent connected to Lusha.

Get free access Read the Docs