Studio One · ClaySpace Operating Platform

No single application held a complete transaction. Bookings, staffing, memberships, payments, payroll, and customer communication each lived somewhere different, so staff re-entered the same information and reconciled the differences by hand across scheduling, finance, forms, and file storage. Nobody could state the business position without checking several systems and trusting the reconciliation between them.

Rather than start from the tools, I followed the work: user journeys end to end, the handoffs where one system gave way to another, the recurring cost of each, the points where someone had to approve, and the paths taken when something failed. Customers, instructors, administrators, and management were mapped separately, because each met the systems differently and each absorbed a different share of the manual effort. The Current-State Service Blueprint held the result as one picture — twelve applications, what each was responsible for, where data crossed between them, and which exceptions were being absorbed as human work. Current state was accepted before any consolidation target was set.