Suppose a customer proposes an idea to improve the software or SaaS offering of a company. The company likes the idea so much that it integrates the idea into its next upgrade. The question becomes, who owns the idea that is integrated into the software or SaaS offering?

As a general rule, the person who creates an idea, authored work, invention, or process, owns the related intellectual property.  There are exceptions to the general rule.  But, in the software and SaaS arena involving licensors and licensees, the general rule applies in most circumstances.

With ownership established by law, there are several ways to handle the intellectual property rights related to customer feedback through contracts and policies.  Here are some of the approaches companies take:

“We don’t want your ideas”

One approach is to not solicit or accept customer feedback.  This is the approach that McDonald’s has taken with regard to its Customer E-mail Center Terms and Conditions.  A rationale for this approach is to avoid confusion or conflict of ownership if a customer has the same idea as someone within the organization.  As is the case for other organizations that have adopted this approach, McDonald’s policy is that if a customer ignores McDonald’s request that they not send ideas or suggestions, the customer grants McDonald’s a license to use, copy, and display whatever the customer provides to McDonald’s.  For a variety of reasons, such as the negative public relations associated with not wanting customer suggestions or ideas, most SaaS and software companies do not choose this approach.

“We own your ideas”

At the other end of the spectrum, the recipient of the ideas, authored works, inventions, or processes can take the position that everything that is submitted to the recipient is owned by the recipient.  One sees this approach in a variety of contexts, especially where either contracts or terms of service are not heavily negotiated or where the relevant idea, authored work, invention, or process created will have little value to the creator.  Radiant Systems is an example of a company that has used this approach.

“We can use your ideas”

Somewhere in between the above two alternatives is the concept that while the creator of the idea, authored work, invention, or process owns it, the recipient has a royalty-free right to use, copy, and display it.  This allows the company to use the customer feedback, but the customer retains ownership of it.  Adobe, Hewlett Packard, SAP, Google, and others take this approach with at least some of their offerings and general public feedback.

Ignoring the issue

Sometimes contracts and terms of service ignore the customer feedback issue.  Presumably, this is just an oversight or the companies are taking the position that they at least have an implied license to the feedback.

For many businesses, listening to and incorporating customer feedback into the product or service improvement process not only is good for sound customer relationships but it just makes good business sense.   Similarly, for software and SaaS companies, ensuring that the companies’ contracts adequately address intellectual property ownership and license rights to that customer feedback makes good legal sense.