docs(product-support): exclude internal and test orgs from revenue metrics - #199
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What is this change?
This PR updates the
echo-readonly-postgresskill by adding a new "SaaS Revenue Queries & MRR Reporting" section. It codifies the rule that internal and test organizations (like Jorim Theuns' internal subscription) must always be excluded from total revenue/MRR figures posted to the team, and provides a template SQL query to enforce this filter.What did Sam notice that led to this?
Sameer corrected the drafted self-serve MRR figure (noting that the €86 internal test seat for Jorim Theuns should be excluded from the headline and that internal/test organisations should never count toward a posted revenue number, as it costs team credibility). Codifying this under the database query skill ensures future reports and alerts follow this policy.
Tier?
Tier 1.
Confidence?
Highly confident. The guidance and reasoning came directly from Sameer and are now documented at the exact point where we look up database query recipes.