ORACA Property OS
The operating layer for buildings and the people in them.
Property OS is where the everyday work of a building happens: the inquiry at 9:40 pm, the viewing on Thursday, the request on Sunday, the approval on Monday. It gathers, answers, books and routes; your team decides. Installed and operated by ORACA, beside the system of record you already keep.
Four desks, one record.
Every inquiry captured on web, text, email and WhatsApp, answered in under a minute from your listings, a viewing offered from the real calendar, follow-up until it is held or the prospect says no. Runs today
Resident questions answered from your own policies on the building’s number and email, day and night, with a person taking over the moment judgment is needed. Runs today
Unit, photos and urgency collected; emergency words page your on-call contact; everything else waits for a named approval before a contractor is contacted. Proposed
What needs a decision today, sorted by what it costs to ignore, with every rate’s denominator shown. The portfolio view of this screen is ORACA Hive. Runs today
Three kinds of owner, one system.
A digital front door from the first rendering. Inquiries captured and answered while the building is still a drawing, a waitlist that is followed up, and a lease-up that runs on a calendar. Read more
One morning screen across what you own: what needs a decision, what is waiting on whom, and a record of who decided what. Rent and occupancy stay in your system of record. Read more
The leasing desk and, when named approval roles are in place, the resident and maintenance desk. Less gathering, routing and chasing; the decisions stay with your team. Read more
What runs today, what is next.
Runs today
| Capability | What it does | Status |
|---|---|---|
| Inquiry capture on web, text, email and WhatsApp | Every inquiry lands in one record with its source, the questions asked and the answers given. | Runs today |
| Answers in under a minute, around the clock | The assistant answers from your listings and your own knowledge base, identifies itself as automated, and hands over to a person on request. | Runs today |
| Viewings booked into a real calendar, reminded, rebooked | Google, Microsoft or iCloud calendars. Reminders, reschedules, no-show recovery. | Runs today |
| Follow-up until a viewing is held or the prospect says no | Consent recorded, send windows respected, unsubscribe honoured on every channel. | Runs today |
| Campaigns traced to inquiries and viewings | Meta and Google spend, cost per inquiry, source on every lead and appointment. | Runs today |
| Resident questions answered from your policies | The same assistant, on the building's own number and email, grounded in your documents. | Runs today |
| The morning screen: what needs a decision today | Sorted by what it costs to ignore. Six of seven card types run on real rows. | Runs today |
| Inquiry to viewing funnel, response times, open requests | Every rate prints its denominator. A figure without data renders as not enough data yet, never as zero. | Runs today |
| Build and lease-up desk: stages, waiting-on, stalled alerts | Runs today for a design practice. Vocabulary comes from config, so a development is a project with different stage names. | Runs today |
| A separate database per client | Row-level security on every table and a three-query leak sweep on every change. | Runs today |
| Personal data encrypted at rest | Names, emails, phones and addresses are encrypted in the database. | Runs today |
| Every automated decision in an append-only log | What was decided, for whom, and why. Exportable on request. | Runs today |
| Outbound fails closed without consent | No recorded consent, nothing sends. Stop means stop on every channel. | Runs today |
| A compliance check on every outgoing reply | A deterministic check refuses to send a reply that breaks a rule you set, whatever the model wrote. | Runs today |
Coming, built with the first property client
| Capability | What it does | Status |
|---|---|---|
| Viewing slots per unit and group viewings | Booking capacity is per business today, not per unit. Group viewings with personal invite links exist for events and would be lifted into leasing. | Proposed for property |
| Rental application with private documents | Intake plus private, signed-URL uploads. Documents are never public and never used for training. A person decides the application. | Proposed for property |
| Maintenance intake with photos and urgency | Unit, issue, photos and urgency collected. Flood, gas, fire, no heat recognised first and paged to your on-call contact in the same turn. | Proposed for property |
| Named approval before any contractor is contacted | A person on your team approves, asks for more, or declines. The decision is written to the audit log with their name. | Your team decides |
| Work orders with a confirmation link and a chase | The vendor receives the job sheet; no reply within the window brings it back to your desk. The resident is kept informed. | Proposed for property |
| Renewal drafts 90 and 60 days out, sent after review | Needs a tenancy record. Nothing stores a lease today. | Proposed for property |
| Portfolio roll-up with property-level permissions | The group view exists for the agency console. Property-level roles for leasing teams and owners are new. | Proposed for property |
Stays in your system of record
| Capability | What it does | Status |
|---|---|---|
| Rent collection, arrears, occupancy | These live in your property management system. ORACA reads them where an API or export allows and never estimates them. | With your system of record |
One property first.
- 1Discovery and portfolio assessment
Your properties, channels, systems and the hours that disappear into interruptions. A written map of what runs on day one and what needs building.
- 2The leasing desk on one property
Inquiries, qualification, viewings, follow-up, the morning screen. Measured from a declared start date.
- 3The resident and maintenance desk
Once named approval roles are in place. Intake, triage, approvals, work orders, resolution reporting.
- 4The portfolio view
ORACA Hive across every property, with property-level permissions, once there is a portfolio of data to show.
Published prices, a 21-day pilot, and a call to see where the hours go.