Flexible workspace
Technology for coworking and flexible workspace operators
Livmore builds software, integrations and practical AI automation for coworking and flexible workspace operators. The team spent 8+ years inside the sector, including building Hamlet, the workspace operating platform used across Australia and New Zealand. We work with operators on any platform.
Where flexible workspaces lose time
- Enquiries landing in an inbox, a form and a phone, with no single view of the pipeline
- Tours booked and rescheduled by hand around staff availability
- Sign-up and contracts done as email attachments, then re-keyed into the platform
- Renewals and upgrades noticed late, or only when a member asks
- Membership changes mid-month that have to be prorated manually
- Invoice runs checked line by line before they go out
- Arrears chased by whoever remembers, with no consistent sequence
- Reconciliation between the workspace platform and the accounting system done in a spreadsheet
- Meeting room bookings that don't flow through to billing or access
- Access credentials issued and revoked by hand as members come and go
- Visitor arrivals handled at the front desk instead of on the door
- Desk and room usage nobody can report on without exporting data
- Multi-site reporting rebuilt by hand each month, site by site
- Staff onboarding, rosters and checklists spread across tools
- A shared support inbox with no triage, so the same questions get answered repeatedly
- Member communication sent from three different systems with three different lists
What we do about it
Member journey
We join the enquiry, tour, sign-up and onboarding steps into one flow, so a lead entered once carries through to a member record without re-keying. Contracts are generated and signed in sequence, onboarding starts itself, and renewals surface before they lapse rather than after.
Money
We automate the billing work your team currently does by hand: prorated changes, recurring invoice runs, payment retries and an arrears sequence that runs consistently. We connect the workspace platform to your accounting system so reconciliation stops being a monthly spreadsheet exercise.
Space
We connect bookings, access control and billing so a room booking issues the right access and lands on the right invoice. Visitor arrivals, credential changes and door events are handled by the systems rather than by the front desk.
Operations
We build the multi-site reporting your team currently assembles manually, and automate the internal admin around it. Support enquiries are triaged and routed, and member communication runs from one source rather than three.
Your technology stack
We don't need to replace everything to make it work better
Most operators already have important systems in place. The job is usually to make them work together better, remove the manual work between them and only replace something when there is a good reason to.
Sometimes the answer is better configuration. Sometimes it's connecting two systems that don't talk. Sometimes it's automating the work between them. Occasionally the right answer is building something that doesn't exist yet.
Working with Livmore does not require moving to Hamlet.
Systems we have implemented and integrated
The exact stack varies from operator to operator. We work around what is already useful rather than forcing every client into the same architecture. Everything listed here is something we have actually implemented or integrated, not a partnership badge.
Workspace and operations
- Hamlet
Finance and payments
- Xero
- Stripe
- Payrix
Access and infrastructure
- Salto KS
- Essensys
Scheduling
- Google Calendar
Web and application technology
- WordPress
- React / Next.js
- Node.js
- PostgreSQL
- GraphQL
- Payload CMS
- Google Cloud
Things we've actually worked on
Some of this is completed client work, some of it is capability we can apply to your stack. Where the difference matters we will tell you which is which on the call rather than blurring it here.
Member onboarding
Reduce the hand-offs between sales and operations so information entered once follows the member through the rest of the journey.
- Enquiry capture
- Tours
- Proposals
- Agreements
- First payment
- Access
- Welcome sequence
Billing and payments
Take the monthly billing routine off your team and make the numbers agree with the accounting system.
- Recurring billing
- Proration
- Invoice generation
- Payment retries
- Arrears sequences
- Accounting reconciliation
Access and space
Connect what someone has booked or paid for with what the door and the calendar allow.
- Meeting rooms
- Desks
- Offices
- Access credentials
- Visitor access
- Booking permissions
- Access system integrations
Member experience
The parts members actually touch, connected to the operation behind them.
- Member portals
- Mobile experiences
- Bookings
- Passes
- Events
- Community
- Notifications
Operational reporting
Reporting that assembles itself instead of being rebuilt by hand each month.
- Occupancy
- Revenue
- Multi-site reporting
- Inventory
- Utilisation
- Management reporting
AI and support
Applied where it removes repetitive work, and left out where it would make the experience worse.
- Inbox triage
- Support assistance
- Internal knowledge
- Repetitive member questions
- Reporting assistance
- Operational agents
One member, seven steps, too many systems
This is the journey almost every operator runs. The problem is rarely any single step. It is that each step lives in a different place, so the same information gets entered again and again.
- 01EnquiryWebsite and enquiry forms
- 02TourInbox and calendar
- 03ProposalWorkspace platform
- 04AgreementE-signature
- 05PaymentPayments and accounting
- 06AccessAccess control
- 07MemberMember communication
Livmore builds the layer that carries one member's details across all of it, so the work happens once.
How Hamlet came about
WOTSO had trialled the existing coworking management platforms and found them more complicated than the problems they were meant to solve. Livmore worked inside WOTSO's operating team across memberships, bookings, billing, access and multi-site operations. That work developed into Hamlet, the workspace operating platform.
Read the full WOTSO storyEight years is enough time to see the same problems more than once
The reason we can be specific about flexible workspace is that we have worked inside it, with an operator and with the industry body, not just alongside it.
Workspace software & operational systems
Eight years, dozens of locations and one very complicated workspace business. Eventually we built the software too.
Read the storyIndustry website / digital platform
Australia's flexible workspace industry needed a better home on the internet. So we're building one.
Read the storyQuestions from flexible workspace operators
Last updated September 2026
We're on another platform. Do you still work with us?
Yes. Most of our work is connecting and automating around the systems you already have, whatever they are.
Do we have to move to Hamlet?
No. We built Hamlet, and we also work with operators on other platforms. If Hamlet is the right fit we'll say so. If it isn't, we'll say that too.
What does a typical engagement look like?
It starts with a 30-minute call. From there we scope a first piece of work with a fixed price, deliver it, and stay on for ongoing support if that's useful to you.
Can you work with OfficeRnD or Nexudus?
Yes. We work around the workspace platform you already run. What is possible depends on the APIs and data that platform exposes, and we will check that before proposing anything.
Can you integrate access control with our workspace platform?
Usually yes, and it is one of the most common requests. It depends on the access system and the platform involved, so we review both before committing to an approach.
Can you automate member onboarding?
Yes. A typical version joins enquiry, tour, proposal, agreement, first payment, access and the welcome sequence, so details entered once follow the member through instead of being re-keyed at each step.
Can you help if we don't know what needs replacing?
That is what the first 30-minute call is for. You show us where the time goes, we tell you what we would change first, what we would leave alone and whether anything needs replacing at all.
Do you build custom software?
Yes, where configuration and integration are not enough. We would rather make what you have work than build something new, but when the software you need does not exist we build it.
Are you trying to sell us Hamlet?
No. Hamlet is part of why we understand the sector as deeply as we do, but Livmore works independently. We would rather improve the systems you already have than recommend a platform change that doesn't make sense.
Bring us one workflow that wastes time
We will tell you what we would automate, what we would not, and whether we can help.