A better way in.
Resident onboarding, persistent communications and optional building internet. Give residents one place to find information and request help.
Move-in identity · messages · access · optional connectivityCONNECTED PROPERTY OPERATIONS · SEPARATE PRODUCT
BuildingOS
Every building.
A clearer
operating picture.
Resident support. Repairs. Owner visibility. BuildingOS is a separate product connecting the everyday work of residential buildings, with one central portfolio view and a local presence in each building.
EVERY ISSUE VISIBLE. EVERY ACTION TRACKED.
People.
Ideas. Action.
A brighter tomorrow. ♡
Ideas. Action.
A brighter tomorrow. ♡
Your portfolio.Owner view
The building, the issue and the next action.
Resident supportLinkedContext with the request
RepairsTrackedResponsibility visible
Owner pictureVisibleActions in one timeline
BUILDINGS + NEXT ACTIONS
Harbour HouseRepair in review
Garden CourtNotice prepared
Unit 07 · lightingApproval needed
Owner decisionCost attached
ACTION TIMELINE
- Resident reports an issueBuilding + unit context attached
- Concierge prepares the next stepRepair owner assigned
- Owner reviews the costContractor visit awaits approval
Illustrative workspace · fictional records · no live actions
9:41▴ ▴ ▰
BuildingOS
Resident Hub · concept
HARBOUR HOUSE · SAMPLEYour building.
Your support.
Your support.
“The landing light isn’t working.”
Issue recorded → repair owner → your next updateIllustrative resident view
BuildingOS product concept · fictional records · no live actions
Connect
Optional connectivity.
Concierge
A resident front door.
Care
Repairs with an owner.
Pulse
Portfolio transparency.
Let
Move-in to move-out.
Hub + Vault
The building’s context.
Pilot development
Separate product · illustrative workspaces · availability and scope confirmed in a private briefing.
THE PROPERTY OPERATING PROBLEM
One building.
Too many disconnected handovers.
A resident reports a fault. A manager forwards it. A contractor needs the context. The owner asks what it will cost. The records end up in different inboxes.
BuildingOS is being developed to hold the conversation, the responsibility, the decision and the outcome together — from one building to a whole portfolio.
THE BUILDINGOS PRODUCT
The building’s everyday work.
Connected.
One central Portfolio Command Centre, with a local building hub for residents. Each module has a distinct job; connectivity can be added where it fits the deployment.
Ask the building.
A virtual concierge designed around the building’s own knowledge, resident context and permitted workflows. Answer routine queries and prepare the next useful step.
Building knowledge · query triage · human escalationA repair with a next step.
Connect issue intake, responsibility, contractor coordination and resident updates. Keep the job’s decisions and history visible as it moves.
Repair record · assigned owner · cost review · statusSee behind the summary.
A proposed owner view across buildings, open jobs, costs and recurring issues. Give the portfolio a clear operating picture with an auditable history.
Owner visibility · service activity · portfolio reportingKeep the changeover moving.
Bring voids, enquiries, viewings and resident onboarding into a coordinated workflow. Accountable people remain responsible for legal and regulated steps.
Void workflow · enquiries · onboarding · handoversA building that keeps its context.
Notices, documents and useful local information in one resident hub. Keep building records accessible within the right identity and permission scope.
Notices · documents · local information · access scopeProduct scope in development. These are planned workflows and illustrative views; availability is agreed per pilot.
ONE EVENT. A SHARED RECORD.
From a resident’s request
to an owner’s decision.
The same issue should carry its context through every handover. BuildingOS is designed to connect resident support, operational responsibility and owner oversight.
Humans retain physical work, regulated responsibilities and approval decisions. The product coordinates the administration around them.
Intended workflow · illustrative example“The landing light is out.”
The building and unit context travel with the request.
Make it a tracked job.
Prepare the repair, assign responsibility and arrange the next update.
Review the action and cost.
Approval sits with the accountable person before work is authorised.
Keep the outcome visible.
The resident receives an update; the building retains the record.
THE COMMERCIAL THESIS
Recurring software.
Portfolio distribution.
The proposed model starts with a useful owner and resident operating layer. A portfolio relationship creates a route from the first building to many units.
Price around the units.
A proposed per-unit subscription for core workflows, with managed and enterprise scope as portfolio needs grow.
Working commercial model · pilot validation requiredMake the first deployment useful.
Building setup, portfolio data, knowledge configuration and workflow onboarding create a scoped implementation service.
Deployment scope agreed before rolloutA practical entry point.
Resident-funded or owner-funded connectivity can add an amenity and a route into the building hub. BuildingOS can operate without it.
Network economics and support scoped separatelyPricing, costs and unit economics are working assumptions in the private brief. No revenue, adoption or margin outcome is claimed here.
MIDDLE STREET · BRIGHTON
Pilot developmentProve one building.
Earn the next portfolio.
Middle Street is the reference pilot in the project plan. The next step is evidence: resident demand, connected workflows, an owner view and a repeatable deployment. Pilot outcomes will shape wider rollout.
- Resident adoptionEstablish whether residents use the hub, support and optional connectivity.
- Operational valueMeasure response handling, repair visibility and time spent coordinating work.
- Owner engagementDemonstrate that owners and managers use the shared operating picture.
- Repeatable economicsTest deployment cost, support load and willingness to pay before expansion.
The pilot is a development and validation programme. Results, service availability and commercial readiness are confirmed in the private briefing.
THE INVESTOR CASE
A separate product.
A specific commercial problem.
BuildingOS gives ElevnAI a focused property proposition: connected resident service and owner transparency, with a proposed recurring model and distribution through multi-unit portfolios.
The next milestone is a dependable building workflow with evidence worth taking to the next owner.
A clearer building. A stronger operating model.
Review the BuildingOS product plan, pilot scope and proposed route to recurring portfolio revenue.
tomorrow.♡