ARINZEBack to work

Zedx Original · Studio operations · 2026

Turning studio bookings into one connected operation.

Zedx had bookable creative spaces, but the experience around them was split between a WordPress plugin, manual follow-up and staff work happening elsewhere. I led the product strategy, experience design and engineering of a system that connects discovery, booking, payment and day-to-day studio operations.

My role
Product strategy, UX direction and engineering
Built with
Laravel, Livewire, Tailwind, MySQL, Paystack and Resend
Team
Led through Design Sync with the Zedx studio team

A booking is only simple from the customer's side.

Behind a single reservation are studio schedules, durations, buffers, payments, cancellations, walk-ins and staff handovers. The old setup exposed the form but left too much of that work to people. The real brief was to design the operation around the booking.

Four steps, with the complexity kept behind them.

  1. 01

    Choose

    Compare spaces, pricing and what each studio is best suited for.

  2. 02

    Schedule

    Pick a duration and see only the dates and times that can actually be booked.

  3. 03

    Pay

    Confirm the booking through a verified payment flow.

  4. 04

    Manage

    Use a secure link to review, reschedule or cancel without calling the studio.

Customer side

Find and book the right studio

Clear studio pages, live slot selection, checkout and a secure self-service link after booking.

Staff side

Run the day from one workspace

A shared view of bookings, payments, walk-ins, customers, studio rules and activity.

The decisions that made it dependable.

01

Make availability a rule, not a calendar decoration

The slot engine accounts for operating hours, booking duration, existing reservations, studio blackouts and setup buffers. Customers see viable options instead of choosing a time staff later have to correct.

02

Treat payment confirmation as a backend responsibility

A successful screen is not proof of payment. The system verifies transactions on the server, processes provider callbacks safely and keeps each payment tied to the booking staff can see.

03

Give the team an operating product, not another inbox

Bookings, walk-ins, customers, studios, coupons, payments and activity history sit in one staff workspace. It supports the work around a booking, not only the moment it is created.

The staff experience was part of the product.

I replaced the generic admin layer with a focused workspace built around how the team runs the studios: what is happening today, what needs payment, who is arriving and what changed.

Zedx staff dashboard showing bookings, payments and recent activity

From a booking plugin to a product the business can operate.

Zedx now has a live booking experience and a connected staff system. Customers can move from choosing a space to managing their reservation, while the team has the controls and visibility needed to run the service without rebuilding the story from messages and spreadsheets.

4bookable studio spaces
2connected product experiences
Liveat book.zedxoriginal.com
Visit the live booking product ↗