A version of this problem I've seen is that often customers (particularly enterprise customers) want you to make solutions specific to their exact needs rather than the broad needs of their whole category. Even if they want the same problem addressed that you do they will want you to make the product suit their needs EXACTLY. That won't scale and backs you into being a services company instead of a product company. Strategies we've used to fight this are to listen to feedback from all users and only build what everyone agrees is needed, and also offer an API so we don't have to flat out say no. Instead with an API we can say, you're welcome to do whatever you'd like... Finally, when we do have to say something like "no" instead we just put a astronomical price tag on it and let the customer decide no for themselves. ...or maybe they'll say ok and then we'll know our thinking might be flawed if some feature is worth a hefty premium. Hope that's helpful to others!