Good one, Liam! We're still bringing this up within the team but for now, here's something Yash posted in a similar thread to forecast credits:
"
I haven’t seen one of these but would love to see it if you make it!
took a few minutes to whip up the basic outline of how I’d think about it, feel free to duplicate:
https://docs.google.com/spreadsheets/d/1Hbj8uCj8hm92D0RexQRzSxVWCkaKLc9GP6Pb1cwVY0Y/edit?usp=sharing
the thing that’s complicated to account for here (which I gave an example of), some data points come with all the other ones because they’re from the same integration.
for example, if you want revenue and employee count, don’t list the credit costs for them separately, because they both come from the same integrations.
the best way to handle this (most likely) is just to bundle together all the most important data points you get from particular integrations.
won’t be 100% accurate since the data point overlap isn’t 100%, but will be roughly accurate enough for a forecast to use!
"
.png){kind=logo}
