JevMade Sign in
← Back to guides

JevMade field notes / Worked recipe

Show why a sales enquiry receives its priority

This recipe rates fit, buying influence, need, timing, and budget separately, then combines them with weights the sales team can inspect.

Original by Jeroen Erne / NexibeoClassification

Listen to this guide

JevMade’s plain-English explanation

0:00 /

Our summary

A sales team may want to contact some enquiries before others, but one unexplained score is hard to challenge. This recipe breaks the judgment into several questions about the company, the contact's influence, their needs, timing, and available budget.

Jev rates each part against a description of the intended customer. The program puts the ratings onto comparable scales and combines them using chosen weights. It also applies a firm rule: someone outside the customer profile cannot receive the highest priorities simply by sounding urgent.

The example uses a fictional business and a small labelled sample, with several debatable outcomes. Its priorities are not universal sales rules. Teams need to check the separate ratings, adjust their own weights, and verify whether the resulting order actually helps their work.

Key takeaways

  1. Keep the parts of a priority score visible.
  2. Apply firm eligibility rules outside the AI question.
  3. Review disagreements with the people who use the ranking.

Contact details, enquiry messages, and the intended-customer description go to Jev. Minimize and approve any personal or confidential information before using real enquiries.

GitHub cookbook

Read the original guide Opens the author’s site in a new tab.

Keep this for later

Sign in to bookmark experiments, guides and videos, and keep notes only you can see.

Continue to sign in

We’ll bring you back to this listing.