Hendra One is made by a publican in Cornwall

Hendra One started from the view that a village pub should not have to pay corporate prices just to stay compliant. That is why it is one system that does the lot, and every pub pays the same flat price per site whatever its size.

Who makes Hendra One

Hotels: Fairmont, Four Seasons
2026: back to Cornwall, running a pub

Hendra One’s founder, Nick Laws, designed and coded it himself. He is a hotelier turned publican who spent his career with large hospitality corporates, Fairmont and Four Seasons among them, working with the sort of systems that put the operation on screen and make the everyday jobs automatic.

In 2026 he moved back to Cornwall to run a pub on behalf of a private company, and saw the other end of the industry. Smaller pubs and venues were paying hefty software prices just to stay compliant, and the tools big operators take for granted were out of their reach.

So he wrote his own, to run the pub with. Hendra One puts every feature in one place and charges every venue the same flat rate for all of it.

Three things we will not do

Charge by tier

Every feature is in the £100 per site per month, compliance included, and nobody counts your seats. A two-room freehouse gets the same system as a fifty-site group, because the smaller pub is the one this was built for.

Charge per cover

Pay by the cover and the software costs more in exactly the year the pub does well. It also quietly makes your guest list somebody else’s asset.

Tie you to a contract

It is month to month. If it stops earning its place, leave.

Why it is all one system

The usual advice is to buy the best tool for each job and wire them together. That is reasonable in a large group with an IT department. In a pub it means five subscriptions, each with its own login and its own support desk, and a guest list kept in three versions that disagree. None of them knows that the guest who left a two-star review last month has a birthday booking on Saturday.

What makes one system worth having is the way its parts are connected. The rota can see the covers forecast. When a compliance check is missed, the escalation goes to whoever the org chart says is responsible. Before a review request goes out, it checks whether the guest opted out. Nobody is going to build those links between five separate vendors, and they are most of the value.

You can see how it fits together on the pages for bookings, compliance and rotas and the team, and the pricing page sets out what the £100 covers.

Talk to the person who built it

Thirty minutes on a video call, using your own menus and your own tables, with Nick. Email us and we will find a time that is not Friday night.

Book a demo