The operating pains a hosting partner recognizes
Owen represents the service providers who clone, maintain, and support client environments. Their problem is not campaign reporting. It is making a technical delivery model repeatable while preserving a clear boundary around every client.
New client instances have to be repeatable
Clone Mautic installations for new clients. Takes 5-10 minutes to setup, most of that time is waiting for the files and database to be copied automatically.
Practitioner source on the Mautic Forum.
Once provisioning becomes a service, every component added after the clone has to fit a process the partner can repeat for the next client.
A shared install collapses the data boundary
The contacts won’t be separated by client, it is still one Mautic install. Web tracking is shared between clients, it is a GDPR nightmare if you share one Maitic install.
Practitioner source on the Mautic Forum.
For a managed host, separation is an architecture decision: each client needs an environment and database whose records are not mixed with another client's records.
One difficult upgrade can consume the week
The issue is when we need to upgrade there’s always something that goes wrong and I waste a week dealing with it.
Practitioner source on the Mautic Forum.
That burden compounds when the same partner is responsible for a roster of client deployments with their own plugins, data, and maintenance windows.
Evidence note: Owen is the research persona used to organize this workflow. The quotations above come from the linked practitioners, not from one person named Owen.
How Deal Flow maps to those hosting pains
Each capability below answers a named operating problem. Deal Flow does not provision hosting or replace the partner's deployment and maintenance process.
A per-instance install fits the cloned-provisioning endpoint
After a partner gives a cloned client environment its own URL and database, Deal Flow installs through the standard Mautic plugin flow inside that instance. The partner can then apply the same pipeline setup checklist to the next client. Deal Flow does not clone or provision Mautic itself.
The instance and database, not the license, provide isolation
Separate Mautic instances and databases create the client boundary. One Deal Flow license binds to one instance and subdomain; that license scopes use of the plugin, but it does not split contacts or web tracking inside a shared install.
Pipeline setup can become part of the service scope
A partner can include plugin installation, pipeline configuration, buying-committee setup, and client training around a separately licensed client deployment. That is service packaging, not software or license-key resale. The published terms do not permit reselling, redistributing, or sublicensing the software or key; confirm any multi-instance arrangement through the partner application.
One year of plugin updates belongs in the maintenance plan
One year of Deal Flow plugin updates is included. That gives the partner a defined update window for the plugin, but it does not determine the outcome of a Mautic core upgrade. Backups, staging, compatibility checks, and rollback planning still belong in every upgrade runbook.
How this works in one managed client deployment
The concrete test is whether a partner can take one isolated client instance from provisioned environment to a deal workflow the client can understand.
Provision the client's separate environment
The partner creates or clones the client's Mautic instance with its own subdomain and database, preserving the client boundary before Deal Flow is introduced.
Install Deal Flow in that instance
The partner follows the standard plugin installation path and activates the license for that instance and subdomain. A separate client deployment requires its own license.
Configure and present the client's pipeline board
The partner creates a named pipeline and ordered stages, then adds a representative deal with its owner, amount, and expected close date. The client sees a board that reflects the way its team actually moves revenue work.
Show the buying committee on the same deal
The partner attaches the relevant contacts and labels roles such as Champion, Decision Maker, Technical Evaluator, or Budget Holder. The demonstration connects the pipeline board to the people shaping the decision.
Resources for hosting partners evaluating the fit
Use these pages to review the rollout path, the first pipeline setup, and the available ways to put deal tracking around Mautic.
Mautic Pipeline for Agencies
The operational guide for teams that manage separate client instances and need a repeatable pipeline rollout.
How to Add a Pipeline to Mautic
The step-by-step path from plugin installation to a named pipeline, ordered stages, and the first deal.
Mautic Pipeline Plugins Compared
A sourced evaluation of the different product models available to teams adding pipeline work in or around Mautic.
Frequently asked questions from hosting partners
Does one license cover multiple client instances?
No. One Deal Flow license binds to one Mautic instance and subdomain. A hosting partner provisioning separate client instances needs a separate license for each deployment.
Does Deal Flow make a shared Mautic installation multi-tenant?
No. Client data separation comes from running separate Mautic instances and databases. A Deal Flow license defines the licensed instance; it is not a data-isolation mechanism.
Does one year of updates make every Mautic core upgrade safe?
One year of Deal Flow plugin updates is included. Mautic core upgrades still need backups, staging, compatibility checks, and a rollback plan because the included plugin updates do not determine the outcome of a core upgrade.
Can I include Deal Flow in a managed offer for clients?
A partner can package implementation, configuration, and training around a separately licensed client deployment. The published terms do not permit reselling, redistributing, or sublicensing the software or license key; confirm any multi-instance arrangement through the partner application.
Add a deal layer to the client environments you already manage
Review the licensing path for the next client instance, then decide how pipeline setup and buying-committee training fit into your managed service.
See Pricing Try free for 7 days