Show IH: Website chat without the bloat
I built Knok because I needed a simple website chat widget for my SaaS. I realised that all the existing products I used and loved turned into full-blown CRMs with AI and a load of features I didn’t need. And a price to match! Knok is simple, fast, and affordable.
Trending on Indie Hackers
This interface looks incredibly clean, awesome job on the launch!
This is a clean wedge. “Website chat without the bloat” is easy to understand, and the anti-CRM angle is strong because most chat tools really have become too heavy for small SaaS teams.
The risk is that Knok may undercut that simplicity a bit. The product promise is lightweight, fast, and no-bloat, but the name plus .chat extension keeps it boxed into “just another chat widget.” If this stays small, that is fine. But if you add inbox, routing, team workflows, customer history, or lightweight support automation later, the current naming frame may start feeling too narrow very quickly.
For the broader direction, Xevoa .com would carry this better. It feels more like a clean software/workflow product, while Knok.chat feels like a feature-level tool. I would pressure-test this before launch pages, docs, and customer memory harden around the current name.
I want to keep Knok intentionally small.
The gap in the market is there because many existing players realised they could capture a bigger share by continuously adding more features. But in doing so, they also pushed away a lot of smaller customers who just wanted simple website chat.
Knok exists to fill that gap.
I think resisting “just one more feature” will probably be one of the hardest parts as the product grows.
That makes sense. If the whole strategy is intentional restraint, then the positioning should probably lean harder into that rather than making Knok sound like another support suite.
The question I’d pressure-test is not “should Knok become bigger?” It is whether the name/domain makes the product feel simple and trustworthy, or simple and disposable.
That distinction matters for small SaaS teams because they still need customer conversations to feel reliable, even if they do not want a heavy CRM.
If useful, I can do a focused naming/positioning audit on this: current name risk, .chat perception, trust signal, category framing, and whether Knok can hold the “simple but serious” position before launch/customer memory builds around it.
I’m doing a few of these at $99 while refining the format. If not useful, no worries.
That makes sense, and honestly that restraint is probably the real product strategy here.
If Knok wins, it will not be because it becomes Intercom-lite. It will be because it stays deliberately smaller, faster, and easier to adopt than the tools that kept adding layers until small teams no longer wanted them.
My naming point is slightly different then.
Even if the product stays small, the name still has to carry trust. For a tiny side widget, Knok.chat works. But if this becomes the simple customer conversation layer a small SaaS puts on its public site, the brand has to feel lightweight without feeling disposable.
That is where I’d still pressure-test it. The product can stay intentionally small, but the name should not make it feel temporary or feature-level. Xevoa.com would give you the same clean software feel without forcing you into a bigger product roadmap.