First Contact
Discovery
Information
Decision
First Class
Enrollment
Retention
2
1
3
4
5
6
7
BEFORE
Scattered referrals
WhatsApp flyers, Instagram, word-of-mouth — no single source of truth
Cold WhatsApp message
20–30 min manual loop
Student arrives with zero context. Every inquiry starts from scratch.
Structure, schedule, philosophy, pricing — explained from zero, every time
No guided filtering
No "who this is for" framing — misaligned students enrolled anyway
Manual follow-up, payment via screenshot — zero automation
No prior context set — first class could surprise or disappoint
5–6 month retention held — but growth was capped by bandwidth
Google Form + screenshot
Expectation gap
Strong but capped
Phase 1 Redesign - what the website now does
AFTER
SEO-indexed website
One canonical source. Search, referral, flyer — all arrive at the same truth.
Cold WhatsApp message
20–30 min manual loop
Student arrives having read what the practice is, who it's for, what to expect
80%+ of recurring questions answered digitally before a message is sent
No guided filtering
Clear expectation-setting means only aligned students reach the CTA
Wording signals a considered process. Filters for seriousness before the 1:1.
Student knows the philosophy, pace, and structure before they arrive
5–6 month retention holds. Phase 2 automation foundation already built.
Google Form + screenshot
Expectation gap
Strong but capped
First Contact
Discovery
Information
Decision
First Class
Enrollment
Retention
USER ACTION
Sees referral or flyer, searches online
Lands on website — reads hero & about
Reads FAQ, Offerings, "Who This Is For"
Reads testimonials → clicks CTA
Sends WhatsApp inquiry — pre-informed
Attends first class with accurate expectations
Renews — aligned from the start
FOUNDERACTION
NO ACTION NEEDED. HANDLE BY WEBSITE.
Intentional 1:1 — confirms seriousness, builds the trust that drives retention
Teaches class — full attention, no admin overhead
Monitors retention, gathers feedback
The website's job is to handle as much work as possible, so the founder's time is spent only where human judgment is irreplaceable.
"
Vaidehi Yoga: Designing a service system for a live practice
A real business with real retention. I designed the full customer arc from first discovery to long-term retention as founder, sole designer, and the person accountable for every outcome.
ROLE
TIMELINE
SCOPE
HEADLINE OUTCOME
Founder · UX & Service Designer · Operator
Jan 2024 – present (live & evolving)
Onboarding friction cut 50–60% · 5–6 month avg. retention
Research · Service blueprint · Onboarding · Communication · Pricing · Operations
The complete service arc, before and after Phase 1. Same seven stages, redesigned system: the ~3 hr/week manual explanation loop became digital self-service, cold inquiries became pre-informed ones, and 50–60% of onboarding time was eliminated — stage by stage, with the friction named at each step.
A teacher with a practice. No system around it.
01 Context
I'm a 500-hour certified Hatha Yoga teacher. In early 2025, I had a real product (live online classes), real users (students), and full authority over every decision - plus full exposure to every consequence.
What I didn't have was a service. Inquiries arrived through scattered channels with the same questions every time. Onboarding happened over long back-and-forth message threads. Scheduling, payment, and class communication were all manual. Each new student costs hours; each hour comes out of teaching.
This case study is about turning a practice into a designed service system - and because I was both designer and operator, every decision here was tested against reality within weeks.
The interface was fine. The seams were broken.
02 The problem
Success had to be measured on both sides of the service blueprint: frontstage (students feel informed, welcomed, and committed) and backstage (my time per student drops enough that the service can grow).
How does a one-person service deliver a many-person experience, without breaking the one person?
The classes themselves were good — retention proved that later. The friction lived between touchpoints: between a social media post and an inquiry, between an inquiry and a first class, between a free trial and a payment. Framed as a design problem:
The blueprint's one rule: the website absorbs every task it can — discovery through decision — so founder time is spent only where human judgment is irreplaceable: the enrollment conversation, the teaching, the retention.
Fifteen competitors, real conversations, and one uncomfortable pattern
03 Research
Finding
Decision
Result
Every inquiry asked the same 6–8 questions (schedule, level, language, fees, equipment, trial). The information existed — it just wasn't structured anywhere findable.
Restructure the entire pre-enrollment journey around answering questions before they're asked: rebuilt information architecture, a single registration flow with Terms & Conditions built in.
Inquiries now arrive pre-informed. Onboarding conversation time cut 50–60%.
I ran product discovery the way I would for any client: competitive analysis across 15+ yoga and wellness services, conversations with current and prospective students, and a full audit of my own inquiry threads — the rawest research data a designer can get, because people ask exactly what confuses them.
Three findings shaped everything that followed:
Finding
Decision
Result
Competitors split into two camps: high-volume marketplaces competing on price, and personal teachers competing on trust. The middle was empty, and the marketplaces' own reviews showed students missing personal attention.
Position deliberately as small-batch and personal: limited cohort sizes, a single intentional evening batch instead of scattered slots, premium-of-one pricing — raised for new students, honored for existing ones.
Free pilot participants converted to paying customers within 2 months of launch. Average retention reached 5–6 months in a market where month-to-month churn is the norm.
Finding
Decision
Result
Drop-off risk concentrated at the start of each class and in the gaps between classes — students arrived rushed, and silence between sessions read as indifference.
Design the ritual layer: a consistent class-opening protocol (students settle in Shavasana before class begins) and a warm, brief, predictable communication cadence between sessions.
The experience became recognizable and calm — the qualities students cited when they stayed. Retention is the metric this shows up in.
Designing the full arc, not just the screens
04 The system
The enrollment flow across three system states. Pre-website: every inquiry triggered a manual explain-and-clarify loop. Phase 1 (shipped): the website carries that conversation, so inquiries arrive aligned. Phase 2 (designed, ready to build): direct registration, integrated payment, automated confirmation — the backstage fully systematized.
I launched assuming more schedule options meant more value, multiple batches, and maximum flexibility. The service data said otherwise: scattered slots fragmented the cohort, diluted the group energy that makes a live class worth showing up for, and multiplied my operational load without adding students. I consolidated to one intentional evening batch. It felt like shrinking the product; it was actually the product decision that made retention possible. Flexibility is a feature only when users value it more than what it costs them.
A wrong assumption I had to unwind
The deliverable wasn't a UI — it was a service blueprint covering five stages, each with designed frontstage moments and backstage operations:
Discovery — content strategy across Instagram, Facebook, and YouTube Shorts built around a clear teaching identity, plus SEO discoverability built from zero so the service could be found, not just followed.
Inquiry → enrollment — one structured registration flow (form, expectations, terms, payment) replacing open-ended message threads. Expectation management designed in: level, language, equipment, and class protocol stated upfront.
First class — a designed first-session experience, because the first class is the product's onboarding screen. Protocol, preparation, and welcome communication all standardized.
Ongoing practice — scheduling, payment, and group communication systematized into repeatable workflows; a monthly thematic structure (an "asana of the month") giving the service a content rhythm students can feel.
Retention & renewal — feedback loops informing iterative service improvements, batch consolidation when data showed scattered slots diluted the experience, and special sessions offered only when genuinely warranted.
Registration wireframe. The form asks about practice history and injuries upfront — qualification designed into the form itself, replacing what used to be a 20–30 minute manual conversation. #add SC from something else here
Homepage wireframe. "Who This Practice Is For" sits directly under the hero — expectation-setting as information architecture. Filtering happens on the page, before the first message is ever sent. Live at vaidehiyoga.com.
Where AI made this faster and where it didn't get a vote
This project is where my AI-augmented process became a documented system rather than an experiment. The honest accounting:
05 The AI-augmented workflow
AI ACCELERATEd
Content production: first drafts of class communications, social content, and service copy — rewritten to my voice and standard.
Competitive scans — first-pass landscape mapping across 15+ services before I go deep manually.
Synthesis: clustering inquiry threads, student feedback, and competitor notes into candidate themes — hours instead of days.
Repeatability: reusable prompt workflows for recurring analysis, so rigor didn't depend on my energy that week.
I DECIDED
The positioning call: small-batch premium over volume — a strategy decision AI can argue both sides of, which is exactly why it can't make it.
The framing: that this was a service-system problem, not a marketing problem.
The framing: that this was a service-system problem, not a marketing problem.
The voice: every student-facing word. Warm, brief, and mine.
AI synthesis surfaced "price sensitivity" as a dominant theme and nudged toward discount-led growth. The source data said something subtler: people questioned price before understanding the service, and stopped questioning it after a structured trial experience. I killed the discounting direction and invested in expectation-setting instead — then raised prices. Retention went up, not down. That's the difference between AI output and design judgment, and it's why the ~40% acceleration figure refers to speed of synthesis and production — never to decision-making.
A theme I killed, and why it matters
Measured on a living practice
06 Outcomes
50–60%
2 months
5–6 mo.
reduction in onboarding friction — structured flows replaced open-ended message threads; inquiries arrive pre-informed.
from launch to converting free pilot participants into paying customers — validated product-market fit on real money.
average customer retention through iterative, feedback-driven service improvements.
~40%
From zero
Phase 2
faster research synthesis and content production via the documented AI-augmented workflow.
SEO discoverability and a three-platform content system (Instagram, Facebook, YouTube Shorts) built from nothing.
operational foundation ready for automation — enrollment, scheduling, and payments systematized for scale.
Because nothing here was hypothetical. Every persona was a person who paid me or didn't. Every flow was tested by someone who could simply leave. When a designer says "I'd validate with users," I can say: I did — and they stayed, for months at a time.
What I'd do next: Phase 2 automates the backstage, enrollment confirmations, payment reminders, and scheduling, while keeping every human touchpoint human.
07 What this project proves
Why a living practice belongs in a product portfolio
Next case study →
© 2026 · Designed by Vaidehi Yelkawar, accelerated by AI