I'm currently developing a zero-backend AI website builder, but the market seems really crowded right now. User conversion is getting tougher, as many established teams prefer bigger platforms. I'm considering a pivot to focus on zero-backend Stripe billing, which would allow users to easily manage pricing plans, credits, and usage limits without the need for complex backend setups. Before I dive into development, I want to know if this is genuinely a problem worth addressing, or if existing solutions cover it sufficiently well. I'd really value your honest opinions on this idea.
4 Answers
From my perspective, this isn’t really a pain point. Most of the solutions we use are working just fine. It feels like a niche problem that may not appeal to a broader audience.
I have some reservations about adding yet another layer on top of Stripe. If this new service isn’t open source, it could lead to vendor lock-in, which is something I try to avoid. I'm curious about what aspects of lock-in you feel would be most problematic.
I'd be most worried about data portability and what happens if I want to switch later. Losing control over pricing changes is also a concern for me.
I think there’s a market for this, but it’s definitely niche—mostly smaller SaaS companies or side projects. The key challenge will be showing that it’s quicker and less prone to errors while integrating well with existing systems. If you can nail that, it might have potential!
Honestly, I’m not sure this is a big issue for most companies. Many are already comfortable with Stripe as it is. Adding another layer might just complicate things rather than help.
That’s an important perspective to consider. Thanks for sharing your thoughts!