Variant of ERP v1 built with enterprise-level feature depth. More modules, more automation, more reporting. Built to explore how far the system could stretch.
The problem
Once ERP v1 was working, the obvious question was how far it could go. Where does an all-in-one system stop being useful and start being a burden? You don't answer that by guessing. You answer it by building the heavy version and seeing what breaks, what gets used, and what just adds weight.
What I built
The enterprise variant: ERP v1 pushed to feature depth. More modules, more automation, more reporting. It was deliberately maximal, built to find the ceiling of the system rather than to ship the smallest thing that works.
How it works
Same Next.js foundation as ERP v1, scaled up. Extra modules, deeper automation across them, and a heavier reporting layer on top. The architecture is the same shape as v1, just stretched to carry far more surface area.
Outcome
Deployed to a real client and used in production; it later gave way to the leaner build that became Klyft. What it really produced was a clear data point at the heavy end of the spectrum, sitting opposite the lean variant. Between the two, it became obvious that depth wasn't the thing the market actually wanted, which is the conclusion that pointed everything toward the leaner direction. The result here is the lesson, not a usage figure.