How to Score Free Trial Users in HubSpot (Product Usage Data)

Quick answer: The best way to score free trial users in HubSpot is to sync product usage events (feature adoption, engagement frequency, activation milestones) directly into HubSpot and use a calculation property or workflow to assign point values based on actions that predict conversion.

• Calculation property - Real-time scoring based on product usage fields already on the contact record. Native to HubSpot, no workflow lag.
• Workflow-based scoring - More flexible for complex logic and time-decay rules. Can increment scores as events occur.
• Manual scoring by sales - Doesn't scale, inconsistent, and misses real-time signals.
• Zoody - Syncs product events to HubSpot in real-time (no warehouse, no engineering), then score with HubSpot properties or workflows. $149/mo.

Why Product Usage Data Is Critical for Scoring Trial Users

Traditional lead scoring in HubSpot assigns points for job title, company size, email opens, and form submissions. That works fine for cold leads moving through a marketing funnel. It falls apart for free trial users.

A VP at a Fortune 500 company who never logs in is not a hot lead. A mid-level manager at a 30-person startup who connects three integrations and invites their team in the first 48 hours absolutely is.

Trial conversion isn't predicted by demographics. It's predicted by whether someone experiences value in your product before their trial expires.

The Problem with Traditional Lead Scoring for Trial Users

If you're scoring trial users based on company size and job title, you're optimizing for the wrong proxy. You're assuming that "big company VP" = likely buyer. In reality, that VP signed up on a whim, poked around for 10 minutes, and forgot about your product.

Meanwhile, your actual high-intent users are:

• Logging in daily
• Completing onboarding steps
• Building workflows or connecting integrations
• Inviting teammates
• Hitting activation milestones that correlate with paid conversion

None of that shows up in demographic scoring. You're flying blind on the signals that actually matter.

Why Product Signals Beat Demographic Data

Product usage data reveals actual intent and realized value, not hypothetical fit.

When someone connects your Slack integration, creates their first automation, and invites three coworkers in 72 hours, they're telling you they see value and they're socializing the tool internally. That's a buying signal.

When someone logs in once, clicks around, and never returns, that's disengagement - even if they match your ICP perfectly on paper.

A 2023 OpenView Partners study of 200+ PLG companies found that users who hit three key activation milestones in the first week converted to paid at 4.3x the rate of users who only completed one milestone. Engagement frequency (daily active users during trial) had a 0.72 correlation with trial-to-paid conversion. Job title had a 0.14 correlation.

The gap most RevOps teams face: product usage data lives in your application database or analytics tool (Mixpanel, Amplitude, PostHog), not in HubSpot where your sales workflows and scoring properties live. Bridging that gap is the bottleneck.

Essential Product Usage Signals to Track for Trial Scoring

Not all product usage events are equally predictive. You need to identify the actions that correlate with conversion for your specific product. But across hundreds of B2B SaaS products, these categories consistently matter.

Activation Metrics That Matter

Activation is the moment a user experiences your product's core value for the first time. For Slack, it's sending 2,000 messages. For Dropbox, it's storing a file on one device and accessing it from another. For Zoody, it's syncing the first product event to a HubSpot contact record.

Track:

• Setup completion percentage - Did they finish onboarding? Connected required integrations? Imported data?
• Time to first value - How long from signup to first meaningful action? Faster = stronger intent.
• Core feature adoption - Did they use the 2-3 features that define your product's value prop?

Example property names in HubSpot:

• activation_completed (boolean)
• days_to_activation (number)
• onboarding_steps_completed (number, 0-5)
• first_value_moment_date (date)

Engagement Frequency Indicators

A user who logs in daily is exponentially more likely to convert than a user who logs in once a week.

Track:

• Daily/weekly active usage - Number of days with activity in the trial period
• Session count - Total sessions during trial (not just logins, but meaningful engagement sessions)
• Average session duration - Longer sessions often mean deeper exploration
• Return rate - Did they come back after the first session? After the first week?

Example properties:

• trial_active_days (number)
• trial_session_count (number)
• last_active_date (date)
• days_since_last_login (number, calculated)

Feature Depth and Power User Signals

Surface-level usage vs. power user behavior. Someone who explores advanced features is signaling sophistication and intent.

Track:

• Advanced features used - Reports built, automations created, API keys generated, advanced filters applied
• Customization actions - Custom fields created, templates built, settings configured
• Data volume - Number of records imported, events tracked, reports generated
• Integration depth - Connected multiple integrations, not just one

Example properties:

• workflows_created (number)
• reports_generated (number)
• integrations_connected (number)
• advanced_features_used (multi-select)

Team Collaboration and Expansion Indicators

B2B products sell to teams, not individuals. Multi-user adoption is one of the strongest conversion signals.

Track:

• Team members invited - Number of seats filled
• Cross-functional usage - Multiple departments or roles active
• Shared resources - Workspaces created, dashboards shared, collaborative docs
• Admin actions - User permissions set, billing info added (even if not converted yet)

Example properties:

• team_members_invited (number)
• active_team_members (number)
• departments_represented (multi-select)
• shared_workspaces (number)

Building Your Trial User Scoring Model in HubSpot

You have two main approaches to scoring in HubSpot: calculation properties (real-time, formula-based) or workflows (flexible, can handle complex logic and time-based rules). Most teams start with a calculation property for simplicity, then add workflow-based increments for advanced scenarios.

Setting Up Your Scoring Property

Create a new custom property on the Contact object (or Company object for account-level scoring):

1. Navigate to Settings → Properties → Contact properties
2. Click "Create property"
3. Property type: Number
4. Field type: Calculation (if using formula) or Number (if using workflows)
5. Property name: trial_product_score or pql_score
6. Description: "Automated scoring based on product usage during free trial"

If using a calculation property, you can build a formula like:

(activation_completed * 20) + 
(trial_active_days * 2) + 
(workflows_created * 10) + 
(integrations_connected * 8) + 
(team_members_invited * 5) + 
(reports_generated * 3)

This updates in real-time as the underlying properties change. No workflow lag.

If using workflows for scoring (more flexible but introduces lag), create a workflow that triggers "When contact property activation_completed is true" and increments trial_product_score by 20. Repeat for each scoring event.

Assigning Point Values to Product Actions

Start with these baseline point values, then adjust based on your own conversion data after 1-2 months:

Product Action	Points	Why
Completed onboarding / activation	20	Strongest predictor of conversion - they experienced core value
Invited 1+ team members	15	Multi-user adoption = organizational buy-in
Connected 2+ integrations	12	Deep commitment, harder to churn
Created first automation/workflow	10	Power user behavior, customization
Daily active usage (per day)	2	Consistent engagement compounds
Generated first report	8	Value realization moment
Used advanced feature	6	Sophistication signal
Invited 3+ team members	+10	Expansion beyond pilot user
Logged in 5+ days in first week	+5	Frequency = intent

Negative scoring signals (subtract points):

• 3+ days inactive during trial: -5
• Abandoned onboarding halfway: -10
• Declined to invite team when prompted: -3
• Multiple error events (failed workflows, sync errors): -2 per error

Determining Score Thresholds and Segments

Define score bands that trigger different sales actions. These are example thresholds - adjust based on your trial length and typical user behavior:

• 0-25 points (Cold / At Risk) - Signed up but not activated. Trigger re-engagement campaigns, onboarding reminders, support offers.
• 26-50 points (Warm / Engaged) - Some activation, decent engagement. Trigger feature education emails, success stories, use case content.
• 51-75 points (Hot / Qualified) - Strong activation + engagement. Trigger sales assignment, upgrade prompt, demo offer.
• 76+ points (Very Hot / PQL) - Power user behavior, team adoption. Trigger immediate sales outreach, enterprise plan offer, white-glove onboarding.

Create HubSpot lists for each segment:

• List name: "Trial Users - PQL (76+)"
• Filter: Contact property trial_product_score is greater than or equal to 76

Incorporating Time-Based Decay

Trial urgency matters. A user who hits 60 points in the first 3 days is hotter than a user who hits 60 points on day 12 of a 14-day trial.

Two approaches:

1. Velocity-based scoring - Track score change rate, not just absolute score. Add a calculated property:

trial_score_velocity = (trial_product_score - trial_product_score_7_days_ago) / 7

High velocity = strong momentum = prioritize for sales.

2. Time-decay multiplier - Reduce point values as trial progresses. In a workflow, check days_in_trial:

• Days 1-3: multiply points by 1.5x
• Days 4-7: multiply by 1.0x
• Days 8-10: multiply by 0.75x
• Days 11-14: multiply by 0.5x

This rewards early activation and engagement over last-minute scrambles.

How to Get Product Usage Data Into HubSpot

Product usage events happen in your application. HubSpot is your CRM. These systems don't talk to each other by default. You need a bridge.

The Product Data Integration Challenge

Your product emits events: user_logged_in, workflow_created, integration_connected, report_generated. Those events might be tracked in:

• Your application database
• A product analytics tool (Mixpanel, Amplitude, PostHog, Heap)
• An event stream (Segment, RudderStack)

HubSpot has no native way to consume those events. HubSpot's tracking code only captures website/marketing interactions, not in-app product usage.

So your RevOps team is stuck scoring trial users based on demographics and email behavior while the actual conversion signals - product usage - are invisible in HubSpot.

Traditional Approaches (and Their Drawbacks)

Option 1: Build a custom integration

Write code that reads product events from your database or analytics tool, maps them to HubSpot contact/company properties, and pushes updates via the HubSpot API.

• Setup time: 2-6 weeks of engineering work
• Ongoing maintenance: API rate limits, error handling, schema drift, HubSpot property changes
• Cost: Engineering time (expensive, high opportunity cost)
• Best for: Large engineering teams with spare capacity

The HubSpot API allows 100 calls per 10 seconds on Professional/Enterprise tiers. You'll need to batch updates, handle rate limit errors, and build retry logic. Every product event schema change requires updating your integration code.

Option 2: Data warehouse + reverse ETL

Set up a data warehouse (Snowflake, BigQuery, Redshift), pipe product events into it, then use a reverse ETL tool (Hightouch, Census) to sync warehouse data to HubSpot.

• Setup time: 4-12 weeks (warehouse setup + event pipelines + reverse ETL config)
• Ongoing maintenance: Warehouse costs, reverse ETL subscription, dbt models, schema management
• Cost: Warehouse ($200-$2,000/mo) + reverse ETL ($350-$800/mo) + data engineering time
• Best for: Companies already running a warehouse, need multi-tool syncs

This is the most powerful approach if you're syncing data to 10+ tools and already have a data team. It's overkill if you only need product data in HubSpot.

Option 3: Operations Hub custom code workflows

HubSpot's Operations Hub add-on (starts at $720/mo for Professional) includes custom code actions in workflows. You can write JavaScript/Python that fetches product data from an API and updates HubSpot records.

• Setup time: 1-2 weeks
• Ongoing maintenance: Code changes for new events, API auth refresh, debugging workflow failures
• Cost: $720-$2,000/mo (Operations Hub) + engineering time
• Best for: Teams already on Operations Hub, need custom data transformations

Workflows trigger on schedules or property changes, not real-time. You'll have lag between product events and HubSpot updates (5-60 minutes typical).

The No-Code Solution: Real-Time Product Data Sync

Zoody is built specifically for this use case: get product usage data into HubSpot without engineering work or a warehouse.

How it works:

1. Track product events in your app (Segment, PostHog, custom events - anything that sends JSON)
2. Zoody receives events via webhook or SDK
3. Zoody maps events to HubSpot contact/company properties in real-time
4. Product usage data appears on HubSpot records instantly (< 5 second lag)

No warehouse. No custom code. No rate limit management. Just product events → HubSpot properties.

Setup time: 30 minutes (connect event source, map properties, sync)

Ongoing maintenance: None. Add new event types in the UI when your product changes.

Cost: $149/mo flat rate (unlimited events, unlimited contacts)

Best for: RevOps teams who want product data in HubSpot today, not in 6 weeks after engineering builds something.

How Zoody Eliminates the Integration Bottleneck

Traditional reverse ETL tools (Hightouch, Census) require a data warehouse as the source. Zoody doesn't. You send events directly from your product or analytics tool.

Operations Hub requires writing custom code for each data transformation. Zoody provides a visual mapper - click to define which events become which HubSpot properties.

Custom integrations require engineering on your team. Zoody is a SaaS app you configure yourself in the HubSpot UI.

The result: RevOps managers can ship product-based trial scoring in HubSpot the same day they decide to do it, not 6 weeks later after engineering prioritizes it.

Limitations to know:

• HubSpot only (doesn't sync to Salesforce, Marketo, etc.)
• Doesn't replace your product analytics tool (Mixpanel, Amplitude) - those still show detailed user paths, funnels, retention cohorts. Zoody just gets the scoring signals into HubSpot.
• Event data must be structured (JSON properties) - can't parse unstructured logs

If you need multi-CRM syncs or already run a warehouse for other reasons, Hightouch or Census might be better. If you just need product data in HubSpot, Zoody is faster and cheaper.

Automating Sales Outreach Based on Product Scores

Once product usage scores are live in HubSpot, use workflows to trigger sales actions automatically. No manual list pulls, no daily "check the scores" rituals.

Setting Up Score-Based Workflows

Create four core workflows, one for each score segment:

Workflow 1: PQL - Immediate Sales Assignment

• Trigger: Contact property trial_product_score is greater than or equal to 76
• Actions:
  1. Assign contact to sales rep (round-robin or territory-based)
  2. Create deal in "Trial - High Intent" pipeline stage
  3. Send internal Slack notification: "New PQL: [contact name] at [company], score [score], activated [activation_date]"
  4. Add to sequence: "Trial - PQL Outreach" (personalized demo offer)

Workflow 2: Hot - Upgrade Prompt + Soft Touch

• Trigger: Contact property trial_product_score is between 51 and 75
• Actions:
  1. Send email: "You're getting great results with [Product] - here's how to unlock more" (feature comparison, upgrade CTA)
  2. Wait 2 days
  3. If still in trial and score hasn't increased to PQL: Send email with customer success story in their industry
  4. If score increases to 76+: Unenroll and trigger PQL workflow

Workflow 3: Warm - Feature Education

• Trigger: Contact property trial_product_score is between 26 and 50
• Actions:
  1. Check which advanced features they haven't used yet (via properties)
  2. Send targeted email series: "How to get more value from [Product]" with tips for unused features
  3. Offer live onboarding session (Calendly link)
  4. Tag with "Needs Activation Support" for customer success team review

Workflow 4: Cold - Re-engagement Campaign

• Trigger: Contact property trial_product_score is less than 26 AND days_in_trial is greater than 3
• Actions:
  1. Send email: "Having trouble getting started? Here's help" (onboarding checklist, support link, video tutorial)
  2. Wait 2 days
  3. If days_since_last_login is greater than 5: Send email from founder/CEO with personal offer to help
  4. If still no activity after 3 more days: Move to "At Risk - Trial" list for manual outreach

High-Intent Trial User Playbook

When a contact hits PQL status (76+ points), speed matters. Conversion rates drop significantly if sales doesn't reach out within 24 hours of the PQL signal.

What sales should do:

1. Check product usage context before reaching out. Don't just say "I saw you're active in the product." Say "I saw you connected Salesforce and built three lead scoring workflows - that's exactly what [customer X] did before they scaled to 10,000 contacts."
2. Reference specific activation milestones. "You hit our core activation moment (first data sync) in 18 hours - that's faster than 90% of trials. What's your timeline for rolling this out?"
3. Offer immediate value add. "I can show you how to set up your next three workflows in 15 minutes, or share a template library customers use." Not "Do you have time for a demo?"
4. Create urgency tied to trial expiration. "You have 6 days left in trial - if we start your paid plan this week, I can get you white-glove migration support for your full contact database."

Personalization tokens to use in email templates:

• {{contact.trial_product_score}} - Show them the score
• {{contact.activation_completed_date}} - Reference when they activated
• {{contact.workflows_created}} - Specific product actions
• {{contact.team_members_invited}} - Team expansion signal

Nurturing Mid-Score Users to Activation

50-75 point users are engaged but haven't fully activated or adopted advanced features. Your goal: help them experience more value before trial expires.

Tactics:

1. Feature-based email sequences - If they haven't used integrations, send integration setup guide. If they haven't invited team, send collaboration use case.
2. Live training offers - "Join a 20-minute workflow workshop tomorrow at 2pm PT" (low-commitment, high-value)
3. Peer validation - "Companies like [similar company] use [feature you haven't tried] to [outcome]"
4. Progress visualization - "You've completed 3 of 5 key setup steps - finish the last two and you'll hit full activation"

Don't assign to sales yet. Let marketing/customer success nurture them up the score ladder. Sales outreach too early risks burning the lead.

Re-engaging Low-Activity Trial Users

Sub-25 point users signed up but didn't activate. They're at risk of churning silently. The goal here is rescue, not sales.

Tactics:

1. Simplify onboarding - "Skip the full setup. Just do these 2 things to see value in 5 minutes" (link to quickstart)
2. Address common blockers - "Most teams get stuck on [common issue]. Here's the fix in 90 seconds" (video)
3. Founder/executive outreach - Personal email from CEO: "I saw you signed up but haven't logged in. What can I help with?" (works surprisingly well)
4. Offer human help - "Book 15 minutes with our team to get set up together" (not a sales call, actual onboarding help)

If they're still inactive after 7 days, move to a monthly nurture sequence. Some users sign up before they're ready. Keep them warm for future re-engagement.

Advanced Trial Scoring Strategies

Once your basic scoring model is running, add these layers to increase predictive accuracy.

Incorporating Negative Scoring Signals

Not all activity is good. Subtract points for disengagement and friction:

• Declining usage - If days_since_last_login increases from 2 to 5: -5 points
• Abandoned onboarding - Started setup, didn't finish: -10 points
• Error events - Multiple failed API calls, sync errors, broken workflows: -2 points per error
• Feature churn - Tried a feature once, never used again: -3 points
• Team member removal - Invited users then removed them: -5 points (might indicate internal pushback)

Negative scoring helps you identify users who are struggling vs. users who are disengaged. Different rescue strategies for each.

Set a workflow: "If trial_product_score decreases by 10+ points in 48 hours, create task for customer success: Investigate product friction."

Account vs. Contact Scoring for Teams

B2B SaaS trials often involve multiple users from the same company. Do you score at the contact level or aggregate to the company/account level?

Contact-level scoring:

• Pro: See individual power users vs. casual users
• Pro: Easier to track who to route to sales
• Con: Misses team-wide adoption signals
• Best for: Individual contributor tools (analytics, design tools)

Company-level scoring:

• Pro: Captures total team activity and expansion
• Pro: Better for account-based sales motions
• Con: Obscures who the champion is
• Best for: Team collaboration tools (CRM, project management)

Hybrid approach (recommended):

• Score each contact individually based on their usage
• Roll up to company-level aggregate score: company_trial_score = SUM(contact scores) + (unique_active_users * 10)
• This gives you both: individual champions to engage AND total account health

Create a calculated property on the Company object:

company_trial_score = 
  (SUM of all associated contact trial_product_scores) + 
  (count of associated contacts with trial_product_score > 25) * 10

Route to sales when company score hits 150+ (e.g., 3 power users + team expansion).

Blending Product Scores with Fit Scores

Product-led scoring tells you who's engaged. Fit scoring tells you who matches your ICP (company size, industry, tech stack). The best leads are both.

Create two properties:

1. trial_product_score (usage-based, 0-100)
2. fit_score (ICP-based, 0-100)

Build a third combined property:

combined_pql_score = (trial_product_score * 0.7) + (fit_score * 0.3)

Weight product higher (70%) because usage predicts conversion better than fit for trial users. But fit matters for LTV and churn risk post-conversion.

Example scoring logic:

Product Score	Fit Score	Combined Score	Segment	Action
80	80	80	Perfect PQL	Immediate sales, enterprise plan
80	30	65	Engaged non-ICP	Sales call, but qualify budget/authority
40	80	52	Good fit, low usage	CS re-engagement, not sales yet
40	30	37	Poor fit, low usage	Nurture only, don't burn sales time

This prevents sales from chasing high-engagement leads that will churn (too small, wrong use case) while still prioritizing strong product signals.

Measuring and Optimizing Your Scoring Model

Your first scoring model won't be perfect. It shouldn't be. Ship a baseline, measure, iterate.

Essential Metrics to Monitor

Track these in HubSpot reports:

1. Score-to-Conversion Correlation

Create a report: "Trial conversions by score band"

• X-axis: Score ranges (0-25, 26-50, 51-75, 76+)
• Y-axis: Conversion rate to paid
• Goal: See clear separation. If 51-75 converts at 8% and 76+ converts at 35%, your thresholds are working.

If conversion rates are flat across score bands, your scoring isn't predictive. Revisit your point values.

2. Sales Velocity by Score

Measure average days from trial start to closed-won, segmented by initial PQL score.

• High-score leads should close faster (shorter sales cycle)
• If they don't, your score might be identifying engagement but not buying intent

3. False Positive Rate

How many PQL-scored leads (76+) don't convert?

• If it's over 60%, you're routing too many low-intent users to sales. Raise the PQL threshold or adjust point values.
• If it's under 20%, you might be missing real opportunities. Lower the threshold.

4. Score Distribution

Create a histogram of trial user scores.

• If 80% of users are in the 0-25 band, your activation bar might be too high or your onboarding is broken
• If 50% of users hit PQL, you're over-scoring (PQL should be top 10-15%)

Building Scoring Performance Dashboards

Set up a HubSpot dashboard with these reports:

Report 1: Trial Score Funnel

• Bar chart showing count of contacts in each score band
• Filter: trial_status = active or trial_status = expired
• Refresh: Daily

Report 2: Weekly PQL Volume

• Line chart showing PQLs created over time
• Y-axis: Count of contacts entering PQL status (score 76+)
• X-axis: Week
• Use to spot trends (is PQL volume growing as you improve onboarding?)

Report 3: Conversion Rate by Score Band

• Table report
• Rows: Score ranges (0-25, 26-50, 51-75, 76+)
• Columns: Total contacts, Converted to paid (deal closed-won), Conversion rate
• Refresh: Weekly

Report 4: Top Product Signals

• List which product actions correlate most with conversion
• Pull a contact list: Converted to paid = true, export to CSV
• Manually analyze: What % had workflows_created > 0? What % had team_members_invited > 2?
• This tells you which events deserve more points

Continuous Optimization Process

Run this process monthly:

Week 1: Data review

• Pull conversion data by score band
• Identify which product signals are most common in converted users vs. non-converted

Week 2: Hypothesis

• "I think integrations_connected deserves 15 points instead of 12 because 85% of converted users connected integrations vs. 30% of non-converted."
• Or: "I think we're over-weighting trial_active_days - users who log in daily but don't activate are scoring too high."

Week 3: Adjust

• Change point values in your calculation property or workflow
• Document the change in a HubSpot note on a test contact

Week 4: Monitor

• Watch how new score distribution changes
• Track conversion rate over next 30 days
• If improvement, keep the change. If worse, revert.

After 3-6 months of iteration, your scoring model will be significantly more predictive than your initial version.

Implementing Your Trial Scoring System: Step-by-Step Checklist

Here's your 30-day implementation plan:

Days 1-3: Define product events

• List all product actions users can take (login, create workflow, invite team, etc.)
• Identify 5-10 events that correlate with conversion (talk to sales, review conversion data)
• Define activation milestone (the one action that signals value realization)

Days 4-7: Set up product data sync

• Choose your integration method (Zoody, custom build, reverse ETL, Ops Hub)
• Connect your product event source to HubSpot
• Map product events to HubSpot contact/company properties
• Test: Trigger a test event in your product, verify it appears in HubSpot within expected time

Days 8-10: Build scoring property

• Create trial_product_score number property (calculation or workflow-based)
• Assign initial point values to each product action (use examples from this post)
• Set up negative scoring for disengagement signals
• Test: Manually set product properties on a test contact, verify score calculates correctly

Days 11-14: Create score segments

• Define score thresholds (0-25 cold, 26-50 warm, 51-75 hot, 76+ PQL)
• Create HubSpot lists for each segment
• Build a dashboard showing count of contacts in each segment

Days 15-20: Build workflows

• Workflow 1: PQL (76+) → assign to sales, create deal, send notification
• Workflow 2: Hot (51-75) → upgrade email campaign
• Workflow 3: Warm (26-50) → feature education sequence
• Workflow 4: Cold (0-25) → re-engagement campaign
• Test each workflow with test contacts in each score band

Days 21-25: Train sales team

• Document how to interpret product scores in HubSpot
• Create sales playbook: what to say to PQLs vs. warm leads
• Show team where to find product usage context on contact records (timeline, properties)
• Run role-play: "Here's a PQL with score 82, what's your outreach message?"

Days 26-30: Launch and monitor

• Turn on workflows for all active trial users
• Set up weekly review meeting to discuss PQL quality with sales
• Create feedback loop: sales reports which PQLs were good vs. bad leads
• Schedule first optimization review for day 60

By day 30, you should have real PQLs routing to sales automatically based on product usage. By day 60, you'll have data to start iterating point values and thresholds.

FAQ

What's the best way to manage free trials?

The best way to manage free trials is to combine product usage scoring with automated sales workflows in HubSpot. Track activation milestones (setup completion, first value moment, feature adoption), engagement frequency (daily active usage, return visits), and team expansion signals (invites sent, seats filled), then assign point values to each action. Use HubSpot workflows to automatically route high-score users (76+ points) to sales, nurture mid-score users with feature education, and re-engage low-score users with onboarding help. This ensures sales focuses on trial users showing real buying intent based on product behavior, not just demographics.

How do I get product usage data into HubSpot without engineering resources?

Use a no-code product data sync tool like Zoody ($149/mo) that connects your product events directly to HubSpot without requiring a data warehouse or custom integration code. You send product events (via webhook or SDK), map them to HubSpot properties in a visual UI, and events sync to contact/company records in real-time. Alternative approaches require more resources: custom API integrations need 2-6 weeks of engineering work, data warehouse + reverse ETL costs $500-$2,500/mo plus setup time, and HubSpot Operations Hub ($720+/mo) requires writing custom JavaScript for each data transformation.

What product signals are most predictive of trial conversion?

The most predictive product signals for trial conversion are activation completion (experiencing core product value for the first time), team expansion (inviting 2+ teammates), daily active usage frequency (logging in 5+ days in first week), and advanced feature adoption (building workflows, connecting integrations, generating reports). A 2023 OpenView Partners study found users who hit three key activation milestones in the first week converted at 4.3x the rate of users who completed only one milestone. Engagement frequency had a 0.72 correlation with conversion while demographic signals like job title had only 0.14 correlation. For B2B products, collaboration signals (multiple active users from the same company) are especially strong predictors.

How should I set score thresholds for trial users in HubSpot?

Set four score thresholds based on product usage intensity: 0-25 points (cold/at-risk, trigger re-engagement campaigns), 26-50 points (warm/engaged, trigger feature education), 51-75 points (hot/qualified, trigger sales assignment), and 76+ points (PQL/very hot, trigger immediate outreach). These ranges assume a 0-100 point scale with activation worth 20 points, team invites worth 15 points, and daily engagement worth 2 points per day. Adjust based on your specific trial length and conversion data - your PQL threshold should capture the top 10-15% of trial users by score, and those users should convert at 3-5x the rate of lower-score users. Review conversion rates by score band monthly and shift thresholds if segments overlap.

Should I use contact-level or company-level scoring for B2B trial users?

Use a hybrid approach: score each contact individually based on their product usage, then roll up to a company-level aggregate score that includes both total team activity and unique active user count. Contact-level scoring (0-100 points per person) helps you identify individual champions and power users to engage directly. Company-level scoring (sum of all contact scores + bonus points for team expansion) reveals account health and buying committee engagement. Create a calculated company property like company_trial_score = SUM(contact scores) + (active_users * 10) to capture both dimensions. Route to sales when company score exceeds 150 (e.g., 3 engaged users) rather than relying solely on a single contact's activity, since B2B purchases typically involve multiple stakeholders.