Rob started working in restaurants at 17. From 2000 to 2014 he ran them as a manager, Director of Operations, and COO, owned his own, and consulted for other operators. He then moved into accounting and finance, and in 2022 joined Mirus as Corporate Controller, became VP of Finance, and has been President since July 2025. His view is simple: data that does not change a decision is not worth reporting. Mirus exists to make the decision obvious.
Restaurant data, since 1999.
One industry, one problem, for more than twenty-five years: getting a multi-unit operator's systems into one place and keeping the numbers trustworthy.
- Restaurant data since
- 1999
- Headquartered in
- Houston
- Published client interviews
- 17
How it started
Mirus began with a spreadsheet that was far too large.
It started in 1998, when Brad Anderson was asked by one of his Cornell professors (who ran a consulting business on the side) to crunch an enormous quantity of numbers for menu-engineering decisions.
The work was the kind every multi-unit operator recognises: the data existed, it just lived in too many places and in the wrong shape. Mirus was founded the following year to solve that properly, and has done nothing else since.
More than 25 years on, the problem has not changed; only the number of systems it is spread across has. Mirus is still headquartered in Houston, still focused on one industry, and still doing the one thing it was founded to do.
The discipline is the same one we have held since 1999. The way we deliver it is faster and sharper than the company you remember.
How we work
One industry since 1999. The retail calendar, the store master file and the tie-out process are the product, not features bolted onto a generic BI tool.
Mirus reports across whatever you already run. A platform suite can only analyse the data inside its own walls; that is the difference.
Platform upgrades are included, and new source systems are added as they are needed.
Who you will be working with.
Dina has been at Mirus for more than 20 years and has worked most of the jobs in the building along the way. She leads Development, Quality Assurance, and Client Services, so the person who decides what gets built is the same person who answers when a client calls. Nothing ships that she would not stand behind on that call.
Runs the systems and data pipelines behind the platform, and has since 2009. Over 25 years in restaurant technology, including IT Manager for a publicly traded national chain, and ETL lead on dozens of client implementations. If a number is on a Mirus screen, his pipelines put it there, standardized and tied back to its source.
Scope to go-live.
- Contract and scopeSystems, units and feeds agreed upfront
- Kickoff and warehouse buildYour warehouse created, first POS configured
- Data integrationFeeds connected via agent, file transfer or API
- Tie-out and validationReconciled against your source systems, jointly
- Client review and go-liveLive only after you sign off.
See it against your own systems.
A scoped demo built on your POS, labor and accounting feeds: not a generic walkthrough.