Company
We build software
for people who are busy.
Wasavo is an Indian SaaS company. Our customers are receptionists, school clerks, counter staff and shop owners — people with a queue in front of them who do not have time to learn a system. That constraint decides almost everything we build.
What "SaaS" means here
Software as a Service: you rent working software instead of buying a one-time build.
The traditional route was to pay a development shop a few lakh rupees, have the system installed on one computer in the office, and then pay again for every change. When that computer failed — and it always eventually failed — the data went with it.
A subscription inverts that. You pay monthly, open a browser and work. The servers, the backups, the security patches and the updates are our problem. If we stop earning your subscription, that is our signal to fix something — not your problem to live with for the next five years because you already paid.
How we build
Four things we hold to.
One engine, many products
Every product runs on the same messaging core on Meta's official Cloud API. A fee alert and an appointment reminder travel identical plumbing. That's why a new industry product takes weeks rather than a year, and why a fix in the core improves all five at once.
Tenant isolation at the database
Many customers share one system, and every single query is scoped to the account ID. It's enforced in the data layer, not hidden in the interface, and every new endpoint is tested with a deliberate cross-tenant request that must fail.
Derived, never duplicated
Invoice status is recomputed from the payments on record. Appointment status is written in exactly one place. Totals are calculated server-side. When two parts of a system are allowed to disagree about a fact, eventually they will.
Built for the person at the counter
The inbox looks like WhatsApp because that's what the staff already know. Nothing needs a manual. Onboarding is a 30-minute session, and if it takes longer than that, we treat the screen as the problem.
Limits
What we won't do.
A short list, because saying it out loud is more useful than discovering it after you've signed.
Unofficial WhatsApp automation
Only Meta's Cloud API. The cheap tools that drive the consumer app are exactly why people's numbers get banned.
Bought contact lists
You can message people who gave you their number. We won't help send to a purchased database, whatever the use case sounds like.
Clinical decisions by software
No AI prescription suggestions, no disease prediction. The prescribing doctor carries the liability, and we won't put a guess next to their signature.
Holding your data
Full export whenever you want it, including on the way out. Lock-in by inconvenience is not a business model we're interested in.
Under the hood
For the people who ask.
Most customers never need this page. Some do, usually the one technical person on the buying side — so here it is.
Messaging
Meta WhatsApp Business Cloud API, with webhook delivery receipts per message.
Backend
Node and Express, PostgreSQL, versioned migrations, parameterised queries throughout.
Frontend
React with Vite. Built and tested before deploy, never edited on a live server.
Security
bcrypt password hashing, short-lived scoped JWTs, rate limiting, allow-listed CORS, authenticated file access.
Come and poke holes in it.
Bring the awkward questions to the demo — about data, about costs, about what breaks on a bad day. Those are the ones worth answering.