1
0 Comments

Deciding to build Zickt

So it seems that the leading customer support and live chat tools have gaps - I actually need to have a decent customer support tool for another project which is enterprise B2B SAAS.

So I'm doing the unreasonable thing and creating a lower ticket tool that I can use myself. This way I can build what I need and hopefully others find it useful too. The main problem will be distribution. Partly the reason I'm building this is to try to understand distribution and traction closely. What channels will be effective. What channels can I re-use for my enterprise SAAS.

This tool is coming as AI is coming to change the landscape. I can see how incumbents in the area such as Fin are using AI, and while I think there's a lot to model from that, there's also possibly some mistakes. I look forward to having a system where AI is first class but optional. The system should be useful regardless of AI, so firstly I'm building the primitives and the capabilities any system (AI enabled or not) would need, and then bringing in the AI capabilities once I'm happy with a base system.

posted toAvatar for product Zickt
Zickt