G2 buyer intent to first-touch drafts: find who's researching your category and write to them
This recipe uses the official G2, Hunter and HubSpot MCP servers, and all of them work in Claude and ChatGPT. Steps that write, send or spend credits wait for your approval.
Who is this for?
SDRs and marketing teams who pay for G2 buyer intent and want those accounts worked within days, not left in a dashboard. G2 can be swapped for Demandbase or 6sense account intent, Hunter for Apollo, Prospeo or Findymail, and HubSpot for Salesforce, Attio or Pipedrive.
What do you get?
Intent accounts, CRM check and one first-touch draft. Sample output: every company and person in it is fictional.
G2 buyer intent, last 7 days: 9 companies. 5 are new to HubSpot. | Company | G2 activity | HubSpot | |---|---|---| | Larkspur Freightworks (fictional) | Viewed our category page and compared us with 2 competitors | No record | | Mossgate Labs (fictional) | Viewed our product page and pricing | Company exists, owner Sam Whitlock, open deal. Skipped | | Tidewell Robotics (fictional) | Read reviews in our category | No record | Contacts found with Hunter after your approval (3 searches used): - Larkspur Freightworks: Dana Okafor, VP Operations, [email protected] (verified) Draft 1 (text only, not sent): Subject: Comparing tools for dispatch reporting? Hi Dana, Teams at freight companies your size often look at us when weekly carrier reporting starts eating a day of someone's time. If that's on your list this quarter, I can show you how Fernhill Software (fictional) cut theirs to an hour. Worth 20 minutes next week? Jordan Nothing has been created in HubSpot or Hunter, and nothing was sent.
How long does it take, and what does it cost?
Estimate About 20–30 minutes for 5 accounts, most of it editing drafts.
Assumptions: One run over 5 new intent accounts, with 2–3 contacts found per account.
- G2: Reads only: buyer intent for your product and category for the period you choose. Credit use not confirmed by G2.
- Hunter: After you approve: one Domain Search or Email Finder call per contact, about 10–15 searches, plus an optional verification each. Some tools use credits. A search uses 1 credit and a verification 0.5 (Free plan figures); Discover company search is free, and saving, updating and deleting leads is free. Other usage counts against the user's Hunter plan. Source: hunter.io, checked 2026-10-16
- HubSpot: Reads only: one company search per intent account to check for an existing record and owner. 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
-
ClaudeChatGPTRead + writeCredits not confirmed
https://mcp.g2.com/mcp -
ClaudeChatGPTClaude CodeCursorCopilotRead + writeSome tools use credits
https://mcp.hunter.io/mcp -
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 G2 without code (Claude, ChatGPT)
- Connect Hunter without code (Claude, ChatGPT)
- Connect HubSpot without code (Claude, ChatGPT)
Developer setup
Auth setup and mcp.json for Claude Code and Cursor
- G2: Sign in with OAuth in your client (run
/mcpin Claude Code). Do it once interactively, and the client stores and refreshes the token. - Hunter: Use OAuth sign-in for interactive use. For headless runs, use an API key in the
X-Api-Keyheader. - HubSpot: Sign in with OAuth in your client (run
/mcpin 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": {
"g2": {
"url": "https://mcp.g2.com/mcp"
},
"hunter": {
"url": "https://mcp.hunter.io/mcp"
// headless alternative: "headers": { "Authorization": "Bearer YOUR_HUNTER_API_KEY" }
},
"hubspot": {
"url": "https://mcp.hubspot.com"
}
}
}
Step-by-step prompts
- Show me G2 buyer intent for {product} and our category over the last {days} days. List each company, its website, and the activity G2 shows for it. Don't guess at activity G2 doesn't show.
- Look up each company in HubSpot by website domain. Mark which have no record, which have a company owner, and which have an open deal. Keep only the companies with no owner. Don't change any records.
- For the companies I pick, plan Hunter Domain Search or Email Finder lookups for 2–3 people with titles like {titles}. Show me the plan and the number of searches. Run them, and verify each email, only after I approve it.
- Write a short first-touch email for each contact, using the topic they researched but not mentioning G2. Show me the drafts as text only. Don't create a sequence or send anything.
Can I run it on a schedule? (optional)
- Run it weekly, so the intent is still fresh when the email lands.
- In a scheduled run, stop after the G2 and HubSpot reads and send yourself the account table. Approve the Hunter searches and drafts by hand, since each search spends credits.
- G2 has no Dynamic Client Registration, so custom or headless clients must register an OAuth app in the G2 Developer Portal first. Claude and ChatGPT can use the directory connector.
Where does this go wrong?
- Emailing an account someone already owns. An intent account may already be a customer or an open deal. Check HubSpot by website domain before any Hunter search, and skip every account that has an owner unless that owner agrees.
- Drafts that sound like surveillance. Opening with 'I saw you were on G2' puts people off. Use the intent to pick the topic, never quote it back to the buyer, and read each draft for that before you approve it.
- Credits spent on the wrong people. Hunter charges per search. Agree the 2–3 job titles per account before searching, show the planned searches with a count, and approve them before any run.
- Emails that bounce. A found email can still be wrong. Run Hunter's Email Verifier on each address, and leave out anything that doesn't come back valid.
Gotchas
- G2 buyer intent needs a G2 subscription with the right entitlements. Market Intelligence data needs an Enterprise package.
- G2's setup notes say to sign in to Claude with the same email you use for your G2 account.
- Hunter sequences can start and send real emails. This recipe doesn't use them; keep it that way unless you approve one on purpose.
- On Claude Team or Enterprise, only workspace Owners can add Hunter's custom connector. In HubSpot, non-admin users need a Super Admin to approve the connector.
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 g2-buyer-intent-outreach.md
New recipe and breakage notes every week
Vendor sites: HubSpot. If we join an affiliate program, these links will be labeled as affiliate links.