Work
How Livmore's work with WOTSO led to Hamlet
WOTSO trialled the coworking management platforms on the market and found them more complicated than the problems they were meant to solve. Livmore worked inside the operating team instead, and that work developed into Hamlet.
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 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.
Result
Repetitive work came off the team
Hamlet's automation freed WOTSO staff from repetitive work, so time that had gone into manual admin could go back to members and to running the sites. WOTSO's own public material connects Livmore with the creation of Hamlet.