We have a product that is sold to schools as a site license. It is used by teachers and students alike. We found that entry was a lot easier when the purchasing process was perceived as simple and transparent for the end user.
The site license is installed on all computers at the school + student's notebooks if they are a notebook school. Typically the school sizes are 500-2000 students. We keep it simple and this appears to work. They pay <1500 per annum for the site license. We are happy, and they are happy.
When it comes to colleges the numbers are much larger and there are many departments. Does anyone have experience as to what is a good pricing/site license model for colleges? The software will only be of use to the Science and Athletic Departments. It is of no use to the departments.
We are considering:
Scaling your current model to accommodate the larger volume of the university/college may work just fine for you. One consideration is that the University settings quite often have rigid departmental boundries and budgets. This can often make each department function financially independent, making a college wide site license a tough sell.
We sell our Virtual TimeClock time and attendance software pretty significantly into secondary schools as well as colleges. At the college level, we regularly start with a significant license for a department. Over time word gets out and we sell large licenses into multiple departments. Our efforts to consolidate these licenses for the college are often met with huge resistance due to their budgeting independence.
In terms of pricing, our experience over the last decade has been that Universities generally have larger budgets and really streamlines purchasing procedures. As a rule, I'd say they are less price sensitive and more accustomed to purchasing at higher prices for their larger volume.