Audit → proposal → order

From the walkthrough to the signature.

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.

See the stack
One engine
the numbers can't disagree
Incentives native
rebates, 179D, tax credits
Tablet-ready
structured capture on site
haloPropose
AUDIT · Site capture
Everything downstream is only as good as the walkthrough.
  • Location → Area → Sub-Area hierarchy with per-area inventory
  • Illuminance readings, existing controls, occupancy, reflectance and dimensions
  • Operating, Rate, Cooling and Heating schedules as calculation defaults
22
Modelled domain entities
179D
Deduction handled natively
1
Costing engine, unit-tested

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.

Five stages, one project

Each step feeds the next. Automatically.

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.

AUDIT · Site capture

Everything downstream is only as good as the walkthrough.

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.

  • Location → Area → Sub-Area hierarchy with per-area inventory
  • Illuminance readings, existing controls, occupancy, reflectance and dimensions
  • Operating, Rate, Cooling and Heating schedules as calculation defaults
  • A project-wide schedule of every distinct existing asset, with a grouped By-Area view
How it works

Built around a system type, not a single trade.

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.

Runtime
Next.js, TypeScript, Vercel
Data
Postgres, tenant-scoped, 22 models
Auth
Sealed-cookie sessions, six project roles
In-app agent
Retrieval-grounded support, audit-logged

Walk a building. Leave with a proposal.

Bring a real site and a real proposal you've had to assemble by hand. We'll rebuild it in Halo and compare.