Love this idea! I worked on something like this at a previous company—working with Product & Engineering, like Tim suggested.
It really depends if your company has ready access to this data. A surprising number of products are built without a way to track the usage of key parts of the product. And then how easy is that data to capture depending on billing cycle (at the company I did this with, there were monthly & annual plans that renewed at different points in time). We were working on a monthly product usage email, so the question was: Do you send at a certain time of the month, or based on the customer's billing date?
I wish I had the brief for this. It was a lot of work. Because you have to think about highs and lows—what happens if people are over your value metric? What happens if people have low/no usage? You might want to vary the message accordingly and consider those different use cases.
Trying to find an article from one of the people involved in creating Grammarly Insights.
