Overview
A lead scoring model helps marketing operations replace the fragile spreadsheet where fit rules, intent points, lifecycle notes, and handoff actions slowly stop agreeing with each other. This playbook installs a structured scorecard and a plain-English scoring guide so the team can build, review, and revise the model in one place.
The boundary is deliberately narrow. Juno builds the scoring model; it does not promise CRM sync, hidden automation, contact enrichment, or live routing by default. The result is a durable model that sales and marketing can inspect before using it to prioritize leads.
Why you should make lead scoring explainable
Lead scoring breaks down when the spreadsheet becomes a formula graveyard. A demo request, pricing-page visit, job title, company segment, and lifecycle stage may all matter, but they should not be mixed into one number without rationale, caps, or recommended actions.
Salesforce describes lead scoring as a way to rank prospects using attributes and behaviors in its lead scoring guide. That only becomes useful when the model also explains what sales or marketing should do next.
HubSpot's overview of lead scoring models is a helpful reminder that scores should reflect both fit and engagement. This playbook keeps those pieces visible: fit decides whether the lead belongs in the motion, intent decides urgency, lifecycle shapes the next action, and caps prevent bad-fit records from looking sales-ready.
Step-by-step
- 1Confirm the brand, scoring purpose, scoring grain, ICP, disqualifiers, available signals, point budget, owner notes, and whether the model should be reviewed monthly.
- 2Install the Lead scoring model table and Scoring guide document so the scorecard exists before Juno starts drafting rules or judging signals.
- 3Define the model frame: why the score exists, who owns it, which leads it applies to, and what decisions the score should support.
- 4Add fit, intent, lifecycle, and negative-control rules with clear evidence requirements, point values, owners, and rationale.
- 5Create caps and score bands so suppressed, poor-fit, research-needed, nurture-ready, and sales-ready leads map to clear recommended actions.
- 6Calibrate the model against sample leads or known examples when available, preserving open questions instead of hiding weak evidence.
- 7Reuse the same scorecard and guide on optional monthly reviews so the model improves without creating a new spreadsheet each time.
Frequently asked questions
Does this replace our CRM lead scoring?
No. It replaces a lead scoring spreadsheet or planning model. CRM field mapping, automation, routing, and write-back should be approved as separate follow-up work.
What inputs do we need?
Bring the ICP, scoring purpose, available signals, disqualifiers, lifecycle stages, and owner expectations. If those are incomplete, Juno can start with conservative defaults and mark assumptions for review.
Can Juno score real leads with this?
Only after the model is built and the user asks for that next step. The default workflow creates the scoring model, caps, bands, recommended actions, and guide before applying it to live lead rows.
How often should we review the model?
Monthly is a useful default when campaigns, lead sources, forms, or sales feedback change often. The review should update the same installed scorecard rather than create a duplicate model.