{"id":14315,"date":"2007-04-19T15:45:12","date_gmt":"2007-04-19T15:45:12","guid":{"rendered":"https:\/\/blogs.msdn.microsoft.com\/crm\/2007\/04\/19\/weighted-revenue\/"},"modified":"2023-05-31T15:32:33","modified_gmt":"2023-05-31T22:32:33","slug":"weighted-revenue","status":"publish","type":"post","link":"https:\/\/www.microsoft.com\/en-us\/dynamics-365\/blog\/no-audience\/2007\/04\/19\/weighted-revenue\/","title":{"rendered":"Weighted Revenue"},"content":{"rendered":"

For some strange reason the subject of Weighted Revenue has been on my mind lately. Strange in the sense that I don\u2019t own our Opportunity Management feature and I haven\u2019t written an sales pipeline report in a while. Perhaps I\u2019m having flashbacks to an earlier stage in my career where I was passionate about such calculations.<\/p>\n

Opportunities (or Deals if you prefer) have an estimated revenue attribute. This revenue estimation is usually derived be one of two methods: a sum of products to be sold or a guess by the salesperson as to the total deal value. This revenue estimation is then \u2018weighted\u2019 based on the success chance of that deal.<\/p>\n

Now this is where things can turn a little crazy. Most companies weight the revenue based on the opportunity success %. For example, if you have an opportunity with $150K estimated revenue and a 50% success chance then the weighted revenue will be $75K. This weighted revenue amount for each opportunity is then aggregated by the estimated close date (or estimated payment date). This aggregation is supposed to estimate the amount of revenue which a company will revenue in that timeframe. This approach is what I call \u2018simplistic weighting\u2019.<\/p>\n

Consider some<\/i> of the flaws of this approach:<\/p>\n