Skip to content
Iterna
Property & building management

Condo and building management software for Malaysian properties

Most buildings in Malaysia are managed through WhatsApp. Maintenance requests, complaints, vendor coordination, security notices and committee decisions all scroll past in the same thread — nothing searchable, nothing assigned, nothing with a record. Building management software replaces the thread with something that remembers.

Tell us your problem

How this usually runs today

  • Maintenance requests in a resident group chat, reported three times by three people
  • No record of who was assigned what, or whether it was done
  • Facility bookings on a paper sheet at the guardhouse
  • Visitors logged in a book nobody can search
  • Billing and arrears tracked in a spreadsheet
  • Owners with no visibility, so every AGM is an argument

What we’d build

  • Maintenance tickets

    Logged once, routed to the responsible party, with a status anyone can check.

  • Transparency feed

    So owners can see what management is actually doing, which is most of what they’re asking for.

  • Facility booking

    The hall, the courts, the BBQ pits, with rules and limits enforced.

  • Visitor management

    Registration, passes and a searchable record.

  • Billing and arrears

    Charges, receipts and who’s behind.

  • Vendor logs

    One-off contractors and permanent service providers, with what they were called for and what it cost.

  • SOP checklists

    Cleaning and landscaping tasks with photo proof on completion.

  • Notices

    Announcements that reach residents without a group chat.

The parts that are harder than they look

  1. 01

    Ownership changes and the data doesn’t.

    Units outlast owners and tenants. The system has to hold a unit’s history — who owned it when, who lived there, what was charged, what’s outstanding — through transfers, without losing the trail.

  2. 02

    Owners, tenants and committee members need different access to the same unit.

    A tenant can book the hall but shouldn’t see arrears. A committee member sees more than an owner. An owner who rents out and moves away still needs their billing. This is a permissions model, not a user type.

  3. 03

    Every action needs a record, because the AGM is coming.

    Building management runs on accountability. Who approved that vendor, when was the complaint closed, what was the balance in March. Retrofitting an audit trail is close to a rebuild.

  4. 04

    The rules are set by legislation and by the building’s own by-laws, and they differ.

    Charges, notices, meetings and enforcement follow a statutory framework, and each property layers its own house rules on top. The system has to make the house rules configurable rather than hard-coded.

Proof

We’re building exactly this, on the core that already runs Operiq.

The platform is forked from the multi-tenant core behind Operiq, which meant tenancy, roles, permissions and audit trails were already solved and tested rather than started from scratch.

It is in build, so there is no published case study for it yet. The one that shows how we work is Operiq: rosters, attendance, commission and statutory payroll for a real business.

See the Operiq case study

FAQ

Questions we get asked

  1. 01

    Can residents use it without downloading an app?

    Yes. It runs in a browser on a phone, which matters in a building where adoption decides whether the system is used at all. Asking every resident to install something is where most building software quietly dies.

  2. 02

    Can we configure our own by-laws and charges?

    That is the design assumption. Every property layers its own house rules on top of the statutory framework, so booking limits, charges and notice rules are configuration rather than code.

  3. 03

    What happens when a unit changes hands?

    The unit keeps its history and the people attached to it change. Who owned it when, what was charged, what is outstanding — all of that stays with the unit through a transfer, which is exactly what you need when a dispute surfaces two years later.

  4. 04

    Can the guardhouse use it on a cheap tablet?

    Yes. Visitor registration and passes are designed for the device that is actually at the guardhouse, not the one in the demo.

  5. 05

    Can it handle more than one building?

    Yes — the core it is built on is multi-tenant, so a managing agent can run several properties with separate data, separate committees and separate by-laws.

Tell us how your building is managed today.

How many units, who does what, and where the requests currently go. That is enough for us to tell you what the first version should cover.

Tell us your problem