From plan to proposal
Design, bill of materials and quotation produced from a floor plan.
Tecco is a product and technology company. We build Homira — the platform a home runs on: the app residents live with, the cloud behind it, the Studio builders design in, and the software on the device in the wall.
A useful agent needs more than a conversation. It needs to know which room a person means, what the devices in that room can do, who is allowed to act and whether the intended change actually happened.
That is why our work spans the stack: the resident application, the cloud, the project model, the tools used to design and configure a space, and the software on the device in the wall. We wrote every layer ourselves. Owning the execution layer gives an agent a defined path into the physical home, with capabilities and boundaries that a collection of resold systems cannot establish on its own.
Our experience in ICT, connected buildings and physical delivery informs this direction. Today the company is organised around products, software and the intelligence layer being built on top of them.
Tecco develops software across the resident experience, cloud, project model, authoring tools and edge. Owning these interfaces lets us address the gaps between layers, where meaning and responsibility are often lost.
Residents interact with rooms, scenes, comfort, access and energy through a coherent experience.
02Project context, building operations and resident services connect the home to a wider operational system.
03A room, device and control object need an identity that survives a change of interface.
04Floor plans, design decisions and engineering configuration become a connected software workflow.
05Protocols, local behaviour and observations connect a software decision to the physical environment.
Tecco develops the technology and engineering system. Homira brings it into everyday life: room-based control, scenes, environmental information and, where configured, energy, access and community services. Homira Enterprise extends the perspective to building operations, maintenance, work orders and resident services.
The scope of each installation depends on the project and connected systems. The ambition is consistent: make a complex environment more understandable for the people who live in it and the people responsible for it.
Design and delivery are opportunities to establish context. A floor plan, a reviewed device placement and a generated configuration can become the foundation a future agent needs to understand the space.
Manager brings plans, rooms, openings and device placements into a reviewable project. The geometry and its interpretation remain available for engineering decisions.
Studio connects the control object to its room, actuator, protocol and configuration. The goal is continuity between a design decision and what an installed system can actually do.
Move repeatable configuration upstream into software and preparation. Installation can then focus on the physical work, with engineering information carried into the delivered environment.
The resident experience and operational tools expose what happens after handover. The next challenge is to turn observations into dependable diagnosis and better decisions.
Owning the stack lets us turn design into software. A wired smart home traditionally needed specialist programming for each house. Our workflow brings design, the bill of materials and the quotation together, then writes configuration before devices leave the building.
Design, bill of materials and quotation produced from a floor plan.
Written before devices leave the building, ahead of on-site installation.
A licensed electrician installs the prepared system.
Company-reported workflow figures · September 2026.
Inside the engineering workflow →The intelligence layer we are building separates interpretation from physical execution. Language can express intent; what moves in someone’s house is decided deterministically against device capability.
This is why design and delivery matter to AI. They establish the rooms, devices, relationships and engineering context before an agent arrives. Our answer to cold start begins in the work we already do, rather than asking a resident to reconstruct their home from a blank conversation.
Explore the agent architecture →The engineering challenge is no longer only writing code. It is defining the right problem, preserving a shared contract and deciding what evidence is sufficient to ship.
A feature needs a person accountable for the full path from specification to outcome. An agent can contribute work; it does not become the owner of the decision.
A shared interface makes parallel work possible. Models, endpoints and boundaries must be explicit enough for another person or agent to test independently.
The person building a change should not be its only judge. Acceptance criteria, review and release evidence give a team the means to challenge a plausible result.
Corrections should improve the next specification, evaluation or release. Harness brings development context together so learning can outlast the conversation that produced it.
Devices, protocols and local execution determine whether a software decision survives contact with the real world. Tecco’s product work includes its own device software and KNX-based products alongside the tools that configure and operate connected spaces.
Energy is part of this physical foundation. Circuit-level observations can reveal activity that a total-meter reading hides behind solar generation or storage. Those signals need careful interpretation before they become a decision about comfort or flexibility.
Interoperability and expertise matter here. Tecco is a KNX Association member and, since January 2026, an authorised training centre for Basic, Condensed Practical Basic and Refresher courses.
We make the hardware too. As of September 2026, Tecco reports 20 entries across seven device categories in the KNX certified device catalogue, and is the only Australian manufacturer with products listed there. Every switching circuit we ship includes current sensing as standard, creating the circuit-level visibility an energy partner needs to observe and dispatch loads.
Explore connected execution →Spatial authoring, configuration, resident interfaces and building operations establish a practical foundation. Explore the platform pages for specific workflows and interface examples.
Explore platforms →Home intelligence is at MVP stage. Behaviour models, scene synthesis and capability checks connect a request to a proposed environment. Fleet intelligence and its operational learning loops continue to develop.
Explore cloud and edge →Longer-term work asks how spaces can learn from behaviour, respect constraints and combine comfort, safety and energy goals. The planned UNSW programme adds a research path into resilience and building intelligence.
Explore the research →Three agent lines are in production, one is at MVP and two are still being built. Each has a named human owner. These are product and development streams; our leadership page separately introduces the six core responsibilities that connect strategy, product, technology, energy, deployment and operations.
Founded in 2012 and headquartered in St Leonards, Sydney, Tecco brings software development, digital twins, edge AI, design automation, home energy management, factory provisioning and fleet operations into one product organisation.
Our work connects Sydney and Chengdu, with expertise across product, software, energy, deployment and operations. Technology partners, practitioners and research relationships bring different kinds of knowledge to the same physical challenge.
Office · 146 Arthur Street, North Sydney, NSW 2060
Australia Lab · 37 Herbert Street, St Leonards, NSW 2065
China Lab · Building 3, Lepton Center
566 Jitai Road, Tianfu 3rd Street, Wuhou District, Chengdu, Sichuan
Bring a problem you cannot stop thinking about. Bring something you have built. Help us make intelligence useful beyond the screen.
Explore careers