Feature/wm 199 change billing strategy - Approach 1#188
Feature/wm 199 change billing strategy - Approach 1#188baristaGeek wants to merge 75 commits intomainfrom
Conversation
* Update README.md, add title * Update README.md * Update README.md
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
WatermelonAI Summary (BETA)The related PRs and commits tell us about a change in the billing strategy for Watermelon. The technical aspects of the change involve getting the name of the organization programmatically and potentially counting members for the repo where Watermelon is installed, depending on if the GitHub API allows it. The business logic involves charging for the number of GitHub organization members, and having the ability to lower the per seat price if pricing objections arise. The commits help implement this billing strategy by updating the README.md, adding server-only and client-only components, moving to the RSC, removing logging, fixing typings, and setting conditionally. GitHub PRsJira TicketsNo results found :( Slack ThreadsNotion PagesClick here to login to Notion |
In this approach, we count the number of GitHub organization members and charge for that number. For this approach to be correctly implemented from the technical point of view, the following still needs to be solved:
From the business point of view, it has the following advantages:
And the following disadvantage: