How working inside WOTSO led to Hamlet

Context

A growing multi-site workspace operator

WOTSO runs flexible workspace across multiple sites in Australia. Running that kind of business means memberships, bookings, billing, access and reporting all have to agree with each other, every day, at every location. When they do not, the difference is absorbed by staff.

The problem

The platforms were harder than the job

WOTSO trialled the existing coworking management platforms and found them unnecessarily complicated. Software meant to simplify memberships, bookings and billing was adding steps rather than removing them, and the operating team was working around the tools instead of with them.

What Livmore did

We worked inside the operating team

Rather than specifying a system from the outside, Livmore worked inside WOTSO's operating team across memberships, bookings, billing, access and multi-site operations. That meant seeing how the work actually happened day to day, at more than one site, before deciding what the software should do.

What changed

That work developed into Hamlet

The systems built for those operations grew into Hamlet, a workspace operating platform. It was shaped by the operational detail of running flexible workspace, not by a feature list, which is why it handles the parts of the job that generic tools tend to leave to staff. Hamlet's automation took repetitive work off the team, so time that had gone into manual admin could go back to members and to running the sites.