Mautic CRM in Practice: Three Pipeline Setups

Know the automation boundary

Deal Flow adds pipelines, stages, deal amounts, and multi-contact relationships inside Mautic. Moving a deal queues the outbound deal.stage_changed event through Mautic’s webhook system. A configured endpoint can receive that event and decide what happens next.

Deal stages and Mautic contact stages remain separate; Deal Flow does not automatically map or copy one to the other. The automation examples in the tables are therefore receiver-side patterns, not native campaign actions. This boundary keeps the pipeline model clear and prevents a worked example from promising behavior the plugin does not provide.

Setup 1: a four-stage SaaS new-business pipeline

A founder-led SaaS team usually needs a short board that distinguishes interest from evidence. Create a pipeline named SaaS New Business and use an illustrative value of $12,000 for one annual contract. The value stays with the deal as it moves; the stage records progress, not a new valuation.

Four stages are enough when one person owns most follow-up. If the team cannot name a different decision between two columns, combine them. The Mautic CRM setup guide covers the broader choices around contacts, deals, and pipeline structure.

Setup 2: split agency acquisition from renewal

An agency can separate the promise of new work from the decision to continue existing work. Use New Retainer for acquisition and Retainer Renewal for the later review. Illustrative values might be $36,000 for a new engagement and $48,000 for a renewal; choose one value convention and document it for everyone entering deals.

The split makes each board easier to read and keeps renewal timing from distorting new-business work. For more detail on the second board, use the Mautic renewal pipeline stage design.

Setup 3: long-cycle B2B with a buying committee

A long-cycle deal needs both process state and relationship context. Create a pipeline named Enterprise New Business, use an illustrative deal value of $180,000, and associate the relevant Mautic contacts with roles such as Champion, Decision Maker, Technical Evaluator, Budget Holder, and Influencer. The labels explain how each person participates without forcing the relationship into one primary-contact field.

Review the contact roles at every material stage move. A deal can advance while a key relationship remains unknown; keeping roles beside the deal makes that gap visible. The overview of Mautic CRM architectures helps place this pipeline pattern within a wider operating model.

Choose the smallest setup that preserves the decision

Start with the motion, not a universal stage list. Use the SaaS board when speed and a shared next step matter most, the agency split when acquisition and renewal run on different clocks, and the B2B board when several people shape a long decision. Name each stage after evidence your team can observe.

Then configure the outbound webhook endpoint deliberately. Decide which systems need the event, what each receiver does, how failures are monitored, and who owns corrections. The pipeline remains the operating record while the integration boundary stays explicit.

Frequently asked questions

Can one Mautic CRM setup use multiple Deal Flow pipelines?

Yes. Use separate pipelines when the stage language, ownership, or operating rhythm differs. Keep one pipeline when the same stages and decisions apply to every deal.

Do Deal Flow stages sync automatically with Mautic contact stages?

No. Deal Flow stages and Mautic contact stages remain separate. Moving a deal queues the outbound deal.stage_changed event through Mautic’s webhook system; a configured endpoint can use that event to coordinate another system.

What does the example deal value represent?

It is the amount your team chooses to track on the deal, using the deal’s currency. Decide whether that means contract value, annual value, or another consistent measure before comparing pipeline totals.

Can a buying-committee role use the team’s own wording?

Yes. A deal can associate multiple Mautic contacts, and each association can carry a free-text role such as Champion, Decision Maker, Technical Evaluator, Budget Holder, or Influencer.