Founders don't open the CRM: why WhatsApp-first operations is hard to beat
In Türkiye, SMB founders don't log into CRMs — they live in WhatsApp. What we learned building Omnirago about WhatsApp Business automation, multi-tenant SaaS, and tools that operators actually use.
For two years, I’ve had product conversations with SMB founders. Whatever the industry — medical supply, textile dealer networks, clinics, dropshipping — the same pattern repeats: the founder doesn’t log into the CRM.
Some of them don’t even remember the password to the system they paid 50,000 TL for years ago. The Salesforce account they signed for is gathering dust.
What do they actually use? WhatsApp.
The “WhatsApp-first” reality in numbers
WhatsApp penetration in Türkiye for adults over 18 is close to 95%. An SMB founder’s daily WhatsApp message count easily exceeds 200. A textile dealer is simultaneously tracking 6 customers and 3 production workshops across 12 Telegram groups.
If operations happen on WhatsApp, the system must live on WhatsApp. Otherwise the founder bypasses the system, the system conflicts with the founder, and data becomes inconsistent.
The “let’s train the team on the CRM” fallacy
The classic B2B SaaS playbook goes: “Founder not using the CRM? Let’s run training. If they still don’t, let’s track usage metrics and send reminders.”
This is refusing to admit it’s not designed for the founder. The founder is 60, mobile-first, has no concept of work hours, and if a tool’s value proposition is “useful once you learn it” — you’ve lost.
If a tool’s value proposition is “useful once you learn it,” the founder isn’t using it.
Taking the WhatsApp layer seriously
The core decision in building Omnirago was: WhatsApp and Telegram as first-class citizens. Not a CRM with a “WhatsApp Integration” checkbox in the sidebar — a system that runs inside WhatsApp.
What this looks like in practice:
- Customer records open from WhatsApp. If the founder sends “save Ahmet,” an AI assistant extracts name, phone, industry and creates the CRM record.
- Deals close in WhatsApp. When a customer requests 3 SKUs, the message is parsed into a draft order. The founder confirms with one “ok.”
- Invoices fire from WhatsApp. A “bill Mehmet” message connects to the e-invoice infrastructure, returns the PDF to the customer via WhatsApp.
This architecture decision comes with a tax: WhatsApp Business API’s rules (24-hour active session window, template message approval, per-channel rate limits) shape the core. CRMs that bolt on “WhatsApp plugin” later discover this and wear out.
Telegram: the dealer and supplier layer
There’s a quirk in Türkiye. B2C communication happens on WhatsApp; B2B coordination happens on Telegram.
Textile dealer networks, medical distributors, companies working with overseas suppliers — they share collection images, order tables, shipping screens in Telegram groups. The reason is simple: high file size limit, advanced group management, official bot infrastructure.
Omnirago’s Telegram layer is built on this: when a dealer asks, the bot answers stock; from a channel, an order opens; in the team’s private channel, the founder report posts.
The role of AI: operator multiplier
Once WhatsApp and Telegram are natively bound to the system, message volume scales fast. If the founder is solo or works with 1-2 operators, they can’t keep up manually.
The AI layer kicks in here:
- Conversation summarization. An 87-message group, summarized to 3 lines without reading.
- Customer segmentation. “Customers who ordered last month but went silent this month” works in natural language.
- Follow-up suggestion. Which customer, in what tone, consistent with prior conversation.
This is not operator replacement — it’s operator multiplication. One operator manages 200 customers instead of 50, with no increase in error rate.
Practical takeaway
The best software for an SMB founder is the software they can forget exists. WhatsApp feels natural to them; don’t show the system behind it, in fact let them forget about it.
That’s Omnirago’s design target. In the next post I’ll go into the multi-tenant architecture choices — the “every dealer runs on their own data, all on one infrastructure” pattern.
Pilot inquiries: Omnirago is in early access. For an industry-specific pilot: hello@ragomind.com.