Lokee
A booking page for independent yoga and pilates teachers. Students book without creating an account, with no commission.
lokee.me is designed and built in France. It is not affiliated with Lokee Yoga, a yoga studio in Indiana.
Where it started
An independent yoga teacher sells scarce spots. Six, eight, sometimes four per class. And to book one, her students message her: an Instagram DM, a WhatsApp, a text. She answers between classes, keeps the list in her notes, and counts class passes by hand.
Existing tools are built for studios: a back office, an account for every student, often a fee on every payment. For a teacher on her own with ten classes a week, it's too much, and her students don't want another app.
I wanted to build the opposite: one page, one link in bio, nothing new to learn.
What I built
Lokee (lokee.me) is a booking page a teacher puts in her bio. Her students see the classes and the spots left, and book in two taps from a story. No account, just an email.
I designed and built it on my own, from the first screen to production.
What's live
The schedule with spots left, and a waitlist when a class is full.
Booking with no student account, identified by email.
Class passes, deducted automatically on each booking.
Cancellation with the teacher's own notice period, and the class credited back when the student cancels in time.
A trial price for a first class, and a list of known students so they don't get it.
Pay in person by default, online payment through Stripe as an option.
Zero commission: €19.99 a month for the teacher, that's it.
What teachers taught me
I talked to teachers before writing any code, and kept talking to them through the whole build. Three things changed the product.
Paying in person isn't a gap, it's the norm
Many teachers get paid directly, with passes or bank transfers. A tool that forces online payment makes them change a habit that works. On Lokee it's the default.
The real cost of a tool is the student having to learn something new
Every extra step (sign up, download an app) loses bookings. Hence no student accounts at all.
A teacher isn't trying to fill her classes, she wants her time back
Stop sorting messages, know how many people are coming before she arrives, prepare the class instead of the list.
Under the hood
A few choices I'm happy with, because they saved me from bugs I know too well.
One source of truth per calculation
The price shown and the price stored come from the same database function. The moment a value is computed in two places, it drifts, and the student gets the wrong one.
A class is a class, never an amount
Passes live in a ledger of movements, not a counter.
No scheduled jobs
Expirations are computed on read. Fewer moving parts at night, fewer silent failures.
Security in the database
Tables locked by default, and all access goes through the server, which checks which teacher owns each row.
Today
Lokee has been live since July 2026, and teachers use it for their classes. I keep building it with them, one feature at a time, when a teacher actually needs it.