I have multiple SaaS apps I manage and others which I have assisted developing. Starting off, I've always done the following: 1. Free option with a limited nu

I have multiple SaaS apps I manage and others which I have assisted developing. Starting off, I've always done the following: 1. Free option with a limited number of queries 2. Premium option with unlimited number of queries and a few "key" features unlocked. This simplifies development significantly, as all you have to do is track the queries (per hour, day, month, total, etc.). You can also limit routes based on the features. This has been extremely effective on my website Easy-A.net (https://easy-a.net/ https://easy-a.net/), essentially people can view the grade distribution for courses and we estimate the workload. Pricing is always difficult, and by scaling it based on API hits it's much easier to price. It's essentially pay for use. I think (as identified in the first line of the article): > How do you deal with what a user can do on their account in a SaaS app? Can Jane on the "Starter" plan create another widget when she is near the limit of her plan? What if she's a trial user? If as a SaaS you're typically targeting one customer archetype starting off -- then you should only have two plans. One to get their feet wet, the other to help them dive in.