Studio software can look clean in a demo and still miss the daily shape of studio work. The hard parts are rarely the obvious screens. They live in the tiny collisions between recurring classes, substitute teachers, workshops, role benefits, late cancels, room use, community events, and the person at the desk trying to make a fair decision quickly.
Sangha is being shaped from those real operating patterns. Karma Yoga is not a fictional sample studio; it is a working environment with policies, relationships, payment realities, teacher expectations, and community commitments. That context changes the product. It keeps the software honest.
A real studio needs recurring offerings and dated occurrences to behave differently. It needs policies that can change over time without rewriting history. It needs access rules that understand roles, not just products. It needs teacher pay that can explain itself after the fact, when memory is no longer enough.
Designing from real operations also means accepting that studios are not all identical. A product has to hold structure without forcing every community into the same commercial mold. Sangha tries to make the durable parts clear while leaving room for local studio culture, language, and policy.
The result is not a generic booking tool with yoga vocabulary sprinkled on top. It is software built from the messy, beautiful, specific work of running a studio where people are known, policies matter, and community exchange is part of the actual business model.
