<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Forecast: One off vs recurring revenue in Data Hub</title>
    <link>https://community.hubspot.com/t5/Data-Hub/Forecast-One-off-vs-recurring-revenue/m-p/814152#M1602</link>
    <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.hubspot.com/t5/user/viewprofilepage/user-id/584073"&gt;@LWu8&lt;/a&gt;&amp;nbsp;,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I would probably tend to agree with&amp;nbsp;&lt;a href="https://community.hubspot.com/t5/user/viewprofilepage/user-id/475927"&gt;@ArdenM&lt;/a&gt;&amp;nbsp;here. The hubspot reporting for forecasting is centred around pipeline stage probabilities so separate pipelines make the most sense for a no-code solution.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;However, if this is not possible, you could create an alternative version of this with custom code workflows and custom properties if you have operations hub.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;You would need to create a workflow that triggers off change in deal stage. Then write some custom code that calculates the 'projected revenue' for each deal that would apply different probabilities depending on whether it's recurring or one-off, which would be stored in a custom property. Then you could report on this custom property.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;If you decide to go down this route and need some help writing the custom code let me know.&lt;/P&gt;</description>
    <pubDate>Fri, 30 Jun 2023 10:10:17 GMT</pubDate>
    <dc:creator>KimM</dc:creator>
    <dc:date>2023-06-30T10:10:17Z</dc:date>
    <item>
      <title>Forecast: One off vs recurring revenue</title>
      <link>https://community.hubspot.com/t5/Data-Hub/Forecast-One-off-vs-recurring-revenue/m-p/807726#M1581</link>
      <description>&lt;P&gt;Hi team,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;my revenue can be broken down into one off vs recurring revenue. I would like to break that down and assign different probabilities to both and then also forecast both seperately. How can I set this up?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thank you&lt;/P&gt;</description>
      <pubDate>Thu, 15 Jun 2023 09:12:38 GMT</pubDate>
      <guid>https://community.hubspot.com/t5/Data-Hub/Forecast-One-off-vs-recurring-revenue/m-p/807726#M1581</guid>
      <dc:creator>LWu8</dc:creator>
      <dc:date>2023-06-15T09:12:38Z</dc:date>
    </item>
    <item>
      <title>Re: Forecast: One off vs recurring revenue</title>
      <link>https://community.hubspot.com/t5/Data-Hub/Forecast-One-off-vs-recurring-revenue/m-p/808350#M1582</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.hubspot.com/t5/user/viewprofilepage/user-id/584073"&gt;@LWu8&lt;/a&gt;,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Thank you for reaching out to the Community!&lt;/P&gt;
&lt;P&gt;I wanted to tag in a couple of subject matter experts to see if they have any advice:&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.hubspot.com/t5/user/viewprofilepage/user-id/101258"&gt;@Teun&lt;/a&gt;,&amp;nbsp;&lt;a href="https://community.hubspot.com/t5/user/viewprofilepage/user-id/10166"&gt;@johnelmer&lt;/a&gt;,&amp;nbsp;&lt;a href="https://community.hubspot.com/t5/user/viewprofilepage/user-id/20261"&gt;@louischausse&lt;/a&gt;, do you have any tips for&amp;nbsp;&lt;a href="https://community.hubspot.com/t5/user/viewprofilepage/user-id/584073"&gt;@LWu8&lt;/a&gt;? Thank you!&amp;nbsp;&lt;span class="lia-unicode-emoji" title=":star:"&gt;⭐&lt;/span&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Cheers&lt;BR /&gt;Mia, Community Team &amp;nbsp; &amp;nbsp;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 16 Jun 2023 10:32:05 GMT</pubDate>
      <guid>https://community.hubspot.com/t5/Data-Hub/Forecast-One-off-vs-recurring-revenue/m-p/808350#M1582</guid>
      <dc:creator>MiaSrebrnjak</dc:creator>
      <dc:date>2023-06-16T10:32:05Z</dc:date>
    </item>
    <item>
      <title>Re: Forecast: One off vs recurring revenue</title>
      <link>https://community.hubspot.com/t5/Data-Hub/Forecast-One-off-vs-recurring-revenue/m-p/808614#M1583</link>
      <description>&lt;P&gt;I'm not sure that this is the &lt;EM&gt;most&lt;/EM&gt; helpful answer, but it sounds like the easiest way to achieve your goal would be to separate out your one-off sales and recurring sales into different deal pipelines, and forecast them separately that way!&lt;/P&gt;</description>
      <pubDate>Fri, 16 Jun 2023 19:52:01 GMT</pubDate>
      <guid>https://community.hubspot.com/t5/Data-Hub/Forecast-One-off-vs-recurring-revenue/m-p/808614#M1583</guid>
      <dc:creator>ArdenM</dc:creator>
      <dc:date>2023-06-16T19:52:01Z</dc:date>
    </item>
    <item>
      <title>Re: Forecast: One off vs recurring revenue</title>
      <link>https://community.hubspot.com/t5/Data-Hub/Forecast-One-off-vs-recurring-revenue/m-p/814152#M1602</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.hubspot.com/t5/user/viewprofilepage/user-id/584073"&gt;@LWu8&lt;/a&gt;&amp;nbsp;,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I would probably tend to agree with&amp;nbsp;&lt;a href="https://community.hubspot.com/t5/user/viewprofilepage/user-id/475927"&gt;@ArdenM&lt;/a&gt;&amp;nbsp;here. The hubspot reporting for forecasting is centred around pipeline stage probabilities so separate pipelines make the most sense for a no-code solution.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;However, if this is not possible, you could create an alternative version of this with custom code workflows and custom properties if you have operations hub.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;You would need to create a workflow that triggers off change in deal stage. Then write some custom code that calculates the 'projected revenue' for each deal that would apply different probabilities depending on whether it's recurring or one-off, which would be stored in a custom property. Then you could report on this custom property.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;If you decide to go down this route and need some help writing the custom code let me know.&lt;/P&gt;</description>
      <pubDate>Fri, 30 Jun 2023 10:10:17 GMT</pubDate>
      <guid>https://community.hubspot.com/t5/Data-Hub/Forecast-One-off-vs-recurring-revenue/m-p/814152#M1602</guid>
      <dc:creator>KimM</dc:creator>
      <dc:date>2023-06-30T10:10:17Z</dc:date>
    </item>
    <item>
      <title>Re: Forecast: One off vs recurring revenue</title>
      <link>https://community.hubspot.com/t5/Data-Hub/Forecast-One-off-vs-recurring-revenue/m-p/814486#M1604</link>
      <description>&lt;P&gt;Absolutely agree with KimM's points here.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I would stress, however, that you do some very careful consideration before going the custom code route. Custom code in Hubspot can be finnicky, especially if you're not experienced with Javascript or Python, and often requires a fair amount of maintence as your system continues to grow and change.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Additionally, any time you move away from HubSpot's intended functionalities for things, you're going to find doing other things in HubSpot harder and require more customized solutions (which also slowly make it harder to use third party apps). This is not an idle warning - I've done this myself, and it's often a giant pain!&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Best of luck with whichever solution you pursue, and don't hesitate to ask any further related questions.&lt;/P&gt;</description>
      <pubDate>Fri, 30 Jun 2023 21:27:13 GMT</pubDate>
      <guid>https://community.hubspot.com/t5/Data-Hub/Forecast-One-off-vs-recurring-revenue/m-p/814486#M1604</guid>
      <dc:creator>ArdenM</dc:creator>
      <dc:date>2023-06-30T21:27:13Z</dc:date>
    </item>
  </channel>
</rss>

