Most operations software is designed for the person who signs the purchase order. The procurement manager gets a clean dashboard. The maintenance engineer gets a form with forty fields.
We decided early that eQuinox would be the inverse.
The reference user
Our primary reference user isn't the operations director. It's the supervisor who arrives at 06:00, checks what broke overnight, assigns the morning's work orders, and needs the system to get out of the way by 07:00 when the floor opens.
Everything in eQuinox is measured against that constraint. If an action takes more than three taps on a tablet, we ask whether the step is even necessary.
The cockpit metaphor
We call the main dashboard the cockpit — not because we think operations is glamorous, but because pilots need situational awareness at a glance. You can't afford to dig through menus when something is wrong.
The cockpit shows:
- Open work orders by priority and age.
- Assets flagged for attention (overdue PM, fault logged, parts on order).
- Team on shift with their current assignments.
- A single activity feed combining all three.
Four panels. No tabs to switch. Everything you need for the next thirty minutes.
Designing for variable literacy
Facilities aren't uniform. A single site might have a highly technical engineer, a senior technician who has never used a tablet, and a contracted cleaner who needs to log a fault. The system has to work for all three.
Our approach:
- Text labels everywhere. No icon-only controls. Every action has a label.
- Progressive disclosure. Advanced options (custom checklist items, bulk re-assignment) are present but hidden behind a deliberate extra step.
- Offline-tolerant. Work orders, asset records and checklists are cached locally. If the network drops mid-shift, nothing stops.
What we said no to
The list of things we chose not to build is as important as the roadmap. We said no to:
- A built-in messaging system (there are better tools for that).
- A custom reporting builder (too much surface area, too little coherence).
- White-labelling the UI per-customer (a maintenance tax we can't afford at our scale).
Every "no" protects the people on the floor from a tool that's trying to be too many things at once.
The GA milestone
eQuinox General Availability is anchored to 7 July 2026. That date isn't arbitrary — it gives us Q2 to complete the compliance audit, run the closed pilot with our first two customer sites, and resolve any production-grade issues before we open the waitlist to all.
The design stays floor-first throughout.