Operations

The property's numbers, in one place, before the morning meeting.

Operations is the general manager's view of the property: house totals, month end and the machine floor, read from the same file that feeds Player Development and laid out the way you already report them. How the property is performing, without the spreadsheet chase.

What's on it

Three screens the property runs on.

House totals

The house by day, week and month.

The property's totals on one screen, with the trend beside them, so the question at the morning meeting is what to do about the number, not which number is right.

Month end

The pack, in one place.

The month-end metrics your finance team already reports, computed from your file rather than re-keyed, with a printable pack for the meeting and the board.

Machines

What earns and what sits idle.

Machine performance across the floor, unit by unit, so the floor gets weighted toward what players actually play.

How it fits

One file. Two views of the property.

Reads from your systems

Writes nothing back.

Connect by file upload or by API. Operations reads the same export that feeds Player Development, so the house numbers and the player numbers agree, and your system of record stays your system of record.

One login

Each person sees their own module.

The general manager opens Operations. The host desk opens Player Development. Role-based access matches your org chart, per property.

Multi-property

One property or fifty.

One login across every property, budgets and caps set per floor, consolidated billing with a per-property breakdown, and role-based access that matches your org chart. Each property's players stay its own.

See your property's numbers on it.

Thirty minutes. Walk through Operations and Player Development on your own file.

Pick a time →
Google Meet or phone