Waflow.io CRM

For years, I ran a web development services business — building sites and apps for small businesses across India. Somewhere along the way, I noticed the same pattern over and over: no matter what industry the client was in, the actual business — sales, support, orders, follow-ups — was happening in WhatsApp. Not in the CRM I'd just built for them. Not in the inventory spreadsheet. In WhatsApp, on someone's personal phone.

That disconnect kept bothering me. WhatsApp was where the customer relationship lived, but there was no real system behind it — just a phone, a spreadsheet, and whatever the owner could keep in their head.

So I started building Waflow.

What it started as, and what it became

Waflow began as a simple WhatsApp CRM: a shared team inbox so more than one person could handle customer conversations without everyone fighting over one phone. That alone solved a real pain point. But once businesses had their conversations centralized, the next problem showed up immediately — they still had no connection between chatting with a customer and selling to one.

So Waflow grew. Piece by piece, mostly driven by what I kept seeing while building for real businesses:

• Team inbox — WhatsApp and Instagram conversations, contacts, and broadcasts in one place, with roles and automated agent assignment

• Commerce — product catalogs and WhatsApp commerce, so selling can happen inside the chat itself

• Retail operations — inventory, supplier and purchase order management, goods receipts, stock counts and transfers, POS, billing, cash sessions, and returns

• Engagement — customer segmentation, broadcasts, loyalty programs, and analytics

• Automation — an AI-powered chatbot layer (RAG-based, so it actually understands a business's own data instead of following a rigid script)

• Integrations — REST APIs, webhooks, and connections like Razorpay and Google Sheets

Today Waflow is closer to a full operating layer for SMBs on WhatsApp than a "chat tool" — retail, commerce, and customer engagement, all from one place.

Building it solo

I'm building Waflow as a solo, full-stack founder. My background moved from PHP/CodeIgniter web development into Flutter and native Android, then into DevOps (Docker, AWS), and most recently AI/LLM integration — so I've been able to build and operate the entire stack myself rather than translating ideas through a team. That's been slower in some ways, but it means every feature that ships is something I understand end-to-end, from the database to the WhatsApp API to the UI.

I've also gone through the process of becoming a Meta Business Partner and WhatsApp BSP sub-partner directly, which meant learning the compliance and App Review side of this ecosystem as closely as the product side. That part isn't glamorous, but it's exactly the kind of groundwork that's easy to underestimate until you're the one doing it.

Where things stand

Waflow is in early traction right now, focused on Indian SMBs and expanding into GCC markets. The near-term goal is simple: keep talking to the businesses actually using it, keep closing the gaps between "chatting with a customer" and "running the business," and get the direct BSP badge to reduce third-party dependency as we scale.

If you're building for SMBs, working in the WhatsApp/commerce space, or just have thoughts on this problem — I'd genuinely like to hear from you. Happy to answer anything about the stack, the BSP process, or building this solo.