03 / Operate
CASTALD
Property Operating System
One live picture of a property business: the buildings, the units, who's in them, the contracts, the money owed, the equipment, what's broken, who's fixing it and what it cost. Then it drives the work through that picture.
- UnitOne property
- Objects9 types
- ScopeDeliberately deep
- MarketGCC
Well past prototype. Tenancy, maintenance, procurement and the tenant layer already exist.
Six people, six quarters of the truth.
Nothing here is broken, exactly. Every piece is written down somewhere. It's just that no two pieces are written down in the same place.
- The tenant Knows The air conditioning has failed again, and told someone on WhatsApp
- The technician Knows It's the third time on that unit, because he was there for the other two
- Finance Knows The contractor invoice is unpaid, and doesn't know which unit it was for
- Admin Knows The tenancy expires in five weeks and nobody has sent notice
- Management Knows The building is getting expensive, and not why
Five people hold five true things. Nobody holds the sentence that connects them, so the same unit fails a fourth time and it still looks like bad luck.
A generic system sees a ticket.
Task #214
Open · Medium priority
AC unit 4B in Building A has failed for the third time in five months, affecting Tenant X, under Contract Y, assigned to Technician Z, needing Part Q from a supplier with a four day lead time, at AED N so far, against an SLA of four hours.
Same event. One of those two can tell you to replace the unit instead of repairing it a fourth time. The other can tell you the ticket is still open.
Nine kinds of thing, and every one touches the others.
A property contains units. Units hold tenants. Tenants sign contracts. Contracts create payments. The building holds assets. Assets create jobs. Jobs consume materials from suppliers, and all of it costs money.
Activity moving along the edges is what separates an operating state from a database. A database would hold the same nine objects and never notice that one of them just changed.
Seven stages, and the last two are the point.
Most property software stops at track. The two stages after it are where a system stops being an admin cost and starts telling you something.
- 01 See Something changed. A failure, an expiry, an overdue payment. Guarantee: it enters the state once, not into four inboxes.
- 02 Route What has to happen because that happened? Guarantee: priority and owner are decided, not left to whoever notices.
- 03 Execute The right person gets the work, in their own view. Guarantee: a technician sees a job, an owner sees a portfolio.
- 04 Track How long has it been open, and has it stalled? Guarantee: an SLA is watched, not reported on afterwards.
- 05 Learn Has this happened before, to this asset? Guarantee: repeat failure is counted, not rediscovered.
- 06 Diagnose Why is this building getting more expensive? Guarantee: answers come from your own operating history.
- 07 Correct What should management change? Guarantee: a recommendation names the evidence behind it.
Returns to see. A property never stops changing
It gets useful in three stages.
Worth being straight about which of these exists today, because the third one is the reason to care and it's the one still being built.
-
Level 1
Know what you have.
Every property, unit, tenancy, asset, contract and supplier in one place, connected rather than listed. This is the part that replaces the spreadsheets and the WhatsApp threads.
Built -
Level 2
Run the work through it.
Requests become classified, prioritised, assigned jobs with an SLA and a parts trail. Tenancies raise their own notices. Tenants act through their own view instead of messaging a person. Costs attach to the thing that caused them.
Mostly built -
Level 3
Have it tell you what to change.
Once it holds enough of your history, the questions change. Which properties are getting less efficient. Whether you actually need another technician or one building is eating the budget. Which contractor creates the rework. Which asset to replace instead of repairing a fifth time.
In build
Level three isn't a feature you switch on. It needs a year of your own operating history before it can say anything worth acting on, which is exactly why it has to be built on levels one and two rather than sold on its own.
What CASTALD doesn't do
- It doesn't work for any other industry. It knows what a unit, a tenancy, an SLA and a chiller are. That depth is the entire product, and it's why it can't be pointed at a logistics firm next quarter.
- It isn't a dashboard. The screens are a view onto a state it's already maintaining. If the only thing a system does is display, someone is still doing the operating.
- It doesn't replace your judgement about people. It will tell you a contractor generates rework. Whether you keep them is your call and it stays your call.
- It doesn't diagnose on day one. Level three needs your history. Any system that offers you insight in week one is showing you its assumptions, not your business.
- It doesn't pretend a bad process is a software problem. If nobody in the business is accountable for closing a job, this will show you that clearly and then wait for you to fix it.
07 / Enquiry
How many doors do you run?
- 01You tell us the portfolio
- 02We say whether it fits
- 03Or that it doesn't
Ask about CASTALD
Tell us roughly how many properties and units you manage, and the one thing about running them that costs you the most time. That's enough for us to say whether this is relevant yet.
Sent
We answer within one business day.