Why Clove Exists

Clove was built after years spent inside hospitality businesses — from kitchens and dish pits through to large-scale operations, budgeting, staffing, pricing and reporting.

Over time, one thing became increasingly difficult to ignore:

good businesses were still losing control of their margins.

Not because people were lazy or careless, but because hospitality moves quickly. Supplier prices shift. Menus evolve. Assumptions drift. Teams get busy. Decisions get made under pressure.

After watching talented chefs and operators work incredibly hard while still struggling to build sustainable businesses, it became clear that the problem was rarely effort.

More often, the problem was visibility.

Small financial changes were accumulating over time, but nobody had a practical way to see them early enough to react.

Most independent operators don't have time for complicated systems or finance-heavy software. And many of the tools designed to help create more work than clarity.

Clove is an attempt to build something more practical.

The idea is simple:

build a realistic operating model, lock it as a reference point, and then track how things change over time.

The goal is not endless reporting or optimisation theatre. It is simply to help operators spot pressure, drift and risk before they become bigger problems.

Clove is still evolving, but it is being built with a strong bias toward usefulness, simplicity and operational reality.