The renewal date is approaching, someone checks the CRM and realises the original champion has moved roles, finance hasn’t been involved and, while the customer has adopted part of the platform, nobody has pulled the value story together.

B2B SaaS teams should manage renewals as an ongoing process that connects the customer's original goals with evidence of progress, current stakeholders, product adoption, outstanding risks, future priorities and a clear shared renewal plan. Renewal preparation should begin well before the contract end date, so commercial decisions do not depend on a last-minute conversation.

Trumpet can provide the customer-facing workspace for the renewal process, bringing shared goals, stakeholder context, relevant content, Mutual Action Plans, value evidence and commercial resources into one personalised Pod.

What is the SaaS renewal process?

The SaaS renewal process is the structured set of activities used to evaluate customer value, confirm future requirements, coordinate stakeholders, address risk and agree whether and how the subscription will continue.

When should renewal planning begin?

There is no universal number of weeks or months that fits every account. Timing depends on contract value, the customer's procurement process, customer size, the complexity of internal approval, notice periods, security requirements, recent commercial change and the number of stakeholders involved.

Renewal planning should begin early enough to resolve value, stakeholder and commercial questions before contractual deadlines force the conversation.

Start with why the customer bought, and what has changed since

Before looking ahead, it helps to return to the original problem, the business case, the desired outcomes, the success criteria, the stakeholders involved and the value the customer expected. Four questions are worth asking directly: what changed, what was achieved, what remains, and what matters now.

Answering those honestly is what builds the renewal case: the original objectives, progress against them, adoption, outcomes, customer feedback, key milestones, new use cases and any business changes since the contract started.

Product usage, meaning which features are actually being used, typically lives in a product analytics tool or the CS platform. Workspace engagement, meaning how stakeholders interact with shared renewal content inside a Pod, is a different signal that adds colour to the picture rather than replacing it. Pulling the two together into a convincing value-based narrative is what turns a list of features used into a reason to keep paying for them.

Identify the renewal stakeholders

Depending on the account, a renewal may involve the champion, an executive sponsor, finance, procurement, legal, end users, a technical owner, and sometimes new decision-makers who were not part of the original purchase.

Stakeholders can change over the life of a contract. The person who originally bought the product may not own the renewal, and assuming otherwise can leave important decision-makers out of the renewal process.

Trumpet example

Within an existing Pod, the Org Chart shows known stakeholders, their roles and their engagement, and Scout AI can then help identify possible gaps in the stakeholder map. That is a useful starting point for re-confirming the buying group ahead of a renewal, not a substitute for simply asking the customer who else should be in the room.

Create a shared renewal plan

A Mutual Action Plan gives the renewal a structure both sides can see. Typical milestones include a value review, stakeholder confirmation, future requirements, commercial review, a security review where needed, procurement, legal, approval and signature.

Every step on the plan needs an owner, a date, a status and, where relevant, a dependency on an earlier step. A plan without these is a list of intentions rather than a working renewal process.

Within trumpet, a renewal Mutual Action Plan can sit inside the customer's existing Pod, so milestones, responsibilities and target dates appear alongside the content and commercial information already there, rather than in a separate document nobody opens.

What should a renewal workspace include?

A renewal workspace is more useful when it brings the following together in one place:

• Original objectives
• Current success measures
• Value recap
• Usage and adoption evidence
• Customer resources
• Stakeholder information
• Renewal MAP
• Commercial information
• Product roadmap information, where appropriate
• New use cases
• Next steps
• Relevant documents

Trumpet example

An existing Pod, set up during the original sale and carried through onboarding, can evolve into the renewal workspace rather than starting from a blank page. The same space that already holds historical content and stakeholder context can take on a renewal MAP and updated commercial resources as the contract approaches its end date.

How to identify renewal risk

A number of signals are worth watching, including the original champion no longer being involved, an absent executive sponsor, an unclear value story, product adoption issues, repeatedly delayed milestones, procurement not yet engaged, changed business priorities, commercial objections, and low customer engagement.

No single signal predicts churn on its own. These are reasons to look closer, not conclusions in themselves.

Renewal engagement vs product adoption

Using several evidence sources together gives teams a broader understanding of the renewal than any single signal. A dedicated CS platform is typically the right place for product usage and health scoring; a Pod adds the customer-facing engagement layer alongside it, not instead of it.

Preparing for the commercial conversation, and where expansion fits

Before the commercial conversation itself, it helps to have a clear view of value delivered, current scope, future needs, pricing, contract structure, procurement requirements and the approval process.

At TestGorilla, account manager Will Spilsbury picks up the Pod created by the account executive during the original sale, then builds it out with the pricing, roadmap updates and ROI stories the customer will need come renewal time. “With trumpet, I can collate everything that’s relevant to a client in one singular place. Instead of asking them to refer back to an email or search for a quote, it’s all there, neatly presented,” he says. That same workspace also made it easier to see which stakeholders were engaging with new content, which is a reasonable place to start a genuine expansion conversation.

Expansion sits naturally alongside a renewal conversation, but it should come from something real: new needs, new teams, new use cases, proven value or a change in the customer's business. Expansion should follow a genuine customer need, not simply coincide with the renewal date.

Customer renewal checklist

Early renewal planning

• Confirm the renewal date and notice period
• Identify who owns the renewal internally
• Review the original business case and success criteria

Value review

• Pull together adoption and outcome evidence
• Gather customer feedback and recent milestones
• Note any new use cases since the contract started

Stakeholder review

• Confirm the current champion and executive sponsor
• Identify any new decision-makers
• Check procurement and legal requirements

Commercial preparation

• Prepare pricing, scope and contract structure options
• Flag any genuine expansion opportunity
• Confirm the internal approval process

Final approval

• Complete security or legal review if required
• Secure internal sign-off
• Confirm signature process and timeline

Post-renewal

• Record updated objectives for the next term
• Update the shared plan and stakeholder record
• Carry the value story forward rather than starting again

Common SaaS renewal mistakes

• Starting too late
• Only talking about price
• Failing to prove value
• Relying on the original champion
• Ignoring procurement
• Treating product usage as the entire customer story
• No shared renewal plan
• Keeping the renewal process internal
• Introducing expansion without a customer need
• Losing historical context

How trumpet supports customer renewals

One customer-facing workspace can carry the relationship from the first sales conversation through to renewal. Trumpet's Pod carries over from the original sale into onboarding and account management, so the stakeholders, content, agreed objectives and Mutual Action Plan built earlier in the relationship are still there when renewal planning starts, rather than the team beginning again from nothing.

Trumpet connects sales, onboarding, customer success and renewal around that same workspace.

Stakeholders: the Org Chart built up earlier in the relationship keeps reflecting who is currently involved, which matters given how often this changes before a renewal.

Content and commercial resources: value evidence, customer resources, roadmap information, pricing and proposals can live in the same place the customer already uses, rather than scattered across email.

The renewal plan: a Mutual Action Plan sitting inside that same Pod gives both teams shared milestones, owners and dates.

Engagement: trumpet's Digital Sales Rooms let teams see how customers interact with shared content, including which renewal assets are getting attention.

By bringing value evidence, stakeholder engagement, commercial resources and a shared renewal plan into the existing Pod, trumpet gives both teams a customer-facing space to manage the renewal together.

See how trumpet turns customer renewals into a shared, ongoing process.

Book a demo.

Final thoughts

The best renewal conversations should not require the customer or CSM to reconstruct a year of value in the weeks before the contract expires.

A renewal built on continuity, where the original goals, stakeholders and value story are still visible, is a very different conversation to one that starts from a blank page a few weeks before the deadline.

FAQs

What is a SaaS renewal process?

It is the structured set of activities used to evaluate customer value, confirm future requirements, coordinate stakeholders, address risk and agree whether and how a subscription will continue.

When should SaaS renewal planning begin?

There is no fixed timeline that fits every account. It depends on contract value, procurement complexity, customer size, notice periods and the number of stakeholders involved, but planning should begin early enough that value, stakeholder and commercial questions are resolved before the contractual deadline forces the conversation.

What is the difference between renewal engagement and product adoption?

Product adoption shows how the product is actually being used, and typically comes from product analytics or a CS platform. Renewal engagement shows how stakeholders interact with shared renewal content in a workspace such as a Pod. Both are useful, and neither tells the full story alone.

How does trumpet support customer renewals?

Trumpet's Pod carries over from the original sale into onboarding and account management, so the stakeholders, content, agreed objectives and Mutual Action Plan built earlier in the relationship are still there when renewal planning starts.