# Website visitor to buying committee to first-touch drafts

Source: https://mcpforgtm.com/recipes/website-visitors-buying-committee (StackMCP, independent directory of official MCP servers)

## Goal

SDRs who want to turn this week's website visitors into a short list of likely buyers and first-touch drafts, without creating records they haven't checked. Lusha's contact search can be swapped for ZoomInfo, Cognism or Apollo, and HubSpot for Salesforce, Attio or Pipedrive.

## Connected tools

- Lusha: https://mcp.lusha.com (setup: https://mcpforgtm.com/tools/lusha)
- HubSpot: https://mcp.hubspot.com (setup: https://mcpforgtm.com/tools/hubspot)

## Guardrails

- Check HubSpot before searching Lusha. Skip customers and accounts owned by another rep.
- Tell me how many Lusha searches or enrichments a step will run, and run it only after I approve. Find at most 5 people per account.
- Write emails as text only. Never send anything.
- Never mention the website visit or the pages viewed in a draft.
- Don't create HubSpot records or export from Lusha unless I approve it.

## Steps

1. Check my Lusha account usage, then show me the companies that visited our website in the last {7} days from Lusha website visitors, with visit counts and pages if available. Tell me first if this step uses credits.
2. Check each visiting company in HubSpot: does the company exist, who owns it, are there open deals, and which contacts do we already have. Drop customers and accounts owned by another rep, and show me a table. Don't change anything.
3. For the {5} accounts I pick, search Lusha for 3–5 people per account with titles like {titles}, only after I approve it. Show name, title and whether they're already a HubSpot contact.
4. Draft one first-touch email per person as text, under 90 words, about a problem their role usually has. Don't mention the website visit. Don't send anything, and create contacts in HubSpot only after I approve it.

## Expected output

Buying committee and first-touch drafts for one visiting account (text only). Example (all names fictional):

```
Visiting account: Mossgate Labs (fictional), 4 visits this week, pricing and integrations pages
HubSpot: company exists, no owner, no open deals, 1 old contact (left the company)

Likely buying committee (from Lusha, 4 matches):
| Name | Title | In HubSpot? |
|---|---|---|
| Priya Raman | VP Sales | No |
| Sam Whitlock | Head of Revenue Operations | No |
| Jordan Ellery | Sales Enablement Lead | No |
| Tomas Rennick | IT Director | No |

Draft 1 of 4 (not sent):
To: priya.raman@mossgate.example
Subject: Ramp time for new reps at Mossgate

Hi Priya,
Teams growing their sales org often find new reps take a quarter to get productive. We help sales leaders cut that by giving reps one place for account research and call prep. Would a 20-minute look be useful this month, or is this not a priority right now?
Jordan

Lusha matches used: 4. No contacts created in HubSpot, nothing exported.
Reply 'create 1, 2' to add those contacts to HubSpot.
```

## Watch for

- Visitors who aren't buyers: Job seekers, partners and your own customers visit too. Ask for the pages and the visit count, drop accounts that only viewed careers or support pages, and check HubSpot for existing customers before searching for people.
- Duplicate contacts: A person may already be in HubSpot under a personal email or an old title. Search HubSpot by name and company as well as email, and show possible matches before you approve any new contact.
- The wrong people on the committee: Broad title searches return interns and adjacent teams. Give 3–5 exact titles or seniorities, and drop anyone whose title doesn't match before you draft.
- Drafts that feel like surveillance: 'I saw you on our pricing page' puts people off. Tell it to never mention the visit or the pages viewed, and read each draft for it before you use it.