HOAappSign in

The position

Sold to the association

Not to the developer, and not to the builder’s facility-management arm. That is a commercial decision before it is a technical one, and it decides everything else.

A system an association buys for itself answers to the association. A system the builder provides answers to the builder — and the module that records what the developer still owes is the one nobody has an interest in maintaining.

What it refuses to do

Software is usually described by what it offers. These are the things this product will not do, each of which was a decision somebody had to make and could have made the other way.

  • There is no online payment anywhere in the product.

    A constituted association has no bank account in its own name, so a payment button would be collecting into somebody else's. The receipt is the only proof a resident gets, which is why its numbering is gapless and why that matters more than a payment page would.

  • A defect cannot be recorded without a target date.

    An undated defect is how a builder's snag list becomes a list nobody is accountable for. The system cannot represent one — not a validation that can be skipped, a shape the data does not have.

  • A count of defects is never stored.

    A stored summary drifts from the register it summarises, and a summary that disagrees with the register is what a builder's advocate reads aloud. It is computed from the rows every time it is shown.

  • Addressing a notice and reaching one are two different numbers.

    “Sent to all 73 flats” is what most systems report. What is true is that some smaller number had any channel at all, and the gap is invisible when one figure is shown. Both are reported, with a reason for every flat that could not be reached.

  • An in-app badge is not service of a notice.

    The association controls the app and the member may never have opened it. A statutory notice counts only channels that leave a record on a system the association does not own.

  • A tick is not a verification.

    Verifying an owner names who checked it, when, and against which instrument — a deed, a sale agreement. A boolean records that somebody clicked.

  • A conflict is never resolved automatically.

    Where the register and an imported sheet disagree, both values are kept and a question is raised. Choosing silently is how a register ends up describing a building that does not exist.

Your data stays in India

The register, the money records and the documents are held in Mumbai. Sign-in identities sit on infrastructure that cannot currently be pinned to a region, which is a genuine limitation and is stated rather than glossed — it holds an email address and nothing else.

What it is not yet

One association is live on it. It is early, and a committee choosing it is choosing something being actively built rather than something finished. That is worth knowing before a conversation rather than after one.