Write the outreach when a target account visits your website

Built by: Lusha
Time to build: 5 min
Difficulty: Easy
Tools: Claude ▪ Lusha
Type: Prompt

A company in your ICP visited your pricing page three times this week. Nobody filled in a form. The visit is a signal — but without a name, a direct dial, and a message that earns a reply, it stays a signal. This prompt takes the visit data, finds the right decision-maker at the visiting company using Lusha’s verified contact database, and writes a first outreach email grounded in the visit context. Specific enough to be relevant. Professional enough not to spook them.

The Lusha Website Visits API returns company-level data only — it identifies which companies are visiting your website, not which individuals. No personal data is returned at the visitor identification stage. Individual contact data is accessed separately using Lusha’s verified B2B contact database. Lusha is fully GDPR compliant. Full privacy documentation at lusha.com/trust-center.

How to start

1

Identify a target visiting company

Run the Find the high-intent visitors in your ICP play first. Pick a High or Medium ICP-fit company from the output with an engagement score above 65. That company is the input for this prompt.

2

Note the pages they visited

Check your web analytics to see which pages the visiting company hit — pricing, case studies, integrations, competitor comparison. The more specific the page context, the more relevant the outreach angle the prompt can build.

3

Paste the prompt and fill in the brackets

Replace the bracketed placeholders with your company details, visit data, and product context. Claude finds the contact, verifies them, and writes the outreach in one pass.

The prompt

Open in Claude Open in ChatGPT 
@Lusha A target account just visited my website.
Find the right decision-maker, verify them,
and write a first outreach email grounded in
the visit signal.

VISITING COMPANY:
Name: [company name]
Domain: [company domain]
Engagement score: [from Play 1 or Play 2 output]
Sessions this week: [number]
Pages visited: [e.g. Pricing, Case studies,
Integrations page]
Days since last visit: [number]

MY TARGET FUNCTION: [e.g. VP of Sales, Head of RevOps]
MY TARGET SENIORITY: [e.g. VP and above]

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

MY COMPANY: [your company name]

Using Lusha, do the following:

1. FIND AND VERIFY THE CONTACT
   Call POST /v3/contacts/decision-makers
   with the company domain and target function.
   Select the most senior relevant contact.
   Call POST /v3/contacts/enrich to verify:
   - Current title and seniority
   - Confirmed in seat
   - Direct dial and business email
   - Tenure in current role
   Flag if the contact is a recent hire
   (under 6 months) — use as additional hook.

2. CHECK FOR ACCOUNT-LEVEL SIGNALS
   Call POST /v3/companies/enrich for the
   visiting company. Return:
   - Industry, employee count, funding stage
   - Any recent funding events or exec moves
   Use the strongest signal as a secondary
   hook if available.

3. WRITE THE OUTREACH EMAIL
   Subject line: under 8 words.
   Do not mention that you saw them
   on your website. Reference the visit
   context indirectly through the angle —
   not "I saw you visited our pricing page."
   Body: under 100 words.
   Paragraph 1: One sentence that shows
   you know something specific about their
   situation — funding event, new hire,
   company size milestone, or the problem
   their industry is dealing with right now.
   Paragraph 2: Connect that context to
   the specific problem your product solves
   for their role. One sentence.
   Paragraph 3: Single low-friction ask.
   15 minutes. Specific time suggestion.

   Do not:
   - Reference the website visit directly
   - Use "just following up"
   - Pitch features
   - Use more than one CTA

4. RETURN
   - Verified contact: name, title,
     direct dial, business email, tenure
   - Subject line
   - Email body
   - One line explaining the angle chosen
     and why it fits this specific contact

What you'll get back

A verified contact with direct dial and business email, plus a ready-to-send outreach email grounded in account context — not the website visit. Here’s what the output looks like:

Website visitor outreach · Lusha verified contact

FieldValue
ContactR.M. — VP of Sales
Status✓ Confirmed in seat · 3 months tenure ⚑ new hire
Business emailr.m@[company].com ✓
Direct dial+1 512 555 ••••
Account signalSeries B closed — $22M — 11 days ago
Subject lineScaling the sales team after Series B
Email bodyCongrats on the Series B. Most new VPs of Sales at this stage spend their first 90 days fixing the data foundation before the SDR team scales — bad contacts kill ramp speed before it starts. We help teams like yours get verified direct dials on every ICP contact before the first dial. Worth 15 minutes this week? Thursday or Friday works on my end.
Angle usedNew VP + Series B combined — stack evaluation window is open, budget just landed, new hire is forming opinions about the data layer before the team scales.

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 data to see live results.

Why use Lusha in Claude

The most important rule in this prompt is what it does not do. It does not say “I saw you visited our pricing page.” That sentence ends conversations before they start. The visit tells you the company is researching. Lusha tells you who to reach and what is happening at their account. The email is built from the account context — the funding event, the new hire, the company milestone — not from the visit itself. The contact receives a message that is relevant to their situation, not a message that reveals they were being tracked.

The two data sources in this prompt work together in a way neither can achieve alone. The Website Visits API tells you which ICP-fit company is actively researching right now. Lusha’s contact database tells you who to reach there, confirms they are still in seat, and returns a direct dial. The account enrichment layer surfaces the strongest signal at the company — funding event, new hire, hiring surge — so the email angle is grounded in something verified and timely, not a generic opener about the category.

A direct dial attached to a high-engagement website visitor is a different kind of outreach opportunity. The company is already aware of you. They have already spent time on your site. The call is not cold in the traditional sense — it is the first human contact in a research process that has already started. Lusha’s 85%+ direct dial accuracy on verified numbers means the rep reaches a person, not a switchboard, when they make that first call.

Lusha is B2B data provider with a native Claude connector which means the visit signal, the contact verification, the account enrichment, and the outreach writing all happen inside one conversation. No exports, no tab-switching, no manual lookup. From anonymous company visit to ready-to-send email with a verified direct dial in one pass.

Lusha data is sourced and used in accordance with Lusha’s Privacy Policy and Terms of Use. Lusha is fully GDPR compliant, certified by ePrivacyseal GmbH, and validated by TrustArc.

FAQ

  • Should I mention the website visit in the email?

    No. The prompt is specifically designed not to reference the visit directly. Saying “I saw you visited our pricing page” signals to the contact that they were being tracked and puts them on the defensive before the conversation starts. The visit tells you the company is researching — but the email angle should come from something verifiable and professional, like a funding event, a new hire, or a company milestone. That is what makes the outreach feel researched rather than surveillance.

  • What if Lusha finds no account-level signals for the visiting company?

    The prompt falls back to firmographic context — company size, industry, funding stage, and the implied problem that companies at this stage typically face. A message built from verified firmographic context is still significantly more relevant than a generic category pitch. If the company has very thin signal coverage, the prompt will note that and build the angle from what is available rather than inventing a signal that isn’t there.

  • How do I know which pages the company visited?

    The Lusha Website Visits API returns high-intent pageview counts but not specific page URLs. For specific page-level data, check your web analytics tool — Google Analytics, Clearbit Reveal, or your CRM’s website tracking. Cross-reference the visiting company domain with your analytics to see exactly which pages they hit. Paste the most relevant page names into the prompt under “Pages visited” and the outreach angle will be calibrated accordingly.

  • Can I run this for every company on my visitor list?

    For the highest-engagement Tier 1 companies, yes — run it individually for each account. For bulk outreach across a larger visitor list, the prompt will become repetitive if run at scale without variation. The better approach for larger lists is to use the <a href=”https://www.lusha.com/campus/plays/claude-prompt-website-visitors-weekly-report/”>Build a weekly website visitor pipeline report</a> play to prioritize which accounts deserve individual outreach, then run this prompt only for the top-priority accounts.

  • Is it legal to reach out to contacts identified through website visitor data?

    Yes. The outreach uses Lusha’s verified B2B contact database — not the website visit data — to identify and contact individuals. The website visit is used as a prioritisation signal to determine which companies are worth looking up. The contact details come from Lusha’s B2B database under legitimate interest provisions of GDPR, the same legal basis that governs all B2B prospecting in Europe. Lusha is fully GDPR compliant, certified by ePrivacyseal GmbH, and validated by TrustArc. Full documentation at lusha.com/trust-center.

Related Prompts

Ready to run this?

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

Get free access Read the Docs