Why we build on ERPNext instead of a proprietary ERP

Most ERP conversations start with a feature checklist and end with a licence quote that scales badly the moment a business actually grows. Add ten seasonal staff for harvest season, or open a second branch, and a per-user proprietary licence turns headcount growth into a procurement problem.

We standardised on ERPNext, built on the Frappe framework, for a simpler reason than “it’s free”: it removes that trade-off entirely.

What this actually changes for a client

• No per-user licence traps. Add users as the business grows without a renegotiation.
• The data stays yours. Self-host on a VPS, run it on-premise inside Tanzania, or let us host it — the same system, three different trust postures.
• One system, not a suite of point solutions. Accounting, HR, CRM and inventory share one data model, so a sale in the CRM already exists as a transaction in the ledger.
• No forced upgrade cycles. We control the update path, so a version bump never breaks a customisation without warning.

Where this matters most

Donor-funded and NGO clients in particular tend to run multi-year budgets with fixed, scrutinised costs — a licence model that quietly grows with headcount is a real risk to a grant budget. Open-source foundations mean the software cost is the implementation and support we bill for, not a recurring per-seat tax layered on top.

This isn’t a purity argument about open source in the abstract. It’s that owning the system outright is the only model that matches how businesses here actually grow: in bursts, seasonally, and often across an office and a fleet of field staff at once.