There is expressed confusion about the differentiation in team vs pro plan selection. Example from customer here: https://sentry.zendesk.com/agent/tickets/116691 and here, the point of confusion was user was unaware they would not access to the data-visualizations or trends over time and charts. another related example of confusion sentiment (user missing indirect changes)
@nicholas-codecov raised suggestion to "Maybe we should add some :x: to the team plan description to indicate things you don't get with the plan?"
customer feedback notes
Despite being able to share some details with my co-developer, our experience has gone backwards as the key metrics we were looking for are no longer there.
I would advise your team to simplify the pricing structure. What has happened is that I have paid more and got less in return!
Seriously - just have a free tier and a paid tier with all the same metrics, but multi-user.
We have ~25 repos (so far), so the features that are most important to me are:
- The github badge with the coverage %
- The list of all our repos with the ability to sort by coverage %
- The graph through time per repo.
The rest of your features are great, but are a deep-dive exploration driven by these initial entry points.
Without those up-front metrics I don't know where to explore.
By paying and losing this, I'm afraid the pricing structure is counter-productive.
Another piece of feedback is that the names of the features in the offering vs what I see on screen are not very clear. It is hard to know what I am paying for.
Again, I think an all-in pricing model would mitigate this - I would suggest a price point in between the two plans would make sense!
For the moment, I'm afraid it makes more sense for us to cancel and go back to the free tier, and look more closely at our command line outputs,
Problem to solve
There is expressed confusion about the differentiation in team vs pro plan selection. Example from customer here: https://sentry.zendesk.com/agent/tickets/116691 and here, the point of confusion was user was unaware they would not access to the data-visualizations or trends over time and charts. another related example of confusion sentiment (user missing indirect changes)
Solution exploration