Jev’s new System One model dropped and it’s changing GTM agents in a massive way. Jev is an extremely cost effective way to gauge LLM responses, letting us have an intelligent set of eyes sit on top of our existing models monitoring every single generation, and helping us select the best options.
In GTM this can mean leveling up our entire agent stack.
Our email outbounding tool can have Jev sit on top and ensure emails meet both copy guidelines (think subject length, word choice), as well as sales play guidelines i.e. does the generated email speak to the reason we’re reaching out.
There is a massive asymmetry at play here.
Teams using these advanced Jev-based arbiters in their workflows will have dramatically better LLM outputs. Meaning, those teams that adopt this tool in their agents are going to have much more consistent output quality at scale for all their agents be it a lead classifier, an internal knowledge agent, or an outbounding agent.
The only gap here is knowledge. Jev’s low price point combined with open source LLMs can mean ambitious, effective agents without shelling over thousands or tens of thousands of dollars to the top AI labs for state of the art model access.
Putting this into reality, lets be ambitious in today’s post.
We’ll walk through setting up a fully end to end automated agent for sending and replying to a lead list with the goal of booking a meeting.
This’ll be useful for anyone in a GTM related role, whether you’re on a small start up with a tight budget, or a fully VC-backed GTM team.
End to End Meetings Booked Agent
Reaching out to lower tier leads can have questionable ROI, but if we can work them automatically then ROI suddenly doesn’t matter. Any meeting booked from our system is free money.
What we’ll do is use a combination of existing LLMs and Jev to classify leads, generate email outbound, and handle replies to get leads to book a meeting.
The simplest way to do this to start is setting up a new Next.js project. For this build out, we’ll jump straight to code for one big reason -- coding agents. A code-first approach may feel heavy handed, but with Claude Code or similar agents we can use plain English to guide the initial experiment with more flexibility than using a traditional no-code tool.
Leads
We’ve written before on building lead lists with job finders. We’ll use this playbook again for this initiative. Here we’ll do the same thing and use a tool like Sumble or CoreSignal to pull a list of contact emails for companies with job posts connected to our product or service.
Workflows
We’re going to use Vercel Workflows to spin up two core capabilities -- sending an initial email, and responding to replies.
After uploading our list, we’ll use the first workflow to classify, enrich, and send off our initial messages using the Gmail API.
For our second workflow handling replies, we’ll setup a pub/sub on the Gmail API to ping an endpoint on our Next.js app. Our endpoint will find the appropriate lead, and generate a response geared to booking a meeting.
In summary, this is what we’re building towards.

Code
Let’s get tangible and work through some code snippets to build up this agent.



