Most lead scoring articles show a decorative pyramid and a worksheet with vague point values like plus twenty for ICP fit. That is theater, not a scoring model. A useful lead scoring example shows the signals the model reads, the weights the operations lead configured, the record page where the score lands with the top drivers cited, and the counterfactual that shows what would move the score up. The six worked examples on this page cover enterprise SaaS, mid-market services, financial services, healthcare, higher education, and a cold-list resurface scenario. Each example lists the real signals, the real weights, and what the record page actually shows at the end.
Lead scoring examples that teach something share four properties: cited signal fields rather than vague adjectives, actual weight numbers rather than hand-waved multipliers, the resulting record page rather than a slide deck, and the counterfactual that shows what would raise the score. Anything missing one of those four is marketing filler. The examples below carry all four.
A useful example says annual recurring revenue tier equals five to twenty million rather than mid-market fit. The former is a cited field with a known source. The latter is a mood. The Strkr record page cites the field, the source, and the pull timestamp so every reader can audit the signal.
A useful example shows the weight the operations lead configured, not a generic multiplier handed down by the vendor. Firmographic match weight at 0.35 is a tunable number the ops lead can see. Multiplier set to strong is a slogan. The weights in the examples below are the real weights an operations lead would set.
A useful example shows the record page where the score lands with the top drivers cited and the counterfactual visible. Not a slide, not a worksheet, not a dashboard mockup. The Strkr record page is the view the sales team actually opens in the morning.
A useful example shows what would move the score up. The counterfactual turns a static number into a workflow. The sales team sees that confirming an engaged chief technology officer would move the lead from 72 to 85 and acts accordingly. The number alone is useless without it.
A 1,200-FTE SaaS company in North America fills out a demo request form after visiting the pricing page three times in seven days and reading two product documentation pages. The engagement started with a marketing-qualified lead and advanced to a sales-accepted lead after a VP of engineering reply. The model reads nine signals and produces 78.
ICP alignment: SaaS, 500-2,000 FTE, North America, tech stack signal match. The weight is 0.25 of the composite. The hit is 0.95 against the ICP definition. The contribution is 23.8 points.
Pricing page visits (3x in 7 days), documentation reads (2 pages on the enterprise tier), demo request form submitted. The weight is 0.25 of the composite. The hit is 0.85. The contribution is 21.3 points.
Email reply within six hours of the first outbound touch. Response latency is in the top band for the segment. The weight is 0.15. The hit is 0.70. The contribution is 10.5 points.
Engagement from a VP of engineering with a product usage pattern on a related tool. The engaging contact's role is a positive signal; the overall champion depth is modest. The weight is 0.15. The hit is 0.60. The contribution is 9.0 points.
A recent funding announcement and a reported hiring push on the engineering side. No fiscal year end imminent. The weight is 0.08. The hit is 0.55. The contribution is 4.4 points.
The combined custom-field weight and historical conversion signal land at 0.75 against the ideal profile. The weight is 0.12. The contribution is 9.0 points. Total composite score: 78.
A 180-employee professional services firm downloads a benchmark report. The engagement is modest, the ICP fit is partial, and the champion signal is a marketing manager. The model reads eight signals and produces 62. The record page shows a counterfactual that would move the score to 74 if a director-level contact engages.
Professional services, 150-500 FTE, North America. Partial ICP fit (the segment is on the edge of the current ICP band). The weight is 0.25. The hit is 0.70. The contribution is 17.5 points.
Downloaded a benchmark report. Visited the pricing page once. No documentation reads. The weight is 0.25. The hit is 0.50. The contribution is 12.5 points.
Reply latency: 48 hours. Email reply length: short. The engagement is live but low-tempo. The weight is 0.15. The hit is 0.40. The contribution is 6.0 points.
The engaging contact is a marketing manager rather than a director or VP. The role carries a lower champion weight. The weight is 0.15. The hit is 0.35. The contribution is 5.3 points.
The combined timing and custom-field weights land at 0.65 against the segment benchmark. Fiscal year end in two months. The weight is 0.20. The contribution is 13.0 points.
Historical conversion for this segment is thin so the weight is held at zero this cycle. Total composite score: 62. Counterfactual: director-level engagement would move the lead to 74.
A $450M AUM registered investment advisor on Schwab opens an email about a custodian conversion playbook and clicks through to the product documentation. The chief operations officer attends a webinar. The model reads nine financial services signals and produces 83. The record page cites the custodian, the ADV filing, and the engaged COO.
RIA (fits ICP), ADV filing cited. The weight is 0.20. The hit is 1.00. The contribution is 20.0 points.
AUM $450M (fits the top ICP tier). Form ADV cited. The weight is 0.15. The hit is 0.90. The contribution is 13.5 points.
Schwab (fully compatible with product integration). Weight 0.15. Hit 1.00. Contribution 15.0 points.
Active custodian conversion signal (reading the playbook content, COO engagement). Weight 0.15. Hit 0.80. Contribution 12.0 points.
Chief operations officer attended the webinar. Compliance officer not yet engaged. Weight 0.15. Hit 0.75. Contribution 11.3 points.
Fiduciary framework (fit). State registration covered. The combined signal lands at 0.56. Weight 0.20. Contribution 11.3 points. Total composite score: 83.
A 350-bed community hospital on Epic with a Vizient GPO affiliation and an active value-based care program. The chief medical information officer replied to the quarterly outreach three weeks ago. The model reads nine healthcare signals and produces 71. The record page cites the EHR, the GPO, and the trigger.
Community hospital, 350 beds (fits the mid-tier ICP). Weight 0.15. Hit 0.85. Contribution 12.8 points.
Epic (fully compatible with product integration). Weight 0.15. Hit 1.00. Contribution 15.0 points.
Vizient member with vendor on the current contract list. Procurement path shortens materially. Weight 0.15. Hit 0.90. Contribution 13.5 points.
Active value-based care program (public announcement). Weight 0.15. Hit 0.70. Contribution 10.5 points.
CMIO replied three weeks ago, no follow-up yet. Weight 0.15. Hit 0.60. Contribution 9.0 points.
Payer mix skews Medicare-heavy (less fit for the product's commercial anchor). Historical conversion for this segment is thin. Combined signal lands at 0.41. Weight 0.25. Contribution 10.3 points. Total composite score: 71.
A regional R2 university with 12,000 students, a Banner SIS, and an active strategic plan calling out student success technology. The CIO engaged on a webinar. The procurement path runs through a state system cooperative. The model reads nine signals and produces 68. The counterfactual: a scheduled faculty senate agenda item would move the score to 79.
R2 doctoral-granting university, 12,000 students (fits the mid-tier ICP). Weight 0.15. Hit 0.80. Contribution 12.0 points.
Banner (fully compatible). Weight 0.15. Hit 0.90. Contribution 13.5 points.
New strategic plan calls out student success technology as a priority. Weight 0.15. Hit 0.75. Contribution 11.3 points.
CIO engaged on a webinar. Provost not yet engaged. Weight 0.15. Hit 0.65. Contribution 9.8 points.
State system cooperative (vendor is on the preferred list, shorter path). Weight 0.15. Hit 0.60. Contribution 9.0 points.
Current stage: dean approval secured. Faculty senate review not yet scheduled. Weight 0.25. Hit 0.50. Contribution 12.5 points. Total composite score: 68. Counterfactual: a scheduled faculty senate agenda item would move to 79.
A 400-FTE B2B SaaS company sat on the cold list at a score of 24 for seven months. A new trigger event (a new VP of operations hire) fires. The engagement signal re-activates (two documentation reads, a pricing page visit). The model resurfaces the record from 24 to 61 and flags it on the sales development working queue the next morning.
Score 24 at the last recompute. Firmographic hit low. Engagement signal zero. No recent trigger. Record held in the cold-list namespace.
A new VP of operations hire fires the trigger signal. The firmographic hit climbs because the title fits the typical champion profile. Weight 0.15. Hit 0.75. Contribution 11.3 points.
Two documentation reads on the enterprise tier and a pricing page visit in a seven-day window. The behavioral signal re-activates. Weight 0.25. Hit 0.60. Contribution 15.0 points.
ICP firmographic hit holds at 0.65 against the standard ICP definition. Weight 0.25. Contribution 16.3 points.
Combined with the baseline historical and timing contributions, the composite lifts from 24 to 61. The resurface workflow fires, the record moves out of the cold-list namespace, and the sales development queue picks it up the next morning.
The record page shows the resurface context (previous score 24, current score 61, drivers behind the lift) and the sales development representative sees the context before the first touch. Strkr AI drafts an opener that references the new VP hire.
The examples above share four patterns: weights are tunable by the operations lead, the record page shows every driver and citation, the counterfactual turns a static number into a workflow, and the model recomputes on triggers rather than sitting on last quarter's score. Carry the patterns into any scoring model you build; drop them at your peril.
Every example above runs on weights the operations lead configured, not vendor defaults. The weights are visible on the admin page. The recompute runs against the new weights nightly. The model stays useful because the operations lead keeps it tuned.
Every example renders on the record page the sales team actually opens. The drivers are cited. The fields are clickable. The record is the authoritative view. The common failure of a scoring tool whose record page is empty gets avoided.
Every example above shows what would move the score up. The counterfactual is the thing that turns a static ranking into a workflow. The sales team acts on the counterfactual, not on the raw number.
Every example above runs on nightly recompute plus trigger-driven intra-day re-scores. A cold list record resurfaces the same day a trigger fires, not three months later. The model stays current rather than drifting out of alignment with the market.
Strkr lead scoring runs on tunable weights, cited signals, record-page drivers, counterfactual panels, and nightly plus trigger-driven recompute. Fifty dollars per seat flat.
The weights are illustrative of a typical configuration a sales operations lead would set. The actual weights your team runs are tunable on the admin page without a data science engagement. The point of the examples is the structure: tunable weight, cited signal, hit value, contribution math, and a record page where everything lands with explainability.
Trigger events (new leadership, new funding, new behavioral activity, M&A, product launch) fire an intra-day re-score. A cold-list record that was at 24 can lift to 61 the same day the trigger lands. The record moves out of the cold-list namespace and the sales development queue picks it up the next morning with the resurface context on the record page.
A common operations lead configuration weights firmographic match and behavioral intent at 0.25 each, engagement cadence and champion signal at 0.15 each, and timing plus custom plus historical at the remaining 0.20. Your weights should land where the historical conversion data for your closed-won deals points. The Strkr model surfaces that historical pattern so the operations lead tunes from data rather than guess.
The model inspects the signals that have the greatest marginal lift potential against the current record state. A driver such as confirming an engaged VP of engineering or confirming a scheduled faculty senate agenda item is a move the model knows would raise the composite. The counterfactual appears on the record page with the predicted score the move would produce.
Yes. The signal taxonomy, the weight structure, and the record-page layout are configurable on the admin page and exportable through the open API. The sales operations lead can use these examples as the starting pattern and tune to the actual deal shape.
The model runs nightly across every lead and open opportunity. Intra-day re-scores fire on explicit triggers (new behavioral event, new campaign touch, new trigger event) so recently-moved records show the updated score within the hour. The common failure of a scoring tool stuck on last quarter's number gets avoided.
No sales call, no migration consultant, no four-month implementation. Enter your card, get 14 days of the full Pro tier, cancel any time before day 14 with zero charge. Spin up a workspace, import your CSV, and have something useful before lunch.
