Improve customer usage stats to improve our expansion sales motion

Created by: Joelkw

A pattern I’ve noticed 3 times this week:

1. An unfortunate/unintended thing happens that causes some users to lose access to an add-on feature they were using
   1. Recent examples: we locked down code insights unless you have a license and all the communications about that didn't reach every user at a customer; an admin migrated their instance DB incorrectly and lose all their insights but didn’t realize it until someone else calls it out
2. These users get noisy about these issues to their site admins/EBs/our contacts
3. Our customer contacts then go to our sales teams and say “hey, we didn’t even realize people were using it, but it turns out we’d like to talk about buying [the add-on]”

This is interesting (luckily folks I’ve seen aren’t too upset about the bad things; and sometimes the bad thing is their fault) – and there are certainly other improvements to solve the specific bad things as well – because a high-level take is that admins/EBs/champions aren’t aware of their full usage on their instance (we don't show this well now). We may be missing or delaying sales we could discover faster if admins had more visibility into their usage.

Another reason to prioritize this, and why our looker-pdf-export-send-to-customer workaround isn’t enough, is that: usage stats could show site admins much more specific information than we can collect in pings.

I’ve seen that it’s not very useful to go to a site admin and say “hey someone created 12 insights, ask around and see if you can figure out who” but it’s way more impactful to the sales process if we can quickly show “hey someone created 8 insights to solve these 4-5 specific initiatives" (as seen through the insights' titles, which are too sensitive to send in pings but could be shown on a site admin page).

Relevant to this product gap: https://sourcegraph2020.lightning.force.com/lightning/r/Product_Gap__c/a1B5b00000K4zBIEAZ/view