Hi Warga runs the money and the daily operations of a housing estate in Indonesia. Every month it issues the IPL (the estate service fee) and water bills, records each payment in the cash book, and keeps residents updated through an app. It is a company product, and I built all of it myself.
The challenge
Most estates still track payments in a spreadsheet and a WhatsApp group. The treasurer rebuilds the same recap every month, late fees are counted by hand, and nobody knows which houses have paid without asking. The system had to replace that for three very different users at once.
One system, three users
- Managers and treasurers work in the browser: bills, arrears, and late fees, transfer proof checks, the cash book and reports, announcements, and import from old spreadsheets.
- Residents use the app or a phone browser: see and pay bills, download receipts, read announcements, report issues with a photo, and reach security with an emergency button.
- Field officers use a mobile app that keeps working with no signal: water meter readings with photos, patrols with a QR scan at every checkpoint, resident reports, and emergency alarms.
What I did
- Designed and built every part on my own: the landing page, the back office, the resident app, the field officer app, and the backend.
- Back office and resident app on Laravel, Inertia, React, and TypeScript, with PostgreSQL. Field officer app in React Native. Everything runs in Docker.
- Built the monthly cycle so bills issue themselves on the 1st: IPL, water from the meter reading, and last month’s balance in one bill.
- Turned payment chasing into one button: every unpaid house gets a reminder, and late fees follow each estate’s own rules.
- Made the field app offline-first: readings and patrol scans save on the device and sync once the officer is back online.
Result
- Managers see which houses have paid IPL this month without a manual recap.
- The cash report for the residents’ meeting is one PDF at the end of the month, with opening and closing balances.