Jev workflow cuts AI support costs by 90%
TypeSafe CEO Diogo Almeida shared a Jev support workflow that checks saved results first, then routes each ticket to an approved reply, an Opus investigation, or human review, logging every decision.
THIS IS F*CKING INSANE Diogo Almeida, CEO of TypeSafe AI, just shared a Jev workflow that cuts AI support costs by 90%. pair it with Opus 5.5 and stop overpaying for routine tickets time required: 1 minute action: copy and paste into your AI agent the budget killer is sending every ticket to the strongest model, then paying again when it retries without knowing what failed discovery before code: have the agent ask 7 questions about your support process, approved answers, escalation rules, and what counts as a resolved ticket Jev routing: check saved results first, then decide whether to use an approved response, launch an Opus investigation, or request human review decision log: record the route, the reason, and the outcome. see which calls were useful and which tickets the filter wrongly rejected targeted fixes: send Opus the failed check and relevant evidence. one correction instead of another full run with the same instructions an article below takes this further: saved results, fewer retries, and budget calculations for a workflow targeting 20x efficiency ↓
This post quotes another post: x.com/0xnineinch/status/2108604801411879139