WBOS • WhatsApp Business Operating System

Every business needs software.
Nobody needs another app.

A CRM and operations engine inside WhatsApp.
No website.
No app.
No server bill.
Live demo ready.
Built by
Rishvin Reddy • Sparsh Jhunjhunwala • Lakshya Bamboli
APIs Dashboard Realtime Zero Apps
WhatsApp
Conversation Engine
Owner
Staff
Dispatch
Customer
The problem

Small businesses get
sold the wrong thing.

Expectation

What they're told to buy

  • A custom website — ₹30k–₹1L, then hosting forever
  • A mobile app nobody downloads for one shop
  • Infrastructure that falls over the one day traffic spikes
  • A dashboard they need training to operate
Reality

What actually happens

  • The site goes stale in three months
  • Customers call or WhatsApp anyway
  • Orders live in chat scroll and memory
  • Zero record, zero analytics, zero follow-up
The software isn't the hard part.
Getting a customer to use it is.
The insight

Stop building destinations.
Go where the customers already are.

Already installed

WhatsApp is on effectively every phone your customer owns. Install rate: 100%. Learning curve: none.

Already open

They check it dozens of times a day. You don't need to earn a visit — you're already in the list.

Already trusted

No signup, no password, no payment page anxiety. It's a chat with a shop they know.

So we put the CRM behind the chat
instead of building a storefront beside it.
What we built

Not an app. An engine.

Interface

Customer side

2 kg rice, 3 milk packets, 1 oil
🧾 Order #14 · ₹586
Packing started · track: /track/14

Plain text. No menus to learn, no link to click, no account to make.

System

Business side

  • CRM InboxEvery customer, every message, searchable, with one-tap human takeover.
  • Job BoardLive pipeline, no refresh.
  • Floor TerminalChecklist for whoever fulfils it.
  • DispatchCustomer tracking link.
The core bet

Every business is the same five steps.

01
Conversation
Customer states what they want
02
Catalogue
Match it to what you sell
03
Job
Priced, confirmed, recorded
04
Pipeline
Staff move it through stages
05
Proof
Delivered, notified, logged

A grocery order, a pharmacy refill, a restaurant ticket, a laundry pickup,
or a repair job—all follow an IDENTICAL SHAPE.
Build the engine once and configure the vocabulary for each business.

Proof of the engine

We shipped one vertical end to end.

Grocery retail was chosen because it's operationally the hardest.
If the engine works here, simpler industries become configuration problems.

Chat bot

Onboarding, catalogue, order capture, status pushes

OS console

Live board + CRM inbox + human takeover

Floor terminal

Fulfilment checklist, stock control

Dispatch

Assignment, acceptance, live map for the customer

Shared WebSocket Bus

All four sync over one WebSocket bus.
No polling. No refresh button.

Live demo · what you'll see

Chat to doorstep in six moves.

01
Customer
Menu shown
List sent
02
Parse
Catalogue matched
Invoice returned
03
Accept
Job created
Invoice sent
04
Fulfill
Checklist complete
Stock updated
05
Dispatch
Assigned
Tracking shared
06
Closed
Receipt sent
Revenue booked
LIVE API CALLS • LIVE WEBSOCKET EVENTS

Nothing in this demo is a click-through mockup.

Same engine, different business

Change the vocabulary, not the code.

Business
Catalogue
Pipeline
Closes
Grocery Built
Stock Keeping Unit
Pack Ready
Rider
Pharmacy
Medicines + Rx
Verify Pack
Rider
Restaurant
Menu
Kitchen Ready
Pickup
Laundry
Services
Wash Ready
Return
Hardware
Products
Quote Approve
Counter
Salon
Services
Confirm Visit
Walk-in

Five of six industries require
ZERO NEW PRIMITIVES.
Only vocabulary changes.

Architecture

One service. One event bus. Four role surfaces.

WhatsApp
Meta Cloud Webhook
Conversation Engine
State Machine • Catalogue • Jobs
Database
WebSocket Bus
Owner
Console
Staff
Terminal
Dispatch
Portal
Customer
Tracker
How a new business gets onboarded

The engine never changes.
Four things do.

📦

① Catalogue

  • Products
  • Pricing
  • Units
  • Stock
🔀

② Pipeline

  • Rename stages
  • Reorder flow
💬

③ Messages

  • Greetings
  • Templates
  • Status updates
👥

④ Roles

  • Rename roles
  • Chef
  • Technician
  • Pharmacist
NEVER CHANGES
Webhooks
Engine
CRM
Human Takeover
Tracking
WebSockets
TARGET ONBOARDING
1 WORKING DAY
1. Connect WhatsApp
2. Import Catalogue
3. Configure Messages
4. Train Staff
Straight answers

Where we actually are.

LIVE TODAY
  • Webhooks
  • CRM
  • State Machine
  • Realtime Sync
  • Grocery Complete
DEMO SHORTCUTS
  • GPS simulated
  • Cash / UPI
  • Analytics seeded

Everything shown today
is production architecture.
Only configuration remains.

Why this wins

Distribution beats features.

Customer Experience

📱 Zero Install

Customer uses WhatsApp
Owner uses a browser
Nothing to install

No Traffic

Chat queues
No homepage spikes
No crashed sites
Operations

💻 One Laptop

Single process
Low infrastructure cost
Affordable for SMEs

📝 Audit Trail

Every message logged
Every status tracked
Database-backed
Platform

♻️ One Engine

Shared engine
Industry-specific config
No rewrites

🛡️ Graceful

Offline simulator
No credentials required
Reliable demos

Every advantage comes from the architecture,
not feature count.

Built, not slideware

What's actually running.

Platform
🌐
REST APIs
Public + Internal endpoints
1
Realtime Event Bus
🗄
7
Core Tables
Product
🖥
4
Live Interfaces
Role-based dashboards
📦
0
Apps to Install
Browser & WhatsApp only
NEXT 90 DAYS
✓ Configuration Layer Multi-Tenant Payments Live GPS Analytics
The architecture is running.
The next 90 days are configuration, not reinvention.
Thank you

Software where
the customer
already is.

Live demo ready.
Message the WhatsApp number.
Watch four dashboards react.
Tell us your business.
We'll show you exactly
what changes—and what doesn't.
One engine.
Many businesses.
Zero rewrites.
Questions?
WBOS • WHATSAPP BUSINESS CRM