GM — General ManagerSign in

Operational intelligence for physical business

You don't watch
the cameras.
GM does.

GroundMind turns existing cameras into operational intelligence — helping businesses understand what's happening, identify inefficiencies and uncover opportunities to improve performance. Built first for restaurants and hospitality.

Works with Ring today; RTSP/IP cameras in pilot. Product facts · FAQ

01What GM sounds like

“Guests were waiting while tables were being reset. One party left before a table was ready. The delay wasn’t at the door. It was in the turnover.”

Not “motion detected.”

A conclusion, with context.

02The whole operation

One location.
Hundreds of things happening.
One GM connecting them.

After-hours activity is only the beginning. GM is built to understand the questions an operator actually asks.

01

Guests

  • Who arrived, and who waited?
  • Was someone acknowledged — and seated?
  • Did anyone leave before being seated?
02

Tables & capacity

  • When did guests leave?
  • How long did resetting take?
  • Was a ready table available while guests were waiting?
03

Service

  • Where did service slow down?
  • Where did a delay begin?
  • What happened before and after it?
04

After hours

  • Who or what was present?
  • Was it expected?
  • Did it fit this location's normal routine?

“Someone stayed near the rear entrance for about seven minutes at 2:14 AM. Your cleaning crew normally finishes by 2. This doesn't match any routine I know here.”

05

Deliveries & back of house

  • When and where did activity occur?
  • Did something happen outside the usual pattern?
06

Opportunity

  • Where did friction overlap with real demand?
  • Where might capacity have been recovered?

03Connection, not detection

Other systems see five events.
GM sees one story.

  1. 7:42 PMA party of four arrives.
  2. 7:44 PMThey wait near the host stand.
  3. 7:46 PMGuests at table 12 leave.
  4. 7:58 PMTable 12 is still being reset.
  5. 8:03 PMThe party walks out.

GM

“A party of four left at 8:03 without being seated. Table 12 had been free since 7:46 but took 17 minutes to reset — longer than your target. A ready table would likely have kept them.”

The sequence is the insight. GM understands what happened, in what order, and what it cost.

Illustrative example

04Revenue Recovery

Not only what happened.
What it was worth.

GM connects operational friction to real demand — showing where capacity may have been recovered, conservatively and with the evidence behind every figure.

Example analysis · One eveningSimulation · Synthetic test data

7

guests left before seating

Across 2 parties

100 min

over reset target

Summed across slow table resets

≈3.1

covers estimated recoverable

From 282.5 recoverable seat-minutes

About $560 in estimated potential revenue was associated with the parties who left. Illustrative figures from synthetic test data — not a customer result.

05Ask GM

Ask your location
anything.

Not another dashboard to interpret. A manager you can ask, in your own words.

“Why did we lose guests last night?”

“Which tables took longest to reset?”

“Was anyone at the rear entrance after closing?”

“What should I know about yesterday?”

“Was anyone here between 1 and 5 AM?”

06Memory

GM learns what is
normal here.

Every location is different. GM becomes specific to yours — and when it gets something wrong, you tell it, and it remembers.

  • Your hours
  • Your areas and tables
  • Your routines
  • What you've told GM
  • Your corrections
  • What matters to you

07Coming to GM

Some things shouldn't
wait for the report.

Tell GM what you never want to miss. When a condition you choose occurs, GM will be able to let you know right away.

“Text me if anyone enters through the rear entrance after closing.”

  1. 01

    In GM

    Everything worth knowing, always there.

  2. 02

    Daily briefing

    What mattered yesterday, in a few sentences.

  3. 03

    Text, immediately

    Only for what you choose.

08Where GM is going

The intelligence layer
for the whole floor.

Guests and tables are where GM starts. This is the wider operation it is being built to understand.

Bar & POS

Drinks poured, compared with drinks recorded.

The pass

How long finished dishes wait before pickup.

Returns

Food coming back from the dining room.

Waste

Patterns in what gets thrown away.

Labor

Where your team is, across the floor.

Closing

Activity that continues past close.

09Portfolio

One location or hundreds.
One operating picture.

Each location keeps its own context — its hours, its rhythm, its normal. GM tells you what matters across all of them, without you watching any of them.

10Privacy

Built to understand operations, not identify people.

GM doesn't use face recognition and doesn't build identities. It pays attention to what happens — arrivals, waits, tables, routines — so you can run a better operation. Read our privacy approach

Stop watching.
Start knowing.