Customer & sales

Lead scoring

See whether a lead fits your product, how interested they are, and what you still need to ask.

For founders and sales teams

Jev AI playground

Checking availability…

Text

289 / 50,000

Try different inputs · Lead scoring

Load an input to edit it. Tokens are used only when you run it.

Normal input

A strong fit can have evaluation interest without purchase readiness.

Ambiguous input

Variable volume can straddle the fit threshold while intent stays tentative.

Missing information

Do not infer team type, message volume, budget, or a buying timeline.

Questions3

choiceCompare the inquiry with the supplied target customer. Use insufficient_information when the essential customer or volume facts are absent.⌄

Question

Answer options

scoreRate demonstrated buying intent separately from fit. Do not treat company size as intent.⌄

Question

Scale points, from lowest to highest

Yes / NoAre budget or implementation requirements still unspecified?⌄

Question

Advanced: edit JSON

Edit or paste a question configuration.

[
  {
    "id": "fit",
    "type": "choice",
    "instructions": "Compare the inquiry with the supplied target customer. Use insufficient_information when the essential customer or volume facts are absent.",
    "options": [
      {
        "label": "strong_match",
        "description": "The inquiry meets the stated customer type and usage requirements."
      },
      {
        "label": "possible_match",
        "description": "Some requirements match, but a relevant requirement is uncertain."
      },
      {
        "label": "poor_match",
        "description": "A stated fact conflicts with an essential requirement."
      },
      {
        "label": "insufficient_information",
        "description": "Essential facts are absent, so fit cannot be assessed."
      }
    ]
  },
  {
    "id": "buying_intent",
    "type": "score",
    "instructions": "Rate demonstrated buying intent separately from fit. Do not treat company size as intent.",
    "options": [
      {
        "label": "0",
        "description": "No interest in evaluating or buying is expressed"
      },
      {
        "label": "1",
        "description": "General curiosity or a request for information"
      },
      {
        "label": "2",
        "description": "An evaluation request with a stated use case or timeline"
      },
      {
        "label": "3",
        "description": "A concrete purchasing request with an agreed scope and budget"
      }
    ]
  },
  {
    "id": "missing_information",
    "type": "noul",
    "instructions": "Are budget or implementation requirements still unspecified?",
    "options": []
  }
]

Runs use input tokens and are saved to your account.

Results

Your answers will appear here.

Add your text and questions, then run Jev.

Probabilities express model confidence, not a guarantee of correctness.

Set up this template

Find promising inquiries and decide what to ask next. A good fit doesn’t always mean someone is ready to buy.

What to provide

Your target customer criteria and the original inquiry, including any known volume, timing, budget, and integration needs.

Describe the target customer and product requirements.
Paste the inquiry with its stated timing and constraints.
Compare customer fit with buying intent before choosing a follow-up.

Outputs and rules

fit · choice

Match against the defined target customer, not likelihood of purchase.

Compare the inquiry with the supplied target customer. Use insufficient_information when the essential customer or volume facts are absent.

strong_match: The inquiry meets the stated customer type and usage requirements.
possible_match: Some requirements match, but a relevant requirement is uncertain.
poor_match: A stated fact conflicts with an essential requirement.
insufficient_information: Essential facts are absent, so fit cannot be assessed.

buying_intent · score

A 0–3 scale for evidence of an evaluation or purchase.

Rate demonstrated buying intent separately from fit. Do not treat company size as intent.

0: No interest in evaluating or buying is expressed
1: General curiosity or a request for information
2: An evaluation request with a stated use case or timeline
3: A concrete purchasing request with an agreed scope and budget

missing_information · Yes / No

Whether qualification requires more budget or implementation detail.

Are budget or implementation requirements still unspecified?

Try different inputs

Normal input

A strong fit can have evaluation interest without purchase readiness.

Our product: a feedback analysis API for software teams with at least 1,000 comments a month. Inquiry: We are a 12-person SaaS team handling 4,000 feedback messages a month. We want to tag them inside our existing dashboard next quarter. Could we try your API? We haven’t set a budget yet.

Ambiguous input

Variable volume can straddle the fit threshold while intent stays tentative.

Our product: a feedback analysis API for software teams with at least 1,000 comments a month. Inquiry: We handle around 900–1,100 messages a month depending on the season. We are comparing several tools for a possible project.

Missing information

Do not infer team type, message volume, budget, or a buying timeline.

Our product: a feedback analysis API for software teams with at least 1,000 comments a month. Inquiry: Interested. Please send pricing.

Use the result

Send a relevant trial example to an evaluation-stage lead. Ask for the missing requirements rather than automatically marking it sales-qualified.

Limits to keep in mind

Scores use only the details provided. A missing budget or timeline stays unknown, and a high score doesn’t guarantee a sale.

Jev AI playground

Your answers will appear here.

Set up this template

What to provide

Outputs and rules

Try different inputs

Use the result

Limits to keep in mind

Related tasks