Skip to content
This repository was archived by the owner on Mar 12, 2024. It is now read-only.

Feature/wm 199 change billing strategy - Approach 1#188

Closed
baristaGeek wants to merge 75 commits intomainfrom
feature/WM-199-change-billing-strategy
Closed

Feature/wm 199 change billing strategy - Approach 1#188
baristaGeek wants to merge 75 commits intomainfrom
feature/WM-199-change-billing-strategy

Conversation

@baristaGeek
Copy link
Copy Markdown
Collaborator

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:

  • Get the name of the organization programmatically
  • (Optional If possible. Although my research says GH API doesn't have an endpoint for this): Count members not for the whole organization but for the repo where Watermelon is installed

From the business point of view, it has the following advantages:

  • No revenue goes uncharged. If we get pricing objections, we can always lower the per seat price.

And the following disadvantage:

  • People might get turned off if they say we're charging for a whole organization. This, for larger organizations that have various development teams.

@vercel
Copy link
Copy Markdown

vercel Bot commented Jul 5, 2023

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Updated (UTC)
watermelon ❌ Failed (Inspect) Jul 5, 2023 10:13pm

@watermelon-copilot-for-code-review
Copy link
Copy Markdown

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 PRs

Jira Tickets

No results found :(

Slack Threads

Notion Pages

Click here to login to Notion
Your team WatermelonTools has used Watermelon 71 times.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants