---
title: "Net Revenue Retention Playbook: Renewals in HubSpot"
description: HubSpot has no native renewal pipeline. Here's how RevOps teams build NRR-driven renewal and expansion motions using deal stages, properties, and workflows.
---

[![GenFlows](https://www.genflows.com/hubfs/genflows-theme/images/genflows-logo-orange-white.png)](https://www.genflows.com/)

[Case Studies](https://www.genflows.com/#case-studies) [Deliverables](https://www.genflows.com/#deliverables) [Process](https://www.genflows.com/#process) [Team](https://www.genflows.com/#team) [FAQ](https://www.genflows.com/#faq) 

[Book a Call](https://app.iclosed.io/e/genflows/discovery-genflows)

[Home](https://www.genflows.com/) / [Blog](https://www.genflows.com/blog)

[RevOps](https://www.genflows.com/blog/tag/revops)

# Net Revenue Retention Playbook: Renewals in HubSpot

GenFlows Team · Sep 18, 2026, 4:30:56 PM · 13 min read

TL;DR

- **Net revenue retention (NRR)** = (Starting recurring revenue + expansion − churn/downgrades) ÷ Starting recurring revenue. Unlike gross revenue retention, it can exceed 100%.
- **HubSpot has no dedicated "renewal" object.** HubSpot's own documentation recommends building a separate renewal pipeline manually — there's no out-of-the-box equivalent to a Salesforce CS add-on.
- **Recurring-revenue reporting is tier-gated.** Revenue Analytics (the report that tracks NRR-relevant new/existing/lost recurring revenue) requires Sales Hub or Service Hub Enterprise; auto-renewing contracts and renewal quotes require Revenue Hub.
- **The biggest operational gap is ownership, not tooling** — expansion deals stall between CS (owns the relationship, no quota) and Sales/AM (owns the quota, not looped in until it's a risk).
- **A dedicated CS platform (ChurnZero, Vitally, PlanHat) adds health scoring and usage-data ingestion HubSpot doesn't have natively** — but a well-built pipeline and property set in HubSpot covers the fundamentals for teams not ready for that spend.

If you're running outbound to fill the top of the funnel, the temptation is to treat every closed deal as done. It isn't. Net revenue retention — how much recurring revenue you keep and grow from customers you already have — usually determines whether a B2B pipeline actually compounds or just treads water. And if you're running that revenue engine in HubSpot rather than Salesforce-plus-a-CS-suite, the honest answer is that HubSpot doesn't hand you a renewal motion out of the box. You have to build one.

*Note: benchmark figures below are cited to their original source and marked VERIFIED or DIRECTIONAL. Where a widely-repeated number couldn't be traced to a real, named source, we've said so rather than restating it as fact.*

## The Short Answer

NRR measures the percentage of recurring revenue you keep from your existing customer base over a period, including expansion (upsells, seat growth, cross-sell) and net of churn and downgrades. It can go above 100% because expansion is added back in — which is the whole point: NRR is the single number that tells you whether your existing base is growing or shrinking on its own, independent of new-logo sales. HubSpot gives you the raw ingredients to track and act on it (deal properties, workflows, contracts, and — on Enterprise tiers — a recurring-revenue report), but not a packaged "renewal module." Most RevOps teams end up building a separate renewal pipeline with its own stages, tying it to a health-score property and a clear ownership rule between CS and Sales, and deciding case-by-case whether a bolt-on CS platform earns its cost.

## NRR vs. GRR: Why the Distinction Matters

Net revenue retention and gross revenue retention (GRR) are often used interchangeably in casual conversation, and that's a mistake — they answer different questions.

- **GRR** only counts churn and downgrades against your starting revenue base. It excludes expansion entirely, which caps it at 100%. GRR answers: "How much of my starting revenue did I keep, ignoring any growth?"
- **NRR** adds expansion revenue back in. It answers: "How much did my existing customer base actually grow or shrink, all-in?" A company can have 90% GRR (losing 10% of its base to churn/downgrades) but still post 115% NRR if the customers who stayed expanded enough to more than offset that loss.

The formula, consistent across every vendor and finance glossary that publishes it: **NRR = (Starting Recurring Revenue + Expansion Revenue − Churned/Downgrade Revenue) ÷ Starting Recurring Revenue**. *(VERIFIED — Stripe, Zuora, and ChurnZero all independently publish the identical formula.)*

Why this matters for a RevOps team building the motion in HubSpot: if you only track "did the deal renew, yes/no," you're measuring something closer to logo retention, not NRR. A customer can renew (logo retained) while quietly downgrading seats — and if nobody's watching downgrades as a distinct signal, that erosion is invisible until the ARR report comes in soft at the end of the quarter.

**Common trap:** confusing NRR with logo/customer-count retention. A team can retain 100% of accounts and still post NRR under 100% if seats or usage contracted across the base — or lose several accounts entirely and still post NRR above 100% if the survivors expanded hard enough. Track them as two separate numbers.

## What's a "Good" NRR Number?

This is where a lot of blog content overreaches. There is no single agreed "good" NRR — it varies meaningfully by company stage and ARR band, and most of the specific numbers circulating online trace back to the same handful of secondary aggregations of a couple of industry benchmark reports, not to one clean, citable dataset.

What's directionally consistent across multiple sources: earlier-stage companies (roughly under $10M ARR) tend to post higher NRR — often cited in the 105–145% range — because a smaller, more concentrated customer base can swing further on a handful of large expansions. Later-stage companies (over $100M ARR) tend to converge closer to 105–125%, since the base is larger and more averaged-out. *(DIRECTIONAL — this range comes from a billing-vendor analysis of public-company disclosures, not from the disclosures themselves; treat as a rough shape, not a precise benchmark.)* A frequently-cited industry figure puts median NRR for SaaS companies around 110% in recent benchmark surveys. *(DIRECTIONAL — this number is repeated widely citing an industry benchmark report, but we could not independently confirm the exact figure on the report's own primary page; cite it as a commonly-referenced industry figure, not a hard number.)*

The one number that isn't a benchmark claim at all, just arithmetic: **100% NRR is the break-even floor** — below it, your existing base is shrinking even before you add a single new customer. Above it, expansion is outrunning churn. That's the number worth anchoring internal targets to before reaching for an external "good NRR" figure that may not map to your stage or motion.

## Why HubSpot Doesn't Give You This For Free

HubSpot's own documentation is explicit that renewal and recurring-revenue motions are something you build, not something that ships configured. Three concrete gaps, straight from HubSpot's knowledge base:

- **No native renewal pipeline.** HubSpot's contracts documentation recommends "establishing a dedicated renewal pipeline" as a manual setup step for teams using auto-renewing (evergreen) contracts — confirming there's no pipeline that appears automatically.
- **Recurring-revenue reporting is Enterprise-gated.** The "Recurring revenue deal type" property (New business / Renewal / Upgrade / Downgrade) is available broadly, but the Revenue Analytics report that turns it into new/existing/lost recurring-revenue tracking requires Sales Hub Enterprise or Service Hub Enterprise.
- **Renewal quotes require Revenue Hub.** Generating a renewal quote directly from a contract is a Revenue Hub feature (with a seat requirement), not something available on Sales Hub alone.

HubSpot's own blog confirms the practical result of this: renewal reminders and cadences are something "service reps can build" via workflows and custom properties — there's no native "notify me 90 days before this renews" toggle. If you've seen agency or consultant content describing HubSpot as automatically creating a renewal deal and assigning a CSM task at a fixed day count (120 days is a commonly-cited figure), that's describing someone's custom workflow build, not a native HubSpot behavior — don't take it as a documented feature.

## Building the Renewal & Expansion Motion in HubSpot

### 1. A separate pipeline, not a recycled deal stage

The single most consistent piece of practitioner guidance — echoed in HubSpot's own community and documentation — is to run renewals through a *separate pipeline* from new business, not as a late stage bolted onto the original deal. Reusing the original deal or pipeline corrupts your new-business win-rate and cycle-time reporting, since renewal cycle times and close rates behave completely differently from net-new sales.

### 2. A property set that actually drives the workflow

At minimum: a renewal/contract end date, the "Recurring revenue deal type" property, a health-score property (even a simple manually-set or engagement-derived score beats nothing), and a deal owner field that's explicitly the AM/CS owner, not whoever originally closed the new-business deal. These are the fields your renewal-pipeline workflows key off of.

### 3. Time-boxed workflow triggers, not a single reminder

A commonly-used practitioner cadence is staged reminders at roughly 120/90/60 days before contract end, escalating in urgency and audience (CSM first, then CSM+AM, then a manager-visibility flag if there's no logged engagement). *(DIRECTIONAL — this is a widely-repeated practitioner convention across agency and consultant content, not a documented HubSpot standard; build your own cadence around your actual sales-cycle length rather than copying it verbatim.)* The reason lead time matters: complex, multi-stakeholder renewals often need 90+ days to surface budget risk or build an expansion case before the contract lapses — starting at 30 days out is often too late to do anything but react.

### 4. A named handoff rule between CS and Sales

This is the gap that costs the most revenue in practice, and it's an ownership problem, not a tooling problem: Customer Success typically owns the relationship but doesn't carry a sales quota, while the AM or Sales rep who owns the quota often isn't looped in until the account is already flashing red. A lifecycle-stage change plus an automatic deal-owner reassignment — triggered off the health-score or renewal-date property — is the standard way to force that handoff to happen on a schedule instead of waiting for someone to notice.

**Note:** the "Recurring revenue deal type" property is a static reporting tag. Setting it does nothing on its own — no reminder fires, no task gets created — unless it's wired into a workflow. Teams sometimes set the property correctly and then wonder why "nothing is automated."

## Native HubSpot vs. Bolt-On CS Platform vs. Custom Build

| Capability | Native in HubSpot | Bolt-on tool (ChurnZero/Vitally/PlanHat) | Custom build required |
| --- | --- | --- | --- |
| Recurring revenue (MRR/ARR) on a deal | Yes — auto-calculated with recurring line items | — | — |
| Deal-type tagging (New/Renewal/Upgrade/Downgrade) | Yes — native property | — | Reporting/dashboards on top of it |
| Recurring-revenue / NRR-style reporting | Sales Hub / Service Hub Enterprise only | Most CS platforms report this natively | Lower tiers: custom reports/dashboards |
| Dedicated renewal pipeline | No — HubSpot's own docs say to build one | Often included as a template | Yes — standard practitioner pattern |
| Renewal quotes from a contract | Revenue Hub (seat required) | — | — |
| Customer health scoring | No native health-score object | Yes — purpose-built (ChurnZero, Vitally, PlanHat) | Crude version via weighted custom property |
| Product usage / adoption data as a retention signal | No | Yes — typically ingested natively | Custom integration/webhook if no CS platform |
| CS-to-Sales renewal/expansion handoff | No native "handoff" object | Sometimes via the platform's own workflows | Yes — lifecycle-stage change + owner reassignment |

## Do You Actually Need a Dedicated CS Platform?

Not necessarily, and not right away. A well-built pipeline, a real property set, and disciplined workflow automation in HubSpot covers the fundamentals for a lot of teams — particularly ones that are still early in formalizing a renewal motion at all. Where a dedicated platform like ChurnZero, Vitally, or PlanHat earns its cost is purpose-built health scoring, direct product-usage-data ingestion, and pre-built renewal playbooks — none of which HubSpot does natively. All three integrate with HubSpot via bidirectional sync (accounts, contacts, deals, and in Vitally's and PlanHat's case, custom objects and health scores pushed back into HubSpot) rather than replacing it. None of the three CS platforms publish list pricing — it's a "contact sales," size-based model across the board, so treat any specific dollar figure you see quoted for them as directional, not a rate card.

## Six Traps That Undercut an NRR-Driven Motion

1. **Watching churn and ignoring downgrades.** A full cancellation gets noticed. A seat reduction or tier downgrade often doesn't — and it erodes NRR just as directly.
2. **Starting the renewal conversation too late.** Complex, multi-stakeholder renewals frequently need 90+ days of lead time; starting at 30 days is often a save attempt, not a renewal strategy.
3. **No single owner for expansion deals.** CS owns the relationship without a quota; Sales/AM owns the quota without visibility. Expansion revenue falls in that gap by default unless a handoff rule forces it to move.
4. **Recycling the original deal for the renewal.** This corrupts new-business win-rate and cycle-time reporting — run renewals through a separate pipeline.
5. **Treating a property as if it were a workflow.** Tagging a deal "Renewal" does nothing by itself; it has to trigger something.
6. **Quoting a single "good NRR" number as gospel.** The benchmark varies by stage and by which report you're reading — anchor internal targets to your own trend and to the 100% break-even floor before importing an external number.

## Frequently Asked Questions

### What is net revenue retention (NRR)?

NRR measures the percentage of recurring revenue a company retains from its existing customer base over a period, including expansion (upsells/cross-sells) and net of churn and downgrades. It's calculated as (Starting Recurring Revenue + Expansion − Churn) ÷ Starting Recurring Revenue.

### What's the difference between NRR and gross revenue retention (GRR)?

GRR only counts churn and downgrades against the starting revenue base and excludes any expansion revenue, which caps it at 100%. NRR adds back expansion revenue, so it can exceed 100% when upsells outweigh churn — making NRR the more complete picture of account-level growth.

### Does HubSpot have a native renewal pipeline or deal type?

Not a dedicated, purpose-built renewal object out of the box. HubSpot offers a "Recurring revenue deal type" property (New business/Renewal/Upgrade/Downgrade) and, with a Revenue Hub subscription, renewal quotes generated from contracts — but HubSpot's own documentation recommends manually building a separate renewal pipeline with custom stages.

### What HubSpot tier do you need to track recurring revenue and NRR?

Revenue Analytics — the built-in report that tracks new/existing/lost recurring revenue — requires Sales Hub Enterprise or Service Hub Enterprise. Auto-renewing contracts and renewal quotes require a Revenue Hub subscription and seat.

### Do you need a separate customer success platform if you use HubSpot?

Not necessarily for early-stage teams — a well-built renewal pipeline, health-score property, and workflow automation in HubSpot can cover the basics. Dedicated CS platforms add purpose-built health scoring, usage-data ingestion, and playbook automation that HubSpot doesn't natively provide, and they integrate with HubSpot via bidirectional sync rather than replacing it.

### What's the most common mistake teams make with NRR-driven renewal motions?

Waiting until the renewal date is close to start expansion conversations, and having no single clear owner — AM, CS, or Sales — for expansion-stage deals, both of which cause expansion revenue to get missed or renewal risk to surface too late to act on.

---

**If your HubSpot deal stages already need a rework before a renewal pipeline can sit on top of them cleanly, start with [how to set up HubSpot deal stages for outbound teams](https://www.genflows.com/blog/hubspot-deal-stages-outbound-teams-2026) — or [talk to our team](https://www.genflows.com/) about building the RevOps foundation (deal stages, properties, reporting) your renewal and expansion motion needs to run on.**

*By the GenFlows GTM engineering team. Sources cited inline; benchmark figures without a traceable primary source are marked directional. Last updated September 2026.*

[#RevOps](https://www.genflows.com/blog/tag/revops)

Share [in](https://www.linkedin.com/sharing/share-offsite/?url=https%3A%2F%2Fwww.genflows.com%2Fblog%2Fnet-revenue-retention-hubspot-playbook-2026) [X](https://twitter.com/intent/tweet?url=https%3A%2F%2Fwww.genflows.com%2Fblog%2Fnet-revenue-retention-hubspot-playbook-2026&text=%3Cspan+id%3D%22hs_cos_wrapper_name%22+class%3D%22hs_cos_wrapper+hs_cos_wrapper_meta_field+hs_cos_wrapper_type_text%22+style%3D%22%22+data-hs-cos-general-type%3D%22meta_field%22+data-hs-cos-type%3D%22text%22+%3ENet+Revenue+Retention+Playbook%3A+Renewals+in+HubSpot%3C%2Fspan%3E)

↗

Written by

GenFlows Team

The GenFlows team builds AI-powered cold outbound systems for B2B teams.

On this page

## Keep reading

### [Outbound Systems Close CRM Power Dialer: Plans, Setup & Limits Oct 8, 2026, 11:54:26 AM Read →](https://www.genflows.com/blog/close-crm-power-dialer-outbound-calling-2026)

### [Outbound Systems Close CRM Reporting for Outbound: Reports & Metrics Oct 8, 2026, 11:50:47 AM Read →](https://www.genflows.com/blog/close-crm-reporting-outbound-2026)

### [Outbound Systems Close CRM Smart Views for Outbound: Filters & Recipes Oct 7, 2026, 12:50:20 PM Read →](https://www.genflows.com/blog/close-crm-smart-views-outbound-2026)

## Ready to fill your calendar?

We build AI-powered cold outbound engines that book meetings on autopilot. Let's see if it fits your team.

[Book a Call](https://app.iclosed.io/e/genflows/discovery-genflows)

![GenFlows](https://www.genflows.com/hubfs/genflows-theme/images/genflows-logo-orange-white.png)

Precision-engineered outbound systems for B2B companies.

[![Clay Artisan Solutions Partner 2026](https://www.genflows.com/hubfs/genflows-theme/images/clay-artisan-pill-2026.png)](https://www.clay.com/experts/partner/wouter-harink?via=wouter) [![First 100 Partner Badge](https://www.genflows.com/hubfs/genflows-theme/images/first-100-partner-badge.png)](https://www.clay.com/experts/partner/wouter-harink?via=wouter) [![Smartlead Certified Partner](https://www.genflows.com/hubfs/genflows-theme/images/smartlead-certified-partner.png)](https://www.smartlead.ai/partner/wouter-harink)

Explore

- [How it works](https://www.genflows.com/#process)
- [Results](https://www.genflows.com/#results)
- [Revenue calculator](https://www.genflows.com/#calculator)
- [About](https://www.genflows.com/#founder)

Reach us

- [info@genflowsagency.com](mailto:info@genflowsagency.com)
- [Book a call](https://app.iclosed.io/e/genflows/discovery-genflows)
- [LinkedIn](https://www.linkedin.com/company/genflows-agency/)

© 2026 GenFlows Agency. All rights reserved.

[Privacy](https://www.genflows.com/privacy) [Terms](https://www.genflows.com/terms) v1.0

```json
{
  "@context" : "https://schema.org",
  "@type" : "BlogPosting",
  "author" : {
    "@type" : "Person",
    "name" : "GenFlows Team"
  },
  "dateModified" : "2026-09-18T14:30:57Z",
  "datePublished" : "2026-09-18T14:30:56Z",
  "description" : "HubSpot has no native renewal pipeline. Here's how RevOps teams build NRR-driven renewal and expansion motions using deal stages, properties, and workflows.",
  "headline" : "<span id=\"hs_cos_wrapper_name\" class=\"hs_cos_wrapper hs_cos_wrapper_meta_field hs_cos_wrapper_type_text\" style=\"\" data-hs-cos-general-type=\"meta_field\" data-hs-cos-type=\"text\" >Net Revenue Retention Playbook: Renewals in HubSpot</span>",
  "image" : [ "" ],
  "keywords" : "RevOps",
  "mainEntityOfPage" : {
    "@id" : "https://www.genflows.com/blog/net-revenue-retention-hubspot-playbook-2026",
    "@type" : "WebPage"
  },
  "publisher" : {
    "@type" : "Organization",
    "logo" : {
      "@type" : "ImageObject",
      "url" : ""
    },
    "name" : "GenFlows"
  },
  "wordCount" : 2563
}
```

```json
{
  "@context" : "https://schema.org",
  "@type" : "BreadcrumbList",
  "itemListElement" : [ {
    "@type" : "ListItem",
    "item" : "https://www.genflows.com/",
    "name" : "Home",
    "position" : 1
  }, {
    "@type" : "ListItem",
    "item" : "https://www.genflows.com/blog",
    "name" : "Blog",
    "position" : 2
  }, {
    "@type" : "ListItem",
    "name" : "<span id=\"hs_cos_wrapper_name\" class=\"hs_cos_wrapper hs_cos_wrapper_meta_field hs_cos_wrapper_type_text\" style=\"\" data-hs-cos-general-type=\"meta_field\" data-hs-cos-type=\"text\" >Net Revenue Retention Playbook: Renewals in HubSpot</span>",
    "position" : 3
  } ]
}
```

```json
{
  "@context" : "https://schema.org",
  "@type" : "BlogPosting",
  "author" : {
    "@type" : "Person",
    "name" : "GenFlows Team",
    "url" : "https://www.genflows.com/blog/author/genflows-team"
  },
  "datePublished" : "2026-09-18T14:30:56.000Z",
  "headline" : "Net Revenue Retention Playbook: Renewals in HubSpot",
  "mainEntityOfPage" : {
    "@id" : "https://www.genflows.com/blog/net-revenue-retention-hubspot-playbook-2026",
    "@type" : "WebPage"
  },
  "publisher" : {
    "@type" : "Organization",
    "logo" : {
      "@type" : "ImageObject"
    }
  }
}
```

```json
{
  "@context" : "https://schema.org",
  "@type" : "FAQPage",
  "mainEntity" : [ {
    "@type" : "Question",
    "acceptedAnswer" : {
      "@type" : "Answer",
      "text" : "NRR measures the percentage of recurring revenue a company retains from its existing customer base over a period, including expansion (upsells/cross-sells) and net of churn and downgrades. It's calculated as (Starting Recurring Revenue + Expansion − Churn) ÷ Starting Recurring Revenue."
    },
    "name" : "What is net revenue retention (NRR)?"
  }, {
    "@type" : "Question",
    "acceptedAnswer" : {
      "@type" : "Answer",
      "text" : "GRR only counts churn and downgrades against the starting revenue base and excludes any expansion revenue, which caps it at 100%. NRR adds back expansion revenue, so it can exceed 100% when upsells outweigh churn — making NRR the more complete picture of account-level growth."
    },
    "name" : "What's the difference between NRR and gross revenue retention (GRR)?"
  }, {
    "@type" : "Question",
    "acceptedAnswer" : {
      "@type" : "Answer",
      "text" : "Not a dedicated, purpose-built renewal object out of the box. HubSpot offers a \"Recurring revenue deal type\" property (New business/Renewal/Upgrade/Downgrade) and, with a Revenue Hub subscription, renewal quotes generated from contracts — but HubSpot's own documentation recommends manually building a separate renewal pipeline with custom stages."
    },
    "name" : "Does HubSpot have a native renewal pipeline or deal type?"
  }, {
    "@type" : "Question",
    "acceptedAnswer" : {
      "@type" : "Answer",
      "text" : "Revenue Analytics — the built-in report that tracks new/existing/lost recurring revenue — requires Sales Hub Enterprise or Service Hub Enterprise. Auto-renewing contracts and renewal quotes require a Revenue Hub subscription and seat."
    },
    "name" : "What HubSpot tier do you need to track recurring revenue and NRR?"
  }, {
    "@type" : "Question",
    "acceptedAnswer" : {
      "@type" : "Answer",
      "text" : "Not necessarily for early-stage teams — a well-built renewal pipeline, health-score property, and workflow automation in HubSpot can cover the basics. Dedicated CS platforms add purpose-built health scoring, usage-data ingestion, and playbook automation that HubSpot doesn't natively provide, and they integrate with HubSpot via bidirectional sync rather than replacing it."
    },
    "name" : "Do you need a separate customer success platform if you use HubSpot?"
  }, {
    "@type" : "Question",
    "acceptedAnswer" : {
      "@type" : "Answer",
      "text" : "Waiting until the renewal date is close to start expansion conversations, and having no single clear owner — AM, CS, or Sales — for expansion-stage deals, both of which cause expansion revenue to get missed or renewal risk to surface too late to act on."
    },
    "name" : "What's the most common mistake teams make with NRR-driven renewal motions?"
  } ]
}
```