Find pipeline accounts with no marketing coverage

Images on this page are for illustrative purposes only. Example outputs in this play are illustrative — the structure, fields, and format reflect real Lusha, Gmail, and Slack connector output, but were not pulled from a live session. Run the prompt with your own pipeline data and connectors to see live results. Personal details in any live examples are masked or abbreviated for privacy.

A pipeline account with no marketing coverage is a deal where sales is working alone — no content sent, no ads running, no multi-thread outreach, no one at the account hearing from the company except the rep. This Claude prompt checks every active pipeline account against Gmail for any marketing email history, maps additional verified contacts at each account via Lusha that marketing could engage, and returns a prioritized coverage action list sorted by ACV — posted to Slack before the next marketing and sales planning meeting.

The prompt

<context>
I want to find every account in active pipeline where marketing has never been involved — no email sent, no campaign contact, no known marketing touchpoint. These are accounts sales is working alone, and marketing could be supporting with content, ads, or multi-thread outreach. I also want to find any pipeline account where the only contact is a single rep-to-rep thread — no marketing coverage at all.

My pipeline:
- Active pipeline accounts: [PASTE COMPANY NAMES, DEAL STAGE, ACV, PRIMARY CONTACT — one per line]
- What we sell: [PRODUCT / SOLUTION]
- Marketing email domain: [YOUR DOMAIN — for Gmail send history check]
- Marketing Slack channel: [CHANNEL NAME OR "skip"]
</context>

<task>
1. For each pipeline account, search Gmail for any marketing or campaign email history:
   - Has anyone from a marketing email address sent to this company domain?
   - Has the account received any campaign emails, newsletters, or event invites?
   - Has anyone other than the assigned sales rep been in contact with this account?
   - Last marketing touch date — if any

2. Use Lusha to map the full contact landscape at each account:
   - Validate the primary sales contact — still at company, title current
   - Find any additional verified contacts in the buying function not yet in the sales thread
   - Check for any account signal in the last 30 days

3. Categorise each pipeline account:
   - NO MARKETING COVERAGE: no marketing email ever sent to this domain
   - STALE MARKETING COVERAGE: last marketing touch was more than 90 days ago
   - SINGLE-THREADED: sales has one contact, marketing has no additional contacts at the account
   - ACTIVE COVERAGE: marketing has been in contact within the last 90 days — no action needed

4. For every NO MARKETING COVERAGE and STALE account, build a coverage recommendation:
   - What marketing can do: content send, paid retargeting, event invite, multi-thread outreach
   - Which additional contacts Lusha found that marketing could engage
   - Deal stage and ACV — so marketing can prioritise by revenue impact

5. Return:
   - Full pipeline coverage audit: account, deal stage, ACV, last marketing touch, category
   - Priority list for marketing action — sorted by ACV, NO COVERAGE first
   - Additional Lusha contacts per account marketing could engage
   - If Slack channel specified: post coverage gap summary to marketing channel
   - Summary: X accounts with no marketing coverage, X stale, X single-threaded, X active
</task>

<constraints>
- ACTIVE COVERAGE accounts need no action — don't pad the output with accounts that are fine.
- Priority list must be sorted by ACV — marketing should support the biggest deals first.
- Additional contacts must be Lusha-verified — not guessed.
- Coverage recommendation must be specific: not "run ads" but which channel and what message
  angle based on deal stage.
</constraints>

What you'll get back

The situation: A marketing manager runs this audit before the quarterly sales and marketing alignment meeting. Six active pipeline accounts, various deal stages.


Pipeline coverage audit

AccountStageACVLast marketing touchCategory
Dunmore AnalyticsProposal$72KNever❌ NO COVERAGE
Ashford PlatformsNegotiation$95KNever❌ NO COVERAGE
Crestline SoftwareDiscovery$60K112 days ago⚠ STALE
Briarway SaaSDiscovery$50KNever❌ NO COVERAGE
Greenway CloudProposal$45K34 days ago✓ ACTIVE
Halcyon DataDiscovery$38KNever❌ NO COVERAGE

Priority action list — sorted by ACV


1. Ashford Platforms · Negotiation · $95K · NO COVERAGE

Contact validated: D.R., Head of Sales Strategy & Ops ✓ Additional Lusha contacts: M.L., Head of Sales Operations ✓ · CFO not yet identified Account signal: No signal

This deal is at Negotiation stage and marketing has never touched the domain. At $95K, it’s the highest-value uncovered account.

Coverage recommendation:

  • Multi-thread: M.L. is verified and not in the sales thread — marketing can send a relevant case study to M.L. directly without crossing the AE’s primary relationship with D.R.
  • Content: Send the mid-market SaaS data quality case study to D.R. as a “thought you might find this useful” touchpoint from marketing — provides social proof at a critical stage without interrupting the negotiation.
  • Do not run paid retargeting during active negotiation — signals uncertainty.

2. Dunmore Analytics · Proposal · $72K · NO COVERAGE

Contact validated: T.K., VP of Sales ✓ Additional Lusha contacts: VP of Revenue Operations — verified separate contact available Account signal: Series B closed 18 days ago

Coverage recommendation:

  • Paid: Series B companies actively research vendors. Run LinkedIn paid to the Dunmore domain targeting RevOps and Sales titles — reinforce the brand while the proposal is under review.
  • Multi-thread: VP RevOps is verified and separate from T.K.’s thread. Marketing can engage with a funding congratulations + relevant content send.

3. Crestline Software · Discovery · $60K · STALE (112 days)

Contact validated: R.V., VP Revenue Operations ✓ Account signal: Hiring surge +22% in the last 30 days

Coverage recommendation:

  • Re-engage: last marketing touch was 112 days ago — the hiring surge is a fresh reason to reach back out. Send an event invite or relevant content referencing the headcount growth.
  • Timing: hiring surge makes this a NOW window. Don’t wait for the next newsletter cycle.

4. Briarway SaaS · Discovery · $50K · NO COVERAGE P.O., VP of Sales ✓ · No signal · No additional contacts found above VP floor Coverage recommendation: Add to next event invite batch. No signal — no urgency.

5. Halcyon Data · Discovery · $38K · NO COVERAGE S.P., VP RevOps ✓ · No signal · Secondary contact available via Lusha Coverage recommendation: Content send from marketing. Lowest ACV in the audit — sequence after higher-priority accounts.


No action needed: Greenway Cloud — active marketing coverage within 90 days ✓


Slack summary posted to #marketing

📊 Pipeline coverage audit — 4 accounts with no marketing coverage · 1 stale · 1 active Highest priority: Ashford Platforms ($95K, Negotiation) and Dunmore Analytics ($72K, Proposal) — both have verified additional contacts marketing can engage now.

Summary: 4 no coverage · 1 stale · 0 single-threaded · 1 active

Illustrative example — fictional company names used. Run with your own pipeline data to see live results.

Built by: Lusha
Time to build: 4 min
Difficulty: Easy
Tools: Claude, Gmail, Lusha, Slack
Type: Prompt

Why use Lusha in Claude

Lusha in Claude connects the sales pipeline to the marketing contact map and the email send history in one pass — a connection that almost never exists in practice because sales lives in the CRM and marketing lives in the email platform and neither looks at the other’s data. The Ashford finding is the critical one: a $95K deal at Negotiation stage that marketing has never touched. M.L. is a verified second contact in the buying function who marketing can engage with a case study send without disrupting D.R.’s negotiation thread. That’s a specific, actionable, zero-risk marketing touchpoint on the highest-value deal in the pipeline. Without the Lusha contact map, marketing doesn’t know M.L. exists. Without the Gmail check, marketing doesn’t know the domain has never been touched.

Data drawn from 300M+ verified contacts under GDPR, CCPA, SOC 2, ISO 27701, ISO 31700, and TRUSTe.

FAQ

  • How does the prompt know what counts as a marketing email vs a sales email?

    The check uses the marketing email domain specified in the prompt — any email sent from that domain to the company’s domain counts as a marketing touch. Sales emails sent from the rep’s address are not counted as marketing coverage. If the company uses a shared domain for both sales and marketing, add a note to distinguish by sender name or email prefix.

  • What if the same person is both the sales contact and has received marketing emails?

    That counts as ACTIVE COVERAGE for that contact but may still be SINGLE-THREADED if no other person at the account has been engaged. The single-threaded flag captures deals where only one person has been reached regardless of channel.

  • Should marketing engage pipeline accounts directly without telling the sales rep?

    The coverage recommendation always specifies which contacts marketing can engage and which channels to use. For accounts in active negotiation — like Ashford at $95K — the recommendation explicitly avoids paid retargeting that could signal uncertainty. Any direct outreach to a contact in the sales rep’s active thread should be coordinated with the rep first.

  • How often should this audit run?

    Monthly before the sales and marketing alignment meeting. The coverage picture changes as new pipeline is created and as marketing campaigns run — a monthly cadence catches gaps before close rates are affected.

  • How is this different from the audit multi-thread coverage play?

    The multi-thread coverage play is a sales play — it audits whether the rep has enough contacts in a deal and recommends who to add to the thread. This play is a marketing play — it audits whether marketing has been involved at all and recommends how marketing can support active pipeline. Different owner, different output, complementary use.

Ready to run this?

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