Everyone who does freelance work should have a basic set of requirements for prospective clients up front. These are things that will be in the contract if the relationship gets that far — they’re also things you need to know in the beginning. This is important because it saves time and helps create a clear, honest, and open relationship with your client, right from the start. It also helps filter out clients that are just not right for you. One of the prerequisites on my list, along with an insistence on using Slack for all client communications, is that I require that all code I deliver be licensed under the GNU General Public License (GPL). I do this for a lot of reasons. It helps me deliver better work, keeps budgets reasonable, and it also acts as a way to throw up an early red flag with clients that I probably don’t want to work with anyway. In this article, I’m going to share why this is so important to me, and why I think it is important to clients. I should point out that I don’t do “enterprise-level” work and hardly ever do full-site projects. I tend to do custom plugins, custom integrations, importers, and other architectural type work. My projects are billed in the thousands,
Share This