Built by an instructor. Not a studio chain.

Before Flowbuk, Maya spent six years teaching yoga — mornings at a studio she didn't own, evenings with private clients, weekends filling in wherever someone needed her. She loved the teaching. She did not love the rest of it.

Her booking system was a shared Google Sheet, an Instagram DM inbox, and a Venmo history she'd scroll through at midnight trying to remember who'd actually paid. One Tuesday morning, two students showed up for the same mat space because a sign-up had been logged in the sheet but never made it to her phone. It was a small mistake. It still felt terrible — she'd built her whole practice on people trusting her to have it together.

She looked for something built for someone like her: no studio, no front desk, no second employee to hand the admin to. Everything she found was either a bloated studio platform charging for twenty seats she'd never use, or a generic scheduling tool that had no idea what a class pack or a drop-in rate was. So she started sketching her own version on the back of a class attendance sheet, then learned enough code on weeknights to build it herself.

The first version of Flowbuk had exactly one user: Maya. The second version had five — instructor friends she'd talked into trying it in exchange for brutally honest feedback. What she heard back was consistent: this is the first tool that feels like it was made by someone who's actually taught a class, not sold software to one.

That's still the standard Flowbuk is held to today. We're a small team building for people doing what Maya used to do every day — and for a lot of that time, still does. She keeps a weekly class on the schedule. It's the fastest way we know to stay honest about what we're building.