How Do You Run a Weekly Sales Pipeline Review in Mautic?

Use one stage-by-stage agenda every week

Run a weekly pipeline review stage by stage. Start with every open deal on the board, apply your team’s aging threshold to deals that need scrutiny, confirm one owned next task and due date, compare raw stage totals with the weighted forecast, and check that the important buying roles are represented. Finish by recording each decision and moving a card only when the sale’s current stage has changed.

Deal Flow provides the documented stage board, deal-linked task record, forecast views, and role-labeled contacts used in this agenda. The weekly sequence itself is an operating practice: your team defines its aging threshold, decides which deals need deeper discussion, and owns the decisions made in the review.

Prepare the review around current deal records

Choose the pipeline the team will review and make sure owners are ready to confirm each deal’s current stage, amount, next task, and involved contacts. Core Mautic remains the contact and engagement layer; the separate deal record holds the sale’s pipeline stage, work, and stakeholder relationships. The Mautic sales guide explains that handoff and the boundaries between the two records.

1. Select the pipeline. Review one named sales process at a time so its ordered stages provide the agenda.
2. State the aging rule. Agree on the human-defined condition that earns extra scrutiny before anyone starts judging individual deals.
3. Bring the forecast inputs. Amount and current stage must reflect the team’s present view before raw or weighted totals can be useful.
4. Keep updates close to the record. Make stage, task, and role decisions while the deal is being discussed.

Walk the board from the first stage to the last

Deal Flow’s board represents ordered pipeline stages as left-to-right columns and deals as cards. A card sits under its current stage; dragging it to another column changes the saved stage. Use that layout as the review order, moving through every column rather than jumping straight to the largest deals. The Mautic kanban board guide documents the stage order, card placement, and drag-and-drop behavior.

1. Read the stage name. Restate what the stage means in the team’s process before reviewing its cards.
2. Check each card against reality. Ask whether the deal still belongs in that stage based on the sale’s current state.
3. Move only when the stage changed. A board move updates the deal stage, so use it to record a decision rather than to signal attention.
4. Leave with the board current. Complete the column before moving the agenda to the next stage.

Review aging deals with a human-defined rule

Aging is a management rule in this review, not an automated product claim. The five shipped guides used as sources for this page do not document an automatic deal-age calculation, age-in-stage threshold, or aging alert. Define the condition yourselves, apply it consistently, and ask the owner to explain what changed, what remains unresolved, and whether the recorded stage is still accurate.

For every deal that meets the team’s rule, choose a concrete outcome: keep the current stage and update the next action, move the deal because its state changed, or take the separate action your sales process requires. The threshold and outcome criteria belong to the team; the board records the stage decision.

Confirm one accountable next task

The documented DealTask record keeps a task attached to its deal and includes a title, status, priority, due time, owner, and deal relationship. During the review, confirm that the next action still advances the current stage, its owner is clear, and its due date remains realistic. When the decision changes the follow-up, update the same task record. The Mautic sales tasks guide documents the fields and this review pattern.

If the decision needs supporting context, preserve that explanation as a deal note instead of hiding it inside a task title. The shipped task guide treats tasks and notes as separate deal-associated resources. It also does not document automatic reminder delivery from task date fields, so this agenda reviews the recorded next action without assuming an alert will be sent.

Compare raw pipeline value with the weighted forecast

Read the two forecast views separately. Raw stage totals show the full deal value recorded in each stage. The weighted forecast multiplies each open deal amount by its stage probability and adds those contributions. The first view answers where full pipeline value sits; the second applies the stage-probability model. The Mautic sales forecasting guide documents both views and the calculation.

1. Check the inputs first. Confirm that open deals have current amounts and stages before reading either number.
2. Read raw stage totals. Look for concentration and for values that no longer match the deal discussion.
3. Read the weighted view. Use the probability-adjusted result as a separate model of the same open deals.
4. Resolve inconsistencies on the records. Correct stale inputs instead of explaining away a total that rests on an outdated amount or stage.

Map buying roles on the deals that matter

For deals the team chooses for deeper review, confirm which Mautic contacts are attached and how their roles are labeled. Deal Flow documents Champion, Decision Maker, Budget Holder, Technical Evaluator, and Influencer labels, plus custom roles. The Mautic buying committee guide shows how those role labels stay on the deal.

• Champion: Is the person pushing internally visible on the deal?
• Decision Maker and Budget Holder: Has the team identified the relevant authority and budget role without assuming they are the same person?
• Technical Evaluator: Is the person validating fit represented where that role matters?
• Influencer or custom role: Does the deal need another label that matches how this buying process works?

This is a coverage check, not a requirement that every deal carry every built-in role. Record the people and labels supported by what the team actually knows, then make any missing relationship an explicit follow-up rather than an invented contact.

Finish with a recorded decision for every reviewed deal

A useful review changes the records that were discussed. Before leaving a deal, state its resulting stage, whether it met the team’s aging rule, its next task and owner, whether its amount and stage support the forecast inputs, and which buying roles need follow-up. If the decision needs explanation, put that context in a deal note.

• The board reflects the current stage decision.
• The next task names the action, owner, and due date.
• Raw value and weighted forecast remain separate.
• Known buying roles are attached to the deal.
• Any gap becomes a named follow-up rather than an assumption.

Continue with the source guides

• Use Mautic for Sales for the contact-to-deal handoff and practical sales workflow.
• Use the Mautic Kanban Board guide for ordered columns and stage movement.
• Use Mautic Sales Tasks and Deal Follow-Ups for the deal-linked task record.
• Use Mautic Sales Forecasting for raw totals and weighted forecast math.
• Use the Mautic Buying Committee guide for stakeholder role labels.

Sources

Product behavior cited on this page was checked 2026-09-01 against these five shipped guides.

• Mautic for Sales — contact and deal boundaries, ordered stages, deal tasks, and buying-role associations.
• Mautic Kanban Board — stage columns, deal cards, and drag-and-drop stage changes.
• Mautic Sales Tasks and Deal Follow-Ups — task fields, deal association, and review cadence.
• Mautic Sales Forecasting — raw stage totals, open-deal inputs, and weighted forecast calculation.
• Mautic Buying Committee — contacts attached to deals with built-in and custom role labels.

Frequently asked questions

What belongs on a weekly sales pipeline review agenda?

A weekly sales pipeline review should cover each board stage, deals meeting the team's aging rule, deal-linked next tasks, raw and weighted forecast views, and buying-role coverage. End with a recorded decision for every reviewed deal.

Does Deal Flow automatically flag aging deals?

The five shipped guides checked for this page do not document an automated deal-age or age-in-stage flag. Define the threshold as a team rule and apply it manually in the review.

What is the difference between raw pipeline value and a weighted forecast?

Raw pipeline value is the full amount recorded across open deals or within a stage. A weighted forecast multiplies each open deal amount by its stage probability and adds the results. Keep both views separate because they answer different questions.

Which buying roles should the review check?

Review the Champion, Decision Maker, Budget Holder, Technical Evaluator, and Influencer labels, plus any custom roles your process uses. The goal is to make the relevant people and their roles visible on the deal before the team relies on its next-step or forecast assumptions.