Jev decision module for an AI sales outreach pipeline
A leaked Jev setup splits sales outreach into brief, source, qualify and human-gate steps, with every send waiting for approval.
WHOEVER LEAKED THIS JEV DECISION MODULE SHOULD BE RUNNING YOUR GTM I thought spinning up an AI sales op meant a Zapier chain, 300 cold emails a day, and a block list by week two. Apparently not. This module's setup is much more interesting: → BRIEF locks the goal to $2,000/mo across 14 days with opus-5.5 on delegate mode, no scope creep, no "while you're at it" → SOURCES scopes the whole run to one city and one niche (Austin, dental), 248 records max, no vertical mixing on retry → KB.INDEX loads prices, policies and 48 FAQs into a 1,536-dim vector DB at $25/mo, 0.94 recall, before a single outreach fires → QUALIFY filters 272 chats down to 54 leads at a 1-in-5 rate, writes a typed lead.json (name, need, budget), no "maybe interested" → HUMAN GATE compares p(close) against 0.85, drafts the send above, asks you below, but every send still waits for your yes, flags 7 drafts that tried to go out without a sourced price so you get: Briefs locked. Sources scoped. Leads typed. Sends gated. the interesting part isn't automating sales harder. it's giving every send a gate the agent can't fire past without you. Instead of a cold-email chain burning your domain by Tuesday, you run 14 days on $0 infra, $25/mo vector DB, 1 of 4 clients closed at $500/mo modeled, and the gate stops every send that isn't sourced. Lock the brief. Scope the source. Gate the send.
This post quotes another post: “Long read: how to build a Jev-powered agent stack”