Sounds like you need an authorization solution for specific aspects of the toolset. Is there a reason you can't lock down specific functionality (e.g., "Create New Project")?
Yes, we are thinking about specifying the licensing term such that clients cannot use it to create new project.
We are looking for the proper phrasing, wording, template and general experience of folks who have been on either side of the table on this issue. The more we know, the better we will negotiate so to speak ;)
