01 · Model
Define the tenant boundary
We designed accounts, numbers, users, access, and licensing before adding customer-facing features.
Case study · SaaS product engineering
WhatsApp SaaS development case study: Loopwave
Loopwave turns one WhatsApp number into a shared team inbox with CRM, tickets, broadcasts, AI replies, and tenant licensing. Its backend shipped with 110 passing API tests.
Measured result
What changed after launch
110
passing API integration tests
1 number
shared by a complete team
Real time
multi-agent conversation sync
Per tenant
licensing and expiry controls
The brief
The product problem we had to solve
A team answering customers from one WhatsApp number quickly loses context. Two people reply at once, another message gets missed, and sales data stays trapped inside a chat history.
Loopwave also had to be a product that could be sold to separate businesses. That meant real-time sync, permissions, tenant isolation, licensing, operational tools, and a backend that could be tested with confidence.
What we built
Shared real-time WhatsApp inbox
Conversation assignment and resolution
CRM, tags, and customer lifecycle
Tickets and message templates
Broadcast campaign tools
AI auto-reply workflow
Role-based team access
Per-tenant licensing and expiry
Analytics and audit logs
API integration test suite
Delivery timeline
From problem to production
02 · Core
Build real-time messaging
The WhatsApp engine and live team inbox established the product's hardest technical path.
03 · Product
Add the operating system
CRM, tickets, broadcasts, AI replies, analytics, and roles turned messaging into a sellable SaaS.
04 · Proof
Test the backend deeply
The release reached 110 passing API integration tests across the product's critical behavior.
The outcome
Built to keep working after handover
One number could support a full team without losing ownership of each conversation.
Per-tenant licensing let the product be branded, sold, and controlled for separate customers.
The 110-test API suite gave future changes a clear safety net after handover.
This case study maps directly to our product engineering service. We can use the same delivery system for your product without copying the product itself.
Client note
What they said
“One number, the whole team replying in real time, with a CRM, tickets, and licensing built in. It's a product we can actually sell, not just use.”
Loopwave
Shared WhatsApp team inbox