So we built one system that does the lot, for one flat price, for every pub, whatever its size.
Hendra One was designed and coded by Nick Laws, a hotelier turned publican. Nick spent his career with large hospitality corporates, including Fairmont and Four Seasons, working with the kind of sophisticated systems that digitise operations and make the everyday automatic.
When he moved back to Cornwall in 2026 to run a pub on behalf of a private company, he saw the other side of the industry: smaller pubs and venues facing hefty software prices just to stay compliant, locked out of the very tools big operators take for granted.
So he built it. Every feature, one flat rate, for every venue. Operations made simple, fast, and all in one place.
A mission is only worth stating if it rules things out. These are the things ours rules out, and they are the reason the product is shaped the way it is.
The received wisdom is to buy the best tool for each job and connect them. In a large group with an IT function, that is reasonable. In a pub it produces five subscriptions, five logins, five support relationships and a guest database that exists in three incompatible versions, none of which knows that the guest who left a two-star review last month has a birthday booking on Saturday.
One system is not better because it is bigger. It is better because the connections are the point. The rota knows the covers forecast. The compliance escalation knows the org chart. The review request knows the guest opted out. Those are not integrations anyone would bother building between five vendors, and they are most of the value.
See what that looks like on bookings, compliance and rotas and team, or read the pricing in full.
Thirty minutes, on your own menus and your own tables, with the person who built it.