The reporting gap every Mautic agency eventually hits
An agency running Mautic for clients starts every relationship on solid ground: campaigns launch, emails send, forms convert, and the monthly report shows opens, clicks and lead scores climbing. That report is genuinely useful for the first few months of a retainer.
Then a client asks the question every account eventually reaches: “okay, but what’s actually closing?” Mautic has no answer, because it was never built to hold one. It tracks contacts, campaigns and lifecycle stages — marketing-activity data. A pipeline report needs a deal: an amount, a stage, a close date, and the contact or contacts working it. Core Mautic has nowhere to put that, for any client, in any instance.
The pattern is structural, not a one-off client complaint. Reviews of running multiple Mautic instances for marketing-automation work consistently point to the same trade-off: instance isolation is good for client data separation, and weak for anything that needs to roll activity up into a business number like pipeline value.
Why "one Mautic instance per client" makes this harder, not easier
Most agencies serving multiple clients run one Mautic instance per client rather than a shared multi-tenant install — it keeps each client's contact data, sending reputation and branding fully separate. Practitioners on the Mautic forum describe getting genuinely fast at the operational side of this: one described spinning up a new client instance — SSL, domain forwarding, email sending — in about five minutes once the process is repeatable.
That isolation is a feature for data hygiene and a cost for reporting. There is no shared dashboard across instances unless the agency builds one, and any pipeline layer added to solve the reporting gap has to be installed — and licensed — per instance, not once for the agency.
The honest math on per-instance licensing
This is worth stating plainly rather than glossing over: a per-subdomain license means an agency running Mautic for ten clients pays for the pipeline layer ten times, not once. That is the real trade-off of the single-tenant model agencies already chose for data-isolation reasons, and it is worth weighing before rolling a pipeline plugin out client-wide.
Weighed against a retainer, $99 one-time per client instance is usually a small addition to a single engagement — and unlike a per-seat CRM, it does not grow again as the agency's own team grows, or as more people at the client ask for access. There is no bundle or multi-instance discount today; if licensing ten instances at once matters to your rollout, the honest advice is to install it on your highest-value or most pipeline-curious client first and expand from evidence, not commit to all ten up front.
How Deal Flow fits an agency's Mautic workflow
Deal Flow installs into each client's Mautic instance the same way any other plugin does — it does not require a shared or multi-tenant setup, and it does not touch client isolation.
- A real deal object per client instance — amount, stage, close date, owner — so "what's in the pipeline" has an actual answer inside the tool the agency already operates.
- Kanban pipelines the agency (or the client, if given access) can view directly, instead of a manually assembled report.
- Buying committee roles — label which contact on a client's deal is the champion, the economic buyer, or a blocker, which is exactly the kind of question a retainer conversation turns on.
- Bidirectional stage sync to the contact stages and campaigns already configured on that instance, so nothing about the agency's existing automation has to be rebuilt.
- A REST API and webhooks for agencies that want to pull deal data into their own cross-client reporting tool rather than reporting client-by-client inside Mautic.
Positioning note for the client conversation: Mautic on its own isn't a CRM — Deal Flow is the CRM layer that turns the monthly activity report into a pipeline conversation, inside the Mautic the client is already paying the agency to run.
Setting it up across client instances
-
1
Pick the first instance
Start with one client — ideally one already asking pipeline-shaped questions — rather than rolling it out to every instance at once.
-
2
Install via wget/unzip
Same install method as any other Mautic plugin, no Composer or Packagist dependency; the full steps are in the installation guide.
-
3
Set up one pipeline and stages
Map the client's actual sales process into stages so the board reflects how they really sell, not a generic template.
-
4
Wire stage sync to existing campaigns
Let deal stage changes drive the contact stages and campaigns already built on that instance, so existing automation keeps working.
-
5
Bring the pipeline into the monthly report
Replace or supplement the opens/clicks summary with pipeline value and stage movement — the retainer conversation this whole guide is about.
-
6
Repeat per client, from evidence
Expand to additional client instances once the first shows the reporting change is worth the retainer conversation, licensing each instance as you go.
Pricing is one-time, per instance. $99 per client's Mautic instance, unlimited users on that instance, one year of updates included. No per-seat charge as a client's team grows.
Frequently asked questions
Why can't I show clients a pipeline directly from Mautic?
Because Mautic has no deal or opportunity record. It reports on contacts, campaigns, opens, clicks and scores — all marketing-activity metrics. A pipeline report needs a deal: an amount, a stage, a close date, tied to the contacts working it. Core Mautic has nowhere to put that.
Does running one Mautic instance per client make this harder?
It changes the shape of the problem rather than solving it. Each instance is already isolated, which is good for data separation, but it also means any pipeline layer has to be installed and licensed per instance — there is no shared dashboard across clients unless you build one.
Isn't a per-instance license expensive for an agency with many clients?
It scales with client count, which is the honest trade-off: $99 once per client instance, not a subscription. Weighed against a retainer, it is usually a small one-time addition to a single client engagement — and unlike a per-seat CRM, it does not grow again as the agency's own team grows.
Will a pipeline plugin survive Mautic upgrades across many client instances?
Deal Flow installs as a standard Mautic plugin — wget/unzip into the plugins directory, no core modifications — and each license includes a year of updates. It is installed and upgraded per instance the same way the rest of the Mautic plugin ecosystem is.
Give one client a pipeline this week
Deal Flow is $99 one-time per Mautic instance — unlimited users, one year of updates included.
Get Deal Flow — $99 Try free for 7 days