Question about the license business model for agencies
I have a question for the Fluent team regarding the business model of wholesale license sales for Agencies.
My portfolio includes licenses from several companies. One company conveniently came up with the idea of creating child licenses under a master license. These are very easy to control and provide to my clients—one license per client.
Another company has a master license but activates them via an additional two-factor message. It's not very convenient; you need to figure out a way to deliver the message to your clients if you don't do it manually yourself. You have to put effort into automation, parsing emails, and forwarding the message to the client's email. I haven't tried it yet, but I'm thinking about how to do it.
In your case, it seems there is one license for multiple installations, and to activate them for clients, you have to connect them yourself so the client doesn't see the license code and can't share it with someone else. It's inconvenient to control and requires a lot of effort to safely activate the license for the client. Working with one license for everyone is very inconvenient.
Is it possible to offer a business model with child licenses so that each client has their own individual child license, tied to only one domain? This would make it convenient to control and manage client connections. This way, licenses could be provided as a service.
Thank you for your feedback.
Following
I understand where you’re coming from and the desire for easier license management for agency workflows makes sense. That said, introducing 'child licenses' would very likely open the door to license reselling rather than licenses being used strictly for client work.. which is something most plugin vendors including WPManageNinja explicitly prohibit in their ToS, especially for LTDs . The current model is designed so agencies use their own license when building or maintaining a clients Wordpress site, without transferring or exposing the license key to the client. In practice this usually means logging into the clients site and activating the license yourself. If you ever need to manage or revoke access you can do so directly from the Licenses section in your dashboard by removing connected domains.
While I agree it’s not as “hands off” as child licenses, it does help prevent misuse and unauthorized redistribution. Because of that I personally doubt WPMN would implement a child license system like the one you’re describing
Magik Thank you for the explanation. This approach clarifies why the Fluent team uses a single license. This business model for an agency requires detailed development of a marketing campaign, which must skillfully describe the service, specifying what is included and how it will be presented. Specifically, it should state that the client will receive a set of business tools, but only if the agency itself connects the plugins. It turns out that the price of the agency plugin can (or cannot?) be stated, but this plugin will be installed by the agency itself.
Following