The agency pains this page is for
Priya's workflow is not one marketing team with one stack. It is many client environments, each with its own sending setup, reporting expectations, and people asking what marketing is doing for revenue.
Client reports stop at opens and clicks
The persona research is clear on the reporting gap: agencies can show activity metrics inside Mautic, but pipeline visibility is a separate problem because core Mautic has no deal record to hold stage, owner, amount, or close date.
Each client instance is isolated on purpose
Agency operators choose one instance per client to keep data, domains, and sending reputation separate. That protects client accounts, but it also means the pipeline layer has to work cleanly inside each instance instead of assuming one shared board.
Real client deals involve more than one contact
Agencies selling or supporting relationship-driven services rarely have one person attached to an opportunity. They need to keep the champion, decision maker, and other stakeholders tied to the same client deal without scattering context across separate contact records.
Persona source: this page uses Priya's vocabulary from the repo's persona research: one instance per client, clean client separation, and the gap between activity reports and pipeline questions.
How Deal Flow maps to those agency pains
This is not a generic features list. Each capability below exists because one of the pains above is structural in the way agencies run Mautic for clients.
Deal records and pipelines live inside each client instance
Deal Flow adds a native deal object with stage, owner, amount, currency, and expected close date, plus named pipelines and ordered stages. That gives the agency a real answer when a client asks what is moving, not just who clicked.
The plugin fits the per-client install pattern agencies already use
Deal Flow installs as a standard Mautic plugin in the client's own instance. It does not require a shared tenant, and it does not change the isolation pattern agencies rely on for client separation and deliverability hygiene.
Buying committee roles keep client stakeholders on one opportunity
One deal can hold multiple contacts, each labeled by role. For an agency this matters when the account owner, champion, finance contact, and technical evaluator all shape the same client buying motion.
Stage sync, API, webhooks, and n8n support the wider client workflow
Deal stages can sync with Mautic contact stages, and the plugin exposes a REST API, inbound and outbound webhooks, and an n8n node. That gives agencies a path to client-specific automation and cross-instance reporting without inventing a new data model.
How this works in an agency engagement
The useful test is not whether a feature exists in isolation. It is whether an agency can take a fresh client instance and turn it into a cleaner revenue conversation without leaving Mautic.
Install on the client instance you already operate
The agency keeps its normal one-instance-per-client pattern. Deal Flow is added to that instance with the same plugin installation path documented in the site's installation guide.
Create the client's actual pipeline and stages
Instead of a generic list of lifecycle labels, the agency sets up a named pipeline and stages that match how that client sells. The result is a board that belongs to a deal, not just a contact.
Attach the full stakeholder set to one deal
As the opportunity develops, the agency or the client team can add multiple contacts to the same deal and label who is driving, approving, influencing, or blocking the decision.
Use stage sync and automation where the client already works
When a deal moves, the related contact stage can move with it. If the agency is building cross-client operations, the REST API, webhooks, and n8n node are there to move deal data into its wider reporting workflow.
Resources for agencies evaluating the fit
Agencies usually evaluate this from three angles: how hard the setup is, whether the client workflow is real, and how the options differ. Start with the pages below.
Mautic for Agencies
The broader explainer on why agencies hit the reporting gap and how per-client rollout works when each instance is isolated.
How to Add a Pipeline to Mautic
The procedural setup path from installation to the first named pipeline and the first deal on the board.
Mautic Pipeline Plugins Compared
A sourced comparison page for teams deciding between a native in-Mautic pipeline and other ways to add deal flow around Mautic.
Frequently asked questions from agency operators
Why is pipeline reporting a separate problem for agencies running Mautic?
Because Mautic reports on contacts, campaigns, opens, clicks, and scores. An agency that needs to answer which client deals are moving also needs a deal record with its own stage, owner, amount, and close date.
Does this work if each client has a separate Mautic instance?
Yes. Deal Flow installs into each client instance. That matches the common agency pattern of keeping client data and sending reputation isolated per instance.
How does Deal Flow help with multi-stakeholder client accounts?
A single deal can hold multiple contacts, each labeled by role such as champion, decision maker, or influencer. That keeps the whole buying committee attached to one opportunity instead of spreading context across separate contact records.
Can an agency automate client-specific pipeline workflows?
Yes. Deal stages can sync with Mautic contact stages, and the plugin includes a REST API, webhooks, and an n8n node for agencies that want cross-instance reporting or workflow automation.
See whether Deal Flow fits your client-instance model
If your agency already runs Mautic per client, the next question is whether the missing piece is a native deal layer inside each instance.
See Pricing Try free for 7 days