Two businesses, one front door.
Every flexible space is a property business and a hospitality business. Hamlet runs the back of house for both, so the owner gets numbers they can trust and the team gets its day back for people.
The manifesto
A flexible space is a property business. It lives on occupancy, revenue per site, arrears and the report the owner reads on Monday morning.
It's also a hospitality business. It lives on the welcome, the regulars, the person who remembers your name, and whether the room feels right at four on a Tuesday.
The admin between those two businesses usually lands on the same few people. The community manager raises the invoices, re-sends the receipt, chases the same payment twice and copies numbers into a spreadsheet for the owner. They were hired to look after people. Most days they end up looking after software.
We think software should do that work, and do it quietly.
So Hamlet is the back of house. It raises the invoices overnight and collects them. It retries the payments that fail and puts the ones that need a human on the debtors report. It confirms the boardroom someone booked at 9pm, and takes their money first. It keeps the books the way the owner needs them, per site or across the portfolio, and sends the report before anyone asks.
When it works, nobody notices. That's the job.
Every screen we add has to earn its place. The best version of most tasks is the one nobody had to open, and anyone on the team should be able to use the rest on their first shift.
We'll keep handing the machine more of the work where a person adds nothing. Matching payments. Drafting reminders. Answering "where's my receipt". As AI gets genuinely good at that work, it gets the job.
The work that needs a person stays with a person. The member asking to cancel. The late payer with a reason. Somebody's first morning.
The operator is the host. Hamlet is the help nobody sees, working behind the pass.
James Brouard, co-founder
Built for both halves of the business
Property
For owners, landlords, asset managers and finance.
- Books set up the way your portfolio is owned, per site or across several.
- Revenue by site and portfolio, and utilisation with peak against average.
- Roles that decide who sees what, plus SIG Lite, an MSA and a DPA for your procurement team.
Hospitality
For community, front-of-house and site teams.
- Invoices that raise, collect and retry on their own.
- Cancel a membership and the next invoice never exists.
- Guests book and pay for a room without needing an account.
The human line
Every job in a flexible space sits on one side of a line. Hamlet takes the ones where a person adds nothing, and hands the rest to your team with the context attached.
Hamlet takes
- Raising the month's invoices
- Collecting payment, and retrying the ones that fail
- Overdue reminders, on your schedule
- Receipts and booking confirmations
- Taking a guest's booking and payment at 9pm
- Sending the report before anyone asks
Your team keeps
- The member asking to cancel
- The late payer with a reason
- Somebody's first morning
- The tour
- Putting a double booking right, and the gesture that goes with it
- Knowing the regulars
As AI gets genuinely good at a job, we'll move it across the line, and we'll say which jobs moved and why.
How we build
- Every screen earns its place. If a job can happen without anyone opening a page, it does.
- Anyone on the team can run it on their first shift.
- Done, then logged. Work that's safe to automate happens first and leaves a record, so nobody has to click to approve it.