Our company execs want to be able to track the revenue potential for building new features.
My thought is to develop the following, but is there a better or already-defined process for doing this?
1. Create a new opportunity picklist field named "New Feature Requested" and offer a list of known features under consideration.
2. Include "other" as a value
3. Create a text field called "Other New Feature Request" that is dependent on the "other" value on the field above.
4. Run an opportunity summary report that identifies the total revenue potential, summarized by the two fields above.
Have I over-simplified this? Is there already a more dynamic solution for this?
Thanks in advance for the advice,
Sue
4 respostas
I would track feature requests in a custom object. Then relate them to opportunities with a junction object. this way you can have many feature requests on one opportunity. You can also track additional details around feature requests, such as totals, dates, status, desciptions, etc...
On the junction object, you might also want to track additional customer notes such as "I need this feature, as it will enable me to...." You may end up with different reasons for thesame feature, which may affect the final design - such as customization options and such. Technically a picklist will work, but if you're going to track it, I bet there's a lot of additional useful data there. Including date of request and such.
So picture this scenario... You're tracking feature requests as i described above... you have 50+ opportunities associated, and you also placed specific contacts on the junction records. So once the feature request status changes to 'building' or 'devlivered' you can now send a notification to all of the contacts that had requested the feature - and a note to sales people to reach out to their contacts to sell the additional features... There's a lot you'll be able to do with this data!
