Re:How we manage plans and features in our SaaS app
by jv22222 on Sunday March 24, 2019 @02:16AM
(#19474745)
Just a note that if you're using Stripe you get that upgrade downgrade history for free, so might not need the complexity.
Also ProfitWell plugs in to Stripe and does a pretty good job with analytics for that for free too.
Of course if you're using multiple payment providers you'll want to roll your own abstraction as the above comment describes.
Re:How we manage plans and features in our SaaS app
by nfm on Sunday March 24, 2019 @05:25AM
(#19475346)
The data isn't lost, but it's not straightforward to query if you don't have a record of it in your own database.
Eventually you'll want to find out what your resubscribe rate is, or what the average interval between subscriptions is. Answering these types of questions via Stripe's API is no fun.
Re:How we manage plans and features in our SaaS app
by shimms on Sunday March 24, 2019 @05:49PM
(#19478985)
Yup - we’ve always duplicated that data in our systems. Aside from anything, if Stripe/payment-processor-of-choice changes their data model, or rearranges feature tiers in the future to make reporting beyond the last 180 days an enterprise add on or whatever, we’d rather not be beholden to them to be able to analyse our business performance metrics.
Re:How we manage plans and features in our SaaS app
by tnolet on Sunday March 24, 2019 @04:59AM
(#19475261)
Valuable addition! And actually, we check do for account_type. So what a trial actually consists of can change over time, as long as the type stays "trial". I left this out of the post for simplicity, but should probably add it.
All billing dunning etc. is done by Stripe billing at this stage.
The account has many subscriptions, only one of which can be the current. The subscription is linked to a plan.
When a customer upgrades, the current subscription ends, and is replaced by a new one. Tracking start and end dates helps with churn and upgrade/downgrade metrics reports, such as time on premium before downgrade etc.
I've also been stung before by checking for a specific plan, as opposed to checking for the abilities or attributes of the current plan. In your example you're checking if the plan name is "trial" to determine if they should have trial limitations put upon them. This becomes tricky if you need to introduce a new trial option, named differently in the future, that needs to co-exist with your current single trial plan set up. I'd prefer to be checking "is the current plan a trial" or ideally link them to a real plan, but check if it is "in trial" (via dates, boolean etc).
I've seen (but not done myself) products that let you move up and down between plans during trial so you can really assess the impact of not having feature available on higher plans. Doing this is impossible with a single plan called "trial".
Subscription billing, dunning, pro-rated upgrade, taxes, discounts etc is a ridiculously complex set of functionality.