Active deals · AEs, CSMs, and founder-led sales

Multithread any deal in one Cowork session.

Scenario: after a call, your buyer mentions that the CISO and CEO will both weigh in. That is useful context, but only if you act on it quickly.

Using Claude + Via, you can pull those stakeholders from the transcript, find warm paths through your team and customer champions, and draft the exact Slack and email messages needed to activate those paths. You review every draft and send the ones you like.

In seconds, you learn your VP Sales worked with the CISO at Stripe, and one of your customers was a YC batchmate of the CEO.

Instead of sending a generic follow-up and hoping your champion forwards it, you now have two warm plays to expand the deal.

Example stack

Via

Granola

Slack

Gmail

Try for free How to run it

An illustrative run. Claude drafts every message for you to review, and nothing is sent on your behalf.

Post-discovery follow-ups, Acme

Find yesterday's Acme discovery call transcript. From the transcript, extract all people the buyer mentioned who may be involved in the evaluation, decision, implementation, approval, or budget process…

Full prompt in Step 3 ↓

May 5

Pulled Acme discovery transcript · 7 stakeholders extracted · 2 with warm paths · 2 drafts ready for review

Pulling the Acme discovery transcript from Granola, extracting stakeholders the buyer mentioned, scoring each via Via for a warm path, then drafting outreach in Slack and Gmail for the ones with a usable path.

Granola: pulled transcript Result Acme discovery, May 4 · 45 min

Via · run_network_query · People + Access Result 7 stakeholders · 2 with warm paths

Claude: drafted a Slack intro request Result 1 message to Sarah Kim

Gmail: drafted intro email Result 1 email to Daniel Sun

Stakeholders ranked · drafts ready for review

Stakeholder	Role in deal	Best warm path	Source	Next action
Priya Shah CISO, Acme	Security gate; must sign off	Sarah Kim Worked at Stripe together	Team Network	Review Slack draft
Marcus Lee CEO, Acme	Exec sponsor for the tier	Daniel Sun YC W21 batchmate	Customer Champion	Review email draft

How to run it

Four steps. One Claude conversation.

Install the connectors, open Cowork, paste the prompt, review the drafts. A runbook, not an article.

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 →
Your call recorder: Granola, Fireflies, Otter, or Zoom. Whichever your team already uses.
Slack: for drafting messages to teammates in your Team Network.
Your email client: Gmail or Outlook, for drafting vouch-note requests to your Customer Champions Network.

Open Claude Cowork.

Multi-tool workflows like this run more reliably in Claude Cowork than in regular chat. It handles the sequential tool calls without losing context and keeps each step visible. Drafts save to Slack or email where those connectors support it, or stay in the chat for you to copy.

Paste this prompt in Cowork.

Replace Acme with the prospect company. The prompt tells Claude to prioritize Team Network paths first, fall back to Customer Champion paths, and draft only. Nothing gets sent automatically. Uncertain matches go into a "Needs Review" section at the bottom for your eyes.

Heads up: this prompt assumes you've set up a Team Network and a Customer Champions Network in Via. You can do that directly from Claude, just ask Via MCP something like: "Create a Customer Champions Network with the following LinkedIn URLs: [paste URLs]." Same pattern for the Team Network.

The multithread prompt pasted into Claude Cowork's composer — The prompt pasted into Cowork's composer. Copy the current version below.

Use my authorized call-recorder connector for the transcript, not Via or chat history. Batch the named people in Via run_network_query using the two authorized network sources below. Inspect Access and open selected-person Pathways for routes. Keep unresolved or incomplete results in Needs Review. Draft messages in the chat unless an authorized messaging connector supports saving drafts. Never substitute sending for drafting. Find yesterday's Acme discovery call transcript. From the transcript, extract all people the buyer mentioned who may be involved in the evaluation, decision, implementation, approval, or budget process. For each person, use Via MCP to find the warmest path through either: - My Team Network - My Customer Champions Network Prioritize Team Network paths first. If no strong Team Network path exists, use the strongest Customer Champion path. Return a table with: - Person mentioned - Their likely role in the deal - Evidence from the call - Best warm path - Network source - Recommended next action Then draft the appropriate outreach: For Team Network paths: Draft a Slack message to the teammate asking them to ping the Acme contact directly. For Customer Champion paths: Draft an email to the connector asking whether they'd be open to sending a short note to the Acme contact. Do not send any messages or emails. Draft only. Put uncertain matches or weak paths in a "Needs Review" section.

Review every draft before you send.

Claude returns every stakeholder the buyer named, the warm path to each, and a draft for each: a Slack to a teammate for Team Network paths, a short vouch-note request email to your champion for Customer Champion paths. Always keep a human in the loop on personalized outreach. The prompt is set up to draft only. Nothing leaves your inbox or Slack until you press send. Two things to do for every draft:

Check for accuracy. Verify the trust signal Via cited (the past job overlap, the YC batch, the investor relationship), the role you're attributing to the stakeholder, the spelling of names. Drafts are starting points, not finished sends. An inaccurate detail in a vouch-note request reads worse than no request at all.
Add the line only you could write. Claude has the transcript, but it doesn't have the side conversations, the body language, the gut read on what your champion will and won't endorse, or your voice. Drop in a detail Claude couldn't have known: something your champion mentioned off the record, a callback to a past exchange that lives only in your DMs, or a phrase the recipient will recognize as you. That's what turns the draft into a message that actually lands.

Multithread any deal in one Cowork session.

Four steps. One Claude conversation.

Pair this with the rest of your motion.

Stop letting deals stall on a single thread.