If Trials Live in Product, Deals in CRM, and MRR in Billing, Nobody Sees the Whole Picture

Most SaaS teams have:

• Product tracking signups and trials.
• Sales tracking opps in a CRM.
• Finance tracking MRR in Stripe/Chargebee/etc.

If HubSpot only sees one of those, you get:

• No single view of “where an account is”.
• Sales and CS blind to product usage.
• Leadership guessing about trial → opp → MRR conversion.

HubSpot should be:

The GTM system of record for:

• Trials/accounts.
• Opportunities.
• Commercial MRR/ARR.

Here’s how we set that up.

Step 1 – Make “Account” the Center: Companies + Contacts

In SaaS, value happens at the account/workspace level.

Use:

• Companies = accounts/workspaces.
• Contacts = users.

On Companies:

• Account type (Free trial, Free plan, Self-serve paid, Sales-assisted, Enterprise).
• Plan / Tier.
• MRR / ARR (synced from billing).
• Segment (SMB / Mid / Enterprise).
• Region.
• Primary use case or vertical.
• Customer status (Prospect, Trial, Active customer, Churned).

On Contacts:

• Role (Admin, Champion, Buyer, End user).
• Signup source.
• Lifecycle stage (Subscriber, Lead, PQL, SQL, Customer).

You can now see who is in each account and what that account is commercially.

Step 2 – Mirror Trials in HubSpot

Trials must be visible in HubSpot for GTM to act on them.

From product to HubSpot, send:

• For each new trial signup:
• Contact creation (if new) or update.
• Company creation/association (workspace/account).
• Properties:
• Trial start date.
• Trial end date.
• Trial plan (if multiple).

Use workflows to:

• Set Customer status = Trial.
• Set Lifecycle stage on Contact = PQL candidate / SQL candidate if criteria met.
• Optionally set Account type = Trial on Company.

Now GTM can see “who’s in trial now” and when it ends.

Step 3 – Bring Key Product Usage Signals Into HubSpot

You don’t need raw events—just curated signals:

On Companies:

• Active users last 7/30 days.
• Core feature adoption (checkboxes or flags).
• Usage level (Low/Med/High).
• Last active date.

On Contacts:

• Last login date.
• Used core feature? (Yes/No).
• Invited teammates? (Yes/No).

These can be populated via:

• Product analytics tools (Segment, Rudderstack, etc.).
• Direct API integration.

Use them to:

• Identify activated trials.
• Flag accounts at risk (usage drop).
• Surface PQLs for sales-assist.

Step 4 – Define PQL (Product-Qualified Lead) and PQA (Account)

Agree criteria, then codify them as properties.

Examples:

• PQL (Contact) when:
• Signup + completed onboarding.
• Performed X key actions.
• Invited ≥ N teammates.

PQA (Company) when:

• ≥ N active users.
• Used core features Y times.
• Approaching plan limits or usage thresholds.

In HubSpot:

• PQL status on Contacts (Not PQL / New PQL / Working / Disqualified).
• PQA status on Companies (Not PQA / New PQA / Active PQA).

Workflows:

• When product usage meets criteria → flip the flags.
• Trigger routing and tasks (see next step).

Now you have signals that a trial is worth human attention.

Step 5 – Build Pipelines for Sales-Assisted and Enterprise Deals

Not every signup needs a Deal. But real sales motions do.

We recommend:

• No Deals for pure low-touch self-serve upgrades.

Track MRR changes via billing sync on Companies.

Sales-Assisted New Business pipeline for PQL/PQA opps that need a rep:

• Discovery → Solution fit → Trial/POC → Proposal → Commit → Closed Won/Lost.

Enterprise/Complex pipeline for big deals:

• Similar stages, but deeper qualification and approvals.

On Deals:

• Deal type (New, Expansion, Renewal).
• Motion (Self-serve/PLG, Sales-assisted, Enterprise).
• MRR / ARR for this deal.
• Segment and Region.

Deals are associated to the Company and (optionally) key Contacts.

Step 6 – Connect Billing to HubSpot for MRR/ARR

From Stripe/Chargebee/other billing into HubSpot:

On Companies:

• Current MRR / ARR.
• Billing status (Active, Trial, Canceled, Past due).
• Plan / Product.
• Renewal date (for contracted terms).

Workflows:

• When a subscription becomes Active:
• Set Customer status = Active customer.
• Lifecycle = Customer for primary contacts.

When subscription cancels:

• Set Customer status = Churned.
• Flag account for potential winback.

Now HubSpot knows live commercial state per account.

Step 7 – Use Workflows to Manage Trial → Opp → Customer Flow

Glue it together:

Trial starts

• Set Customer status = Trial.
• Enroll users/companies in onboarding/nurture workflows.

PQL/PQA identified

• Company-based or Contact-based workflows:
• Assign PQL/PQA to PLG AE/CSM.
• Create tasks for review and outreach.
• Optionally create Deals for promising accounts.

Deal Closed Won

• Ensure billing is set up.
• Update Current MRR/ARR when billing confirms.
• Lifecycle + Customer status updated accordingly.

This creates a continuous chain: trial → usage → opp → MRR.

Step 8 – Build Unified SaaS Dashboards

Dashboards that show the full picture:

Trials & Activation

• Trials started by source/segment.
• Activation rate (% reaching key usage threshold).
• PQL/PQA counts and trends.

Pipeline & New MRR

• Sales-assisted and Enterprise pipelines by stage.
• Closed Won new MRR by segment and motion.
• Win rate and cycle time.

MRR & NRR

• Current MRR/ARR by segment/plan.
• New, Expansion, Churned MRR per period.
• NRR/GRR trends.

PLG Signals

• Accounts near plan limits.
• Accounts with strong multi-seat adoption.
• Accounts at risk (usage drops).

This lets leadership and RevOps see how trials, opps, and MRR fit together.

Step 9 – Keep HubSpot, Warehouse, and Product Analytics in Their Lanes

PLG/SaaS stack best practice:

HubSpot

• System of record for GTM data (accounts, contacts, deals, GTM-usable usage and billing).
• Where reps and CS actually work.

Data Warehouse + BI

• Deep cohort analysis, retention curves, attribution.
• Full event-level product analytics.

Product Analytics

• UX and feature optimization.

Do not:

• Flood HubSpot with every event.
• Try to do full retention/cohort analysis only in HubSpot.

Do:

• Push back curated, meaningful metrics into HubSpot.
• Use those to route, prioritize, and personalise touchpoints.

Step 10 – Iterate Based on Real Conversion and Retention Data

Over time:

• Check which PQL/PQA definitions actually correlate with:
• Opp creation.
• Win rate.
• MRR expansion.

Refine signals and routing rules:

• Maybe some actions are noise.
• Some combinations (role + feature use + team size) are gold.

Adjust PLG and sales motions in HubSpot:

• Which accounts get sales-assist.
• Which stay fully self-serve.
• Where CS/AM should focus for expansion.

Use HubSpot dashboards + warehouse analytics to close this loop.

Want Help Making HubSpot the Single Pane of Glass for Trials, Opps, and MRR?

If your SaaS team is toggling between product tools, billing, and a basic CRM, we can help you architect HubSpot as the GTM engine.

Through our HubSpot Implementation Blueprints, Portal Health Check, and Managed RevOps Retainer, we:

• Design a SaaS data model for accounts, trials, opps, and MRR.
• Connect product and billing tools to bring in the right signals.
• Implement PQL/PQA routing and sales-assist pipelines.
• Build dashboards that show trials, opportunities, and MRR in one system.