Home/Via MCP/The agentic GTM stack
Full stack · Built by GTM engineers, used by every rep

The agentic GTM stack: warm-first outbound in one conversation.

Scenario: your GTM stack already has the pieces: prospecting tool, CRM, email. Connect them through Claude + Via and they become a warm outbound prioritization machine: every ICP-fit company gets scored by warm path, then routed: warm-first to AEs with intro drafts to your connectors, cold-only into a sequence once you approve the list.

Example stack Via Apollo HubSpot Gmail
Try for free How to run it

An illustrative run. Via finds the warm paths; Apollo, HubSpot and Gmail do the prospecting, CRM updates, drafts and enrollment, and nothing is written or enrolled until you approve it.

How to run it

Four steps. One Claude conversation.

Install once, paste the prompt, schedule the whole pipeline weekly.

Install the MCPs in Claude.

Start a 7-day free trial, then add Via in Claude as a custom connector at https://mcp.connectvia.ai/mcp and sign in (the setup guide walks through it), then connect the other three tools this workflow uses.

  • Via: for the warm-path tool calls. Try for free →
  • Apollo: the source of the target list and where the cold-only sequence runs. (Or swap Clay on the prospecting side.)
  • Your CRM: HubSpot or Salesforce. Where the warm-first segment lands for AE outreach.
  • Gmail: where intro request drafts to each connector land for review before send.
Open Claude Cowork.

Multi-tool workflows like this run more reliably in Claude Cowork than in regular chat. It handles the sequential connector calls without losing context and keeps each step visible, so when something downstream breaks (an Apollo contact fails to enroll, a HubSpot field lands in the wrong place) you can see exactly where. It also means you approve the CRM updates and sequence enrollment before they happen.

Paste this prompt.

Replace [define ICP] with your target company filters (e.g. "Series B SaaS companies headquartered in NYC, 50–500 employees") and [define persona] with the titles you want to reach (e.g. "VP Engineering, Head of Engineering, CTO"). Claude pulls in batches of 25, dedupes against HubSpot, scores warm paths through Via, pushes warm-first companies to HubSpot with a Gmail draft to each connector, and finds Apollo contacts at cold-only companies to enroll in an Apollo sequence: one prompt.

Heads up: set up an Apollo sequence named "Q2 cold-only" with the cadence and copy you want before running this. The prompt enrolls cold contacts into it but won't create it for you, and Claude asks you to approve the enrollment list first, because an active sequence starts sending on its own schedule.

Use only connectors I have authorized. Via supplies People or Companies results with Access summaries; open selected-person Pathways for routes. Batch named targets in run_network_query instead of searching per company. Keep unresolved, pending, partial or failed results in Needs Review, never cold-only. Use available, authorized contact details; do not invent email addresses. Show proposed CRM writes and sequence enrollments and ask for approval before applying them. Sequence enrollment can send email. Via itself does not send outreach; Apollo owns sequence sends and Gmail owns draft storage. Run my full Q2 outbound pipeline. Use Apollo to find companies that match this ICP: [define ICP] Use this persona spec to define the right contact at each company: [define persona] Pull companies from Apollo in batches of 25. After each batch, dedupe the companies against HubSpot. Remove any company that already exists in HubSpot based on website/domain. If a match is uncertain, put it in a "Needs Review" section and do not count it toward either final segment. Continue pulling additional Apollo batches until you have reviewed enough net-new companies to produce: - Up to 25 warm-first companies - A separate cold-only segment for ICP-fit companies where no usable warm path exists Stop when either: - You have 25 warm-first companies, or - Apollo has no more results that match the ICP For each net-new company, use Via MCP to determine whether there is a usable warm path through my team's network to a person matching the persona spec. Segment 1: Warm-first Companies with a usable warm path to a relevant reachable person at the company. For each warm-first company, identify: - Reachable target at the company - Reachable target's title/function - Via connector who can help us reach them - Connector's email address - Context of the connector's relationship with the reachable target Prioritize the warm-first segment by: 1. Warm path strength 2. Relevance of the reachable person 3. ICP fit Push the warm-first companies to HubSpot tagged: "Q2 warm-first" For each warm-first company in HubSpot, add the following as custom fields where available: - Via Reachable Target - Via Reachable Target Title - Via Connector - Via Relationship Context If those custom fields do not exist or cannot be updated, add the same information as a HubSpot note on the company record. Then, for each warm-first company, create a Gmail draft to the Via connector requesting a soft intro to the reachable target. If the same connector is the path to multiple companies, batch them into a single draft asking about all of the reachable targets at once. Each Gmail draft should: - Be addressed to the connector's email - Reference the relationship context Via surfaced - Briefly state who I'd like to be introduced to and why - Stay short and friendly, leave the connector room to forward or decline - Save to Gmail drafts for me to review and send (do not auto-send) Segment 2: Cold-only Companies that match the ICP but Via did not find a usable warm path to. For each cold-only company, use Apollo to find up to 2 contacts matching the persona spec. Save them as contacts in my Apollo CRM. Add the new contacts to the Apollo email sequence: "Q2 cold-only" Verify that this existing sequence has 6 touches and no warm-context personalization. Do not edit its configuration. If it differs, stop and ask me to configure it before enrollment. Do not create duplicate companies or contacts. Do not push uncertain matches. Do not tag cold-only accounts as warm-first. Do not tag warm-first accounts as cold-only. Do not enroll warm-first companies in the Apollo sequence. Do not auto-send any Gmail drafts. Return a final report with: - Total Apollo companies reviewed - Total companies excluded because they already existed in HubSpot - Total uncertain matches needing review - Number of companies tagged "Q2 warm-first" in HubSpot - Number of Gmail intro drafts created (and how many connectors they cover) - Number of contacts enrolled in Apollo "Q2 cold-only" sequence - Any ICP filters that may need to be broadened if fewer than 25 warm-first accounts were found
Review two outputs.

One prompt produces two things to review:

  • Gmail intro request drafts: one per connector, waiting in your drafts folder. Review and send when you're ready; nothing auto-sent. The warm-first companies are also tagged "Q2 warm-first" in HubSpot.
  • Apollo cold-only sequence enrollments: after your approval, the Apollo connector adds the selected contacts to "Q2 cold-only". Apollo then sends on that sequence's cadence. Review recipients and schedule before enrollment, not after the first send.
Bonus

Take the pipeline further.

Graduate to Claude Code as the pipeline grows.

This is a lot of integrated pieces (pull → dedupe → score → route → draft → enroll across four MCPs), and at scale, parts will fail: Apollo's people search drops a contact, a Gmail OAuth blips, a sequence rejects a duplicate. In Cowork, every failure is a manual retry. Move to Claude Code and the prompt lives in a repo alongside your other GTM scripts, runs on a weekly schedule, retries failures with real error handling, and leaves a full audit trail when something downstream breaks. It's also where layering in timing, intent, and event signals on top of warm paths stops feeling brittle. Explore warm-outbound signals →

Other Via MCP workflows

Pair this with the rest of your motion.

Outbound
Build a warm outbound list.

The first half of this pipeline as a standalone: pull, score, push to CRM. Start here if outreach plumbing isn't ready yet.

For AEs, SDRs, and founder-led sales →
Active deals
Multithread any deal.

After every prospect call, surface stakeholders the buyer named and queue the right outreach for each.

For AEs, CSMs, and founder-led sales →
Account scoring
Score accounts by warm-path strength.

Score your existing CRM list and write connector context back to each record so reps work the warm slice first.

For AEs, RevOps, and sales leadership →
Get started

Run the whole pipeline in one chat.

Built for teams running multi-tool GTM motions in Claude or ChatGPT. 7-day free trial. No credit card or data sync to get started.

Try for free Back to Via MCP