I’d be surprised if anyone is using it much heavier than I am. 

I’ve up to about ~3K tasks per week / 12-16K task per month. We have other use cases our company has going and we still end up in the ~25-30K per month range, well below our 50K enterprise plan

I’m not sure task to member ratio makes sense, as most of mine are post-related automations. But we see about 900 active users per month, so we’re in the 2-3 per user ratio. 

I’m at 150+ Zaps running each week. Filter is your friend, as it doesn’t count towards runs. A lot of mine trigger on a new post and then filter as the first step. (Ex. community posts to specific product slack channels based on keywords and/or tags)

Awesome as always.

Thanks @DannyPancratz.

Task to member was just me making up metrics. 😊

but since I do not know how many active users we will get I was hoping to get some guidance.

Just out of curiosity I checked ours and we’re at about 1400 tasks over the past 30 days over 8 Zaps. Like Danny, ours fire on posts not members so I could provide the metric but it wouldn’t be relevant.

Also important to note I’m taking a pretty conservative approach to Zaps these days since I’m sort of intruding on an existing plan here. Not like the plan I had while running Zapier Community. 😂