Start with the board’s point-in-time numbers

Deal Flow’s kanban stage headers show the deal count and total amount in each stage. Both figures describe the board now. The count answers how many deals currently sit in that stage; the raw stage total answers how much recorded deal value sits there before probability weighting.

These numbers show inventory, not movement. A stage with eight deals today does not tell you how many deals entered, advanced, or left during the week. Pipeline Summary and Stage Coverage provide the same useful grouping by current stage: both organize count and value, while the board keeps those figures beside the deals themselves.

Snapshot rule: Use stage counts and raw stage totals to describe where deals and value sit at the time you look. Do not label either number a conversion rate.

Sources: the Deal Flow changelog for stage-header counts and totals, Deal Flow Reports for Stage Coverage, and dashboard widgets for Pipeline Summary, checked September 2, 2026.

Keep raw stage totals separate from weighted forecast

Raw stage totals use the full recorded amount of the deals currently in each stage. The weighted forecast applies the configured probability of each deal’s current stage, then sums the probability-adjusted contributions from open deals.

Weighted forecast = sum(open deal amount × stage probability)

Read the two views side by side. Raw stage totals show concentration at the current stage. The weighted forecast shows the same open deals after stage probability is applied. A change in either number is a prompt to inspect the contributing deals, not a substitute for that review.

See Sales Forecasting in Mautic for the formula and review cadence. See Mautic Deal Value Reporting for the boundaries between deal amounts, per-stage totals, and downstream calculations.

Source: Deal Flow Reports, checked September 2, 2026.

Calculate stage conversion from movement, not board counts

Stage conversion needs a time boundary and dated movement. For a weekly reading, define the group of deals that entered a stage and the period in which you will observe their outcomes. For that same group, divide the number that advanced from the stage by the number that entered it. State the group, observation period, and treatment of closed-lost deals beside the result so the next review uses the same definition.

Stage conversion = deals that advanced ÷ deals that entered for one defined group and observation period.

Do not divide this week’s count in one column by this week’s count in the next column. Those point-in-time inventories can contain different deals from different periods. Record the stage-entry and advancement events in the review record or reporting tool your team uses, then calculate the rate from those matched events.

Trace a stalled number back to its deals

A flat or worsening figure tells you where to look, not why it happened. Open the records behind the number and test the inputs before changing a stage definition, probability, or team process.

Figure What it says What to inspect when it stalls
Stage countCurrent deals in one stageStage accuracy, recent movement, ownership, and the next task on each deal
Raw stage totalFull recorded value in one stage nowMissing or changed amounts, stage placement, and whether one large deal drives the result
Weighted forecastOpen amounts adjusted by stage probabilityOpen status, current stage, amount, and the configured probability for each contributing deal
Stage conversionMovement for one defined group and periodEntry and advancement dates, loss treatment, observation window, and consistent definitions

Deal Flow’s board health indicators use days in stage and configured thresholds. Use that health signal to find deals that deserve inspection, then ask whether the stage is still accurate, what the next task is, who owns it, and what evidence supports moving it. The team remains responsible for the decision.

For a full meeting sequence, follow the weekly sales pipeline review.

Source: Deal Flow risk-threshold documentation, checked September 2, 2026.

Use the same reading order every week

  1. Capture the stage snapshot. Read the deal count and raw total in every stage at the same point in the weekly cadence.
  2. Compare the weighted view. Note which open deals and stage probabilities explain the change in weighted forecast.
  3. Calculate movement separately. Use matched stage-entry and advancement events for the defined group and period.
  4. Inspect stalled records. Review days in stage, amount, owner, next task, and whether the recorded stage still matches the sale.
  5. Record the decision. Assign the next action and update a deal only when its underlying facts changed.

This order prevents one number from carrying more meaning than it has. Inventory describes the current board, weighted value applies a probability model, conversion describes movement, and record-level review explains what the team should do next.

Put weekly pipeline numbers beside the work

Deal Flow keeps deal records, stage views, tasks, and documented reporting surfaces inside Mautic.

See Deal Flow Pricing

Sources checked September 2, 2026

Frequently asked questions

Which Mautic sales pipeline numbers should I review each week?

Review the deal count and raw total in each stage, the weighted forecast, stage conversion for a defined period, and days-in-stage health. Each answers a different question.

Do board stage counts show stage conversion?

No. A board stage count is a point-in-time inventory. Stage conversion needs a defined period and separate counts for deals that entered the stage and deals that advanced from it.

How is the weighted forecast calculated?

The documented formula is the sum of each open deal amount multiplied by its stage probability. Read it beside raw stage totals, not as a replacement for them.

What should I do when a pipeline number stalls?

Inspect the deals behind the number. Check stage accuracy, days in stage, the next task, ownership, amount, and whether the deal moved during the review period before changing the process.