Halo turns a single site capture into costed solutions, applied incentives, computed returns, and the document your client actually reads — without a spreadsheet in the middle.
The same inputs yield the same outputs in the summary, the engineering view and the estimate — because all three read one centralised, unit-tested calculation layer.
A project is the spine — audits, designs, estimates, proposals and orders all live inside it. Change an input upstream and everything downstream recomputes, so the estimate and the proposal can never drift apart.
Halo models the building as Locations, Areas and Sub-Areas, so every space you audit has somewhere to live and a full hierarchy path. Field techs record existing inventory, measurements and operating schedules on a tablet, and that single capture feeds every calculation and document that follows.
Halo carries a system-type attribute through templates and attribute sets, so the audit domain is a property of the project rather than an assumption baked into the schema. Lighting and energy retrofit is the first domain it serves.
Attract, qualify, propose, support. Each product stands on its own — together they carry a customer from first visit to long-term account.
Your site starts a conversation and captures the lead.
Explore →The lead becomes a record your team can work and trust.
Explore →The opportunity becomes a costed, evidenced proposal.
You are hereThe customer keeps talking to you, on one thread.
Explore →Bring a real site and a real proposal you've had to assemble by hand. We'll rebuild it in Halo and compare.