For mixed-use developments

Homes above, a café below, offices across the courtyard. One place, several businesses, no shared inbox.

A mixed-use development is several businesses sharing one address. The café takes bookings. The clinic takes appointments. The residents report leaks. The operator coordinates the lobby, the loading bay and the snow. ORACA gives each of them their own front desk and the operator one view, and keeps every line between them separate and consented.

Separation firstThis is the same multi-tenant model every ORACA client runs on. A clinic and a law firm share a deployment today and have never shared a row.

How residential, commercial and shared services are kept apart, and where they meet.

Residentialits own front desk
Leasing inquiriesResident questionsMaintenance requestsRenewalsIts own database
Each commercial tenantits own front desk
Customer inquiriesBookings and appointmentsReviews and follow-upIts own databaseNothing shared with the building
The operatorshared services, one view
Lobby and loading bay schedulingShared vendorsBuilding noticesApprovalsRoll-up reporting, counts only

The operator sees that the café received 40 inquiries this month. The operator never sees who they were. A building notice reaches residents who opted in to notices and commercial tenants who opted in separately. A line that crosses from one business to another exists only where both sides consented to it, with the wording and the time recorded.

What runs today, what is proposed

Honest about the order of work.

A front desk per commercial tenant

Inquiries answered, appointments booked, follow-up run, on the tenant’s own number and brand. This is ORACA’s core product and runs for businesses today. Runs today

A leasing desk for the residential side

The same engine with unit vocabulary. Runs today

Shared vendor coordination

Snow, cleaning, security, lifts: one vendor, one schedule, one confirmation across buildings. Needs the work-order object. Proposed

Building notices with consent

Opt-in lists per audience, recorded with wording and time, on the existing consent rails. Proposed

Operator roll-up

Counts across the development, never contents. Property-level roles are the addition. Proposed

Amenity and local service discovery

Residents finding approved services and neighbourhood businesses. A community product, described on the communities page. Roadmap

Bring the tenant mix. We will map which desks run on day one and where consent lines are needed.

Explore what ORACA could power