Amazing job on building something, but you're giving up way too soon. With respect to Jason, there's no guarantee that every SaaS charging less than $50 / month is going to drown in support costs. Let's do the math, shall we?<p>Suppose you want to make $10k MRR with this. You need 500 monthly users, right? Realistically, a good chunk of them aren't going to even use the product very often, despite paying for it. This is even more true since it's cheap. You could easily end up with fewer than 100 of the 500 logging in and using the product on any given day. Of those, maybe 5-10 are going to actually need support, and you could easily cover half of that with an FAQ, training videos, etc. So on any given day, you might get 2-5 emails from your 500 customers. Even if it's 10x that, you could probably churn through 20-30 support emails in 1-2 hours just by yourself, or you could hire someone for $500 / month to do it for you. And support requests are going to drop over time as you improve the product, fix bugs, etc.<p>For the record, none of this is theoretical. I've run multiple profitable saas / recurring revenue projects and I've never had to deal with "drowning" in ongoing support requests. Supporting <i>free</i> users is a different question, and freemium can genuinely be challenging in terms of support requests, but even there it's not <i>that</i> difficult to handle larger volumes of support requests with automated methods to cut down 90% of it. And if you have a handful of problematic customers who are a constant source of stress, you can fire them. They're not worth your sanity, especially for $20 / month.<p>A better question might be: why are you giving up so quickly? Is it really that you think it's not possible? Or maybe something else going on here?