RXM

RXM is not a one-off restaurant dashboard. The product goal is a modern SaaS ERP that any company can adopt: its own workspace, the modules it needs, and room to grow into HR, accounting, inventory, CRM, and operations without rewriting the frontend for every industry.

The platform is already in production at therxm.com with real users. On the frontend I own the multi-tenant workspace context, company surfaces, invitations, roles, and the module shells that will become the full ERP. Finance, employees, attendance, expenses, invoices, inventory, procurement, and admin tenancy are part of the product surface we are hardening into a coherent modular system.

What matters architecturally is genericity. The UI cannot assume one business type. Tables, forms, permissions, and workspace switching have to stay reusable so restaurants, clinics, gyms, and other companies can run on the same product later. I am actively leading company onboarding, subscription packaging, and deeper module wiring, so I frame RXM as a shipped production foundation under expansion, not a finished every-module ERP.