Industries

Software for hospitality groups, covers, staff and stock.

Augustova builds custom software and automation for UK hospitality groups and restaurants, covering booking and no-show recovery, staff scheduling across sites, supplier ordering and consolidated reporting. Margins are thin enough that small operational gains matter more than in most sectors.

Typical buildTwo to four weeks
Where it paysStaffing and covers
Multi siteOne view, not five

Thin margins make small gains significant

A percentage point of labour cost or a handful of recovered covers a week is the difference between a good and a bad quarter in hospitality. That is unusual, and it means automation with a modest effect still pays back quickly.

It also means the sector is unusually badly served, because generic software is priced for businesses with fatter margins.

What we build for operators

01No-show reduction and automatic re-offering of released tables
02Staff scheduling against forecast covers rather than last week rota
03Shift swapping and availability without a group chat
04Supplier ordering driven by actual usage
05Consolidated reporting across sites in one view
06Recruitment pipelines for a sector with continuous turnover

Recruitment never stops here

Turnover in hospitality is structural rather than a failure, which means recruitment is a permanent process rather than an occasional project. Treating it as an always on pipeline rather than a series of emergencies is the single biggest operational change available.

What it costs for an operator

One booking calendar fed by every channel, with confirmations and reminders, sits at the lower end of the £8,000 to £30,000 range, or inside web development at £4,000 to £16,000 when it forms part of a new site. Rota and staffing work is usually a separate phase.

For a single site independent, the site with booking is often the whole answer. For a group, the consolidated view across sites is where the money is.

What to measure before and after

Covers lost to no-shows and late cancellations, and how long a released table or slot stays unsold. Then minutes per day spent reconciling bookings between channels, which is the administrative cost that hides in plain sight.

On staffing, measure hours per week spent building and amending the rota, including the messages required to confirm a change. The confirmation loop is usually larger than the rota itself.

How an engagement runs for a restaurant, hotel or venue

A 30-minute call to hear how the operation runs today, then a paid discovery step: interviews with the people doing the work, a look at the systems and data you already hold, and a ranked list of what would pay back, each with a price, a timeline and the monthly running cost once live. In most restaurant, hotel or venue engagements the first thing built is bookings, enquiries and no-show reduction handled without the phone ringing out at service, because it is measurable inside a month and it funds the rest.

The build runs in weekly demos against your real inputs, including the messy ones. Integration with the systems you already run comes before anything clever, because that is where most of the value and most of the risk sits. Go-live is followed by handover: the code, the provider accounts and the credentials in your name, a runbook, documentation and a recorded walkthrough, plus a session for the people who will use it daily. Every price is fixed in writing before work starts, with a list of what is not included.

The rules a venue has to build around

Food hygiene under the Food Standards Agency, allergen information under the labelling rules, licensing conditions, and employment rules for a workforce that is often young and part-time all produce checks and records. Software can keep the allergen matrix current from the recipe data, log the temperature checks, schedule the rota within the rules and chase the certificates, and it can answer the questions guests ask most, including the allergen ones, from the same source of truth. Guest data and card details carry the usual UK GDPR and payment-security duties, and deposit and cancellation terms have to be fair under consumer law.

What it costs, and what it replaces

Our published prices apply to every sector: an AI adoption audit at £2,500 to £6,000 fixed, credited in full against any build; a first AI implementation at £4,000 to £15,000; a custom AI system at £8,000 to £25,000; applications at £8,000 to £30,000 per phase; websites at £4,000 to £16,000; training from £1,200. For a venue that usually means an AI that answers the phone and messages for bookings and enquiries as the first implementation, then rota, stock and allergen tooling as a custom system, with the booking platform you already use kept as the record.

The running cost is stated before go-live, per feature, and it scales with volume rather than headcount. From operating our own AI products, the model is rarely the expensive part; the channels around it, telephony and messaging, usually are, and a well-designed workflow sends most of its work to the small, cheap models. Every system we build reports cost per feature from day one and has spending ceilings that were tested by watching them fire.

Service, the phone and the empty table

A restaurant’s phone rings during service, which is exactly when nobody can answer it. Every unanswered call is a booking taken elsewhere. An AI that answers, takes the booking into your system, confirms the deposit and answers the questions about parking, dogs and allergens is the single automation that pays back fastest in hospitality. Reminders with a real reply channel cut the no-shows; a waiting list that fills a cancelled table automatically recovers the rest. Our receptionist page sets out how it works and what it hands to a person.

Common questions

Do you replace our booking or till system?

No. Those are well served and staff know them. We build the layer that connects them and acts on what they record, which is where the gaps usually are.

Can scheduling really account for forecast demand?

Yes, using your own historical covers by day, service and season. Even a simple forecast beats scheduling from last week, which is what most sites do.

Is this affordable for a small group?

A focused build sits at the lower end of our range. With margins this thin, a modest labour or cover improvement usually covers it inside a year.

We use a booking platform already. What would change?

Usually the reconciliation and the communication rather than the booking. Where covers arrive by phone, email and platform, one calendar that holds all three removes a daily manual job and the double bookings that come with it.

Can a system handle our seasonal peaks?

It should be scoped against the peak rather than the average, and that is how we quote it. Load and cost are modelled on the busiest weeks, because a system that only holds up in a quiet month fails when it matters.

Can an AI take our bookings by phone?

Yes, during service and out of hours, into the booking system you already use, with deposits confirmed and anything unusual handed to a person. Guests are told it is an AI.

Can it answer allergen questions?

From your own allergen matrix, yes, and it should say so and offer a person for anything it cannot answer with certainty. The matrix has to be kept current, which is a second thing we automate.

What should a venue automate first?

Phone and message bookings, because the unanswered call during service is a booking lost every night.

Read next

AI consultancy in London →AI automation agency in London →Bespoke software development in London →

Talk about covers and labour

Tell us how you schedule staff today and what happens when a table cancels at 6pm.

Start a conversation →