R 4 NETWORK ROADMAPS Many sales and marketing ideas meet with customers' needs and are sometimes planned based on demonstrating the capabilities of the product. Although in many cases this implies a demonstration based on existing capabilities of the product in the current network, in many cases increasing it implies showing some proof of concept of a certain feature. Although the feature may not completely work as per the field definitions, it would be defined to show some capabilities of the feature in question to convince the customer about capabilities of the product. Business inputs about when such proof of concept demonstrations are needed are vital to the network roadmap. Also, in the telecom industry in particular, many product launches and feature demonstrations are planned to be unveiled in noted symposiums attended by vendors and customers alike. Businesses should give input about which features are planned for such demonstrations so they can be part of the network roadmap. For example, every year, many product launches are planned for the Barcelona Mobile World Congress held in Spain. So the network roadmap must be planned to incorporate development of the feature to be ready in time for the planned demo. When it is time to stop supporting some features or options for the product, this call should come from product management. Businesses should assess the impact of not supporting a particular feature in terms of the effect on the customer base and actual usage. It is also the onus of business development to communicate such decisions to key customers and ensure their acceptance is received. It is most likely that such end-of-life decisions will be turned into opportunities to push support for newer platforms or upgraded features by product management when they interact with customers, old and new. Typically, organizations get a limited amount of money as a budget to work their business plans. Deciding how this budget will be allocated for product development and which features get prioritized into the