Ask HN: How do you split your SaaS features into plans?
I&#x27;m doing a side project which purpose is to experiment if I can build a SaaS product and maybe earn some dollars. The app is a web-based REST api monitoring&#x2F;tester tool, and I&#x27;ve been struggling with splitting features into packages that actually makes sense.
The core features are like having API calls defined with parameters and assertions as cases, and then you can run them in every 1&#x2F;5&#x2F;15&#x2F;60 minutes and get a report in email&#x2F;slack if something went wrong.<p>I have no experience on what works in real life so I&#x27;d appreciate any feedback from similar people who has done A&#x2F;B testing or has any experience regarding this.<p>My current idea is: - Basic: max 1 user &#x2F; max 5 case &#x2F; 60 mins frequency - Startup: max 5 users &#x2F; max 100 case&#x2F; 5 minutes frequency - Enterprise: unlimited users &#x2F; unlimited case &#x2F; 1 minutes frequency<p>And the main selling point for the most expensive plan would be an ability to run collections through an API so that it can be wired into CI build.<p>Any thougths? Thanks!