Build a HubSpot lead-scoring model in three minutes.
Six questions about your ICP, sales cycle, and HubSpot tier. The output is a complete starter model: Fit and Engagement point values, an MQL threshold, decay timing, and A/B/C tier ranges, all formatted for copy-paste into HubSpot's lead-scoring tool. Tier-aware, so Pro portals stay inside the 100-point cap and Enterprise scales to 500.
Select every action that signals buying intent for your team.
Select every signal that should subtract from the score.
Fill in the four required inputs (buyer role, company size, cycle length, and HubSpot tier) to see your starter scoring model. The two multi-select inputs are optional but improve the model.
0 of 4 required filled
Where the recommendations come from
HubSpot product limits and recommendations. Score caps are HubSpot's published per-tier limits: 100 points on Marketing Pro, 500 on Marketing Enterprise. The 50/50 Fit/Engagement default is HubSpot's recommended starting split. MQL thresholds typically fall between 50 and 80 on the 100-point scale per common practice.
Industry-standard point values. Demo +25, free trial +25, contact form +20, pricing visit +15, role match +10, content download +5. Standard negative values: free email -15, role mismatch -25, competitor domain -50. These are widely cited starting points in HubSpot lead-scoring documentation and partner playbooks.
Dunamis model assumptions. MQL thresholds adjust by sales cycle (60 / 70 / 75 / 80 across the four cycle bands) and decay periods adjust the same way (30 / 60 / 90 / 90 days). The Fit/Engagement split also shifts with cycle length, anchored at HubSpot's 50/50 default for the median 30 to 90 day band. Shorter cycles weight engagement more (transactional buying); longer cycles weight fit more (considered enterprise sales).
Enterprise scaling. On Enterprise, point values and the threshold scale 5x to fit the 500-point cap proportionally. Most Enterprise teams extend this baseline with more granular intent rules (specific page visits, intent-data signals, custom event triggers) to use the additional headroom.
We'll send the full model with copy-paste blocks for HubSpot. Optional. The builder works without it.
Finish the four required inputs to enable the report.
Answers to the questions we actually get.
What does the builder output?
A complete starter HubSpot lead-scoring model: a Fit-versus-Engagement point split, an MQL threshold, point values for the high-intent and disqualifier signals you flagged, a decay period for engagement points, and A/B/C tier ranges. Everything is formatted for copy-paste into HubSpot's lead-scoring tool, so the output is a build reference, not a black box.
How is it tier-aware?
HubSpot's lead-scoring tool has different point ceilings per tier: Pro caps the score at 100, Enterprise scales to 500. The builder asks for your tier and scales the point values, MQL threshold, and tier ranges so the model fits inside the cap with usable resolution between A, B, and C bands.
Why six inputs and not more?
Six inputs cover the dimensions that change the model's shape: buyer role, company-size band, sales-cycle length, the high-intent actions you actually have data on, your common disqualifiers, and your HubSpot tier. Adding more inputs (industry vertical, deal size, lifecycle stage definitions) makes the model more bespoke but does not change the structural shape of a starter model. The output is meant as a starting point you tune in HubSpot, not a finished model.
Can I run this against an existing scoring model?
Yes. Run the builder, compare the output to what your portal has today, and treat the deltas as a sanity check. If your existing MQL threshold is far above or below what the builder returns, that is a signal worth investigating. The builder is also useful as a clean-slate reference when migrating from a legacy scoring property to HubSpot's native lead-scoring tool.