⟜
Trigger-to-sequence builder
OutboundTurns one buying trigger into a complete hyper-personalized multi-touch outbound sequence — 3 emails, a LinkedIn note, and a call opener — each tied to the trigger and a distinct compliance angle, ready to load into Salesloft/Outreach.
The routing recipe
Job typeCreative & marketingPolicyBalanced
routes to
Llama 3.1 Nemotron Ultra 253B v1 nvidia
nvidia:nvidia/llama-3.1-nemotron-ultra-253b-v1
86.3
match score
90.3
task fit
100
cost
53.4
speed
Why this model from benchmarks & capabilities
- "Creative & marketing" leans hardest on creative; Llama 3.1 Nemotron Ultra 253B v1 scores 87/100 there — top-1 of 40 chat models.
- Strength on this class of work shows up on EQ-Bench, LMArena (human preference), where NVIDIA models are competitive.
- Cost: runs on NVIDIA free credits / self-hostable NIM — effectively $0 marginal. Speed: ~45 tok/s (estimated).
- Chosen over Qwen3 Coder 480B-A35B Instruct for higher task-fit (90.3 vs 86.7).
| Capability the job needs | Weight | Llama 3.1 Nemotron Ultra 253B v1 | Catalog rank |
|---|---|---|---|
| creative | 1.00 | #1 of 40 | |
| instruction | 0.70 | #1 of 40 | |
| knowledge | 0.50 | #7 of 40 |
Relevant benchmarksEQ-Bench LMArena (human preference)
EconomicsCost: runs on NVIDIA free credits / self-hostable NIM — effectively $0 marginal.
Speed: ~45 tok/s (estimated). vs runner-upChosen over Qwen3 Coder 480B-A35B Instruct for higher task-fit (90.3 vs 86.7). (Qwen3 Coder 480B-A35B Instruct, score 86)
Speed: ~45 tok/s (estimated). vs runner-upChosen over Qwen3 Coder 480B-A35B Instruct for higher task-fit (90.3 vs 86.7). (Qwen3 Coder 480B-A35B Instruct, score 86)
Example result
Sample input ▾
Prospect: Dana Okafor, Head of Security, Lumenpay (140-emp fintech). Trigger: Posted a job 4 days ago for a 'Compliance Manager to drive SOC 2 Type II and prepare for PCI DSS', and a press item says they just signed their first bank partner.
TOUCH 1 — Email · Day 1
Subject: the bank partner + PCI clock
Dana — saw Lumenpay landed its first bank partner and is hiring a Compliance Manager for SOC 2 Type II + PCI. That sequencing is the hard part: bank partners almost always demand SOC 2 Type II evidence before go-live, and PCI lands right behind it. icompaas maps your existing AWS/Okta/GitHub stack to both frameworks and auto-collects evidence, so the new hire inherits a running program instead of a blank Confluence page. Worth a 20-min look before the audit window sets?
TOUCH 2 — LinkedIn note · Day 3
Congrats on the first bank partner, Dana. Most fintechs hit a wall when the partner's security team asks for SOC 2 Type II evidence mid-integration. Happy to share how teams your size get ahead of it — connecting either way.
TOUCH 3 — Email · Day 5 (angle: questionnaire velocity)
Subject: when the bank's security team sends the questionnaire
Quick follow-up, Dana. The bank partnership won't stall on your product — it'll stall on their 200-line security questionnaire. icompaas pre-builds a Trust Center + answer library so your team returns those in days, not the 4-6 weeks it usually takes a 140-person team. Want the questionnaire-acceleration walkthrough?
TOUCH 4 — Call opener · Day 8 (spoken)
Hi Dana, it's Sam from icompaas — I'll be quick. You're hiring for SOC 2 Type II and PCI right as the first bank partner comes online; I called because that exact overlap is where fintechs lose a quarter. Is locking the compliance timeline before the new Compliance Manager starts on your radar?
TOUCH 5 — Email · Day 12 (break-up)
Subject: closing the loop
Dana — I'll stop here so I'm not crowding your inbox. If SOC 2 Type II and PCI for the bank partnership land on someone else's plate, I'd be glad to be pointed their way. And if timing's just early, reply 'Q4' and I'll circle back then.
Why this works: every touch is anchored to the same dual trigger (bank partner + the SOC 2/PCI hire) but rotates the angle — sequencing risk → questionnaire velocity → timeline-before-hire → graceful exit — so it reads like a person who did the homework, not a cadence.
Test it on your own data