After building renewal pipelines for dozens of mid-market companies, we see the same mistakes over and over. Some cost thousands in missed renewals. Others slowly poison your data until nobody trusts the CRM. Given that retaining customers costs 5–25x less than acquiring new ones, these mistakes directly erode your bottom line.
Here are the 12 we see most often — and how to fix each one.
This article is part of our Complete Guide to Building a Renewal Pipeline in HubSpot.
Mistake 1: The Infinite Loop
What happens: Your workflow creates a Year 2 renewal deal when Year 1 closes as Won. Perfect. But when Year 2 closes as Won, nothing happens. Year 3 never gets created.
Why it happens: HubSpot’s re-enrollment protection prevents a deal from triggering the same workflow that created it.
The cost: Every multi-year customer stops getting automatic renewal deals after Year 1. Manual intervention is needed forever, and some renewals will be missed.
The fix: Use the boolean toggle pattern or the dual-workflow pattern. This is the #1 most common renewal automation issue — we wrote an entire article on fixing it.
Mistake 2: Mixing Deal Types in One Pipeline
What happens: New business, renewals, and expansions all live in the same pipeline with the same stages.
Why it happens: It feels simpler. “Why create multiple pipelines when we can just add a Deal Type property?”
The cost:
- Forecasts are meaningless (20% new business close rates mixed with 90% renewal close rates)
- Stage definitions don’t fit renewals (“Discovery” and “Demo” don’t apply)
- CSMs and AEs are working in the same pipeline with different processes
- Reports can’t cleanly separate revenue types without constant filtering
The fix: Separate your renewal pipeline. Even if you keep a Deal Type property (you should), dedicated pipelines with dedicated stages give you accurate forecasting, clean automation, and clear ownership.
Mistake 3: Starting Renewal Conversations at 90 Days
What happens: The first renewal touchpoint is 90 days before the contract expires.
Why it happens: 90 days feels like plenty of time. It’s a nice round number. Most automation guides use it.
The cost: For enterprise and mid-market contracts, 90 days is often too late. Budget cycles take 60–90 days alone. If the customer is unhappy, 90 days isn’t enough time to fix the relationship AND close the renewal.
The fix: Start the renewal motion at 180 days for contracts over $50K annually. Use the first 90 days (180→90) for health checks, QBRs, and relationship building. Use the last 90 days (90→0) for the actual renewal proposal and negotiation.
Mistake 4: No Churn Reason Taxonomy
What happens: When a renewal deal closes as Lost, the churn reason is either blank, “Other,” or a vague category like “Lost to competitor.”
Why it happens: Nobody set up the dropdown values, or the existing values are too broad to be useful.
The cost: You can’t analyze churn patterns. Was it pricing? Product fit? The champion leaving? Without structured churn data, every quarter’s churn is a surprise.
The fix: Create a specific churn reason dropdown with 10–12 values — including involuntary churn from payment failures, which Recurly’s research shows can account for up to 6% of total churn. Make it required when a deal moves to Closed Lost. Add a companion freeform text field for details. Review churn reasons quarterly. See the full taxonomy in our churn prevention guide.
Mistake 5: Revenue Double-Counting Across Pipelines
What happens: An expansion is reflected both as an increase in the renewal deal amount AND as a separate expansion deal. Revenue gets counted twice.
Why it happens: The CSM updates the renewal deal with the new higher amount, and then Sales creates an expansion deal for the same upsell.
The cost: Your revenue reports overstate reality. NRR calculations are inflated. Finance loses trust in CRM data.
The fix: Establish a clear rule: renewal deals reflect same-terms value only. Any increase goes to an expansion deal. Any decrease is tracked via contraction properties on the renewal deal. See our multi-pipeline architecture guide for the full framework.
Mistake 6: Treating Silence as Satisfaction
What happens: A customer hasn’t submitted a support ticket in 6 months, their CSM hasn’t talked to them in 3 months, and everyone assumes they’re happy.
Why it happens: No news feels like good news. Busy teams focus on the squeaky wheels.
The cost: The customer has been quietly evaluating alternatives. By the time the renewal conversation starts, they’ve already chosen a competitor. As Jason Lemkin notes, high NRR can mask this problem — a few large account expansions hide the fact that many smaller accounts are silently churning.
The fix: Build proactive health monitoring. Track email engagement, meeting frequency, QBR attendance, and product usage (if available). A customer who goes quiet is a customer who needs attention. Build health-based alert workflows that flag disengagement early.
Mistake 7: Using Sales Pipeline Probabilities for Renewals
What happens: Your renewal pipeline uses the same 10%/20%/40%/60% probability scale as your sales pipeline.
Why it happens: HubSpot defaults new pipeline stages to low probabilities. Nobody adjusts them for renewals.
The cost: Your renewal forecast chronically understates reality. A $2M renewal pipeline at “average 35% weighted probability” shows as $700K. The actual number is closer to $1.7M. Your CFO is planning based on the wrong number.
The fix: Set renewal stage probabilities to 80–95%. Calibrate quarterly against actuals. See how to fix your renewal forecasting.
Mistake 8: No Renewal Date Property (Using Close Date Instead)
What happens: Teams use the standard “Close Date” field for when they expect the renewal to close, not when the contract actually expires.
Why it happens: Close Date is a default HubSpot field. It’s right there. Why create another date?
The cost: Close Date represents when your team plans to close the deal. Renewal Date represents when the contract expires. These are different dates. Using Close Date for both means your time-based automations fire at the wrong time, and your “days to renewal” calculations are wrong.
The fix: Create a dedicated “Renewal Date” property. Use it for all time-based automation and reporting. Close Date remains the date the deal was actually won or lost. Both dates serve different purposes. See the full property setup guide.
Mistake 9: Ownership Confusion — Nobody Owns the Renewal
What happens: The AE thinks the CSM owns the renewal. The CSM thinks the AE owns it. The renewal deal sits untouched.
Why it happens: No clear handoff process from Sales to Customer Success. No documentation of who owns what in which pipeline.
The cost: Renewals slip through the cracks. Customers don’t hear from anyone. By the time someone notices, the contract has lapsed.
The fix: Define a written ownership model: “CSMs own all deals in the Renewal Pipeline. AEs own all deals in the Sales Pipeline.” Use automation to set the deal owner correctly when renewal deals are created. Build alerts for unassigned or untouched deals.
Mistake 10: Not Copying Line Items to Renewal Deals
What happens: Your workflow creates a renewal deal with the correct total amount, but no line items. The deal looks incomplete — there’s no record of which products or services are being renewed.
Why it happens: HubSpot workflows can copy deal properties but cannot copy line items. This is a platform limitation.
The cost: CSMs don’t know what the customer is renewing. Pricing errors when terms change. Manual re-entry is tedious and error-prone.
The fix: Use a third-party tool like CloneNer (copies line items automatically), build a Zapier/Make integration using the HubSpot Line Items API, or accept manual line item entry for low-volume renewals. This is the #2 most-requested HubSpot Ideas feature.
Mistake 11: Timing Collisions — Renewal Outreach During Open Support Issues
What happens: A customer has an unresolved critical support ticket. The automated renewal workflow sends them a “Time to renew!” email.
Why it happens: The renewal workflow doesn’t know about the support ticket. It’s operating on dates alone.
The cost: The customer feels unheard. The renewal email comes across as tone-deaf. An already-strained relationship gets worse.
The fix: Add a condition to your renewal workflows: If the associated company has open high-priority tickets, pause the renewal cadence and create a task for the CSM: “Resolve open tickets before renewal outreach.” Only resume the cadence after tickets are resolved.
Mistake 12: No Audit Trail — “Who Changed What and When?”
What happens: Deal properties change but there’s no record of why. The renewal amount decreased — was that a downgrade or a data entry error? A deal moved to Closed Lost — who made that call?
Why it happens: HubSpot logs property changes in the deal activity timeline, but nobody reviews it. There are no structured notes explaining why changes were made.
The cost: Disputes over deal data. Inability to learn from past renewals. No accountability when deals go sideways.
The fix:
- Require a “Renewal Outcome Notes” text field for any deal that closes (Won or Lost)
- Use “Revenue Change Reason” dropdown when amounts change
- Build a monthly report that flags deals where the amount changed by more than 10% — review these in team meetings
- For Enterprise users, configure audit logs for pipeline changes
Most automation mistakes start in the initial workflow setup — get that right and half these problems disappear.
The Meta-Mistake: Building Without a Plan
The biggest mistake isn’t any single configuration error. It’s building your renewal pipeline one workflow at a time without an overall architecture.
The teams that succeed start with:
- A clear ownership model (who owns which deals)
- A defined stage model (what stages mean and when deals move)
- A property setup (what data you’re tracking and why)
- An automation plan (which workflows and how they interact)
- A reporting plan (what metrics you’re tracking for which audience)
Then they build. In that order.
SWOTBee has seen all 12 of these mistakes — and fixed them — across mid-market companies in Energy, Manufacturing, SaaS, and more. If your renewal pipeline isn’t performing, we can audit it and build you one that works.
