Running RoomAnchor PMS ourselves changed how we design, build and support products for clients. Four lessons we bring to every project.
Building software for clients and running software of your own are different jobs. RoomAnchor PMS, our property management system for independent hotels, taught us the second one. Here’s what changed in how we work.
You find out what “done” really means
When you hand a project over, it can feel finished on launch day. When you run it yourself, launch day is when the real questions start: a report that’s slow on Monday mornings, a payment that fails on one bank’s cards, a screen nobody can find.
Now we plan for life after launch from the first sprint. Monitoring, error reporting and a way to ship small fixes quickly are part of the first version, not an extra.
Boring technology is a feature
On our own product, every unusual tool is something we have to keep running at 2 a.m. That made us choose well-known, well-supported tools by default, and only reach for something new when it clearly earns its place.
We give clients the same advice, and the same stack decisions, because we have to live with them too.
Small releases are calmer releases
Shipping a big update once a month felt efficient until something broke and we had to work out which of fifty changes caused it. Shipping small changes often made every release easier to test, easier to explain and easier to roll back.
Support is part of the product
Hotel staff don’t care which part of the system failed. They care whether the front desk works. Running a product taught us to treat support messages as product feedback, and to fix the cause, not just the ticket.
What it means for you
When we build for clients, we build the way we’d want to run it ourselves: monitored, maintained and easy to improve long after launch. If that’s the kind of partner you’re looking for, let’s talk.
Working on something similar?
Tell us what you're building. We'll come back with questions and a plan.
Start a project
