More Resources
Prompt

Turn one rep’s winning sequence into a team-wide play

Tools: ChatGPT ▪ Claude ▪ Lusha ▪ Outreach ▪ Salesloft

One rep’s sequence is outperforming the team average. Before anyone copies it teamwide, there’s a question worth answering first: is it actually repeatable, or did it work because of something specific to that rep’s accounts? This play checks the signal the sequence is grounded in — funding, hiring surge, exec change — against how many other accounts in the territory show that same signal right now. If the number’s there, it’s a play. If it isn’t, it’s a one-off, and copying it teamwide would just waste the rest of the team’s time.

Typical use case: Before rolling a top rep’s sequence out to the team, confirm the signal it’s grounded in is common enough to be worth repeating.

What is this play?

Scale a Winning Sequence is a Claude prompt that checks whether a rep’s outperforming sequence is grounded in a signal common enough across the territory to templatize, or whether it worked because of something specific to that rep’s book. “Replicate what’s working” only holds up if the thing driving the result shows up more than once.

What Lusha does

Lusha counts how many companies in the stated territory and ICP currently show the same trigger signal the winning sequence is grounded in — funding news, a hiring surge, an executive change — and returns the live list, not just a count, so the template has accounts to run against immediately.

Best for

  • Sales — Get a top rep’s playbook in front of the team with a live account list, not just a talk-track.
  • RevOps — Decide what actually deserves to become a permanent play versus staying a one-off.
  • Sales enablement — Ground team rollout in a real signal count instead of “this seemed to work.”

 

 

Turn this play into action

1

Flag the outperforming sequence

Pull it from Outreach or Salesloft once it’s clearly above team average, and note what signal it was built around.

2

Connect Lusha to Claude

One-time setup at claude.com/connectors/lusha.

3

Run the prompt

Fill in the sequence details, territory, and ICP.

4

Roll out or shelve

SCALE means push the template and account list to the team. LIMITED means the rep keeps it as their own edge.

 

The prompt

Open in Claude Open in ChatGPT 
<context>
One of my reps has a sequence performing well above team average. I want to know if it's worth turning into a team-wide play, or if it's a one-off that only works for that rep's specific accounts.

Rep's outperforming sequence details:
[SEQUENCE NAME, TRIGGER SIGNAL IT'S GROUNDED IN, TARGET SEGMENT/TERRITORY, REPLY RATE OR CONVERSION RATE VS TEAM AVERAGE]

My team's territory: [REGION/TERRITORY]
My team's ICP: [INDUSTRY, COMPANY SIZE]
</context>

<task>
1. Identify the signal the winning sequence is grounded in (e.g. funding, hiring surge, exec change).
2. Use Lusha to count how many other companies in the stated territory and ICP currently show that same signal.
3. Assess reusability:
   - SCALE: signal is common enough across the territory (multiple qualifying accounts right now) — worth templatizing teamwide
   - LIMITED: signal is rare or specific to one account — keep it as that rep's one-off, not a team play
4. If SCALE, return the list of other qualifying accounts right now, so the template has an immediate list to run against.
5. Draft a short rollout note for the team: what signal to watch for, and the sequence structure to use when it fires.
</task>

<constraints>
- Don't recommend scaling a sequence grounded in a signal with fewer than a handful of current matches in the territory.
- Don't invent matches — if Lusha finds none, say so and recommend keeping the sequence as a one-off.
- The rollout note should name the trigger signal explicitly, not describe it vaguely as "when the time is right."
</constraints>

What you'll get back

A sales manager has a rep whose funding-news-triggered sequence is beating team average by a wide margin, working mid-market SaaS accounts in Texas. Before rolling it out, the question is whether that signal shows up often enough elsewhere in the territory to be worth templatizing. This count is real, pulled live from Lusha on August 1, 2026.

Signal check — funding news, mid-market SaaS, Texas

Territory: Texas  |  ICP: Software, 51–200 employees
Trigger signal: financialEventsNews (funding activity)
Current matches: 11 companies right now
Verdict: SCALE — enough live matches to templatize teamwide

CompanyCityEmployees
PxxentAustin173
UxxIQMcKinney179
Txxxey LexxerAustin128
+8 more——

Rollout note drafted for the team: *”Watch for financialEventsNews on mid-market SaaS accounts in Texas. When it fires, run [sequence name] — it’s currently outperforming team average and the signal is showing up on 11 live accounts right now, not just one.”*

Data used

  • Company signal count by type (funding, hiring surge, exec change) and territory
  • Live qualifying account list, not just a count
  • Firmographic filters: industry, size, location

Why it works

“Replicate what’s working” is only useful advice if the thing that made it work shows up more than once. A sequence that outperformed because of one account’s specific situation isn’t a team play, it’s a story. Checking the signal count first means the team spends rollout effort on patterns that are actually still live in the territory, not ones that already closed.

FAQ

  • There’s no universal number — a handful of current matches in the territory is usually the floor. One matching account means the rep got lucky with that specific company, not a repeatable pattern. Set your own threshold based on team size and how often you want to push new plays out.

  • Then this play isn’t the right check. If the sequence worked because of relationship history, timing, or something else specific to that rep, it’s not a signal-driven play and won’t templatize the same way — it stays that rep’s edge, not a team rollout.

  • No, they answer different questions. That play asks “which signals convert once we’ve worked them.” This one asks “before we commit the team to a new play, is the underlying signal common enough to be worth the rollout.” Run that one first to find a promising signal, then this one to check if it scales.

  • The prompt doesn’t check CRM ownership — cross-reference the returned list against your CRM before assigning it out, so the rollout doesn’t create conflicts with existing owners.

  • Whenever a sequence is being considered for team rollout, not on a recurring schedule. The signal count is a decision-point check, not something that needs monitoring like a live prospecting play.

Related Prompts

Ready to run this?

One data connection. Works in Claude, ChatGPT, your CRM, or any agent you build.

Start for free Read the Docs