Operational R&D · Field notes

The Lab

What are you still solving with texts, spreadsheets, and memory?

Let us know what you're struggling with

Not a feature request board. Not a public roadmap. A place to send the recurring work restaurants still hold together by hand.

Field note

Let us know what you're struggling with.

Tell us the manual workflow, who carries it, and what tools or favors hold it together today.

Restaurants are full of small systems held together manually:

reservation favors, opening staffing, vendor calls, event coordination, shift swaps, regulars, pricing memory, candidate referrals, pre-service notes.

Some of them should stay human.

Some deserve quieter infrastructure underneath them.

The Lab is where those systems begin.

Send usField notes
reservation favorsopening staffingvendor callsevent coordinationshift swapsregularspricing memorycandidate referralspre-service notes
Current experiments · 06

Not products. Working observations.

Send a note →
Field active

Reservation Request Line

Requests still arrive by text, favor, guest memory, and a manager who knows who to ask.

Observing

Opening Intelligence

New rooms produce the same questions every morning: staffing, covers, pacing, vendors, and who is carrying what.

Notebook

Event Coordination

Private events move through emails, deposits, menu edits, floor plans, and the person who remembers the last call.

Live memory

Roster

Good people still disappear between Craigslist posts, manager texts, and old staff group chats.

Quiet watch

Vendor Signals

Prices change before anyone has time to decide whether the change matters.

In use

Service Briefs

Operators do not need another dashboard. They need the one thing worth knowing before doors.

Build rule

How Relish decides what to build.

Relish does not build random software.

We build systems that:

repeat across independent hospitality
reduce operational fragility
preserve trust and memory
compound across the network
give operators more time back on the floor
Useful notes answer

Who knows the guest, vendor, candidate, or regular already?

Where did this price, schedule, note, or decision last change?

Which manager is holding the workflow together by memory?

What will break if that person is off tomorrow?