Why I want a new ERP system – KisBook?

If you’re asking why you personally want to build a new ERP system called KisBook, based on our previous discussions, I think the motivation is something like this:

Why KisBook?

KisBook is not just another ERP. It is an attempt to build a simpler, more modern ERP around how businesses actually work.

You have experience with traditional ERP architecture, especially Odoo, and you’ve been thinking about its limitations. The idea behind KisBook seems to come from several frustrations:

1. Traditional ERP systems are too complicated
   • Huge frameworks
   • Hundreds of modules
   • Complex customization
   • Too much infrastructure for a small or medium business
   • Developers need to understand the entire framework before making changes.
2. ERP should be business-oriented, not framework-orientedYou have been exploring your own tbook language partly because you want business logic to look more like business logic:TABLE Customer Name TEXT Email TEXT Balance MONEY ENDRather than forcing business developers to deal with layers of ORM, controllers, services, serializers, etc.
3. Separate the frontend from the ERP backen Your recent Odoo work led you toward a cleaner architecture:Web / Mobile / Desktop │ ▼ JSON API │ ▼ ERP Services │ ▼ PostgreSQLInstead of an ERP where the UI, business logic, ORM, framework and server are tightly coupled.
4. Modern clients should be first-class citizensKisBook could have:KisBook API │ ├── Web → Next.js ├── Mobile → Expo / React Native ├── Desktop → ? └── Integrations → APIThis is particularly important because you’re already building mobile applications with Expo + TypeScript.
5. Multi-application architectureYou have also been thinking about API keys, JWT, Google login, shared users, and multiple frontends.That suggests KisBook isn’t intended to be just:”a website that happens to contain accounting.”It could instead be a business platform with a common identity and API layer.
6. Keep the core smallRather than trying to reproduce every feature of Odoo, KisBook could start with a very small core:Users Companies Customers Suppliers Products Sales Purchases Inventory AccountingThen add functionality around that core.

---

The deeper reason

I think the most important reason is this:

You want an ERP that you can understand completely.

With something like Odoo, you are effectively working inside somebody else’s enormous architecture.

With KisBook, you can decide:

• how authentication works
• how companies work
• how permissions work
• how documents work
• how accounting works
• how APIs work
• how frontend applications communicate
• how business processes are modeled

That could be one of KisBook’s biggest advantages.

KisBook philosophy

KisBook — Keep it Simple.

If KisBook is going to be your actual ERP product, I would make its architecture and philosophy explicit before writing much code. That will prevent it from slowly becoming “another Odoo.”