Workflows

Multi-step agent workflows showing how MCP tools work together for common sales research tasks.

Research a target account

This workflow starts from a product and drills into a specific prospect to understand their pain points and readiness to buy.

1
list_products

Find the product you're selling.

2
list_prospects

Get ranked prospects for that product. Filter by min_deal_score=4 for top-tier targets.

3
get_prospect

Deep-dive on a specific company. Read the findings_summary and recommendation_summary.

4
search_excerpts

Filter evidence by framework_category='Strategic Intent' and min_impact_score=4 for the strongest signals.

Example prompt

Research Travelers Companies (TRV) as a prospect for our Cyber Risk Platform product.
Show me their top strategic intent signals and explain why they're a good fit.

This entire workflow is free — no credits consumed. All four tools are read-only.

Map buying committee, then draft outreach

This workflow extends the research workflow to map the buying committee and generate a personalized message. Note that generate_dealmap and craft_outreach may consume credits.

1
get_prospect

Load the prospect analysis (if not already cached from prior steps).

2
generate_dealmap

Generate the buying committee DealMap. Credits charged only when fresh org-chart data is fetched.

3
get_dealmap

Read the DealMap to see stakeholders and their roles (Economic Buyer, Decision Maker, Champion, etc.).

4
craft_outreach

Draft an email targeting a stakeholder. Use lead_selector: { stakeholder_role: 'Economic Buyer' } or { level: 'c_suite' }.

Example prompt

Map the buying committee at Travelers for our cyber product,
then draft a helpful email to the Economic Buyer.

Credit awareness

This workflow may consume up to 11 credits (10 for fresh DealMap generation + 1 for outreach). If the DealMap is already cached, only 1 credit is consumed for the outreach message.

Use selectors safely in craft_outreach

When using lead_selector, the server resolves the best matching lead from cached results. Here's how to use each selector type safely:

By level (most common)

Picks the top-ranked lead at the specified level:

{ "lead_selector": { "level": "vp" } }

By name and level

Targets a specific person by name. Requires exact match on full_name within the specified level:

{ "lead_selector": { "full_name": "Jane Smith", "level": "c_suite" } }

By node_id

Uses an internal identifier from a previous get_dealmap response. Most precise but least readable:

{ "lead_selector": { "node_id": "abc123" } }

By stakeholder_role

Selects the top-pick stakeholder with a specific buying committee role from the DealMap:

{ "lead_selector": { "stakeholder_role": "Economic Buyer" } }

Fallback behavior

If the selector can't resolve a stakeholder (e.g., no cached stakeholders at the requested level or role), the outreach is still generated but without personalization. Check selected_lead_note in the response for details. Always call generate_dealmap first to ensure the buying committee is mapped.

MCP Workflows | DealSurface Docs