Our own project: software we built and operate ourselves.
Millwright: Project Page
A static page that explains the Millwright MES system (a separate case study sits alongside) in plain language: what problem it solves, how it works, and how much it saves (the computed ROI). You understand the whole story before you open the working demo.
Before opening a demo, people need to understand why it matters
The interactive demo shows the system in action, but a decision-maker from the shop floor rarely wants to click through panels first. They need a short answer first: what problem this solves, how it works, and how much it saves. This page is that answer: a static presentation, not an application.
A static information page, not a working system
A static mock-up of the monitoring panel: a grid of CNC machines and assembly stations with sample utilization and status indicators, sharing the same visual identity as the real Millwright MES.
A lightweight, fast-loading page: a few lines of code handle staggered scroll-reveal and a cursor-following spotlight effect.
Two separate static pages (EN/PL) with manual translation instead of an i18n framework: a simple brochure page, not an application.
The page explains the problem, the algorithm, and the ROI of Millwright MES in plain business language, before anyone even opens the working demo.
Millwright system design targets
intended reduction in changeover time in the MCT-S model, not a measured benchmark.
the MCT-S algorithm's reaction time to a new task; the page explains it without technical jargon.
machines (CNC, assembly, a test station) shown on the panel as an example floor.
Every choice has a reason
Got a nagging problem? Describe it, I'll code the rest.
One sentence is enough to start. Tell me what's bothering you. Within 48 hours I come back with a clear answer: can it be done, and at what fixed price.