Blog
What we are shipping and why.
Most restaurants do not have a software problem — they have five, and none of them talk to each other. The story of building a single restaurant operating system, now serving 20,000+ customers across 20+ UK restaurants.
Most small-hotel software is sold on a feature list written for a 200-room hotel. Walk one ordinary Saturday through a twelve-room guest house instead — it produces about a dozen genuine requirements, and a visitor levy your booking engine is about to have to collect.
Everything in a supplier's pitch is written by the supplier. Five free UK registers aren't — and thirty minutes with them is the cheapest due diligence available to a business buying software.
The rate you quote is the narrowest price on your contract. How to read a UK merchant statement line by line, and the three levers that actually move what you pay to take a card.
One question — if this ended on Friday, what leaves with me? — run across delivery apps, OTAs, booking plumbing, development agencies and AI vendors. And why GDPR portability and the EU switching rules will not rescue a UK business.
A channel manager has never persuaded anyone to book anywhere. What each system in your stack actually does — and six symptoms that tell you which box is broken.
Anyone can build the ordering site in a fortnight. Whether a direct channel survives comes down to six decisions before it — allergens, payments, drivers, the kitchen, delivery pricing and who owns the customer list — and they come in an order.
Ask a hotelier what they pay Booking.com and most say 15%. Here is what actually leaves the account — and the arithmetic that decides whether a direct booking channel is worth building.
Just Eat and Uber Eats publish their rates; Deliveroo does not. Here is what UK restaurants and takeaways actually pay once VAT and the fees underneath are counted — and how to work out whether your own ordering channel is worth building.
