Built by a landlord, run on a real building first

What a real building teaches software

That tenants pay in parts, on different days, by different methods. That a cleaner does not want a dashboard; she wants to know which unit is next. That a guard will keep a log on a phone if it takes three taps and not if it takes five. That the water bill arrives as a single number and has to be split fairly. That official receipts are a booklet with serials, and the BIR will ask. That the owner's accountant wants files, not a login.

None of this is in a requirements document. It is in a year of running a building and being annoyed.

Why some things look oddly specific

The five-calendar-day disciplinary clock, because Philippine labour law has one. Water tariff bands, because the local utility bills that way. A "next unit" button on the cleaner's page, because walking back to a list wastes a minute each time and there are twenty units. The "View as" button, because the owner kept asking "what does Shane see?" These are not features someone imagined a customer might want. They are scars.

What it will never pretend to be

A bank. An accounting system of record. A chat app. A robot that runs your building. It records what happened, raises what is due, tells you what needs you, and stays out of the decisions. The building is still yours.