Replies to an outbound campaign for a DORA compliance platform. Jev answers eleven fixed questions about each reply; rules in code turn the answers into a route. All names, companies and replies are invented.
| Via | From | Reply | Route |
|---|
Select a reply.
Each reply carries a hand-written label: the category and the route a good SDR would give it. The numbers below compare the routing against those labels. In replay mode they only show how the rules behave; in live mode they are the measurement that decides the pilot.
Public benchmarks fill the model. Replace the assumptions with your own numbers; the pilot's first week is for exactly that.
The hours saved pay for the build, not much more. The case is speed and certainty: every positive reply reaches its owner within minutes, every opt-out is honoured the same second, and nothing waits for someone to open the inbox. HBR's audit of inbound leads put the average first response at 42 hours and found firms that responded within an hour were about seven times as likely to qualify the lead. That study is about inbound forms, not outbound replies, so treat it as direction, not as your number. The pilot measures your own.
At agency or platform scale the arithmetic changes: 20 clients on the same volumes mean about 6,600 replies a month, 330 hours of triage and still under $1 of Jev a month. That is the case for building it into a RevOps product rather than running it per team.
Put jev_reply_server.py next to this file, set TYPESAFE_API_KEY as an environment variable (never in the page), run python jev_reply_server.py and open http://127.0.0.1:8788. The page detects the server and switches to live mode. The key stays on the server; the page only sends state and questions.
Jev is a decision model by TypeSafe: it returns typed answers with probabilities, never text. Price $0.042 per million input tokens, output free; most calls return in about 100 ms (TypeSafe documentation, September 2026).