Mautic Pipeline Stages Should Follow Buyer Evidence

Why we are stating the rule now

This post records the pipeline-design rule we are using in September 2026: a stage is a claim about the buyer’s position, so the team needs evidence before it moves a deal. Templates can supply useful names, but they cannot decide which transitions matter in a specific sales motion. That decision belongs to the people who can define what changed for the buyer and what the team can now do differently.

Making the rule explicit matters because a polished board can still hide inconsistent judgment. If one person moves a deal after a promising call and another waits for a confirmed evaluation, the column total combines two different realities. Better labels will not fix an undefined boundary.

How many stages should a pipeline have?

Use the fewest stages that preserve meaningful changes in buyer state. There is no universal count. A longer sales process does not automatically need more columns, and a short process is not improved by compressing distinct commitments into one label.

Start with the moments after which the team’s options change. Merge adjacent stages when they use the same proof, prompt the same next action, and mean the same thing in a review. Split a stage when it contains buyers with materially different commitments or requires different work to move forward. Keep outcome states such as won and lost separate from active progress so the board does not confuse work in motion with a finished decision.

A good boundary records buyer evidence

A seller activity is not automatically a stage boundary. Sending an email, holding an internal forecast meeting, or feeling optimistic says what the team did or believes. A useful boundary records something observable about the buyer: the problem was confirmed, evaluation participants were named, requirements were accepted, commercial terms were reviewed, or a decision was recorded.

The evidence should be easy to point to. It might be a reply, a meeting outcome, an approved evaluation plan, a requested proposal, or a signed decision. The exact artifact depends on the sales motion. The standard does not: another operator should be able to inspect the record and reach the same stage decision.

This does not mean every buyer action deserves a column. A new stakeholder joining may change the work without changing the opportunity’s position. Record the stakeholder and the next task, then move the deal only when the evidence for the next boundary exists.

Write entry and exit criteria together

Define every active stage with both an entry criterion and an exit criterion. The entry criterion explains why the deal belongs here now. The exit criterion names the evidence required to leave. Writing both exposes gaps that a stage name alone can hide.

• Discovery: enter when the buyer confirms a problem worth examining; exit when the buyer agrees on the people, questions, and next evaluation step.
• Evaluation: enter when that evaluation has a defined scope; exit when the buyer confirms fit and asks to review a commercial path.
• Decision: enter when commercial terms are under review; exit when the buyer records an acceptance, a rejection, or a specific unresolved condition.

These are examples, not required labels. Replace them with language your team and buyers use. Keep the test strict enough that a deal cannot advance merely because someone completed a seller-side task.

Map contact stages and deal stages by responsibility

A Mautic contact stage describes one person’s lifecycle. A Deal Flow pipeline stage describes one commercial opportunity. Those levels may influence each other, but they are not interchangeable.

Consider a person who is ready for sales conversation while the opportunity they joined is still being evaluated. The contact’s lifecycle can reflect that person’s readiness; the deal remains in the buyer-evidence stage shared by the opportunity. The reverse can also happen when a deal reaches a decision while a newly added evaluator is still early in their relationship with the organization.

This separation matters because one contact can participate in different deals, and one deal can include several contacts. Define contact-stage changes around person-level lifecycle signals. Define Deal Flow stage changes around opportunity-level evidence. Then document any coordination rule as a deliberate handoff instead of assuming the two labels must always match.

Test the stage set before treating it as policy

Take a sample of current opportunities and ask two operators to place each one using only the written criteria. When they disagree, inspect the boundary rather than averaging their opinions. The evidence may be unclear, two stages may overlap, or the record may be missing a fact the team needs.

Revise the criteria until the same evidence produces the same placement. That consistency makes stage totals, review conversations, and next actions more useful because each column carries a shared meaning.

Frequently asked questions

How many stages should a Mautic sales pipeline have?

Use the fewest stages that describe distinct changes in the buyer’s position. Merge adjacent stages when they rely on the same evidence, and split a stage when it contains meaningfully different buyer commitments that require different work.

What makes a good pipeline stage boundary?

A good boundary is crossed when the buyer does something observable, such as confirming a problem, agreeing to an evaluation, reviewing commercial terms, or recording a decision. A seller’s confidence by itself is not evidence.

How do Mautic contact stages differ from Deal Flow pipeline stages?

A Mautic contact stage describes one person’s lifecycle. A Deal Flow pipeline stage describes one commercial opportunity, which can involve several contacts, while one contact can participate in different deals.