In 2016, we started moving three tea estates from a DOS-based system to ERPNext v7. There was no precedent for this in Indian tea, the estates ran on satellite internet that dropped every afternoon, and the old system let people edit records after the fact with no audit trail. That last part mattered more than we expected when you introduce a system that makes everything visible, not everyone is happy about it. The first few years were less about software and more about getting people to actually use it. Data entry was refused, workarounds were invented, and it took a long time before the system was trusted enough to hold the company's books. Today, every piece of the business runs on one ERPNext instance: daily attendance for 5,000–7,000 workers via biometric integration, 5 million kg of tea tracked annually through perpetual inventory, wages calculated across multiple statutory regimes, and all accounting, compliance, and planning flowing from one schema. Audit cycles went from 50 days to 25. New compliance requirements like e-invoicing and e-waybills roll out in days. Real-time inventory visibility across estates, stock location, ageing, cross-warehouse movement — has reduced wastage and changed how we plan. We'll walk through the actual DocType architecture behind the wage, field and factory module, field by field, so you can see what building natively on Frappe looks like in a statutory-heavy context. It took five years to muster the courage to move accounting. The compounding returns only showed up after that. This talk is for partners delivering ERPNext in complex, old-economy industries and for business owners wondering if the long bet is worth it.