This clause establishes the process and terms under which customers can request new features or functionality from the SaaS provider, and critically, what happens to those requests from an intellectual property perspective. It typically addresses whether feature requests are confidential, whether the vendor can use ideas from multiple customers to develop new features, and whether customers who suggest features receive any compensation, credit, or preferential access. In an intellectual property context, this clause is a potential minefield because it determines who owns the rights to innovations that emerge from customer feedback. If poorly drafted, a customer's valuable suggestion for a competitive advantage could be adopted by the vendor and made available to all competitors, or the vendor could claim ownership of improvements to the customer's own processes.
The clause matters because insurance companies often have sophisticated insights into market needs, regulatory trends, and operational efficiencies that could translate into valuable intellectual property. If your feature requests are treated as non-confidential suggestions that the vendor can freely use, you lose any competitive advantage from your innovation. Conversely, if the clause is too restrictive, the vendor may refuse to consider your requests or may charge premium fees for custom development. The clause also affects your relationship with the vendor—unclear terms can lead to disputes about whether a feature you requested was developed based on your input and whether you should receive preferential pricing or terms.
Clearly distinguish between confidential feature requests (which should remain your confidential information) and general feedback or suggestions (which the vendor can use freely). Request that any feature developed primarily in response to your specific request be offered to you at a discount or on preferential terms for a defined period before general release. Include a provision that the vendor will not disclose your feature requests to competitors without your consent. If you're investing significant resources in defining requirements for a custom feature, negotiate for ownership of the resulting intellectual property or a non-exclusive license with restrictions on the vendor's ability to license it to direct competitors. Establish a formal feature request process with documentation and approval workflows to create a clear record of what was requested and when.
Frequently Asked Questions
What does this clause mean in simple terms?
This clause establishes the process and terms under which customers can request new features or functionality from the SaaS provider, and critically, what happens to those requests from an intellectual property perspective. It typically addresses whether feature requests are confidential, whether the vendor can use ideas from multiple customers to develop new features, and whether customers who suggest features receive any compensation, credit, or preferential access.
Why should I care about this clause?
In an intellectual property context, this clause is a potential minefield because it determines who owns the rights to innovations that emerge from customer feedback. If poorly drafted, a customer's valuable suggestion for a competitive advantage could be adopted by the vendor and made available to all competitors, or the vendor could claim ownership of improvements to the customer's own processes.
What are my options?
The clause matters because insurance companies often have sophisticated insights into market needs, regulatory trends, and operational efficiencies that could translate into valuable intellectual property. If your feature requests are treated as non-confidential suggestions that the vendor can freely use, you lose any competitive advantage from your innovation.
How does this affect small businesses?
Conversely, if the clause is too restrictive, the vendor may refuse to consider your requests or may charge premium fees for custom development. The clause also affects your relationship with the vendor—unclear terms can lead to disputes about whether a feature you requested was developed based on your input and whether you should receive preferential pricing or terms.