ERP feels old because it was designed for the people who install it, not the people who use it every day. Fix the experience and the same records become far more valuable.
The form-and-list inheritance
Open almost any ERP and you see the same two shapes: a list of records and a form for one record. That pattern came from the earliest business systems, where a screen was a fixed grid of fields on a terminal. It is a reasonable way to store data and a poor way to do work. Real tasks cross many records: approving a purchase means looking at the request, the supplier's history, the budget and current stock, all at once.
When the system only offers one form at a time, people compensate. They open six tabs, export to a spreadsheet, or ask a colleague who remembers. The ERP becomes the place where data is entered after the decision has been made somewhere else.
Designed for the implementer
Traditional ERP projects were sold, configured and maintained by implementation partners. The software's main audience was therefore the person configuring it, and the design rewarded flexibility over clarity: every field optional, every label renamable, every workflow customisable. Flexibility is valuable, but without strong defaults it produces systems that only make sense to the people who set them up.
The day-to-day user inherits the result: forms with dozens of fields that are rarely filled, menus named after internal concepts, and error messages written for a developer. None of that is necessary. A good default layout can still be configured; it just does not require configuration to be usable.
Navigation as a map of the database
Many ERP menus are organized by module and document type, which mirrors how the database is structured. A user who wants to see what is owed by a customer has to know that the answer lives under accounts receivable, in a particular report, filtered a particular way.
People do not think in modules. They think in questions and in work: what do I need to approve, what is late, who owes us money. Navigation should start there. Search that finds a customer, an invoice or a report by name, and a workspace that shows the work waiting for you, removes most of the need to memorize a menu tree.
Every screen a different product
ERP suites grow by accretion. A manufacturing module is added one year, a support module another, and each arrives with its own spacing, buttons and conventions. Users feel this as friction: the save button moves, a date field behaves differently, a table that sorts on one screen does not sort on the next.
Consistency is not cosmetic. Every inconsistency is a small tax on attention, and an ERP is used hundreds of times a day by the same people. Sundial's workspace was rebuilt so that every screen follows one design language, checked screen by screen, because that is the only way the tax goes away.
Slow by default
Older systems often treat a page that takes a few seconds as acceptable. For a person posting stock entries all morning, it is not. Slowness changes behavior: people batch their updates, enter data later from memory, and the records drift away from reality. Fast screens are one of the most direct ways to improve data quality.
Speed is also why where the system runs matters. A dedicated instance served over a global network, instead of a shared server in a distant data center, removes a whole category of waiting.
What changes now
The business logic of ERP, double-entry accounting, stock valuation, bills of materials, does not need reinventing. It needs a proven core and a better front door. That is the approach Sundial takes: the open-source Frappe and ERPNext engine underneath, and a redesigned workspace on top that treats the daily user as the main audience.
The other change is that software can now understand plain language. That does not replace forms and records; it gives people a faster way to reach them. Asking which orders will miss their delivery date this week, and getting a list you can act on, is how we think ERP should feel. We are building toward it carefully, with the records and permissions in place first.





