Im after a simple way to bill my clients based on the operations used in Make. I would make separate organisations if it was easy enough, but I can’t see a way to transfer scenarios between organisations other than blueprint export / import. I can also see that the Make module for reporting usage can be summarised by team, however as Im not on the teams plan, looks like I need to run the usage make module on every single scenario for every client. Any ideas on how report on billing accurately without too many headaches?
2 Likes
Amazing question! A few days ago I was thinking about the same things and found something that might be helpful for you.
So the solution would basically be another Make Automation.
I’ve created a “dry build” for you to visualize it.
- you would list all Scenarios that are in a folder.
- Then you set up an iterator to be able to run through every scenario.
- you load the usage data for each scenario
- you save the usage data into a data store of your choice. (e.g google sheets)
This is a very basic setup but I hope it helps! 
Of course, you can make it more fancy and calculate the total usage data etc.
But in this case you can just save everything into google sheets and do some more excel magic there 
Cheers
1 Like
Hello @Evan_Cowan,
Just curious, what keeps them from just migrating scenarios to another account then set the originals to never run at all?
1 Like
Hey @Donald_Mitchell I have about 100 of them, and using the export / import blueprint method then re-connecting all the connections, and setting up new data sources etc, would take a lot of time that I cant charge to anyone. : )