Use case · Health & wellness
Booking and intake for wellness businesses
Booking pages, intake forms, and client portals for coaches, studios, and wellness practices — described in plain English, hosted in minutes.
Overview
Why teams use code-anything here
Coaches, studios and wellness practitioners lose hours stitching together a booking link, a form builder, a reminder email and a spreadsheet that ties them together. code-anything replaces that with one hosted app you describe in plain English: a client picks a slot, fills in an intake form, pays a deposit if you ask for one, and gets a confirmation — with every record in a managed Postgres database you can actually query. It is built for general wellness, coaching and lifestyle businesses. It is not designed for clinical, diagnostic or regulated medical use, and it makes no medical-compliance guarantees.
What you can build
Ship these in an afternoon
BOOKING
Appointment booking page
Clients pick a time, pay a deposit through Stripe if you want one, and receive an automatic confirmation email.
FORMS
Client intake form
A pre-session questionnaire whose responses land in a database you can review in one place, instead of scattered across email replies.
PORTAL
Client portal
A signed-in area where clients see upcoming sessions, plans or the resources you share with them.
PACKAGES
Package & class pass sales
Sell a block of sessions or a class pass through Stripe checkout, with the purchase recorded against the client.
REMINDERS
Reminder & follow-up email
Transactional email that goes out on the events your app already knows about — booked, confirmed, tomorrow, missed.
SITE
Practice website with booking built in
The public site and the booking flow as one app, so the "book now" button is a real feature rather than a link somewhere else.
The advantage
Built for how you actually work
Reminders that send themselves
Transactional email is part of the wired-in stack, so confirmations and reminders go out from the app itself rather than from a separate tool you keep in sync.
Take deposits up front
The checkout endpoint, the redirect and a signed webhook are written in on the plans that include payments, so you can require a deposit or full payment at the moment of booking. You connect your own Stripe account, which is what makes the money yours.
No tool sprawl
One hosted app replaces the booking link, the form builder, the email tool and the sheet that reconciled them — and you can change it yourself.
Client information stays gated
Intake answers belong behind a login. Sign-in is written in with the data layer, and environment values are stored encrypted server-side and never read back to the browser.
One client record, not five
Bookings, intake answers and payments sit in the same Postgres database, so a client is one row you can look at rather than four systems you have to cross-reference.
Yours to adjust between clients
Add a question, change a slot length, rewrite the confirmation — describe it, or click the element in Studio. You are not waiting on anyone.
FAQ
Common questions
Build it for health & wellness today.
Describe what you need and watch it build — managed database, auth, email and payments included.