A building is concrete, steel and glass. It is also every inquiry, request, approval and conversation that decides whether it works for the people in it. ORACA connects that work, from one building to a community.
Scroll to begin
IThe building
Illustrative film. Not a client property.
7:42Runs today
A leasing inquiry
Mira asks about the two-bedroom on the third floor. She gets an answer in under a minute, a few questions about move-in and budget, and Thursday at 5:30 for a viewing.
Runs today
Her inquiry, her answers and the booking land in one record your leasing team can read.
8:05Proposed for property
A maintenance request
Unit 4B reports a slow drip under the kitchen sink and sends a photo. The request is logged, marked non-urgent, and placed in front of the property team.
Your team decides
A named person approves before anyone is sent. An emergency skips the queue and pages your on-call contact.
8:30Proposed for property
The job sheet
Once approved, the plumber receives the unit, the photo, access notes and a link to confirm. The resident is told who is coming and when.
Runs today
The property manager sees what needs attention on the morning screen.
Last 30 daysRuns today
Three properties, one view
Property
Inquiries
First reply
Viewings
Open
Harbour Walk
23
48 s
11
2
Courtyard East
31
52 s
14
4
Mill Row
6
41 s
3
1
Leasing team A sees Harbour Walk and Courtyard East. Team B sees Mill Row. The owner sees all three. Nobody sees a property they are not assigned to.
Sample data. Occupancy and rent figures come from your system of record, not from ORACA.
Proposed for property
Saturday market in the park
A notice goes to residents of three buildings who opted in to community updates.
Runs today
The café on the corner
Takes its own booking inquiries on its own line. Nothing it learns is shared with the building.
Proposed for property
A trusted plumber
A resident asks who the building already works with. The answer is the vendor the manager approved, not a directory.
Proposed for property
Snow clearing, three properties
One vendor, one schedule, one confirmation, coordinated by the manager rather than three phone calls.
Harbour Walk5 storeys · 24 homes · café
Courtyard East7 storeys · 42 homes
Mill Row3 storeys · 8 townhouses
The Pavilion6 commercial units
Leasing and lead intake
Resident and tenant communication
Property management approvals
Maintenance coordination
Vendor workflows
Scheduling
Management reporting
Every place has a story. We help everything behind it work.
One property. Every interaction connected.
One building, or fifty. The same intelligence, with the right people seeing the right property.
The opening film is silent. These are its on-screen lines, act by act. Illustrative film; not a client property.
I. The building — Every place has a story. We help everything behind it work.
7:42 · A leasing inquiry (Runs today): Mira asks about the two-bedroom on the third floor. She gets an answer in under a minute, a few questions about move-in and budget, and Thursday at 5:30 for a viewing. Her inquiry, her answers and the booking land in one record your leasing team can read.
8:05 · A maintenance request (Proposed for property): Unit 4B reports a slow drip under the kitchen sink and sends a photo. The request is logged, marked non-urgent, and placed in front of the property team. A named person approves before anyone is sent. An emergency skips the queue and pages your on-call contact.
8:30 · The job sheet (Proposed for property): Once approved, the plumber receives the unit, the photo, access notes and a link to confirm. The resident is told who is coming and when. The property manager sees what needs attention on the morning screen.
II. The building becomes intelligent — One property. Every interaction connected.
III. One building becomes a portfolio — One building, or fifty. The same intelligence, with the right people seeing the right property.
IV. From portfolio to community — When places work better, life works better.
Saturday market in the park (Proposed for property): A notice goes to residents of three buildings who opted in to community updates.
The café on the corner (Runs today): Takes its own booking inquiries on its own line. Nothing it learns is shared with the building.
A trusted plumber (Proposed for property): A resident asks who the building already works with. The answer is the vendor the manager approved, not a directory.
Snow clearing, three properties (Proposed for property): One vendor, one schedule, one confirmation, coordinated by the manager rather than three phone calls.
V. The bigger vision — One building is the beginning. Imagine what we can build together.
Three desksWhat runs behind a property, and who decides what. Blue is an action the system takes. Brass is a decision a person makes. A dashed mark is proposed for the property vertical.
One property. A thousand moving parts. A clearer way forward.
Runs today
The Leasing Desk
The same engine that answers inquiries and books appointments for businesses today, configured for units, viewings and leases.
Every inquiry answered in under a minute, on web, text, email and WhatsApp
Move-in, household, budget and documents gathered in the prospect's own words
Viewings booked into a real calendar, reminded, no-shows rebooked
Campaigns traced to inquiries and viewings, cost per inquiry shown
Your leasing manager decides every application
Proposed for property
The Resident and Maintenance Desk
Intake, uploads, approvals and the chase pattern exist. The maintenance object, triage rules and work orders are the build for the first property client.
Resident questions answered from your policies, day and night, on the building's own number
Maintenance requests collected with unit, photos and urgency
Flood, gas, fire, no heat recognised first and paged to your on-call contact
Nothing is dispatched without a named administrator's approval
Vendors chased until confirmed, residents told who is coming and when
Runs today
The Owner and Portfolio Desk
The Console is one renderer for every client. A property company sees the same screen a clinic does, with its own vocabulary and only its own data.
The morning screen: what needs a decision today, sorted by what it costs to ignore
Inquiry to viewing funnel, response times, open requests, with every rate's denominator shown
A build and lease-up desk: stages, what is waiting on whom, stalled alerts
One portfolio view with property-level permissions for teams and owners
Occupancy, rent and arrears from your system of record, never estimated
The system actsA person decidesProposed for property
Inside an intelligent propertyThree things that happen in a building every week, shown the way the system handles them. Every step says whether it runs today, needs a person, is proposed, or depends on your system of record.
Beautiful on the outside. Serious infrastructure underneath.
Choose a scenario and step through it. The screens are the shape of the real product on sample data, not a video of a dashboard.
A new leasing inquiry · step 1 of 6Sample data
Harbour Walk leasing · automated assistant, says so on every channel
Hi, is the two-bedroom on the third floor still available? I would be moving in January.
It is. I am the automated leasing assistant for Harbour Walk. The two-bedroom is 3B, 940 square feet, with a west-facing balcony. Rent is $2,150 and it is available from 1 January. Would you like to see it?
Illustrative, on anonymised sample data. Names, units and vendors are invented. The layout is the ORACA Console with property vocabulary.
Runs todayYour team decidesProposed for propertyWith your system of record
Where ORACA sitsNot a replacement for the system that holds your leases and ledgers. The layer between the people who reach a property and the systems that record it.
Your systems keep the record. ORACA does the work in between.
Property management systems are built to be the record. They are not built to answer a message at 9:40 pm, chase a vendor on Thursday, or tell you on Tuesday morning what needs you. That is the gap this layer fills, and it hands every outcome back to the record you already keep.
Where people reach a propertychannels
WebsiteTextEmailWhatsAppPhoneMeta and Google campaignsListing portals
The intelligence layerORACA, operated for you
Capture and answerQualify with reasonsBook and remindRoute for approvalChase and follow upAudit every decisionReport what happened
Systems of recordyours, kept
Property management systemLeasing CRMWork ordersAccountingCalendarsReporting and BI
Connections are by open API where one exists, by partner programme where one is required, and by structured handoff where there is none. The platform page lists each system and what is possible today.
Built to be checkedA property business holds other people’s homes, money and documents. Each of these controls is in the code today; none is a certification claim.
Documented. Auditable. Defensible.
A separate database per client
Row-level security on every table, and a three-query leak sweep before any change ships.
Personal data encrypted at rest
Names, emails, phone numbers and addresses are encrypted in the database.
Every automated decision logged
What was decided, for whom and why, in an append-only trail you can request.
Outbound fails closed
No recorded consent, nothing sends. Stop means stop on every channel.
The assistant says it is automated
On every channel, every time, and hands over to a person when asked.
People decide on people
Applications are decided by your team against criteria reviewed for human rights compliance. Qualification never scores protected grounds.
ORACA does not claim SOC 2, ISO 27001 or other audited certifications. Data residency is confirmed per deployment before it is stated.
Who this is for
The owner of one building should see what it does. The owner of fifty should see how it scales.
Strategic partnershipFor owners, operators and developers who want one accountable partner across a portfolio. Built in stages; each stage has to earn the next.
A growth partnership, not a subscription.
At this level you are not buying a bigger system. You are buying accountability: a baseline, a pilot with terms written down, reviews that end in a decision, and a partner who answers for the result.
1Discovery and baseline
We map how inquiries, viewings, requests and approvals move today, and which systems hold the record. The baseline is written down before anything goes live, so every later number has something honest to be compared with.
2One property, a pilot
The leasing desk on one property, live in 21 days. Term, price, the measures and the point at which either side stops are agreed in writing before day one.
3Connected to your record
Read-only access to your property management system first, granted by your administrator. Wider access only when you agree to it, and only for what the work needs.
4Measured, reviewed, decided
A monthly report against the baseline. A quarterly strategic review with one named ORACA lead, and a decision at each review: widen, adjust or stop.
5Rolled out in stages
Properties join in groups, each after its own go or no-go. A portfolio grows on evidence from the property before it, never on a slide.
6Built with you
Founding partners shape the desks proposed for property, maintenance and the portfolio view first, at founding terms fixed for the length of the agreement.
What ORACA brings
The audit, the configuration and the integration work
Monitoring, escalation rules and a person when the assistant should not answer
One named lead and a one-business-day support line
A quarterly executive report and strategic review
The compliance and AI-use policy pack: privacy, consent and Canada’s anti-spam law
What your team brings
One person who can make decisions
A first property to pilot
Access to the systems that hold the record
Your policies, answers and approved message templates
Baseline numbers, and time for the escalations that need your team
What we measure together
Time to first response, in business hours and after hours
Inquiry to viewing
Viewing to application
Share of inquiries answered without staff
Request acknowledged and resolved, once the maintenance desk is built
Staff hours returned to the work only people can do
Measured, not promised. Occupancy, rent and renewals are reported from your system for context and never credited to ORACA. One property company per metro, two installs a month, and terms set in writing after discovery.
Fair questionsAsked by every owner and operator. Answered in writing.
Before the call.
Is this running for a property company today?
The engine behind it answers inquiries, books appointments and runs follow-up for businesses today. The property configuration is in build, and ORACA takes on one property company at a time so the first install is done properly.
Does the assistant decide who gets a unit?
No. It gathers details and documents and organises them for your team. Your leasing manager decides, against criteria reviewed for compliance with human rights law. Qualification rules never score protected grounds.
What happens in a real emergency?
In the proposed maintenance desk, flood, gas, fire, carbon monoxide and no heat in winter are recognised first. The resident gets safety instructions and your on-call contact is paged in the same moment. That never waits for an approval.
We already use a property management system. Why add a layer?
Keep it. It is the record. ORACA answers, qualifies, books, routes and chases, then hands the outcome to your record by API where one is open, by partner programme where one is required, or by structured handoff where there is none. Nothing is duplicated and nothing is replaced on day one.
How is return counted?
At your leasing fee and management percentage, never at the tenant’s rent. Rent goes to the owner. The return you see is the return you earned.
What do you not claim?
No audited certifications. No occupancy or rent figures unless they come from your system. No live property client yet. Every screen on this site says whether it runs today, needs a person, is proposed, or depends on your systems.
One building is the beginning.
Tell us about your properties, your systems and what slows your team down. We will show you what ORACA could power across them, what runs today, and what a first pilot would look like.