Asana Studio

A yoga studio runs on two things at once: a schedule people book into, and a small business that has to add up at the end of the year. Most studios buy the first and do the second in a spreadsheet. This is both, built as one piece of software in Next.js, shaped around how this studio actually works rather than around what a booking tool usually offers.

The day

The dashboard is the morning view: revenue this month, occupancy over seven days, active members, open invoices, and today's sessions with instructor, room and how full each one is. The schedule sits next to it, a week at a time, every session with its booking count, so a class that is filling up or failing to is visible before anyone asks.

The business

Invoices are issued from the same data that runs the timetable, per membership or per drop-in, with status and dates. Expenses, the balance sheet and the year-end closing are part of the product, not an export: the income statement, revenue against costs month by month, revenue per product, costs per category, and fees per instructor, which matters when most of the teaching is done by external instructors who invoice the studio.

Members

Members, waiting lists, attendance and messaging are one flow. A session can be filled from its waiting list, attendance can be marked on the spot, and everyone booked into a class can be sent one message over WhatsApp or e-mail, with names filled in per person.

What I did

• Product design and interface, from the first structure to the built screens
• The application itself: Next.js, data model, booking, invoicing and reporting
• The financial model behind the closing, including instructor fees