The problem
Indian wellness studio owners (yoga, pilates, fitness) run their business out of WhatsApp and a paper notebook. Class schedules, who paid, whose membership is about to lapse, who still owes cash. It works until the studio passes about thirty members. After that, things fall through: members miss classes they paid for, memberships lapse unrenewed for months, and the owner spends more time on admin than teaching.
WellingZen replaces that patchwork with one system, without asking a one-person studio to run a software project to adopt it. The whole brief was everything you already do from WhatsApp, in one place you trust, calm enough that an owner-instructor who is not a software person switches over in an afternoon.
The brand, and the site people land on
Before a screen, the brand. WellingZen had to read as wellness, not enterprise software, so the whole identity is warm and unhurried: a deep forest green on a warm cream ground, earth-toned and calm, with none of the lotus-flower, yoga-pose clichés every wellness app reaches for. The wordmark carries the idea on its own, “Willing” in a plain sans and “Zen” in a serif, the shift in type standing in for the product’s split personality: functional software with a soulful face.
We designed and built the marketing site at wellingzen.com to match, down to the privacy, terms, and contact pages, and carried the same palette into the product’s transactional emails, so a booking receipt feels like it came from the same place as the booking page. The voice rule throughout: show, don’t claim. The line is “replace your notebook,” never “revolutionise your studio.”
Every studio’s own front door
WellingZen is multi-tenant: one codebase runs every studio. But a member never sees the word “WellingZen.” Each studio gets its own booking page on its own subdomain, carrying its name, colours, and classes, so members experience it as the studio’s own front door.
This is why the brand is deliberately quiet. It has to sit underneath each studio’s identity, not stamp itself on top, so the calm palette and restrained type are a product decision as much as a brand one. The owner works in a full dashboard; the member gets a page they can book from in about ten seconds.
Getting in without passwords, and without a wall
The hardest design problem in the product was the front door itself. A studio has three kinds of people signing in: the owner, a front-desk person, and members who booked once and come back months later. Passwords are a non-starter for that last group.
So sign-in is OTP-first: you prove a phone number or an email with a one-time code, then set a PIN. On a device you’ve used before, it’s just the PIN, no code. Identity is intentionally flexible, a member can exist with a phone, an email, both, or (for a walk-in the front desk just added) neither yet, and claim their account later.
None of this is allowed to leak who is already a member. A registered contact and a stranger get a byte-identical response, so the sign-in screen can never be turned into a way to harvest which phone numbers belong to a studio’s clients.
Getting all three right at once, no passwords, no enumeration hole, and still a ten-second return visit, was the single largest body of work in the product.
Booking built for how a studio actually runs
A booking widget is easy. A booking system a real studio trusts is not, and the edge cases are the product:
- Session-pack memberships. A no-show might or might not burn a session, and the owner decides that per plan. Get it wrong and she’s refunding people by hand.
- More than one active pack. When a member books, which membership pays? The product surfaces the choice instead of silently guessing.
- Rescheduling that keeps the money attached. Moving a class carries its payment and membership tie with it, so a reschedule never quietly drops what it was paid from.
- The last spot. Two people tapping it at the same instant can’t both get it; capacity is locked at the moment of booking so a class can’t be double-sold.
None of these show up in a demo. All of them show up in week one of a real studio.
One reminder, on the channel the member reads
Reminders are where a booking tool earns its keep, and where it becomes spam if you get it wrong. The rule we designed around: verify one contact, then send everything on that one channel. If a member’s WhatsApp number is verified, morning class reminders and expiry warnings go there; otherwise email, opt-in. The same person is never messaged on both. WhatsApp is scoped tightly on purpose, reminders, login codes, and payment notices only, never marketing blasts, because that restraint is what keeps a studio’s number in good standing with the people it matters to.
An assistant you can just ask
The owner can ask the product in plain language, “who hasn’t come this month?”, “who expires this week?”, “how does last month’s revenue compare?”, and get a real answer built from her own studio’s data, with the members and numbers she can click straight through to. It removes the step of learning where each report lives. Every studio’s data stays walled to that studio, the assistant included.
The result
WellingZen is live, with its first studios onboarding on their own payments and WhatsApp numbers. Building our own product this way is deliberate: it is how we pressure-test the way we design and ship for everyone else. Every customer-facing behaviour is written as a plain-language user story with acceptance criteria and tested before it ships, so “it works” is something checked, not felt. Careful is the feature, not a missing coat of paint.