Mizan: Offline-First ERP for Growing Businesses

How I helped shape Mizan into an operating system for growing businesses

The challenge Many small businesses start with notebooks, spreadsheets, or disconnected apps. That works until sales, stock, expenses, customer balances, and cash stop agreeing. The product needed to remain simple for a solo merchant while supporting multiple users, branches, approvals, reporting, and accounting as the business grows.

My role I worked across product definition, domain modeling, architecture, mobile, web, backend, testing, and delivery. The goal was not to add features for their own sake. It was to create a system where every operational action produces reliable financial and inventory consequences.

The solution • Flutter mobile app designed for fast daily operations • Next.js web application for deeper administration and reporting • Java and Spring Boot APIs with PostgreSQL • Sales, receipts, customer balances, inventory, purchasing, and expenses • Cost of goods, gross profit, cash expectations, and period reporting • Returns, refunds, related expenses, and receivable tracking • Multi-user, role, permission, branch, and property boundaries • Offline-capable workflows that preserve work during unreliable connectivity • Auditable records, safe corrections, and clear operational history • Automated tests, CI/CD, environment configuration, and deployment planning

Key product and architecture decisions Mizan treats sales, stock, cash, receivables, expenses, and accounting as one connected domain rather than independent screens. Offline behavior is designed around explicit sync states and conflict-aware operations instead of pretending the network is always available. The data model can begin with one operator and one location, then grow into controlled multi-user and multi-branch operations without replacing the system.

Outcome The result is a practical ERP that gives owners a working view of the business today while preserving the structure needed for reliable reports, accounting, and future growth. It reduces duplicate entry, makes operational problems visible, and gives the client a product that can evolve without losing financial integrity.