Generic lead scoring frameworks treat a SaaS buyer the same as a professional services buyer. That is a mistake. SaaS buyers move faster, self-qualify more aggressively, and leave very specific behavioral signals at each stage of evaluation. The scoring model needs to reflect that. Here is the framework TPG uses when building lead scoring for B2B SaaS companies in HubSpot.
SaaS buyers do most of their evaluation before talking to sales. They visit your pricing page, read integration documentation, compare feature lists, and watch demo videos. A well-built SaaS scoring model detects those specific behaviors and weights them in the order they actually appear in the buyer journey.
Trial signups and product-led growth (PLG) signals are a SaaS-specific variable that most generic scoring models do not account for. If your product has a free trial or freemium tier, trial behavior is the highest-intent signal in your entire model. Score it accordingly.
The other SaaS-specific factor is negative scoring. SaaS products attract high volumes of non-buyers: students, hobbyists, competitors, and researchers. Without aggressive negative scoring, your MQL queue fills with contacts who will never convert.
Score these behaviors based on their position in the buyer journey. Actions that appear in the Decision phase score highest.
| Behavior | Score | Why |
|---|---|---|
| Trial signup | +40 | Direct product-qualified action |
| Demo request page visit (no form fill) | +20 | Decision-phase intent without conversion |
| Pricing page visit | +15 | Strong purchase consideration signal |
| Pricing page visit (second visit within 7 days) | +10 additional | Active comparison shopping |
| Competitor comparison page visit | +12 | Actively evaluating, not just browsing |
| ROI calculator interaction | +12 | Quantifying purchase justification |
| Behavior | Score | Why |
|---|---|---|
| Integration page visit | +10 | Evaluating technical fit for their stack |
| Case study download (matched industry) | +8 | Validating relevance to their use case |
| Feature comparison page visit | +8 | Active product evaluation |
| Webinar registration (product-focused) | +7 | Deeper engagement beyond content |
| Video watch: 75%+ product demo completion | +10 | High-effort engagement with product content |
| Behavior | Score | Why |
|---|---|---|
| Blog post read | +2 | Awareness, not purchase intent |
| Homepage visit | +1 | Too generic to weight heavily |
| Social link click | +2 | Low-effort engagement |
| Newsletter signup | +3 | Interest, not intent |
| Resource download (non-industry-specific) | +3 | Light engagement |
A buyer who returns to your site within 7 days after an initial visit is actively evaluating. Add 12 points for any returning visitor who previously hit a consideration or decision-phase page. This compounds with page-specific scores to surface buyers who are actively in an evaluation cycle.
If your product has a free trial, trial behavior is your most valuable scoring input. Build trial engagement milestones as scoring events in HubSpot using custom behavioral events (available in Marketing Hub Enterprise) or by passing trial engagement data from your product database to HubSpot contact properties via API.
| Trial Event | Score |
|---|---|
| Trial signup | +40 |
| Trial activation (completed setup step 1) | +15 |
| Core feature used (first meaningful action) | +20 |
| Invitation sent to colleague (expansion signal) | +25 |
| Connected integration (technical commitment) | +20 |
| Return login within 3 days | +10 |
| Return login within 7 days | +5 |
| Trial day 7 with 3+ logins | +15 |
| Trial expiration with no upgrade | -10 |
A trial user who activates, uses core features, and invites a colleague within 7 days should be treated as a Sales Qualified Lead regardless of their lead score. Build a workflow that bypasses the standard MQL threshold and routes directly to sales when these three milestones are hit.
"A trial signup is worth 40 points. A trial signup plus core feature activation plus team invite is worth a same-day sales call."
The right job titles vary by product, but the following framework applies to most B2B SaaS tools used by marketing and revenue teams.
| Job Title | Score |
|---|---|
| VP of Marketing | +20 |
| Chief Marketing Officer | +20 |
| Director of Demand Generation | +18 |
| Director of Marketing Operations | +18 |
| Marketing Operations Manager | +15 |
| Revenue Operations Manager | +15 |
| Head of Growth | +18 |
| VP of Revenue Operations | +20 |
Finance and IT titles score lower by default but should receive a conditional boost when combined with pricing page visits. A VP of Finance who visits your pricing page twice is a different signal than one who read a blog post.
| Job Title (base) | Base Score | Pricing Page Modifier |
|---|---|---|
| CFO / VP Finance | +5 | +15 additional if pricing page visited |
| CTO / VP Engineering | +5 | +10 additional if integration page visited |
| IT Director | +3 | +8 additional if security/compliance page visited |
| CEO (SMB company) | +15 | No modifier needed |
| Job Title | Score |
|---|---|
| Student / Intern | -20 |
| Freelancer (without company data) | -10 |
| Professor / Academic | -15 |
| Journalist / Reporter | -10 |
Negative scoring is where SaaS scoring models earn their value. Without it, your MQL queue fills with students, competitors, and low-quality contacts who inflate marketing's numbers and destroy sales' trust in the scoring system.
| Signal | Score |
|---|---|
| Personal email domain (Gmail, Yahoo, Hotmail) | -30 |
| Student email domain (.edu) | -25 |
| Competitor domain (add known competitors to exclusion list) | -50 |
| Email unsubscribed | -25 |
| Contact marked "Bad fit" by sales in CRM | -50 |
| Company size 1-5 employees (if ICP is 50+) | -20 |
| Contact bounced (hard bounce) | -30 |
| No company name (blank field) | -15 |
Build competitor domain exclusion as a rolling list. Keep a property in HubSpot called "Competitor Domain" set to True via workflow enrollment when the contact's email domain matches a list of known competitors. Score it -50 and suppress from all marketing communications. Update the list quarterly.
Go to Settings > Properties > Create Property. Select "HubSpot Score" type. Build separate properties for Fit Score and Behavior Score if you want to track them independently, or use the default HubSpot Score for a combined model.
In the HubSpot Score property editor, add scoring rules for each behavior. For web page visits: select "Page views" and specify the URL. For form submissions: select "Form submissions" and select the form. For email behavior: select "Marketing email" and choose the specific action and email.
Add negative attribute rules for email domain conditions, job title conditions, and company size conditions. Test each rule against 10 known bad-fit contacts to confirm the scoring logic fires correctly before activating.
If your product has a trial, create a custom contact property called "Trial Stage" with dropdown values matching your trial milestones. Build a HubSpot workflow that updates the Trial Stage property based on data synced from your product database. Add scoring rules that fire based on Trial Stage property values.
Analyze your last 50 closed-won SaaS customers. Find the median lead score at the time of their first sales contact (look at contact activity history). Set your initial MQL threshold 10-15% below that median. This creates a slightly permissive threshold that you tighten over 90 days as you gather sales feedback.
Build a HubSpot workflow: when Contact Score is greater than or equal to [MQL threshold], set Lifecycle Stage to Marketing Qualified Lead. Add a notification to the assigned sales rep. Include the contact's score, top 3 scored behaviors, and company information in the notification. Sales needs context, not just a name and a number.
SaaS Lead Scoring QA Checklist Before going live: test positive score rules against 5 known high-intent contacts. Test negative score rules against 5 known bad-fit contacts. Confirm trial milestone workflow fires correctly in a sandbox environment. Verify MQL notification email includes score context. Confirm lifecycle stage automation does not double-count existing MQLs. Set 30-day review date with sales rep.
Should a trial signup automatically make someone an MQL? Not automatically. A trial signup (40 pts) should bring a contact close to or at MQL threshold, but actual MQL status should require the minimum fit score plus the trial signup. A student with a personal email who signs up for a trial should be stopped by negative scoring (-25 for student email, -30 for personal domain) before they reach MQL. Use trial signup as a major intent signal, but keep fit scoring as the gate.
How do I handle PLG freemium accounts where trial users become customers without ever talking to sales? PLG creates a parallel track alongside your scoring model. Build a separate workflow for PLG conversion: when a freemium user hits specific product engagement thresholds (team size, usage volume, feature adoption), route to sales for an expansion conversation rather than treating them as a new lead. Score them separately in a PLG-specific score property so you do not conflate product-qualified accounts with marketing-qualified leads.
What score should an integration page visit get vs. a pricing page visit? In TPG's SaaS framework, pricing page visits score higher (15 pts) than integration page visits (10 pts) because pricing page intent is further down the funnel. However, a contact who visits the integrations page is signaling technical evaluation, which in B2B SaaS correlates strongly with a real buying process. For technical products where integration compatibility drives the purchase decision, some clients weight integration pages higher. Calibrate based on your specific conversion data.
How should I score contacts from my own company's domain? Add your own company domain to the competitor exclusion list with a -50 score modifier, or build a suppression list that excludes employees from all scoring workflows. Internal contacts inflating scores create false positives in your MQL reporting. Suppress them entirely rather than scoring them low.
My SaaS product has a 7-day trial. How do I score trial behavior that happens over a short window? Build time-sensitive scoring using HubSpot's custom behavioral events. Track trial milestones as events with timestamps. Score each milestone when it fires, not based on time elapsed. A contact who hits three trial milestones on day 1 should score identically to one who hits them spread across 7 days. The milestone completion matters more than the timing.
The Pedowitz Group | pedowitzgroup.com | Revenue Marketing Experts Since 2007