Marty vs. Mirus: Reporting and Managed Profit Control
Mirus provides restaurant reporting and exception delivery. Marty is a managed profit-control layer for multi-unit restaurants: it connects signals from existing systems and makes sure issues have an owner, follow-through and a checked result. The useful comparison is the work that happens after information arrives.
Marty focuses on U.S. restaurant groups with 5–50 locations and $10M–$100M in revenue, led by an owner, COO, CFO, controller or operating partner who needs less manual chasing across locations.
What Mirus documents
Mirus describes scheduled report delivery, including exception-based reports that send only when data is present. Its Group Alert Schedule combines reports into a single delivery. That means a user does not necessarily have to log in and pull every report manually. Mirus Group Alert Schedule.
Mirus also describes labor exception alerts using configurable thresholds. The useful questions are which data sources are available, how often they update and who receives each exception in your configuration. Mirus labor alerts.
The baseline and the ongoing routine
The Review works toward findings ranked by dollars and location, supported by evidence, with an owner and recommended action. It includes a 30-day plan walked through with your leadership team.
That baseline starts the routine. Optional Managed Profit Control then provides follow-up, escalation and verification around the agreed controls. Evaluate how that work would operate alongside the reports and alerts you already receive.
To distinguish a labor ratio from its target gap, use the labor cost calculator before deciding what an exception means.
Compare reporting and responsibility
| Work | Mirus capability documented above | Marty scope to evaluate |
|---|---|---|
| Recurring information | Scheduled reports and grouped delivery | Review uses available records to establish priorities |
| Exception delivery | Report conditions and recipients can be configured | Ongoing service monitors agreed controls and alerts managers |
| Investigation | Your operating team must assign an investigator; confirm any vendor services separately | Review develops source-backed findings and recommended actions |
| Follow-through | Decide who in your team owns action and the later check | Optional managed follow-up, escalation and verification |
| Setup | Create the relevant report, schedule and authorized recipient list | Confirm permitted records, scope and refresh cadence; a native Mirus connector is not established here |
| Price | No current Mirus numeric quote verified in this comparison | Review flat fee confirmed first; continuation priced separately |
Hypothetical use case: Mirus delivers a recurring labor exception. If your analyst explains it, the GM acts and the area manager checks the result, the existing process may be sufficient. If exceptions pile up across locations because no one owns that cycle, assess a scoped Marty service around the existing evidence. A duplicate report is not the reason to buy.
When each approach fits
Evaluate Mirus when you need recurring restaurant data reporting and distribution. Consider Marty when your leadership team needs a repeatable profit-control routine with assigned actions, follow-up and verified results. The Review establishes its baseline.
Keeping an existing reporting system can make sense. Confirm the permitted access and records available for the Review rather than assuming a native connection between the products.
Watch how Marty works for the service sequence to evaluate alongside existing Mirus report delivery.
Put the findings to work
Keep useful Mirus reports and scope the work that remains after delivery. Marty is a managed profit-control layer using Find → Assign → Follow up → Verify. Its paid Cash Recovery Plan establishes the baseline; optional Managed Profit Control monitors agreed controls, alerts managers, follows up, escalates missed actions and verifies results.