Draft a documented lead scoring model grounded in your CRM's actual conversion history: weighted attributes, clear MQL and SQL thresholds, and a real lead scored as a worked example.
Draft a lead scoring model for [product] using our CRM's closed-won data: weighted attributes on a 100-point scale, MQL and SQL thresholds, and one recent lead scored as a worked example.
An illustrative example. Your output will reflect your own sources, data, and prompts.
I based the weights on the last 12 months of closed-won deals in your connected CRM: 214 conversions. Seniority and pricing-page visits predicted conversion far more strongly than industry or email opens, and the weights reflect that.
The model scores every lead out of 100 points across six attributes. Seniority fit carries the most weight at 25 points, with pricing-page visits and demo or webinar activity at 20 each: those three signals appeared in over 80% of your closed-won deals.
Attribute weights: 100-point scale
Worked example: a lead created Tuesday, scored line by line.
| Attribute | Priya Nair, Ops Director at Meridian Logistics | Points |
|---|---|---|
| Seniority fit | Director-level, operations: exact ICP match | 25 / 25 |
| Pricing-page visit | Visited pricing twice this week | 20 / 20 |
| Demo or webinar | Registered for the webinar but didn't attend | 0 / 20 |
| Company size fit | 240 employees, inside the 100–500 target band | 15 / 15 |
| Industry fit | Adjacent (3PL) rather than core freight | 5 / 10 |
| Email engagement | Opened 4 of the last 6 sends, one click | 6 / 10 |
Priya scores 71, a clear MQL, four points short of SQL. One demo booking or a webinar attendance pushes her past 75, which is exactly what her next nurture email should offer.
Want me to score this week's leads against the model, or test how many would qualify with a 60-point MQL threshold instead?
Lead Scoring Model looks at your CRM's closed-won history to see which attributes actually preceded conversion, then drafts a full scoring model: weighted attributes on a 100-point scale, MQL and SQL thresholds set at real conversion breakpoints, and a worked example so everyone can see the math.
Point Joy at your connected CRM or add a lead-history file to the Knowledge Center. What matters is which leads converted and what you knew about them beforehand.
Name the product or segment and ask for a 100-point model with MQL and SQL thresholds. Add house rules up front ("competitors always score zero") if you have them.
Get the attribute weights as a chart, the thresholds with the conversion evidence behind them, and a recent lead scored line by line so the model is concrete, not abstract.
Copy the documented model into your marketing automation platform's scoring rules and your team wiki, and use the worked example in the sales-marketing handoff conversation.
Save this ask as a custom command on the assistant your team already uses, then customize it with your own sources and wording, so anyone on the team can run it in one step.
Each attribute's weight reflects how strongly it preceded conversion in your own data, not a template someone published in 2019.
MQL and SQL cutoffs land where conversion rates actually jump in your history, so the lines mean something.
Any lead scored line by line on request, the fastest way to settle a 'why did this one qualify?' debate.
Change a weight or threshold in the chat and see how last month's lead volume would have qualified under the new rules.
Score accounts instead of individual leads for ABM motions, with intent and engagement rolled up per account.
Add point deductions for disqualifiers (students, competitors, free-mail domains) to clean the MQL queue.
Define how behavioral points expire, so a pricing-page visit from March doesn't inflate a lead in September.
Run your existing model against recent closed-won data and find the weights that no longer earn their points.
A lead scoring model assigns points to a lead's attributes and behaviors (job title, company size, pricing-page visits) and uses thresholds to decide who is marketing-qualified (MQL) or sales-qualified (SQL). JoySuite drafts the model from your CRM's conversion history rather than generic templates.
Joy compares your closed-won deals against leads that never converted and weights each attribute by how strongly it separated the two groups. Every weight in the output comes with its evidence, so the model is something your team can inspect and challenge.
At the score levels where conversion rates actually jump in your history, not at round numbers. In the drafted model each threshold cites its breakpoint (for example, conversion rising from 4% to 19% at the MQL line), so the cutoffs are defensible.
No. Joy drafts and documents the model, scores individual leads on request in the chat, and re-scores examples when you change a weight. You copy the final rules into your automation platform, which does the ongoing scoring at scale.
Review it every two to three quarters, or after anything that changes your funnel: new pricing, a new segment, a new product. Because Joy rebuilds from current CRM data on demand, a refresh is one ask instead of a multi-week project.
Join the waitlist and be first to try this workflow when JoySuite launches.