Priya is a yoga teacher. She loves teaching. She hates spreadsheets. She was spending more time chasing payments than leading classes. We built her a way out.
Ho Saksham (Hindi for "become capable") is a SaaS tool for independent service providers — yoga teachers, tutors, trainers, coaches — who need to manage subscribers and collect recurring payments without an accounting degree.
The core idea: make it feel like money is being stored in the app, not like filling out a form. Built around trust, simplicity, and the reality that most small providers run their businesses from WhatsApp.
Priya is a Priya runs her own yoga studio — 15–20 regular students, monthly plans, and a deep aversion to anything that smells like admin. We built an empathy map to understand her world before touching any wireframes.
Before any wireframes, we spent time understanding how Priya thinks about money — not accounting logic, emotional logic. What we found shaped every design decision that followed.
We studied how the best products handle money, onboarding, and payments — then took only what Priya needed.
UX laws as lenses, not rules. Context-specific insight always won.
Inspired by Google Pay's OTP-first approach and Groww's calm, step-by-step onboarding — we designed a sign-up flow that gets Priya from splash screen to verified in under 60 seconds. No password to forget. No form to fill. Just a phone number and a 6-digit code.
Right after verification, Priya sets up her business identity — the name, logo, and category that represent her yoga studio. We kept it minimal: only what's needed to start receiving payments. Logo upload uses the native photo picker, kept privacy-safe with a "this app only accesses selected photos" permission pattern.
This is the heart of the Monzo inspiration. The moment Priya opens the app, she sees one number: how much she received this month. Not expenses. Not balance. Not net. Just: money that came in. Everything else — adding bank account, plans, subscribers — sits below that number.
No wallet. No middleman. Inspired by Google Pay's direct bank transfer model, we built a flow where Priya's payments land straight into her savings account. She can search from popular banks or add details manually — giving her full control over where her money goes.
The subscription plan is Priya's product — her yoga class, her price, her terms. We gave her full control: category tags, billing cycle, location, and discount options. Adding a subscriber then takes 30 seconds — name, mobile, charge date, done.
This is the moment everything comes together. Priya selects a month, picks a plan, sees every subscriber's status at a glance — Active, Inactive, Paid — and sends bills to whoever hasn't paid yet. The whole thing takes under a minute. Then a confirmation screen tells her it's done.
No product solved Priya’s exact problem. The closest — Zoho Billing — is built for businesses 10x her scale and complexity.
This was both a validation that the problem was real and underserved, and a reminder that we had to design from first principles rather than benchmarking existing solutions. When the competition is a sledgehammer, build a scalpel.
Not a handoff — a conversation. We stayed in sync from early wireframes to the final Flutter build, keeping a shared design language so nothing got lost.