Sales evaluation with Jev
Reps leave messy notes, emails, and call snippets. The CRM still owns Opportunity stage, quotes, and SLAs. Jev judges the text you provide so code can set a next-motion field or open a human queue. It does not send outreach or update ARR.
This unofficial page is the evaluation slice of the sales motion decisions pack. Intent: apply the Jev (TypeSafe System One) decision model to sales motion decisions evaluation. Primary search language: Sales Jev evaluation. Confirm patterns on docs.typesafe.ai. This site does not sell, issue, or proxy TypeSafe keys. Use a credential you already have from the console or a documented gateway.
Independent angle (cover ≠ clone): CRM-owned objects + Jev-on-notes (next motion, AE-ready, heat) — not a clone of a sales-automation landing page or rival CRM recipe IA.
Sales use-case context
Evaluation for sales motion decisions is a frozen harness, not a vibe check and not an opinion-blog “Jev review.” Labels: next-motion gold, AE-ready gold, and whether a human would have stolen the account. We publish no unofficial accuracy.
Hub: Use cases. Compare, when the other tool is the real job: CRM workflows.
Evaluation inputs
Replay the same contract you ship:
{
"note": { "id": "n-8821", "text": "CFO asked for a Q4 start; legal wants DPA first.", "source": "call" },
"opp": { "stage": "discovery", "arr_band": "50-100k", "days_in_stage": 18 },
"playbook": { "ae_ready": "Budget + timeline + next meeting, or a named blocker." }
}Freeze questions, criteria, and jev-1.13.0. Record the response model.
Decision signals and actions
Score these, not a blog-grade star rating:
- Auto-motion error rate at your floor (not a jev.pro leaderboard)
- False AE accepts / missed legal blocks
- Handoff rate: if everything reviews, the floor is theater
Pair auto-act errors with handoff rate. If the CRM write-back worker never acts, you have not evaluated sales motion decisions — you have evaluated a human queue.
Do not treat a Noul of 0.5 as a “medium” sales motion decisions score — it means yes and no are equally likely. Conjunctions stay in your code.
Guardrails and escalation
Promote a threshold only when the harness says auto-act error ≤ SLA and reviewers still catch the residual. TypeSafe’s confidence-gated examples use a lower bar for recoverable reads than for irreversible actions. Those numbers are illustrations. For sales motion decisions, treat ae_accept as the high bar (reassigning an Opportunity to an AE or issuing a commercial concession). Tune on labels — see offline evaluation.
Evaluation and rollout notes
After any criteria edit, rerun before production. Cookbook lifts you see on TypeSafe pages are vendor claims — re-measure on your sales note / thread snippets. Pin jev-1.13.0 (the versioned id) after you fit thresholds. jev-latest and the marketing line jev-1.13 can move. Log the response model. TypeSafe’s published list price for jev-1.13 is $0.042 per million input tokens (vendor claim — confirm on the models page); output tokens are free on that same page. Unused distractors still bill as input.
Official Python and JavaScript SDKs read TYPESAFE_API_KEY and retry documented 429/529. This site does not sell, issue, or proxy TypeSafe keys. Use a credential you already have from the console or a documented gateway.
Pack map
| Slice | Page |
|---|---|
| Graph and primitives | decision workflow |
What may enter state |
input contracts |
| What to gather first | evidence collection |
| Atomic rules | policy checks |
| Act / review / abstain | confidence thresholds |
| Reviewer payload | human handoff |
| What to persist | audit trail |
| How it breaks | failure modes |
| Labeled replay | you are here |
| Shadow → canary | production rollout |
FAQ
Will jev.pro publish a leaderboard for this use case? No. Measure on your labels. Vendor cookbook figures stay labeled as vendor claims.
What must stay frozen? Questions, criteria, and the pinned model id. Aliases can move.
Where is the rest of the Sales pack? Start with Sales failure modes and Sales production rollout. Cluster hub: Use cases.
Does Jev replace the CRM workflow engine? No. Salesforce-class workflows still own objects and SLAs. Jev labels messy notes so those workflows can fire. See vs CRM workflows.
Can Jev draft the follow-up email in this pack? Not here. Generate elsewhere; keep this call as typed decisions so you can audit next_motion.
What this page does not claim
- No invented win-rate or cycle-time lifts.
- Schema-safe next_motion ≠ the buyer named a real budget.
- Not official TypeSafe documentation.
- Official TypeSafe status, or that jev.pro issues API keys.
- That a schema-constrained answer is automatically factually correct.
Disclaimer
This is an independent unofficial site and is not affiliated with TypeSafe AI; official documentation is available at https://docs.typesafe.ai.
Primary documentation: https://docs.typesafe.ai. Hub: Use cases.
Sources
Public TypeSafe or adjacent documentation only. No private claims.