Revenue operations desk with a wall of color-coded renewal cards

Subscription renewals with custom objects

Recipe / Customer lifecycle

Subscription renewals with a custom object.

The renewal should exist before the quarter it belongs to. A subscription record holds the date. A workflow creates the deal.

  • Function: Sales and Service
  • Hubs: Sales, Service
  • Complexity: native + object
A desk facing a wall of color-coded planning cards
Service lead who will see the same account

The problem

Renewal dates live in a billing tool, a spreadsheet, or an old deal’s close date. Sales finds out when finance asks why the invoice went out with no conversation.

HubSpot can remind and sell. It should not calculate usage invoices or act as the ledger. Push the renewal date in from billing. Let HubSpot open the commercial conversation.

Build steps

  1. 1

    Subscription object

    Start date, end date, ARR, product, status, billing system ID. Associate to company and to the original deal.

  2. 2

    Ninety-day workflow

    When end date is 90 days away and status is active, create a deal in a Renewals pipeline and copy the owner.

  3. 3

    Service visibility

    A ticket pipeline for at-risk renewals, associated to the same subscription, so support comments show on the deal.

  4. 4

    Close the loop

    Won renewal updates the subscription end date. Lost renewal sets status to churned. Do not leave both records alive with different dates.