The waiter's tap, the food that left the shelf, the wage that was signed, the riyal that reached the bank — all of it is the same record, written once and read everywhere.
Each department has its own staff, its own sign-in, and screens built for that job — writing into the same record as everyone else.
Register · tables · kitchen
LiveSales · food cost · targets · EOD
LivePeople · attendance · Qatar law
LiveRequests · purchasing · suppliers
LiveOrder · wastage · inventory counts
LiveCampaigns · plans · budgets
LiveStaff access · PIN resets · printers
LiveLeave · certificates · requests
LiveReport · fix · cost straight to P&L
LiveStaff housing — villas, beds, occupancy
LiveComplaints · calls · reviews
LiveFood safety · academy · exams
LiveProduce and supply the branches
LiveBake and supply the branches
LiveEvery branch, one screen
CommandA restaurant group does not run on one system. It runs on a till, a spreadsheet, a WhatsApp group, an accountant's file, and four delivery tablets. Each holds a different version of the truth.
Every seam between two systems is a place where money goes missing.
MiM is not a POS with reports bolted on. It is one database that every department writes into and reads from — so there is one version of every number, and it is today's.
A count means somebody has to act. Every number below links to a person, a shelf, or a bank line.
These panels use demo data. On a live install they read from your own branches.
If one person is still re-typing yesterday's numbers into a file every morning, you are the operator this was built for.
Anything marked "coming" is not connected yet. We would rather tell you now than on the install day.
The balance lives on the engine, not on the card — so it cannot be edited at the till.
Twelve audit holes were found and closed before this shipped.
The local rules are not a checkbox we added. They are the way the system counts.
The real SIF format, accepted by the bank
EOSB, rest-day pay, wage floors, Art. 70
Ramadan and Eid computed, not typed
Every screen, including the receipt
Thursday night belongs to Thursday
14 categories · undetermined is never "free"
Prime cost is food plus labour. Move the sliders to your group and see the size of the prize — before anybody promises you anything.
Prime cost benchmark: under 55% is healthy for most full-service operations, 55–65% is worth watching, above 65% usually means the menu or the roster is carrying a problem. Nothing here is sent anywhere — the arithmetic runs in your browser.
MiM was not built for a market. It was built because we needed it, and we are the first ones it has to be right for.
We did not set out to sell software. We set out to stop losing money in the gaps between five systems — and then we could not go back to the old way.
Trust is earned by what a system refuses to ship, not by what it promises.
Every one runs the real code. None just reads it.
Append-only. A correction is added, never an edit.
The till keeps selling when the line drops.
A backup nobody restored is not a backup.
The bug is re-injected to prove the test catches it.
The cockpit and the P&L share the same code.
You are handing over payroll, bank matching and every sale you make. Here is exactly what happens to it.
PostgreSQL on a paid tier with daily automatic backups. Not a free plan, and not a file on a machine in the back office.
There is no open API reading your tables. Every request goes through the engine, with a key, and the key is per install.
Sales, voids, refunds and wage changes are appended to a permanent journal. A correction is a new line, so the original stays readable for ever.
Salaries, ID numbers and documents sit behind a separate HR key. A waiter's screen cannot reach them, and neither can a manager's without it.
The till keeps selling offline and queues every sale. When the link returns it settles up — and an empty answer is never mistaken for a real zero.
Every table exports to a spreadsheet. If you ever stop paying us, you keep your history — that is the point of a permanent journal.
Every department is included in every plan. You are not sold "the HR module" a year later — what changes is the size of the group, not the software.
One restaurant, one kitchen, however many tills you need on the floor.
Several branches, one or more brands, a head office that wants one screen for all of it.
Many brands, franchise partners, or a group that needs its own install and its own keys.
Send one line about your group — how many branches, and which system hurts most. We will show you the same screens we run our own restaurants on.