The next ERP will be judged by how fast a CFO, a buyer or a warehouse lead gets a true answer and acts on it. Not by how many modules it lists.
What ERP got right
ERP began with a simple promise: one set of records for the whole business. Sales, purchasing, inventory, production and accounting stop living in separate ledgers. One transaction updates everything it touches.
That promise was right, and it still is. A sales order that reserves stock, triggers a purchase when stock runs short and lands in the books as revenue when it ships is worth more than any stack of disconnected tools.
What went wrong was the experience. Most ERP was designed around the database and the implementer, not the operator. People learned the system's vocabulary, memorized where each form lived and tolerated screens that looked like five different products. Often they were.
What changed around it
Everyone who runs an ERP at work uses excellent software everywhere else. They search instead of navigating. They expect pages to load instantly and buttons to behave the same way on every screen. They now expect to ask a question in plain language and get a straight answer.
The companies that need ERP most have changed too. A mid-market manufacturer or distributor might run a plant, two warehouses, a field sales team and a four-person finance team across several states. They cannot absorb an eighteen-month implementation or a consultant for every report. They need correct records from day one, and software the whole company can use without a manual.
Four things the next ERP owes you
One calm interface. Every screen, from a journal entry to a job card, follows one design language. Learn one part and you know the rest. It is unglamorous work, and it is most of the work.
Speed as a feature. A clerk posting fifty receipts a day feels every slow page. A system that responds instantly gets used as work happens. One that hesitates gets updated on Friday, from memory.
Answers, not reports. A controller does not want a report. She wants to know which customers are over their credit limit, which orders will ship late and how much cash will be in the bank on the 15th. Those questions should be asked directly and answered from live records.
Agents that work under the same rules as the team. An agent that drafts a purchase order from a low-stock alert and waits for a buyer to approve it is useful. An agent that changes records nobody can trace is a liability. The design has to make that difference obvious.
What Sundial is, concretely
Sundial is the AI-native ERP for modern mid-market companies: one system that runs the whole business. The modules are in the product today: Finance and Accounting, Sales and CRM, Buying, Inventory and Warehousing, Manufacturing, Projects and Services, Assets and Maintenance, Quality, Support, and Point of Sale.
Underneath is the open-source Frappe and ERPNext engine, a proven core with years of accounting, inventory and manufacturing logic behind it. That choice means no lock-in: the schema is documented, the records are yours and you can export all of them. On top, we redesigned the workspace so every screen speaks one design language, on desktop and on a phone.
Every customer runs on a dedicated, single-tenant instance with its own database, served over Cloudflare with daily backups. Role-based permissions and a full audit trail cover every record. We handle onboarding with you, hands-on, and a real team answers when you write in.
What we will not pretend
We are early, and we say so. The AI capabilities on this site describe how Sundial is designed and what we are building: plain-language questions about the business, and agents that draft work and wait for approval. Where something is in preview or on the roadmap, we label it.
If your company runs on spreadsheets, an entry-level accounting package and a lot of goodwill, the next ERP should feel like relief, not a project. That is our bar. The fastest way to judge whether we clear it is to try the demo and click through the screens your team would use every day.





