A wellness concierge that lives in your pocket, not your inbox.
Myhá curates a week of wellness for each client — the right sessions, in the right order, at the right studios across New York. We designed and built the product around it: a client app where a week arrives ready to approve, and a back office where one person can run it all.
- Sessions in a curated week
- [X]
- Sessions in a curated week
- Tap to confirm & pay
- 1
- Tap to confirm & pay
- To onboard a client
- <1 min
- To onboard a client
- Kickoff to launch
- [X] wks
- Kickoff to launch
Myhá, a premium wellness concierge in New York City. Each client gets a personally curated week of sessions — Pilates, sauna, massage, training, breathwork — sequenced by a method, not a menu.
Product definition, UX and Figma prototype, brand-faithful front end with a custom intro animation, client web app, admin back office, payments, email, calendar export, and launch.
A premium client experience that runs on a deliberately simple operation: one person can curate, publish, and track every client's week without leaving one screen.
Premium on the outside, spreadsheets on the inside
Myhá's founder had spent more than a year developing the concept: a wellness-forward lifestyle concierge that's hard to replicate at scale and priced like the hospitality it resembles. The service already worked — by hand. Weekly plans went out as emails. Approvals came back as replies. Changes happened over text. Payments were chased separately. The experience the client saw had to feel like a five-star hotel; the operation behind it had to fit one founder's week.
- 01
The experience lived in email threads.
A curated week deserved better than a Sunday email with a list in it. Clients had nowhere to see their week, tap a session, and know why it was chosen for them.
- 02
Approval was a conversation, not a tap.
“Looks good but swap Thursday” meant a reply, a re-send, another reply. Confirming a week and paying for it were two separate chores in two separate places.
- 03
The founder was the system.
Every schedule was built from scratch. Nothing was reusable. There was no single view of who needed a week built, who hadn't confirmed, and who had paid.
- 04
It had to feel expensive and run cheap.
The brief was explicit: the MVP should look and feel premium but operate simply. AI can automate later; first the workflow has to exist.
[Quote from the founder about the concept or the brief — e.g. "It needed to feel like a hotel concierge and run like a one-person shop."]
— [Max Shaw, Founder, Myhá]
Two faces of one week
We built one product with two faces. Clients get a dark, editorial, premium app where their week arrives ready to approve. The founder gets a light, fast back office where a week is assembled from reusable session cards and published in minutes. The same week, seen from both sides.
- [Address][Duration] · $[cost]Why this session: [Why]Benefits: [Benefits][Note]
Both views are live components, not screenshots — try the builder in section 6.
What shipped
- Branded landing page with intro animation
- Roots grow, the name arrives, the page opens: a first impression that matches the price point. Opening Note, Approach and Inquire sections; inquiry form with instant confirmation email.
- CLIENT
- Installable web app
- Add-to-home-screen on iPhone and Android; clients open their week like an app, and a direct link in a text lands them straight on it.
- CLIENT
- The weekly view
- A client's sessions grouped by day, each card expandable to the full detail: where, when, how long, how much, and why this session was chosen for them. Addresses open in Apple or Google Maps.
- CLIENT
- Approve, trim, confirm
- Remove any session before confirming; the total recalculates; one tap opens checkout with Apple Pay and saved cards.
- CLIENT
- The standing week
- After payment the week locks into a confirmed reference view with a “Request change” path, a calendar file for Apple or Google Calendar, and booking history.
- CLIENT
- Task queue
- The back office home: who needs a week built, who's awaiting confirmation, who's confirmed and paid.
- CONCIERGE
- Session library
- Reusable session cards (type, title, studio, address, time, cost, duration, benefits, why-this-session, note). Duplicate, edit, search, filter. Build once, place many times.
- CONCIERGE
- Weekly builder
- Drag or add sessions from the library into Monday–Sunday, several per day, personalize the “why” per client, see the running total, preview exactly what the client will see, publish.
- CONCIERGE
- Confirmation & payment tracking
- Per client, per week: pending, confirmed, paid, which sessions were declined, and a follow-up flag for anyone who's gone quiet.
- CONCIERGE
- Client management
- Create a client in under a minute; profile with preferences, consultation notes and history.
- CONCIERGE
- Transactional email
- Inquiry received, week published, week confirmed (with calendar attachment), and a 24-hour session reminder, all on brand.
- BOTH
- One-off additions
- An impromptu session added to an already-confirmed week, approved and paid on its own. [confirm]
- BOTH
One week, curated.
Here's a single week for a single client, from inquiry to Sunday night — as it moves between the concierge and the client.
It starts on the landing page: the roots, the name, a short note on the approach, and a form.
After a consultation, the concierge creates the client in under a minute — preferences, notes, the shape of their life.
The week is assembled from the session library — reusable cards for studios and sessions the concierge already trusts — placed into Monday through Sunday, with a personal “why this session” on each.
Preview it exactly as the client will see it. Publish. An email goes out: your week is ready.
The client opens the week, taps into a session to read why it's there, drops the one they can't make, and watches the total update.
One tap. Apple Pay. The week locks into a standing reference, a calendar file lands, and a confirmation email follows.
The night before each session, a reminder with the address and a map link. Sunday, the next week arrives.
Seven steps, two screens, one person running it. That's the whole operation.
The builder and the week
Drag a session into a day — or select one, then tap a day. [Insert real session examples — type, title, studio, cost]
This is a static sample of the real product. Sessions, studios and prices are placeholders.
Deep black, warm cream, and vivid green.
The founder came with a clear visual language and an intro animation he'd been prototyping himself: roots growing toward a name; tiles like fragmented pieces of a life that come together into something coherent through the method. We tuned the timing, built it as lightweight code rather than video, and carried the same language through every screen, every email, and the á in the name.
What changed
to build and publish a client's week, down from [Y]
to onboard a new client
of weeks confirmed and paid within 24 hours of publishing
clients on the platform at launch
The client sees fewer messages and a better experience. The concierge does less and sees more.
A week you can hold.
Clients open an app, not a thread. Every session says where, when, how much and why. The week is confirmed in one tap and lives on their phone and calendar.
A back office that fits one person.
Reusable sessions, a drag-and-drop week, a queue that shows exactly who needs what. Building a week is a few minutes of placement, not an afternoon of writing.
Premium without the overhead.
The experience carries the brand's price point; the operation runs on one screen, low hosting cost, and automated email — with room for AI to take over the scheduling later.
[Quote from the founder about the finished product]
— [Max Shaw, Founder, Myhá]
How we delivered
- [Mon YYYY]
Review
Read the founder's product requirements and an existing proposal; identified where the stack and the scope could be simpler and cheaper to run.
- [Mon YYYY]
Prototype in hours
Clickable Figma prototype of the landing page, client dashboard and admin panel, turned around before the first call, so the conversation was about the product instead of a document.
- [Mon YYYY]
Re-scope
A lean React front end with a document database; the same feature set, about half the monthly hosting cost.
- [Mon YYYY]
Brand & motion
Worked from the founder's own animation prototypes and design notes to build the intro and carry the palette through every surface.
- [Mon YYYY]
Build
Client app, admin back office, checkout, transactional email, calendar export, installable web app.
- [Mon YYYY]
Launch
Live at myha.nyc, [X] weeks after kickoff, with a monthly retainer for hosting and care.
Tech & details
- Platform
- Installable web app (PWA), iOS and Android, desktop and mobile Safari/Chrome
- Front end
- React, ShadCN-style components restyled to the brand; dark client theme, light admin theme
- Data
- Document database (MongoDB); per-client scoping so each client sees only their own week
- Payments
- Stripe Checkout with Apple Pay and saved cards [confirm]
- Transactional email for inquiry, publish, confirm and reminder [confirm provider]
- Calendar
- .ics export for Apple and Google Calendar
- Maps
- Address deep links to Apple Maps and Google Maps
- Motion
- Intro animation in code (SVG/CSS), no video; plays once per session
- Hosting
- Lightweight; monthly care and hosting retainer
Running a premium service on email threads and good intentions?
We build the product that lets a small team deliver a big-brand experience.