Hi @CarolinaDeMares! I love it when we, as active members, have great questions and turn to each other for help. Proof that Community really is helpful and smart. So here’s what I’m thinking. First, I agree that your approach is logical. I think it works overall. Something I found in research is that there’s a suggestion that the behavior in HubSpot depends on whether you’re using subscriptions only, or the newer contracts object alongside them (which is in beta right now, but may help in the future). For your use case, I’d strongly consider tracking the customer lifecycle on contracts and using subscriptions only for recurring billing/billing-adjacent automation, because HubSpot says contracts are the central source of truth for committed revenue, mid-term changes, and renewals.
Now, since I presonally don’t have Contracts as an object, so I’m not sure what your client has, here’s what I’d look at if it were me. First I’d think about the best tracking set up. So, for tracking contract changes and upsells over time, I’d use this pattern:
- Original sale: initial deal + quote + created contract/subscription.
- Renewal: separate renewal deal + renewal quote + new renewal contract.
- Expansion/upsell: separate expansion deal + change quote + contract history.
- Reporting: use contract properties/history as the source of truth for ARR, term, and amendments.
That structure gives you a clean audit trail, avoids overloading the original deal, and makes customer success workflows much easier to manage. It also aligns with HubSpot’s recommendation to use separate pipelines for renewal and change quotes.
I do want to come back to the renewals question, based on how I’ve seen HubSpot work, and the questions I’ve seen here in Community. If I’m understanding your question + set up, renewals aren’t automatically handled. Here’s my understanding: Your current model is Commerce Hub + subscriptions, no invoices/payments, no Contracts object. This would mean renewals are not natively automatic in the CRM. You have two layers:
- First, subscription auto‑renewal (if enabled)
- If you turn on auto‑renewal on a subscription, HubSpot will automatically renew that subscription on the same terms the day after the current term ends.
- This is a billing‑system behavior, not a CRM deal behavior.
- You can disable this so the subscription just stops at term end.
- Number two, commercial “renewal” = a new deal
- HubSpot will not automatically create a new deal when the subscription’s renewal date is reached.
- If you want a renewal opportunity in the pipeline, that must either be:
- created manually, or
- created by a workflow triggered off your Renewal date or Contract end property on the deal.
So, will a new deal be automatically created? No, not out of the box. However, with Commerce Hub and workflows, you can get very close to “automatic.” You can create a date‑based workflow that enrolls deals when: Renewal date is N days away (e.g., 90 or 120 days).
Then, in that workflow, add an action to: Create a new deal (deal type = “Renewal”), associated with the same company, and copy key fields (e.g., renewal date, product line, MRR, ARR, assigned owner).
This is a very common pattern; articles and renewal‑playbook guides explicitly recommend “auto‑create renewal deals X days before contract end” using workflows.
More research brought up this idea, and I like it. I’d explore this within the set up. I’d even maybe use Hub Helper Harry in ChatGPT (shout out Nick Lafakis) to help structure it.
If a subscription is active and the customer adds an add-on mid-term, the expected behavior depends on how you process it:
- If you edit the subscription directly, HubSpot updates the subscription record, can notify the customer, and applies the change immediately or at the next cycle depending on proration.
- If you use a change quote, HubSpot updates the contract when the quote is accepted, and the contract history records the amendment.
So the practical answer is to your overall question is that direct subscription edits are the “billing object” behavior, while change quotes/contracts are the “commercial agreement” behavior. For a SaaS learning platform selling institutional agreements with packages, add-ons, and renewals, the contract-based approach is usually the better long-term operating model.
Based on this, if it were me, I wouldn’t rely on subscriptions alone as your system of record for renewals and upsells. Use quotes to initiate the sale, contracts to track the agreement lifecycle, and separate renewal/change deals to preserve pipeline visibility and reporting. Keep subscriptions only where you need recurring billing mechanics or subscription-style lifecycle actions, and confirm in your portal whether disabling invoicing limits the edit options you expect.
Hopefully this helps. It seems to me you’re on the right path. You’ll just need to think through some automation. And maybe look into the Contracts object in Commerce Hub.
