About Reqva

Clear information. Practical action.

Why Reqva is starting with ingredient costs, dish impact and delivery claims, and where the product is heading.

Restaurant work rarely arrives in one place. An invoice comes by email. A delivery problem is spotted at the door. A recipe changes in the kitchen. The decision belongs to someone who needs the whole picture.

Reqva is being developed to connect those details to a clear next action, with the original evidence close enough to check.

Starting with Food Control

Our first pilot direction follows a small set of important ingredients: compare verified unit costs, understand the effect on confirmed recipes and follow documented delivery claims through to their credit status.

We are inviting pilot conversations. Scope, timing and any terms will be agreed directly with participating restaurants. This website presents the intended experience through illustrative examples.

A wider direction

Kitchen Brief, Safety Control, Owner Pulse and Groups & partners are planned extensions. They bring the same approach to shift handovers, corrective actions, owner decisions and shared oversight. Their scope and sequence will be informed by practical testing.

What guides the product

  • Keep the source. A useful number needs a traceable input and a clear calculation.
  • Make uncertainty visible. An unknown pack size or unresolved quantity needs confirmation.
  • Give people the decision. AI can help structure information; people review uncertain details and approve supplier communication.
  • Describe outcomes accurately. An estimated cost change, an issued credit and an applied credit are different things.

Bring your restaurant into the conversation

We want to understand the paperwork, decisions and handoffs in your operation. Start a pilot conversation or email [email protected].