Blue at Lavender Bay: 125 Luxury Apartments, One Connected Experience

Overview

Blue at Lavender Bay is a luxury residential development on Sydney's lower north shore — 125 apartments and three retail shop tops set against one of the most photographed harbours in the world. For the developer, the residents and the integration team behind it, the brief was simple to describe and complex to deliver: a building that feels less like a stack of apartments and more like a single, intelligent environment.

To make that real, Centro partnered with Tecco — the integrator who rolled out the complete home-automation and active-network solution across the development — and with 2N, whose intercom hardware became part of a unified resident experience. Blue at Lavender Bay was one of the earliest deployments of Centro in a live MDU setting, and it offered an early, real-world look at what the platform can do when it sits as the connective layer between people, their spaces and the services around them.

The Challenge

Luxury MDUs live with a quiet paradox. Residents arrive expecting hotel-grade convenience — a single app, a single interface, instant response. But the buildings themselves are made up of vendor-specific subsystems: a control system for lighting and blinds, a separate intercom for door release and visitor management, a separate platform for concierge and maintenance requests. Each subsystem ships with its own app, its own login and its own learning curve.

That fragmentation creates three pain points that show up over and over again in conversations with developers and property managers:

• For residents, "smart" becomes a synonym for friction — multiple apps, multiple passwords, multiple mental models for one home.
• For onsite staff, every subsystem is a separate dashboard, which means information silos, slower response times and a thinner picture of what is actually happening in the building.
• For developers and asset owners, the cost of pulling all of this together — both at handover and over the lifetime of the asset — can be the difference between a building that ages well and one that quietly slips behind newer competitors within a few years.

At Blue at Lavender Bay, the team set out to avoid that future from day one.

The Solution

The technical backbone of the project was Crestron Home, deployed by Tecco across every residence. Crestron Home controlled lighting, blinds, air conditioning, in-floor heating, heated towel rails, balcony louvres and sunshades — the details that make a luxury apartment feel like one. 2N provided the intercom layer for door entry and visitor flow.

Centro's role was the connective tissue. Sitting on top of Crestron Home and integrating with the 2N intercom, Centro presented residents with a single interface for the things they actually want to do day to day: adjust their environment, answer their door, message the concierge, raise a maintenance request, see what is happening in the building. The same control surfaces residents already knew — the Crestron touchscreens on the wall — could surface intercom calls and broader resident services without bouncing them between vendor apps.

For staff, the picture was inverted in a useful way. The same activity residents experienced as "I tapped a button on my wall" surfaced on the operations side as a structured request with context — who, where, what, when — feeding a single operational view rather than a stack of disconnected inboxes.

Crucially, none of this required a parallel infrastructure. Centro is a software layer designed to make the systems already chosen by the developer and the integrator work harder together. Crestron stayed Crestron. 2N stayed 2N. The experience changed.

The Result

Because Blue at Lavender Bay was an early-stage Centro deployment, the most important outcome is not a metric — it is a proof point. The project demonstrated, in a live luxury building, that the long-standing tradeoff between "best-of-breed subsystems" and "one coherent experience" is a false choice.

Residents at Blue interact with a building that behaves like a product, not a portfolio of vendors. The Crestron home automation is still Crestron. The 2N intercom is still 2N. But the surface area the resident actually touches feels unified — which is the experience luxury MDU buyers and tenants increasingly expect, and increasingly choose between developers on.

For Tecco, Centro added a layer of resident-facing and operations-facing value on top of an already premium Crestron deployment, without asking them to rip out or replace anything that already worked. For 2N, the intercom became a first-class part of the resident experience rather than a parallel app users had to remember. For the developer, the building gained both a story to tell at handover and an architecture that can absorb new capabilities — mobile keys, energy management, scheduling, services — without re-cabling.

Where the Value Shows Up

A smart-home story is only interesting to a developer or asset owner if it translates into something measurable on the asset. Blue at Lavender Bay was an early proof of concept rather than a financial case study, but the value categories it points to are the ones we now design for explicitly with every Centro deployment. They are also, not coincidentally, the levers a luxury MDU developer is being graded on whether they invest in them or not.

• Sales velocity at handover. A residence that demos as a single, intuitive experience converts walk-throughs into deposits faster than one that asks buyers to imagine how four separate apps will feel in three years. The differentiator is no longer "is it smart?" — it is "does it feel like one product?"
• Premium positioning per residence. Luxury MDU buyers price in finish, view and lifestyle. A unified resident experience is becoming part of that lifestyle calculus, in the same way concierge service and harbour views are. Centro lets the developer surface that story without the cost or complexity of a bespoke build.
• Operational efficiency for owner-operators. For build-to-rent and managed luxury portfolios, every minute saved by a concierge or maintenance team — every request routed correctly the first time, every duplicate ticket eliminated — drops to NOI. A single operations view is not a feature, it is operating leverage.
• Long-term asset resilience. Buildings that ship with rigid, vendor-locked tech stacks date quickly. A software experience layer can absorb new integrations — mobile keys, energy, EV charging, package management — without re-cabling or a rip-and-replace. That extends the useful life of the original capex and protects the building's positioning over the decade ahead.

Centro does not put a specific dollar figure on any given project, and we are wary of synthetic ROI math built on assumptions a developer cannot verify. What we will say is that these four categories — sales velocity, premium positioning, operational efficiency and long-term resilience — are the levers a unified experience layer pulls. In every conversation with a developer or operator, they are also the four questions worth asking of any smart-building investment: which of these does it move, and by how much?

Why This Matters for Developers and Property Managers

The pattern from Blue at Lavender Bay is portable. Centro sits on top of a control system and a communications system to deliver a single, coherent resident and operations experience. It does not require a particular brand of hardware. It does not require ripping anything out. It requires a connective layer that has been designed, from the ground up, to live between the systems you have already chosen and the people who actually use them.

For developers and property managers who have been told that this kind of unified experience is only possible with full-stack, single-vendor builds — or only at price points that do not pencil at scale — Blue at Lavender Bay is a useful counter-example. The components are familiar. The result is not.

What's Next

Blue at Lavender Bay was an early prototype of Centro in production. The version of Centro available today is materially more capable: more integrations, more polish on both the resident and operator experiences, and a clearer playbook for partners like Tecco who deliver these projects on the ground. The model — Centro as the experience layer over Crestron, 2N and the rest of the modern MDU stack — is the model we are building on, project by project.

If you are a developer, integrator or operator weighing what a unified resident and operations experience could mean for your next build or your existing portfolio, the conversation we would love to have starts with a simple question: what do you already have in place, and what would "one app, one experience" actually look like for your residents — and your P&L?