The sales team closes the deal and moves to the next opportunity. The customer signs the contract and waits for someone to help them get started. What happens in the next 90 days determines whether that customer stays for three years or churns at renewal. Research across B2B SaaS consistently shows that 60-70% of churn decisions are made in the first 90 days of a customer relationship—before the annual review, before the QBR, before the CSM even has time to build trust.
HubSpot is not a customer success platform. But it can manage a structured onboarding process that catches risk early, automates the routine touchpoints, and gives CS leadership visibility into the entire onboarding portfolio at once.
Onboarding is not a service delivery function—it is a retention investment. Consider the math on a $50,000 ACV SaaS product with a 25% year-one churn rate. If better onboarding reduces year-one churn by 8 points (from 25% to 17%), at 100 new customers per year that is 8 customers saved. At $50,000 ACV, that is $400,000 in preserved annual revenue before expansion is considered.
The onboarding process in HubSpot does not require a custom development project or a purpose-built CS platform like Gainsight. A properly configured HubSpot onboarding pipeline, a set of automated sequences, and a clear ownership structure deliver measurable churn reduction within two to three quarters.
Create a dedicated onboarding pipeline in HubSpot separate from the sales pipeline. The sales pipeline ends at Closed Won. The onboarding pipeline begins at Closed Won. An automated workflow moves every new customer deal to the onboarding pipeline within 24 hours of deal stage changing to Closed Won in the sales pipeline.
Onboarding pipeline stages:
Kickoff Scheduled: The deal moves here when a kickoff call is booked with the customer. Expected time in this stage: 0-5 business days from onboarding pipeline creation. If no kickoff is scheduled within 5 business days, a HubSpot task escalates to the CS Manager. This is the most common failure point—deals sitting in post-close limbo while the customer wonders who they are supposed to talk to.
Kickoff Complete: Kickoff call has happened. Required fields at this stage: Kickoff Date (logged), Primary Success Criteria (what does success look like for this customer at 90 days?), Implementation Timeline (agreed-upon schedule for the key technical or configuration milestones). These fields must be completed before the deal can advance.
Implementation Started: Customer's technical team or internal champion is actively implementing or configuring the product. Definition: at least one internal customer milestone has been completed and logged.
First Value Delivered: The customer has experienced a defined first value event—the specific moment when the product has delivered measurable benefit for the first time. For a CRM implementation, this might be the first pipeline report run successfully. For a marketing platform, the first campaign sent. For an analytics tool, the first dashboard accessed by an end user. Define the First Value Event for your product before building this pipeline. Without a clear definition, this stage is subjective and the data is unreliable.
Fully Onboarded: All agreed-upon implementation milestones complete. Customer confirmed as active and using the product. CS handoff from onboarding CSM to ongoing success management (if you have separate roles) is documented. A 30-day post-onboarding health check is scheduled.
Onboarding Stalled: A catch stage for deals where the customer has gone quiet, implementation is delayed, or risk has been identified. Moving a deal to Onboarding Stalled triggers an escalation workflow—CSM notification, CS Manager task, and an automated re-engagement email to the customer.
Add these properties to the Deal object in HubSpot to make onboarding data trackable:
Kickoff Date (date): When the kickoff call occurred. Auto-stamp when deal advances to Kickoff Complete.
Days to First Value (calculated number): The number of days from Kickoff Date to the date First Value Delivered stage was reached. Track this as a metric: it is the onboarding efficiency number that predicts retention better than almost anything else.
Onboarding Completion Percentage (number, 0-100): A manually updated or workflow-calculated field showing what percentage of the onboarding checklist is complete. Update it as milestones are completed. Surface it in the CS dashboard.
Primary Success Criteria (text): Free text field capturing what the customer said success looks like at 90 days. This is a field the CSM fills in during the kickoff call. Do not let it be optional.
NPS at Day 30 (number, -100 to 100): Record the first NPS score here when the Day 30 check-in survey returns.
NPS at Day 60 (number): Second NPS data point.
NPS at Day 90 (number): Third NPS data point. A declining NPS trend from Day 30 to Day 90 is an early churn signal—build a workflow that flags deals where NPS drops 20+ points between survey intervals.
Onboarding CSM (owner lookup): The specific CSM responsible for this onboarding. Required for CSM-level reporting and task management.
Implementation Type (dropdown): Self-Serve, Guided, Managed, Partner-Led. Drives different automation sequences and expected timeline benchmarks.
At-Risk Flag (checkbox): Manually set by the CSM when risk is identified. Triggers escalation workflow. More reliable than waiting for a system to detect risk algorithmically—trained CSMs see risk earlier than lead score models.
Kickoff Confirmation Sequence (triggered: deal created in onboarding pipeline)
Immediately: Send automated welcome email from the assigned CSM. Include: CSM's calendar link, onboarding overview document, first three things the customer should do before the kickoff call.
Day 2 (if kickoff not yet scheduled): Automated reminder email from CSM: "We're ready to get started—let's find 30 minutes this week." Include the same calendar link.
Day 5 (if kickoff still not scheduled): Escalation task created for CS Manager. Manual outreach required.
Milestone Check-In Sequences (triggered: deal stage changes)
When deal reaches Implementation Started: Email to customer champion with implementation milestone checklist and self-service resources relevant to their Implementation Type.
Health Score Monitoring Sequence
Day 30: Send NPS survey via HubSpot feedback survey or integrated tool (Delighted, Wootric). Log response to NPS at Day 30 property. If NPS is below 7, create an at-risk task for the CSM within 24 hours.
Day 45: Mid-onboarding check-in email from CSM: "You're halfway through your onboarding timeline. Here's what's complete and what's ahead." Include progress summary and link to schedule a sync if anything is unclear.
Day 60: Send second NPS survey. Log to NPS at Day 60 property. Compare to Day 30 score—declining NPS triggers automated flag.
Day 75: "Two weeks to your 90-day milestone" email. Preview what the CS team will review in the 90-day check-in call.
Day 90: 90-day check-in email inviting customer to a formal review call. This becomes the handoff to ongoing success management if onboarding is complete.
CSM Handoff Trigger
When deal reaches Fully Onboarded: If your CS team has separate onboarding CSMs and ongoing success managers, a workflow triggers the handoff. The ongoing CSM is assigned as the deal owner in HubSpot. An internal notification is sent with context: customer name, implementation type, NPS trend, and the primary success criteria stated at kickoff.
Build a CS onboarding dashboard in HubSpot with these reports:
Portfolio view: All deals currently in the onboarding pipeline, grouped by stage. Color-code by days in current stage—deals exceeding stage benchmarks appear in red. This gives the CS Manager a daily snapshot of the full onboarding portfolio in under two minutes.
Days to first value trend: Average days to First Value Delivered stage for new customer cohorts, tracked monthly. Is this number improving or growing? Improving means your onboarding process is getting more efficient. Growing means something is creating friction.
NPS at Day 30 by cohort: Average NPS at Day 30 for customers who started onboarding each month. Identifies whether product changes, team capacity, or customer segment shifts are affecting early experience.
At-risk count by CSM: How many deals does each CSM have with the At-Risk flag set? Is at-risk concentration a capacity problem or a process problem?
Stage conversion rate: What percentage of deals advance from Kickoff Scheduled to Kickoff Complete within 5 business days? What percentage reach First Value Delivered within 45 days? Conversion rates by stage reveal where the onboarding process is leaking.
If your CS team uses Gainsight, Totango, ChurnZero, or a similar customer success platform, HubSpot should feed that system—not duplicate it.
The standard integration approach: HubSpot owns the onboarding pipeline through day 90. When the deal reaches Fully Onboarded, data syncs to the CS platform to create the customer health record that will be monitored for the rest of the relationship. Properties that sync: customer name, primary CSM, contract value, product type, implementation type, kickoff date, first value date, NPS trend.
After day 90, the CS platform drives health monitoring, QBR scheduling, and expansion identification. HubSpot continues to drive marketing communications to the customer base: product update emails, user conference invitations, case study outreach, and renewal marketing sequences.
The division of responsibility: HubSpot for onboarding pipeline and marketing automation to customers. CS platform for health scoring, CSM task management, and expansion pipeline beyond the onboarding period.
This is where most implementations stall: no one clearly owns the HubSpot onboarding pipeline, so it is no one's responsibility to keep it current.
The onboarding pipeline in HubSpot is owned by CS Operations (or RevOps if you do not have a dedicated CS Ops function). The CSMs update deal stages and fill in custom properties as milestones are reached. CS Operations owns the workflow automation, the dashboard, and the data quality—making sure stage timestamps are accurate, NPS data is logged, and the at-risk flags trigger the right responses.
Without a clear process owner, the pipeline becomes a graveyard of deals stuck in "Implementation Started" for six months with no activity logged. A weekly CSM standup reviewing the HubSpot onboarding dashboard is the minimum governance required to keep the data current.
"The first 90 days of a customer relationship determine whether you keep them for three years. That is too important to manage with spreadsheets and good intentions."
When a structured HubSpot onboarding process is in place—kickoff SLA enforced, automation sequences running, NPS monitoring active—three metrics move within the first two quarters: time to first value drops by 20-30% (because the process removes administrative friction and confusion), NPS at day 90 increases by 15-25 points on average compared to unmanaged onboarding, and year-one churn decreases by 6-12 percentage points in the customer cohorts that go through the structured process. That last number is the one that justifies the investment.
Talk to a HubSpot Customer Success Specialist
Should onboarding live in HubSpot or in a dedicated CS platform like Gainsight? Both have roles. HubSpot handles the structured onboarding pipeline, automated communication sequences, and integration with the marketing database. Gainsight (or Totango or ChurnZero) handles health scoring, CSM task management, and the ongoing success lifecycle beyond onboarding. For companies under $20M ARR with a CS team of under five people, HubSpot alone is sufficient and avoids the cost and complexity of a full CS platform. Above that scale, the combination of HubSpot (onboarding and marketing automation) and a CS platform (health monitoring and expansion) is the standard architecture.
What is "first value delivered" and how do we define it for our product? First value is the specific moment when the customer has received measurable benefit from your product for the first time. It must be product-specific and observable—something the CSM can confirm happened, not something based on the customer's subjective feeling. For a CRM implementation: first pipeline report run with real data. For a marketing automation platform: first campaign sent to a live list. For a SaaS analytics product: first custom dashboard built and shared with a stakeholder. Define this with your CS and Product teams before configuring the onboarding pipeline. It is the most important milestone in the 90-day process.
How do we handle onboarding for self-serve customers in HubSpot? Self-serve customers need automation-heavy onboarding because there is no CSM to manage the process manually. Configure a product-triggered workflow that creates a HubSpot contact and enrolls it in a 45-day onboarding sequence the moment a self-serve signup occurs. The sequence is heavier with content and lighter on personal outreach: day 1 welcome, day 3 getting started guide, day 7 feature highlight, day 14 check-in with usage data included if your product integrates with HubSpot via Segment or a similar connector. If a self-serve customer has not completed the first value event by day 21, trigger an automated invitation to a live onboarding session.
What is a realistic timeline for building this in HubSpot? 6-8 weeks for a company starting from scratch: 2 weeks for property configuration and pipeline setup, 2 weeks for automation workflow build and testing, 2 weeks for dashboard configuration and CSM training. Companies with existing HubSpot instances that need to integrate onboarding with existing workflows and deal pipelines may need 8-10 weeks depending on the complexity of existing configuration. The most common delay is internal alignment on stage definitions and what "fully onboarded" actually means—get that agreed upon before any configuration begins.
Who on the CS team should have HubSpot access and at what permission level? CSMs need edit access to deals in the onboarding pipeline and view access to associated contacts and company records. They should not have admin access to workflows, properties, or dashboard configuration—that creates data governance risk. The CS Operations Manager or RevOps Manager owns admin access. Build a separate HubSpot user role for CSMs with edit deal access and read-only workflow access. This gives CSMs what they need to do their jobs without creating configuration risk from inexperienced workflow edits.
The Pedowitz Group | pedowitzgroup.com | Revenue Marketing Experts Since 2007