‎I think automation is the easy thing to measure, so companies naturally talk about it more. Consistency is harder to put into a simple number. But after an agent has been running for months, that reliability could be more valuable than the hours saved.

‎

I think the biggest expectation is moving from show me what’s happening to help me deal with what’s happening. That’s a pretty meaningful difference. Analytics and dashboards are still useful, but people increasingly want the next step handled too.

‎

‎

‎I’d build something that saves people time but also connects directly to the systems they already use. AI generating an answer is nice, but AI that can update the CRM, create the ticket, send the email, and move the task forward is much more useful.

‎I think users care less about whether there’s one agent or ten agents and more about whether the experience feels seamless. If multiple agents can work together without making the user repeat themselves, I don’t really see a problem with specialization.

‎

‎I can definitely see the appeal. Managing an AI agent can turn into a lot of clicking around once you start dealing with knowledge, instructions, analytics and workflows separately. If Backstage can bring most of that into one conversation, that could save a decent amount of time.

‎

The funny thing about early SaaS growth is that the channel you spend the most time planning for isn’t always the one that works. Sometimes it’s one customer, one community post, or one random introduction that starts everything. I’d be really interested to hear how many people here got their first 100 in a way they never expected.
‎

‎I think the biggest thing for me would be whether the platform actually gets better over time. If the AI can learn from real support conversations, spot common issues, and help the team improve the whole process, that’s much more valuable than just having a chatbot answering basic questions.
‎

‎I like the idea, but I think the maintenance side is what would really convince me. It’s easy to say one agent across every channel, but if you still have to keep tweaking things for each channel, some of that simplicity disappears. The shared knowledge and workflows definitely make the approach interesting though, especially for teams dealing with a lot of repetitive support requests.
‎

I’ve started looking at customization a bit differently. Not every improvement needs to become a permanent part of the product. Sometimes a simpler setup that the team can actually maintain is more useful than having an AI stack with tons of clever custom logic. The hard part is knowing what’s worth keeping.
‎

I’ve always felt that real users expose things you just won’t see while building in isolation. You can have hundreds of people join a waitlist and still have no idea what they’ll actually do once they get access. I’d probably launch earlier, keep the first group small, and use their feedback to shape what comes next.
‎

Yeah, I think that’s the real difference. A lot of these platforms look great when you’re just watching a demo, but production is a different story. For me, being able to actually take action, connect with the tools the business already uses, and hand things over to a human without losing the context is what really matters.

Yeah, I’ve noticed that too. Some of the smaller SaaS products I’ve randomly come across are actually really good, but hardly anyone talks about them. I’m always interested in finding those kinds of tools, so I’m curious to see what people recommend here.

Yeah, this is something I’ve been curious about too. PocketBase looks great for getting an idea off the ground quickly, but I always wonder what happens once real users start piling in. I’d love to hear from someone who’s actually been running a SaaS on it for months and what surprised them along the way.