Deal Value Tracking for Retainer and Project Pipelines

Choose one source amount before weighting

Every open opportunity needs one amount that represents the commitment being sold. The Mautic deal value reporting guide covers the reporting discipline around currencies, missing values, and summing each deal once. The business-model rule comes first: calculate a retainer from its monthly amount and term, but take a project's current fixed scope amount directly.

Keep that source amount separate from the weighted planning view. Probability changes how much of the open pipeline enters a forecast calculation; it does not create another deal value. A raw total and a weighted total are two views of the same opportunities, so adding them together counts the pipeline twice.

This post handles the retainer-versus-project split. The deal value tracking worked example shows the arithmetic across a sample pipeline, while the deal value numbers founders track first explains which readings deserve attention. Here, the question is narrower: what amount should enter those calculations for each business model?

Retainer rule: monthly amount times one expected term

For a retainer, multiply the monthly amount by one explicit initial term. Use the committed term when the proposal or agreement supplies it. When it does not, choose a documented expected-term policy for comparable opportunities and label that term as an assumption. Do not substitute an imagined customer lifetime; the amount should describe the opportunity the team is evaluating now.

The monthly amount remains an input, not a second contribution to pipeline value. A future renewal becomes a new deal when it represents a distinct buying decision for a non-overlapping term. Until then, adding a renewal estimate to the initial term would count the same relationship beyond the commitment currently being sold.

Project rule: use the current fixed scope amount

For a one-off project, use the fixed amount attached to the current scope. Update that amount when the proposal changes before the decision. Deposits, invoices, and delivery milestones usually describe when one project is paid or completed; they do not create extra opportunity value.

Split work into separate deals when each part can be purchased, won, or lost independently. If a single proposal combines a retainer and a project, either use one source amount built from non-overlapping components or use independently winnable deals without an amount-bearing umbrella record. In either structure, each unit of value enters the pipeline once.

Keep both models honest in one pipeline

A mixed pipeline can support one sales process if the stages describe comparable buying decisions. It still needs model-specific reporting. Label each deal as a retainer or project using a convention your team can apply consistently, then preserve these boundaries:

• One source amount per deal. Do not add a retainer's monthly input to its initial-term total, or a project's milestones to its fixed scope total.
• One currency context per subtotal. Convert or separate currencies before adding amounts; a bare blended number hides the unit being counted.
• Probability applied once. Keep the source amount raw and calculate the weighted view from it. Do not store an already weighted amount and weight it again.
• Renewals without overlap. Create a renewal opportunity when a new decision begins, not merely because the current retainer may continue.
• Raw and weighted views stay separate. Compare them, but never add them.

The two hypothetical deals above can appear in the same board, but their monthly input, source amount, and weighted view answer different questions. A combined source-amount or weighted subtotal is usable only after each deal contributes once and every value shares the same currency. Label that blend as finite-commitment value, keep each retainer's term basis visible, and never treat the result as monthly run rate.

Review one operating number for each model

For retainers, review stage-weighted open initial-term retainer value. Multiply each open retainer's source amount by its current stage probability, then add those weighted amounts. Keep the term basis beside the subtotal so a policy change cannot quietly inflate or shrink the reading.

For projects, review stage-weighted open fixed-project value. Multiply each open project's fixed scope amount by its current stage probability, then add the results. Keep expected close dates visible as a separate timing check rather than silently changing which deals enter the metric.

These are two labeled weekly readings built with the same weighting method but different source-amount rules. The Mautic sales forecasting guide explains the open-deal formula and the checks that keep probability, close timing, and currency visible. Treat both results as planning signals, review them separately, then inspect the deals that changed each subtotal.

Frequently asked questions

What term should I use to value a retainer deal?

Use the initial committed term when the agreement defines one. Otherwise, use one documented expected-term policy across comparable deals, label it as an assumption, and revise the policy separately from individual opportunities.

Should monthly retainer value and initial-term value both enter the pipeline total?

No. Monthly value is an input to the retainer calculation, while initial-term value is the deal's source amount. Adding both would count part of the same opportunity twice.

Should project milestones be separate deals?

Not when they are payment steps inside one already-scoped purchase. Create separate deals only when each piece is a separate buying decision that can be won or lost on its own.

Can retainer and project deals share one pipeline?

Yes, if every deal has a clear model label, one source amount, one currency context, and stage probability applied once. Review the models separately before using any blended total.

Which single number should each model review weekly?

For retainers, review stage-weighted open initial-term retainer value. For projects, review stage-weighted open fixed-project value. Both calculations weight the deal's source amount once.