Jev deal activity signal

Classify what an account event means for an open deal

Give the open opportunity and one account event. Compare concrete progress, a competitor evaluation, sponsor departure or pause with routine activity under the stated rule.

deal activity signalLive API
Try an example

An alternative is actively being evaluated.

Source: API-collected workflow inspiration; original demonstration below

Source and example scope

This original text demonstration adapts a decision in a repository linked by the cited X post. The examples and explicit uncertainty outcomes are ours. The post is a directory reference, not proof that its author built every linked project. No third-party benchmark, business outcome or external action is reproduced.

Classify the event for the open deal: Competitor for active evaluation of an alternative; Escalation for an unresolved serious support issue; Championexit when the named internal sponsor leaves; Stall for an explicit pause; Progress for a concrete forward step; Routine for ordinary activity.

Decision rules and labels
CompetitorEscalationChampionexitStallProgressRoutineUnclear
A real response from the Jev API

Edit any input to explore a different decision. No request is sent until you run it.

Your next decision

Not run yet

Choose an example or write your own input, then run it to see the ranked choices.

Results are not stored by this site. Your submitted text is processed by the API provider.

The decision

What the decision checks

A CRM event is useful only in context. The same departure matters differently when the person is a named internal sponsor, an unrelated employee or someone moving between offices. The input must establish that relationship.

This classification records the meaning of one event. It does not predict a win, calculate a risk score or count activities over a time window. Dates, event aggregation and any CRM changes belong in code and an authorized review process.

This original text demonstration adapts a decision in a repository linked by the cited X post. The examples and explicit uncertainty outcomes are ours. The post is a directory reference, not proof that its author built every linked project. No third-party benchmark, business outcome or external action is reproduced.

Illustration of routing a message into one of several label groups
Illustration of the decision flow.
How it works

Try the example in four steps

Use the sample to understand the rule, then test your own input for open-deal activity.

  1. Illustration of adding the text or evidence for a decision

    Add the information to check

    Give the open opportunity and one account event.

  2. Illustration of defining a question and its allowed choices

    Confirm the question and labels

    Open the decision rules and keep the intended distinction between Competitor, Escalation, Championexit, Stall, Progress. Edit the choices only when testing your own rule.

  3. Illustration of sending one input and comparing the returned choices

    Run the decision

    Use a sample first, then try your own input. Compare the selected label with the other returned probabilities.

  4. Illustration of reviewing a result and an uncertain item before using it

    Review the next step

    Review Unclear before using a result. The label is a decision about the supplied information, not an executed action.

Our API test

Recorded API observations

Recorded API observations
Original inputObserved labelLeading probability
Alternative pilotCompetitor100%
Competing offer rejectedProgress100%
Sponsor leavesChampionexit100%
Pause requestedStall100%
Routine downloadRoutine84.0%
No account contextChampionexit42.0%

These are six original synthetic inputs, tested once per request revision. The percentage is the leading option probability, not measured accuracy. Authored expectations and any disagreements remain in the downloadable evidence. 5 of 6 results matched the authored fixture expectations. For No account context, the expectation was Unclear; the observed choice was Championexit.Verified

Understand the results

Open-deal activity: six recorded examples

The downloads contain six original inputs, their expected labels and one recorded API observation per input revision. Disagreements stay visible.

Using the result in your application

The single-request SDK runner uses your private TYPESAFE_API_KEY. The offline consumer reads saved observations, checks request hashes and prints a pending output. It does not call the model or change any external system.

Runnable offline example

Run one sample, then inspect the local packet

View the code example
Single-request replay
npm install @typesafe-ai/sdk@0.6.0
# Set TYPESAFE_API_KEY privately in your shell.
node run-choice-sample.mjs samples.json case-1
python preview_choice_workflow.py samples.json saved-api-results.json
Scope of this demo

Where this decision fits

Useful scope

  • Organizing an open-deal review queue
  • Distinguishing competitor mentions from active evaluation
  • Keeping unsupported activity interpretations unresolved

Outside this demonstration

  • Predicting revenue or win probability
  • Inferring a sponsor from a job title
  • Automatically escalating an account
Example FAQ

Using this example

The input contract and these limits define what the result means.

Does no recent reply mean Stall?

Not in this rule. Supply an explicit pause or add a separately documented policy. Counting silent days is a deterministic step, and silence alone does not establish why a deal stopped.

Can an event contain several signals?

Yes. Split independent events or clarify the dominant event before using a single-label contract. The demo does not turn several risks into a composite score.

Does the leading probability measure accuracy?

It describes the distribution over the supplied choices for this request. These six synthetic examples are functional tests with authored expectations, not a production accuracy benchmark.

Will a result change an external system?

No. The demo displays a label and distribution. The downloadable consumer produces a pending preview packet. Application code and a separate authorization policy would control any real action.

Test a different input

Edit the example above to see how a changed fact affects the decision, or open the Playground for another task.