I agree, it's not as simple as "$500 per year". In some cases it can be, but mostly it's not. Firstly, you need to clearly define what is included, and even mo

I agree, it's not as simple as "$500 per year". In some cases it can be, but mostly it's not. Firstly, you need to clearly define what is included, and even more so, what is not included. How many hours is $500? Who decides what us should bug? Can they get new features because they have support? How many installs does the support cover? And do on. And if they start with things like "supplier agreements" etc, just walk away. Yes, some companies have a threshold where managers can just "spend money". Some managers may even use that to support you. But taking any money changes the relationship you have with the user. Right now, it's completely inside your control. Direction, Priorities, Scope, Pace, levels of effort etc. I'm a huge fan of getting paid, I write software for money, but make no mistake - taking money changes things.