We are building a few services that would be expensive to maintain over time without requiring financial support. Instead of asking users to pay for each service individually, we'd rather bundle them all into a single umbrella, pico pro.
Pico pro would be a subscription service, but I don't want to manage subscriptions. Instead I think what we should do is require a year subscription but the user would have to manually review every year. We would send an email notification prior to the subscription ending to ask users to renew.
I also want to employ the sourcehut payment plan where each "tier" offers the same level of features but we allow users to contribute more if they want.
Requiring a year subscription has a few benefits:
- We can fund the entire year for the user upfront
- Fewer options to decide
- We don't need to worry about storing or keeping CC info since it's a one time payment every year
The obvious choice is Stripe. But we could investigate other options if Stripe is too restrictive or expensive.
I think inside the CMS we should have CTAs that nudge users to pico pro. We would have a sub-app dedicated to describing pico pro and why to upgrade. If a user does upgrade they should probably see a fancy banner that indicates they are pro members. I think adding a "support" section could be interesting that opens an IRC client to a private channel for pico pro users. This would be a great way to get immediate support from us.
Right now when you log into the CMS you see the following sections:
Set username Manage posts Manage keys Exit
For non-pro members they would see:
1Set username 2Manage posts 3Manage keys 4+ Pro 5Exit
For pro members they would see:
1Set username 2Manage posts 3Manage keys 4+ Pro 5+ Support 6Exit
What services require payment?
Anything that requires extra resources to fund that increases price based on usage. For example, our image hosting service is going to be expensive to maintain so we want to charge. Basically if it costs us extra time or resources to maintain the service then we want to charge for it.
Open source contributions
We want to take a portion of the proceeds to donate to open source projects we are using. We use lets encrypt so that would be an obvious choice.
I think we should try to contribute 25% of profits to open source. We can play around with the percentage.