Mautic Renewal Pipeline: Five Stages for Repeat Deals

A renewal is not the original sale again

A new-business pipeline asks whether a prospect will begin a commercial relationship. A renewal pipeline asks whether an existing customer will make another commitment, for which term, scope, and amount. Reusing discovery and first-purchase stages makes the board say less precisely what the team is waiting to learn.

Create a new renewal deal when the next decision becomes real work. Keep the original won deal closed so its history remains intact, then give the repeat decision its own owner, expected decision date, value, contacts, notes, tasks, and outcome. The renewal can involve the same company and people without pretending it is the same transaction.

A separate pipeline also makes stage age useful. A repeat deal waiting for a commercial response should not look identical to a first sale waiting for initial discovery. The names, entry conditions, and review questions can follow the actual renewal motion while the original acquisition record stays unchanged.

Use five stages with observable entry conditions

Our September 2026 stage set is Upcoming, Engaged, Negotiating, Committed, and Closed. The names are short because the operating definition belongs in the entry condition. The guide to customizing deal stages in Mautic covers the setup controls; use the following evidence rules for the renewal pipeline itself.

Committed and Closed are alternative terminal outcomes, not sequential steps. In this stage set, Committed carries the won type and Closed carries the lost type, so each finished renewal has one unambiguous result.

Value the term being renewed once

For a recurring retainer, multiply the monthly amount by one documented renewal term. That result is the deal's source amount. If the customer and seller are discussing a changed term or scope, update the documented inputs and the source amount together rather than carrying a stale value into the review.

Keep probability separate. A stage probability can produce a weighted planning view for open renewal deals, but it does not replace the source amount and should not be applied twice. The retainer and project deal-value rule explains this boundary in more detail.

The value should describe the decision represented by this deal. Do not add the original term, an imagined customer lifetime, or a later renewal that has not become a buying decision. One renewal record, one documented term, and one source amount keep repeat revenue legible.

Treat the stage-change webhook as a state signal

Deal Flow exposes the outbound event deal.stage_changed through Mautic's webhook system. Subscribe an endpoint to that event when another system should respond to a renewal move. The webhook documentation shows where to configure the subscription and the event payload.

The event reports that state changed; it does not own a reminder calendar. The receiving system must hold or look up the renewal date, map each stage to the right action, choose the delivery channel, and cancel obsolete reminders when the deal advances. That separation prevents an old Upcoming reminder from firing after the customer has entered Negotiating or Committed.

• On Upcoming, the receiver can create the renewal review sequence from its stored decision date.
• On Engaged, it can retire the opening prompt and create the owner follow-up tied to the customer's next step.
• On Negotiating, it can notify the owner that terms or approvals need attention.
• On Committed, it can stop negotiation prompts and hand the remaining task to contracting or administration.
• On Closed, it should cancel every open reminder for that renewal deal.

This makes the pipeline the source of current decision state and the receiving system the owner of timing and delivery. Test duplicate delivery, out-of-order events, and manual stage corrections before relying on the workflow.

Review evidence, value, and the next decision

A renewal review should expose exceptions rather than reconstruct every record. Ask whether the stage's entry evidence still exists, whether the amount matches the term under discussion, whether the expected decision date is current, and whether the next action belongs to a named owner or customer contact.

Do not move a deal to Committed on verbal confidence alone; require the team's documented win condition. Use Closed when that renewal term ends without a new commitment, stop the related reminders, and keep the record for the next repeat decision.

Frequently asked questions

Why should renewals use a separate pipeline?

A renewal is a new buying decision with different evidence from the original sale. A separate pipeline preserves the history of the won deal and gives the renewal its own owner, value, decision date, stage, and outcome.

What stages belong in a renewal pipeline?

Our current stage set uses Upcoming, Engaged, and Negotiating for open work, Committed for the won outcome, and Closed for the lost outcome. Each stage should have an observable entry condition tied to the renewal decision rather than a seller activity.

How should a team value a retainer renewal?

Multiply the monthly retainer amount by the documented renewal term to create one source amount. Keep stage probability separate and apply it once only when producing a weighted planning view.

Does a stage-change webhook schedule renewal reminders?

No. The deal.stage_changed event tells a receiving system that the deal moved. That receiving system owns the renewal calendar, reminder timing, delivery channel, and cancellation rules.