Hi IH,
I'm looking for some genuine startups (established or new) who need a ticketing system for support of their product. You must have a built product to qualify.
I run https://supportlayer.app, which offers support without the boundaries and feature gates of the main players. Having been a developer for nearly 30 years now, I finally built one that suits me rather than overpaying for ones that have crazy bloat and excessive prices.
I use this exclusvely for supporting my SaaS products, and (yeah, I built it!) I love it.
Your first seat is always free - forever. If you need more, you will get a discount code for FREE access for up to 5 seats for a whole 12 months to help you grow without worry.
Sign up, try it out, and if you need more than the 1 seat, raise a support ticket and reference IndieHackers!
I would love your feedback on the product, so all comments gratefully received.
The strongest angle here is not just “cheaper support ticketing.” A lot of founders already know Zendesk/Freshdesk/Intercom are bloated, but the sharper pain is that early SaaS teams need support to feel professional before they are ready for enterprise-priced tooling.
That positioning matters because “doesn’t break the bank” can sound like a discount tool, while the real promise is more serious: clean support infrastructure without feature gates, pricing traps, or unnecessary complexity.
The naming layer is important here too. SupportLayer.app explains what it does, but it also feels very functional and app-like. If this becomes a trusted support system for startups rather than just a lower-cost ticketing app, Beryxa.com would give it a stronger SaaS brand with more room to grow beyond basic ticketing.
Hi Aryan,
Thanks for your feedback! You're right, it's not intended as a bargain basement ticket system. It has most, if not all, of the features of the 'big guys' without the gating and prohibitive pricing. However, price is very sensitive in the startup world. You need as much as you can get for as little as possible, and this is where we sit.
Thanks again, I'll be sure to check out Beryxa!
Hi Jay, one practical thought after our SupportLayer/Beryxa discussion.
The core positioning challenge here is sharp: you want startups to understand the product is affordable without making it feel like a cheap support tool.
That is exactly the kind of naming/positioning decision I’ve started helping founders pressure-test in a focused audit.
I can do a short written breakdown covering: current name risk, domain perception, category framing, whether SupportLayer can scale beyond ticketing, and what stronger brand direction would make the product feel like professional support infrastructure rather than just a lower-cost app.
Not a long consulting thing. Just a clear outside read you can use before more customers, docs, onboarding, and support links build around the current name.
I’m doing a few of these at $99 while refining the format. If useful, connect here and I can put together a focused read for SupportLayer:
https://www.linkedin.com/in/aryan-y-0163b0278/
That makes sense. Price sensitivity is real for startups, but the key is making the product feel affordable without making the brand feel cheap.
That is the line SupportLayer has to walk.
SupportLayer.app is clear, but it frames the product as a functional support app. If the real promise is professional-grade support infrastructure for startups without enterprise pricing games, the brand has to carry more trust than the category descriptor.
That is why Beryxa stood out here. It feels more like a serious SaaS company than a support utility, and it gives you room to expand beyond ticketing into inbox, customer ops, automation, knowledge base, or broader customer support workflows.
I would not leave the naming decision too late if you already see this becoming more than basic ticketing. Once customers, docs, onboarding, and support links start forming around SupportLayer.app, switching becomes harder.
If Beryxa feels like a serious fit after you check it out, send me a connection request here. We can discuss the acquisition side privately and see if there is a founder-friendly way to make it work before the brand gets locked into the current frame:
https://www.linkedin.com/in/aryan-y-0163b0278/