Recipes / Website visitor to buying committee to first-touch drafts

Website visitor to buying committee to first-touch drafts

This recipe uses the official Lusha and HubSpot MCP servers, and both work in Claude and ChatGPT. Steps that write, send or spend credits wait for your approval.

IntermediateSDRs

Who is this for?

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.

What do you get?

Buying committee and first-touch drafts for one visiting account (text only). Sample output: every company and person in it is 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: [email protected]
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.

How long does it take, and what does it cost?

Estimate About 20–30 minutes for 5 accounts, most of it editing the drafts.

Assumptions: One weekly run over 5 visiting accounts, with up to 5 contact matches per account and up to 10 HubSpot contacts created.

Lusha: One website visitors read, then a contact search for each of 5 accounts. Credits are charged per successful match, so up to about 25. Filter tools and the account usage check are free. Some tools use credits. Lookup/search/enrich tools consume Lusha API credits generally per successful, matched result (failed lookups not charged); *_filters tools and account_usage are free; CRM export charges standard per-record export credits only for records the CRM writes; connecting a CRM is free. Source: docs.lusha.com, checked 2026-10-16
HubSpot: Reads for each visiting account (company, owner, open deals, existing contacts), plus up to 10 contacts created after you approve them. Credit use not confirmed by HubSpot.

Exact credit costs depend on your plan with each vendor. Check the tool pages before a large run.

Which MCP servers does it use?

Every server is confirmed in: ClaudeChatGPT

Lusha Up · auth

ClaudeChatGPTCursorCopilotRead + writeSome tools use credits
https://mcp.lusha.com
HubSpot Up · auth

ClaudeChatGPTRead + writeCredits not confirmedNeeds admin or IT
https://mcp.hubspot.com

How do I set it up in a chat app?

Every server in this recipe is confirmed for Claude and ChatGPT. Connect each one, then paste the prompts below into one conversation.

Connect Lusha without code (Claude, ChatGPT)
Connect HubSpot without code (Claude, ChatGPT)

Developer setup

Auth setup and mcp.json for Claude Code and Cursor

Lusha: Use OAuth sign-in for interactive use. For headless runs, use an API key in the X-Api-Key header.
HubSpot: Sign in with OAuth in your client (run /mcp in Claude Code). Do it once interactively, and the client stores and refreshes the token.

Put this in .mcp.json (Claude Code, project root) or ~/.cursor/mcp.json (Cursor). Swap the example keys for your own, and don't commit real ones. Remove the // comment lines if your client requires strict JSON.

{
  "mcpServers": {
    "lusha": {
      "url": "https://mcp.lusha.com"
    },
    "hubspot": {
      "url": "https://mcp.hubspot.com"
    }
  }
}

Step-by-step prompts

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.
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.
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.
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.

Can I run it on a schedule? (optional)

Run it once or twice a week so you reach visitors while the visit is recent.
In a scheduled run, stop at the committee table and the drafts. Don't run contact searches beyond the cap, and create nothing in HubSpot without your approval.
Ask it to check your Lusha account usage at the start of each run. That check is free.

Where does this go wrong?

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.

Gotchas

Lusha's search and enrich tools charge credits per successful match, and failed lookups aren't charged. A loose 'find everyone' prompt can still add up, so keep the per-account cap.
Lusha can export contacts to your connected CRM, which charges export credits for each record the CRM writes. Keep exports out of this recipe unless you approve them, and create contacts through HubSpot instead.
Lusha's Recommendations tools only work over OAuth. Connections set up with an API key get a 403, and API-key setups need a plan with API access.
HubSpot non-admin users need a Super Admin to approve the connector first.

Download

Get the prompts, guardrails and expected output as one Markdown file. Paste it into a Claude Project or ChatGPT project's instructions, or save it as CLAUDE.md for Claude Code.

Download website-visitors-buying-committee.md

Vendor sites: HubSpot. If we join an affiliate program, these links will be labeled as affiliate links.