Buying-committee mapper

◈

Sales

From a deal's emails and notes, map the buying committee: who's engaged, who's missing, the role/power of each persona, and the specific angle and next move to reach the people you're not yet talking to.

The routing recipe

Job typeComplex reasoningPolicyBest qualityConstraintsctx ≥ 128k

routes to

NVIDIA Nemotron 3 Ultra 550B-A55B nvidia

nvidia:nvidia/nemotron-3-ultra-550b-a55b

93.7

match score

96.5

task fit

100

cost

59.5

speed

Why this model from benchmarks & capabilities

"Complex reasoning" leans hardest on reasoning; NVIDIA Nemotron 3 Ultra 550B-A55B scores 100/100 there — top-1 of 40 chat models.
Strength on this class of work shows up on GPQA Diamond, MMLU-Pro, BIG-Bench Hard, where NVIDIA models are competitive.
Cost: runs on NVIDIA free credits / self-hostable NIM — effectively $0 marginal. Speed: ~70 tok/s (estimated).
Chosen over DeepSeek V4 Pro for cheaper & faster.

Capability the job needs	Weight	NVIDIA Nemotron 3 Ultra 550B-A55B	Catalog rank
reasoning	1.00	100	#1 of 40
math	0.60	99	#3 of 40
knowledge	0.50	92	#4 of 40

Relevant benchmarksGPQA Diamond MMLU-Pro BIG-Bench Hard LiveBench (reasoning) EconomicsCost: runs on NVIDIA free credits / self-hostable NIM — effectively $0 marginal.
Speed: ~70 tok/s (estimated). vs runner-upChosen over DeepSeek V4 Pro for cheaper & faster. (DeepSeek V4 Pro, score 91.8)

Example result

Sample input ▾

Deal: Meridian Fintech, displacing Vanta, needs SOC 2 Type II + PCI before a partner bank's Q4 review. Threads/notes: (1) Priya (Security Eng) — ran demo, loves the PCI evidence automation, emailing weekly. (2) Tom (DevOps) — joined one call, asked about AWS integration. (3) Forwarded email mentions 'Rachel in finance will need to approve budget' — Rachel has never been contacted. (4) A note says 'their procurement requires a full vendor security review before any signature.' No procurement or legal contact named anywhere. (5) One email from Priya: 'our CTO Dev is skeptical we need to switch off Vanta.'

1) COMMITTEE MAP • Priya (Security Eng) · Champion / Technical Evaluator · Power M · Engaged · Ran demo, weekly emails, loves PCI automation. • Tom (DevOps) · End User / Technical · Power L · Light-touch · One call, AWS integration question. • Rachel (Finance) · Economic Buyer · Power H · Unengaged · Named in forwarded email as budget approver; never contacted. • Dev (CTO) · Blocker / Technical authority · Power H · Unengaged (negative) · Priya reports he's skeptical about leaving Vanta. • Procurement · (required) · — · Unknown · Note says full vendor security review required before signature. • Legal · (required) · — · Unknown · No one named; DPA/MSA will surface late. 2) MISSING SEATS (most deal-threatening first) • Economic Buyer not engaged — Rachel controls budget and has zero relationship. No path to signature today. • CTO is a detractor, not neutralized — Dev can veto the Vanta switch. • No Procurement contact — their own process requires a vendor security review that takes weeks; not yet started. • No Legal contact — DPA redlines unscheduled. 3) WHO TO REACH NEXT • Rachel (Economic Buyer) · Angle: ROI vs Vanta + cost of missing the bank's Q4 review / PCI exposure · Next move: ask Priya to forward a 1-page ROI + the Q4 deadline; AE requests a 20-min finance intro. • Dev (CTO, detractor) · Angle: not 'switch tools' but 'one control set → SOC 2 + PCI, automated evidence Vanta does manually'; de-risk migration · Next move: AE + SE offer a technical deep-dive; bring a Vanta-displacement migration plan. • Procurement · Angle: iCompaas's own SOC 2 + security package speeds their review · Next move: ask Priya for the procurement contact now; send our trust-center link + security questionnaire pack. 4) THREADING RISK Effectively SINGLE-THREADED through Priya (Power M). Biggest risk: an un-engaged Economic Buyer (Rachel) plus an actively skeptical CTO (Dev) — the two highest-power people are both outside the conversation.

Test it on your own data