An off-plan unit carries its payment plan as dated instalments by type — booking, DLD, agent commission, construction, handover and post-handover — on the year calendar, with alerts before each one and after any that slips.

Each instalment is a label, a date, an amount and a type. Construction instalments carry their percentage, so a milestone reads as the stage it represents rather than as a date with a number beside it. The plan can be built when the unit is added or edited afterwards.

The year calendar carries instalments beside cheques, move-ins, purchases and expirations, each filterable by type and by building. Money going out and money coming in are read on one surface, which is the only way a construction milestone and a cheque falling in the same week become visible before they both do.

An instalment approaching raises alerts at thirty, fifteen, ten, five, three, two and one day, and on the day itself. One that passes unpaid escalates to an overdue alert with its own identity, so it resurfaces as unread rather than sitting quietly beneath the notification you already dismissed.

No. There is no payment rail in the product. What lives here is the schedule, the status of each instalment and the alerts around its date.
The demo opens instantly, in the role this workflow belongs to, on sample data. There is no account to create and no form in front of it.