We didn’t set out to build another CRM

In the early days, we were building a CRM. Like everyone else, we thought the problem was features — pipelines, fields, dashboards. But when we started working closely with customers, we kept hearing a version of the same thing: “It’s not magic… my WhatsApp can’t just update my CRM.” Not as a feature request — more like a statement of how things are. Messages stay in WhatsApp, the CRM lives somewhere else, and someone has to sit in between and move the information manually.

The more we looked at it, the more we realized we were doing the exact same thing. Our own work was running on WhatsApp — leads, conversations, decisions, important details — all scattered across chats. We tried using CRMs, to-do tools, task managers, bug trackers, Slack, and every other productivity tool we could find. But somehow, everything kept coming back to WhatsApp. It was easier, always there, and just how work naturally happened. The tools existed, but keeping them updated felt like extra work, so they slowly fell out of sync with reality.

That’s when it clicked. The problem wasn’t that businesses needed better CRMs or more tools. The problem was that the way businesses actually run — inside conversations — is completely disconnected from the systems meant to organize them.

So we stopped thinking about building another CRM and started asking a simpler question: what if the system didn’t need updating at all? What if the information organized itself as the conversation happened?

That’s what led to Zeldin.

It listens to the same messages you already rely on and turns them into structured, usable data in the background — capturing what matters, keeping things in sync, and quietly doing the work that usually falls through the cracks.

No extra steps. No separate workflow to maintain.

Just everything staying organized, as the work naturally happens.