Founder's Perspective
Building Innuevation and the long argument behind it. · 5 posts
The Six-Module Constraint: Why We Didn't Build a Marketplace
Every major ERP has an app marketplace. Thousands of add-ons, integrations, and extensions — a thriving ecosystem that makes the platform more capable and the vendor more defensible. We made a different bet: six modules, one architecture, no plug-ins. The constitutional model works only if everything speaks the same language. Here's the reasoning — and the risk we accepted.
What an Alpha Tester Who Acts Like a CFO Taught Us
KC joined as our alpha tester and immediately started treating the system like a live financial operation — not a QA exercise. She wasn't looking for bugs. She was trying to run a business. The gaps that surfaced weren't failures of individual features. They were architectural assumptions we'd made about how a CFO thinks that didn't survive contact with how a CFO actually thinks.
Building on PostgreSQL: Why We Chose the Database Over the Framework
The business logic in Nue lives in the database, not the application layer. Triggers enforce financial rules before data persists. Views derive subledger balances from the ledger without maintaining separate state. Constraints prevent invalid records from existing at all. This is an architectural choice — the database is the thing that can be trusted absolutely, so the database is where the rules live.
The Decision to Build the Ledger First
Most ERP companies build the UI first and figure out the data model as they go. The UI is what sells, what gets demoed, what investors see. The data model is what determines whether the system works correctly at scale. We built the Universal Ledger as the foundation and then built every other module to serve it. Here's what that decision cost us early on — and what it made possible.
Why I Spent 18 Years in ERP Implementations Before Building One
Two decades of implementing other people's ERP software gives you a specific kind of education. You learn what the systems can do and what they claim they can do. You learn where the architecture bends and where it breaks. And eventually, you have a very clear picture of the mistake that virtually every system makes in the same way — a mistake you've been working around on behalf of clients for your entire career.