How can I prevent the client from reselling my workflow.
I’m aware that:
-
Sending raw workflows + setup videos gives zero protection
-
Hosting n8n “as a product” has licensing implications
-
Clients may not want to give API access to a random person long-term
I’m not trying to do anything that complicated just avoid the “ZIP file SaaS” problem where the entire product can be easily forwarded to the next person.
I’d appreciate real-world approaches that actually work, not theory.
Personally, when I build something like this not just workflows but software in general especially for freelancing, I always assume that I’m selling the full workflow/source itself, so pricing should reflect that from the beginning, so you don’t end up overthinking reselling later,
You should also assume that reselling will happen, or that someone else will eventually build the same thing at somepoint,
So, there’s no such thing as absolute protection, even with contracts and legal agreements, once you hand over the workflow/code to someone else, it’s essentially outside of your control,
If you believe your workflow has unique or high value, an alternative approach is not to sell it, instead consider building a SaaS around it or exposing it as an API, so you’re selling access or functionality rather than the source itself,
1 Like